You can convert Oracle Grid Infrastructure cluster networks using DNS for name resolution to cluster networks using Grid Naming Service (GNS) obtaining name resolution through GNS.
Use the following procedure to convert from a standard DNS name resolution network to a GNS name resolution network, with no downtime:
Oracle Grid Infrastructure Installation Guide for your platform to complete preinstallation steps for configuring GNS
grid), and use the following Cluster Verification Utility to check the status for moving the cluster to GNS, where
nodelistis a comma-delimited list of cluster member nodes:
$ cluvfy stage –pre crsinst –n nodelist
domainis the domain delegated to GNS for resolution, and
gns_vipis the GNS VIP:
$ cluvfy comp gns -precrsinst -domain domain -vip gns_vip
root, and use the following SRVCTL command to configure the GNS resource, where
domain_nameis the domain that your network administrator has configured your DNS to delegate for resolution to GNS, and
ip_addressis the IP address on which GNS listens for DNS requests:
# srvctl add gns -domain domain_name -vip ip_address
# srvctl start gns
GNS starts and registers VIP and SCAN names.
root, use the following command to change the network CRS resource to support a mixed mode of static and DHCP network addresses:
# srvctl modify network -nettype MIXED
The necessary VIP addresses are obtained from the DHCP server, and brought up.
cluvfy stage -post crsinst -n all
For each client using a SCAN, change the SCAN that the client uses so that the client uses the SCAN in the domain delegated to GNS.
For each client using VIP names, change the VIP name on each client so that they use the same server VIP name, but with the domain name in the domain delegated to GNS.
rootto update the system with the SCAN name in the GNS subdomain:
# srvctl modify scan -scanname scan_name.gns_domain
In the preceding command syntax,
gns_domain is the domain name you entered in step 3 of this procedure.
$ srvctl modify network -nettype DHCP