In a real time environment, we usually rarely perform the activity of changing the scan IP address or SCAN name and if somehow if we’ve to do it due to the changes of the SCAN IP in DNS server then we also have to update the SCAN IP with new IP address because the changes that the network administrator done at DNS server level will not get propagated automatically to clusterware.
|
OLD SCAN IP |
NEW SCAN IP |
|
192.168.10.58 192.168.10.59 192.168.10.560 |
192.168.10.101 192.168.10.102 192.168.10.103 |
STEP 1: check the current configuration of scan
-bash-4.2$ srvctl config scan
SCAN name: oratest-scan, Network: 1
Subnet IPv4: 192.168.10.0/255.255.255.0/enp0s3, static
Subnet IPv6:
SCAN 1 IPv4 VIP: 192.168.10.58
SCAN VIP is enabled.
SCAN 2 IPv4 VIP: 192.168.10.59
SCAN VIP is enabled.
SCAN 3 IPv4 VIP: 192.168.10.60
SCAN VIP is enabled.
STEP 2: Validate the change IP address first using nslookup and also check whether it’s moving in round-robin fashion or not.
STEP 3: After changes done at DNS server, execute nslookup
command and validate whether it start giving new IP information by <scan-ip>
and if yes then stop the scan listener and scan.
NOTE:
(1) Stop scan
and scan listener can be done using srvctl command however it’s a best practice
to stop it using root user while changing SCAP IP.
(2) Stop scan
listener first and then scan otherwise cluster will try to relocate the scan
listener due to which you’ll start getting error
(3) Please set the blackout first prior to stop the scan and scan listener in order to prevent the unnecessary alert.
STEP 4: Modify the SCAN VIP with the new IP address from DNS Server.
NOTE: Since SCAN IP information store inside the OCR, so it’s mandatory to modify scan configuration from root user so that the OCR can be updated.
STEP 6: Start SCAN and SCAN listener
