The reason of this post is simple: I want to get GNS up and running on my RAC 11.2 cluster, after all it’s one of the major new features. It required me to get acquainted with DNS and now also with DHCP.
Before to go for implementation part let me just brief about GNS and GPNP. As you know GPNP is one of the most important features of 11g R2 RAC which allow us to add the node in cluster in simple and easy way as we just plug the server and start it. GNS (Grid naming service) is a DNS kind of service hosted by Oracle clusterware and running on one of configured static IP and responsible to resolve requested hostname running under Oracle cluster into corresponding IP.
Following points must be noted about GNS-
1) GNS is DNS kind of service hosted by Oracle clusterware and running on any one of cluster node on configured static IP.
2) In case if node goes down where GNS is running it will be automatically failover by clusterware on another alive node since GNS VIP is managed by clusterware itself.
3) GNS use own domain name which represent all the nodes running under clusterware.
4) Forwarders rule must be define between your corporate domain and the GNS domain(Sub-domain) so that whenever corporate domain receive request for GNS domain it will forward on the same IP on which GNS service is running.
Ok so after brief about GNS and GPNP now let's back to the implementation part. How to configure GNS and GPNP for 11g R2 RAC installation.
Follow the followings simple steps to configure GNS and GPNP-
Please Note followings-
DNS & DHCP server- "server1.oracle.com" IP is 192.9.201.53
Corporate Domain name is- "oracle.com"
GNS subdomain name is - "cluster01.oracle.com"
GNS name is - "cluster01-gns"
GNS IP- 192.9.201.180 (GNS IP must public IP range).
Step 1) For GNS and GPNP first we have to setup corporate DNS and DHCP as well. DHCP is required because while installation using GNS, IP for node-vip and scan-vip is automatically requested.
Step 2) Configure delegate between corporate domain and GNS sub-domain so that corporate domain automaticlly forward client request to GNS- For this we have to make changes in DNS configuration file "named.conf" and forward zone file "forward.zone".
To configure delegate between DNS and GNS sub domain, we have to make some changes in named.conf and forward zone file.
Below is the entries for named.conf
options {
listen-on port 53 { 192.9.201.59; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
// Those options should be used carefully because they disable port
// randomization
// query-source port 53;
// query-source-v6 port 53;
allow-query { any; };
allow-query-cache { any; };
};
//logging {
// channel default_debug {
// file "data/named.run";
// severity dynamic;
// };
//};
//view localhost_resolver {
// match-clients { localhost; };
// match-destinations { localhost; };
// recursion yes;
// include "/etc/named.rfc1912.zones";
//};
//named.rfc1912.zones:
// Provided by Red Hat caching-nameserver package
//
// ISC BIND named zone configuration for zones recommended by
// RFC 1912 section 4.1 : localhost TLDs and address zones
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
zone "." IN {
type hint;
file "named.ca";
};
zone "localdomain" IN {
type master;
file "localdomain.zone";
allow-update { none; };
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN {
type master;
file "named.ip6.local";
allow-update { none; };
};
zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};
zone "0.in-addr.arpa" IN {
type master;
file "named.zero";
allow-update { none; };
};
zone "oracle.com" IN {
type master;
file "forward.zone";
allow-transfer { 192.9.201.180; };
};
zone "201.9.192.in-addr.arpa" IN {
type master;
file "reverse.zone";
};
zone "0.0.10.in-addr.arpa" IN {
type master;
file "reverse1.zone";
};
As you can see named.conf file, here I am using forward.zone, reverse.zone and reverse1.zone as zone file to resolve hostname into IP address and vice-versa. I am using two reverse file because because I have two different range of IP. 192.9.201.0 is for public IP and 10.0.0.0 for private IP.
Most of the entries in named.conf file is common to normal DNS configuration. I just added an extra line for "oracle.com" which is mentioned in red color.
Another configuration changes required in forward.zone file. Please add following lines to configure delegate between corporate domain and GNS sun-domain-
Below is the configuration details of my DHCP server-
ddns-update-style interim;
ignore client-updates;
subnet 192.9.201.0 netmask 255.255.255.0 {
# --- default gateway
option routers 192.9.201.1;
option subnet-mask 255.255.255.0;
option nis-domain "oracle.com";
option domain-name "oracle.com";
option domain-name-servers 192.9.201.59;
option time-offset -18000; # Eastern Standard Time
# option ntp-servers 192.168.1.1;
# option netbios-name-servers 192.168.1.1;
# --- Selects point-to-point node (default is hybrid). Don't change this unless
# -- you understand Netbios very well
# option netbios-node-type 2;
range dynamic-bootp 192.9.201.190 192.9.201.254;
default-lease-time 21600;
max-lease-time 43200;
# we want the nameserver to appear at a fixed address
#host ns {
# next-server marvin.redhat.com;
# hardware ethernet 12:34:56:78:AB:CD;
# fixed-address 207.175.42.254;
#}
}
I hope above doc will help you to setup GNS and GPNP. Your suggestions is always welcome to make it more better.
----------------------------------------------------------------------------------------------------------
Related links:
11G R2 RAC PROBLEMS AND SOLUTIONS
CLONE DATABASE HOME IN 11GR2 RAC
NIC BONDING IN 11G R2 RAC
SERVICES CONFUSIONS CLEARED
SETUP 10G RAC ON YOUR LAPTOP
SETUP AND PLAY WITH 11G R2 RAC AT YOUR HOME PC
11g R2 RAC - ADD INSTANCE MANUALLY
11G R2 RAC : DYNAMIC REMASTERING DEMONSTRATED
11gR2 RAC : USE RCONFIG TO CONVERT NON RAC DATABASE TO RAC DATABASE
http://koenigocm.blogspot.in/search/label/11gR2%20RAC%20%3A%20USE%20RCONFIG%20TO%20CONVERT%20NON%20RAC%20DATABASE%20TO%20%20RAC%20DATABASE
11g R2 RAC : RECOVER VOTING DISK - A SCENARIO
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20%3A%20RECOVER%20VOTING%20DISK%20-%20A%20SCENARIO
11g R2 RAC : TRACING SERVICES IN A RAC DATABASE
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20%3A%20TRACING%20SERVICES%20%20IN%20A%20RAC%20DATABASE
Before to go for implementation part let me just brief about GNS and GPNP. As you know GPNP is one of the most important features of 11g R2 RAC which allow us to add the node in cluster in simple and easy way as we just plug the server and start it. GNS (Grid naming service) is a DNS kind of service hosted by Oracle clusterware and running on one of configured static IP and responsible to resolve requested hostname running under Oracle cluster into corresponding IP.
Following points must be noted about GNS-
1) GNS is DNS kind of service hosted by Oracle clusterware and running on any one of cluster node on configured static IP.
2) In case if node goes down where GNS is running it will be automatically failover by clusterware on another alive node since GNS VIP is managed by clusterware itself.
3) GNS use own domain name which represent all the nodes running under clusterware.
4) Forwarders rule must be define between your corporate domain and the GNS domain(Sub-domain) so that whenever corporate domain receive request for GNS domain it will forward on the same IP on which GNS service is running.
Ok so after brief about GNS and GPNP now let's back to the implementation part. How to configure GNS and GPNP for 11g R2 RAC installation.
Follow the followings simple steps to configure GNS and GPNP-
Please Note followings-
DNS & DHCP server- "server1.oracle.com" IP is 192.9.201.53
Corporate Domain name is- "oracle.com"
GNS subdomain name is - "cluster01.oracle.com"
GNS name is - "cluster01-gns"
GNS IP- 192.9.201.180 (GNS IP must public IP range).
Step 1) For GNS and GPNP first we have to setup corporate DNS and DHCP as well. DHCP is required because while installation using GNS, IP for node-vip and scan-vip is automatically requested.
Step 2) Configure delegate between corporate domain and GNS sub-domain so that corporate domain automaticlly forward client request to GNS- For this we have to make changes in DNS configuration file "named.conf" and forward zone file "forward.zone".
To configure delegate between DNS and GNS sub domain, we have to make some changes in named.conf and forward zone file.
Below is the entries for named.conf
options {
listen-on port 53 { 192.9.201.59; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
// Those options should be used carefully because they disable port
// randomization
// query-source port 53;
// query-source-v6 port 53;
allow-query { any; };
allow-query-cache { any; };
};
//logging {
// channel default_debug {
// file "data/named.run";
// severity dynamic;
// };
//};
//view localhost_resolver {
// match-clients { localhost; };
// match-destinations { localhost; };
// recursion yes;
// include "/etc/named.rfc1912.zones";
//};
//named.rfc1912.zones:
// Provided by Red Hat caching-nameserver package
//
// ISC BIND named zone configuration for zones recommended by
// RFC 1912 section 4.1 : localhost TLDs and address zones
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
zone "." IN {
type hint;
file "named.ca";
};
zone "localdomain" IN {
type master;
file "localdomain.zone";
allow-update { none; };
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN {
type master;
file "named.ip6.local";
allow-update { none; };
};
zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};
zone "0.in-addr.arpa" IN {
type master;
file "named.zero";
allow-update { none; };
};
zone "oracle.com" IN {
type master;
file "forward.zone";
allow-transfer { 192.9.201.180; };
};
zone "201.9.192.in-addr.arpa" IN {
type master;
file "reverse.zone";
};
zone "0.0.10.in-addr.arpa" IN {
type master;
file "reverse1.zone";
};
As you can see named.conf file, here I am using forward.zone, reverse.zone and reverse1.zone as zone file to resolve hostname into IP address and vice-versa. I am using two reverse file because because I have two different range of IP. 192.9.201.0 is for public IP and 10.0.0.0 for private IP.
Most of the entries in named.conf file is common to normal DNS configuration. I just added an extra line for "oracle.com" which is mentioned in red color.
Another configuration changes required in forward.zone file. Please add following lines to configure delegate between corporate domain and GNS sun-domain-
$ORIGIN cluster01.oracle.com. @ IN NS cluster01-gns.cluster01.oracle.com. cluster01-gns IN A 192.168.1.92
Below is the configuration details of my DHCP server-
ddns-update-style interim;
ignore client-updates;
subnet 192.9.201.0 netmask 255.255.255.0 {
# --- default gateway
option routers 192.9.201.1;
option subnet-mask 255.255.255.0;
option nis-domain "oracle.com";
option domain-name "oracle.com";
option domain-name-servers 192.9.201.59;
option time-offset -18000; # Eastern Standard Time
# option ntp-servers 192.168.1.1;
# option netbios-name-servers 192.168.1.1;
# --- Selects point-to-point node (default is hybrid). Don't change this unless
# -- you understand Netbios very well
# option netbios-node-type 2;
range dynamic-bootp 192.9.201.190 192.9.201.254;
default-lease-time 21600;
max-lease-time 43200;
# we want the nameserver to appear at a fixed address
#host ns {
# next-server marvin.redhat.com;
# hardware ethernet 12:34:56:78:AB:CD;
# fixed-address 207.175.42.254;
#}
}
I hope above doc will help you to setup GNS and GPNP. Your suggestions is always welcome to make it more better.
----------------------------------------------------------------------------------------------------------
Related links:
HOME
11.2 RAC GOODIES AND SERVERPOOLS
11G R2 RAC PROBLEMS AND SOLUTIONS
CLONE DATABASE HOME IN 11GR2 RAC
NIC BONDING IN 11G R2 RAC
SERVICES CONFUSIONS CLEARED
SETUP 10G RAC ON YOUR LAPTOP
SETUP AND PLAY WITH 11G R2 RAC AT YOUR HOME PC
11g R2 RAC - ADD INSTANCE MANUALLY
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20-%20ADD%
11g R2 RAC - LOCAL ARCHIVE WITH NFS
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20-%20LOCAL%20ARCHIVE%20WITH%20NFS
11g R2 RAC : CACHE FUSION DEMONSTRATED
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20%3A%20CACHE%20FUSION%20DEMONSTRATED
11g R2 RAC - LOCAL ARCHIVE WITH NFS
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20-%20LOCAL%20ARCHIVE%20WITH%20NFS
11g R2 RAC : CACHE FUSION DEMONSTRATED
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20%3A%20CACHE%20FUSION%20DEMONSTRATED
11G R2 RAC : DYNAMIC REMASTERING DEMONSTRATED
11gR2 RAC : USE RCONFIG TO CONVERT NON RAC DATABASE TO RAC DATABASE
http://koenigocm.blogspot.in/search/label/11gR2%20RAC%20%3A%20USE%20RCONFIG%20TO%20CONVERT%20NON%20RAC%20DATABASE%20TO%20%20RAC%20DATABASE
11g R2 RAC : RECOVER VOTING DISK - A SCENARIO
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20%3A%20RECOVER%20VOTING%20DISK%20-%20A%20SCENARIO
11g R2 RAC : TRACING SERVICES IN A RAC DATABASE
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%20%3A%20TRACING%20SERVICES%20%20IN%20A%20RAC%20DATABASE
11G R2 RAC: INSTANCE RECOVERY
http://koenigocm.blogspot.in/search/label/11G%20R2%20RAC%3A%20INSTANCE%20RECOVERY
11g R2 RAC: MANAGING THIRD PARTY APPLICATIONS USING APPLICATION VIP
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%3A%20MANAGING%20THIRD%20PARTY%20APPLICATIONS%20USING%20APPLICATION%20VIP
http://koenigocm.blogspot.in/search/label/11G%20R2%20RAC%3A%20INSTANCE%20RECOVERY
11g R2 RAC: MANAGING THIRD PARTY APPLICATIONS USING APPLICATION VIP
http://koenigocm.blogspot.in/search/label/11g%20R2%20RAC%3A%20MANAGING%20THIRD%20PARTY%20APPLICATIONS%20USING%20APPLICATION%20VIP
No comments:
Post a Comment