11 Replies Latest reply: Jul 13, 2013 11:02 AM by 808880 RSS

    nslookup scan ip not pingable in rac node

    808880

      All,

       

      I'm planning to install 11.2.0.1 rac on my laptop. As a first step I have configured dns in separate vmware and configured rac1 node as well. Both dns and rac1 public ip addresses are pingable from each others and from host machine.But the rac-scan ip is only pingable from dns server and not pingable from rac1 server.  Will this make any problem if dns server running on 32 bit and rac nodes running on 64 bit server ? Please let me know if I have anything missed here. Thanks again.

       

      About posting on this forum. I have used [code]  [/code] to format the code previously. But this time it is not working. Also there is no option to preview the code before posting.

       

      use spaces to separate multiple tags I'm not clear about this. I read https://forums.oracle.com/thread/865295 this article how to post the code. It says to use  \ . If you guide me how to format the code I can use that in future.

       

      Host OS : Windows 8 64 bit

      Guest OS -1 : dns 32 bit Linux

      \

        [root@dns32 ~]# uname -a

         Linux dns32.testenv.com 2.6.18-164.el5 #1 SMP Thu Sep 3 02:16:47 EDT 2009 i686 i686 i386 GNU/Linux

      \


      Guest OS -2 : rac1 64 bit Linux

      \

        [root@rac1 ~]# uname -a

         Linux rac1 2.6.18-194.el5 #1 SMP Mon Mar 29 22:10:29 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

      \

       

      Guest OS-3 : rac2 - yet to configure 64 bit Linux

       

      @ dns server

      ***************

      \

       

      [root@dns32 ~]# nslookup rac-scan

      Server:         192.168.1.26

      Address:        192.168.1.26#53

       

      Name:   rac-scan.testenv.com

      Address: 192.168.1.57

      Name:   rac-scan.testenv.com

      Address: 192.168.1.58

      Name:   rac-scan.testenv.com

      Address: 192.168.1.59

       

       

      [root@dns32 ~]# cat /etc/resolv.conf

      search testenv.com

      nameserver 192.168.1.26

       

       

      [root@dns32 ~]# ifconfig -a

      eth0      Link encap:Ethernet  HWaddr 00:0C:29:EF:03:D3

                inet addr:192.168.1.26  Bcast:192.168.1.255  Mask:255.255.255.0

                inet6 addr: fe80::20c:29ff:feef:3d3/64 Scope:Link

                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

                RX packets:2802 errors:0 dropped:0 overruns:0 frame:0

                TX packets:2691 errors:0 dropped:0 overruns:0 carrier:0

                collisions:0 txqueuelen:1000

                RX bytes:210115 (205.1 KiB)  TX bytes:208344 (203.4 KiB)

                Interrupt:67 Base address:0x2024

       

       

      lo        Link encap:Local Loopback

                inet addr:127.0.0.1  Mask:255.0.0.0

                inet6 addr: ::1/128 Scope:Host

                UP LOOPBACK RUNNING  MTU:16436  Metric:1

                RX packets:2308 errors:0 dropped:0 overruns:0 frame:0

                TX packets:2308 errors:0 dropped:0 overruns:0 carrier:0

                collisions:0 txqueuelen:0

                RX bytes:5494207 (5.2 MiB)  TX bytes:5494207 (5.2 MiB)

       

       

       

       

      sit0      Link encap:IPv6-in-IPv4

                NOARP  MTU:1480  Metric:1

                RX packets:0 errors:0 dropped:0 overruns:0 frame:0

                TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

                collisions:0 txqueuelen:0

                RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

       

      [root@dns32 ~]# ping 192.168.1.26

      PING 192.168.1.26 (192.168.1.26) 56(84) bytes of data.

      64 bytes from 192.168.1.26: icmp_seq=1 ttl=64 time=0.200 ms

       

      --- 192.168.1.26 ping statistics ---

      1 packets transmitted, 1 received, 0% packet loss, time 0ms

      rtt min/avg/max/mdev = 0.200/0.200/0.200/0.000 ms

       

      [root@dns32 ~]# ping 192.168.1.27

      PING 192.168.1.27 (192.168.1.27) 56(84) bytes of data.

      64 bytes from 192.168.1.27: icmp_seq=1 ttl=64 time=0.330 ms

       

      --- 192.168.1.27 ping statistics ---

      1 packets transmitted, 1 received, 0% packet loss, time 0ms

      rtt min/avg/max/mdev = 0.330/0.330/0.330/0.000 ms

       

      \

       

      @rac1 node :

      ***********************

      \

       

      [root@rac1 ~]# cat /etc/resolv.conf

      search testenv.com

      nameserver 192.168.1.26

       

      [root@rac1 ~]#  nslookup rac-scan

      ;; connection timed out; no servers could be reached

       

      [root@rac1 ~]# ifconfig -a

      eth0      Link encap:Ethernet  HWaddr 00:0C:29:75:A9:39

                inet addr:192.168.1.27  Bcast:192.168.1.255  Mask:255.255.255.0

                inet6 addr: fe80::20c:29ff:fe75:a939/64 Scope:Link

                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

                RX packets:500 errors:0 dropped:0 overruns:0 frame:0

                TX packets:357 errors:0 dropped:0 overruns:0 carrier:0

                collisions:0 txqueuelen:1000

                RX bytes:52333 (51.1 KiB)  TX bytes:39556 (38.6 KiB)

       

       

       

      eth1      Link encap:Ethernet  HWaddr 00:0C:29:75:A9:43

                inet addr:192.168.2.37  Bcast:192.168.2.255  Mask:255.255.255.0

                inet6 addr: fe80::20c:29ff:fe75:a943/64 Scope:Link

                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

                RX packets:160 errors:0 dropped:0 overruns:0 frame:0

                TX packets:50 errors:0 dropped:0 overruns:0 carrier:0

                collisions:0 txqueuelen:1000

                RX bytes:20359 (19.8 KiB)  TX bytes:6518 (6.3 KiB)

       

       

       

       

      lo        Link encap:Local Loopback

                inet addr:127.0.0.1  Mask:255.0.0.0

                inet6 addr: ::1/128 Scope:Host

                UP LOOPBACK RUNNING  MTU:16436  Metric:1

                RX packets:1940 errors:0 dropped:0 overruns:0 frame:0

                TX packets:1940 errors:0 dropped:0 overruns:0 carrier:0

                collisions:0 txqueuelen:0

                RX bytes:4783881 (4.5 MiB)  TX bytes:4783881 (4.5 MiB)

       

       

       

      sit0      Link encap:IPv6-in-IPv4

                NOARP  MTU:1480  Metric:1

                RX packets:0 errors:0 dropped:0 overruns:0 frame:0

                TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

                collisions:0 txqueuelen:0

                RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

       

      [root@rac1 ~]# ping 192.168.1.26

      PING 192.168.1.26 (192.168.1.26) 56(84) bytes of data.

      64 bytes from 192.168.1.26: icmp_seq=1 ttl=64 time=0.284 ms

      64 bytes from 192.168.1.26: icmp_seq=2 ttl=64 time=0.456 ms

       

       

      --- 192.168.1.26 ping statistics ---

      2 packets transmitted, 2 received, 0% packet loss, time 1000ms

      rtt min/avg/max/mdev = 0.284/0.370/0.456/0.086 ms

      [root@rac1 ~]# ping 192.168.1.27

      PING 192.168.1.27 (192.168.1.27) 56(84) bytes of data.

      64 bytes from 192.168.1.27: icmp_seq=1 ttl=64 time=0.032 ms

       

       

      --- 192.168.1.27 ping statistics ---

      1 packets transmitted, 1 received, 0% packet loss, time 0ms

      rtt min/avg/max/mdev = 0.032/0.032/0.032/0.000 ms

       

      \

       

      Thanks

      Arul

        • 1. Re: nslookup scan ip not pingable in rac node
          saurabh

          You only need to define the rc-scan ip in dns and doesnot assign any network interface to it on any node.

           

          Try nslookup of your node 1 is it giving you output

          • 2. Re: nslookup scan ip not pingable in rac node
            808880

            I have already tried.

             

            @rac1 node :

            ***********************

            [root@rac1 ~]# cat /etc/resolv.conf

            search testenv.com

            nameserver 192.168.1.26

             

            [root@rac1 ~]#  nslookup rac-scan

            ;; connection timed out; no servers could be reached

            • 3. Re: nslookup scan ip not pingable in rac node
              808880

              [root@rac1 ~]# nslookup rac1

              ;; connection timed out; no servers could be reached

               

              [root@dns32 ~]# nslookup rac1

              Server:         192.168.1.26

              Address:        192.168.1.26#53

              Name:   rac1.testenv.com

              Address: 192.168.1.27

               

              Thanks.

              • 4. Re: nslookup scan ip not pingable in rac node
                saurabh

                As your output shows that you are not even able to do nslookup of your public ip to.

                There might be any issue in your dns configuration.

                 

                post the named.conf and your zone file entry.

                • 5. Re: nslookup scan ip not pingable in rac node
                  808880

                  Thanks Saurabh. I have configured dns using this blog " http://dnccfg.blogspot.in/2012/08/dns-configuration-on-linux.html.html

                   

                  [root@dns32 etc]# cat named.conf

                  //

                  // named.caching-nameserver.conf

                  //

                  // Provided by Red Hat caching-nameserver package to configure the

                  // ISC BIND named(8) DNS server as a caching only nameserver

                  // (as a localhost DNS resolver only).

                  //

                  // See /usr/share/doc/bind*/sample/ for example named configuration files.

                  //

                  // DO NOT EDIT THIS FILE - use system-config-bind or an editor

                  // to create named.conf - edits to this file will be lost on

                  // caching-nameserver package upgrade.

                  //

                  options {

                          listen-on port 53 { 192.168.1.26; };

                          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 { localhost; };

                  };

                  logging {

                          channel default_debug {

                                  file "data/named.run";

                                  severity dynamic;

                          };

                  };

                  view localhost_resolver {

                          match-clients      { any; };

                          match-destinations { 192.168.1.26; };

                          recursion yes;

                          include "/etc/named.rfc1912.zones";

                  };

                   

                  ***********************************

                   

                  [root@dns32 etc]# cat 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 "testenv.com" IN {

                          type master;

                          file "forward.zone";

                          allow-update { none; };

                  };

                   

                   

                  zone "localhost" IN {

                          type master;

                          file "localhost.zone";

                          allow-update { none; };

                  };

                   

                   

                  zone "1.168.192.in-addr.arpa" IN {

                          type master;

                          file "reverse.zone";

                          allow-update { none; };

                  };

                   

                  *******************

                  [root@dns32 named]# cat forward.zone

                  $TTL    86400

                  @               IN SOA  dns32.testenv.com. root.dns32.testenv.com. (

                                                          42              ; serial (d. adams)

                                                          3H              ; refresh

                                                          15M             ; retry

                                                          1W              ; expiry

                                                          1D )            ; minimum

                                  IN NS           dns32.testenv.com.

                  dns32     IN A 192.168.1.26

                  rac1      IN A 192.168.1.27

                  rac2      IN A 192.168.1.28

                  rac1-priv  IN A 192.168.2.37

                  rac2-priv  IN A 192.168.2.38

                  rac1-vip  IN A 192.168.1.47

                  rac2-vip  IN A 192.168.1.48

                  rac-scan  IN A 192.168.1.57

                  rac-scan  IN A 192.168.1.58

                  rac-scan  IN A 192.168.1.59

                   

                  ******************************

                   

                  [root@dns32 named]# cat reverse.zone

                  $TTL    86400

                  @       IN      SOA     dns32.testenv.com. root.dns32.testenv.com.  (

                                                        1997022700 ; Serial

                                                        28800      ; Refresh

                                                        14400      ; Retry

                                                        3600000    ; Expire

                                                        86400 )    ; Minimum

                          IN      NS      dns32.testenv.com.

                  26       IN      PTR     dns32.testenv.com.

                  27        IN      PTR   rac1.testenv.com.

                  28        IN      PTR   rac2.testenv.com.

                  47        IN      PTR   rac1-vip.testenv.com.

                  48        IN      PTR   rac2-vip.testenv.com.

                  57        IN      PTR   rac-scan.testenv.com.

                  58        IN      PTR   rac-scan.testenv.com.

                  59        IN      PTR   rac-scan.testenv.com.

                   

                  Thanks

                  Arul

                  • 6. Re: nslookup scan ip not pingable in rac node
                    saurabh

                    for cluster configuration reverse zone is not require.

                    What i will suggest you as we are not a dedicated sys admin, we should configure a simple dns. If you want you can use following codes to configure as what i have did it.

                     

                    [root@orpheus ~]# cat /etc/named.conf

                     

                    options {

                            directory "/var/named";

                            dump-file "/var/named/data/cache_dump.db";

                            statistics-file "/var/named/data/named_stats.txt";

                            forwarders { 192.168.1.1; };

                    };

                    include "/etc/rndc.key";

                     

                    zone "hadesnet" IN {

                    type master;

                    file "hadesnet.zone";

                    allow-update { none; };

                    };

                     

                    [root@orpheus Server]# cat /var/named/hadesnet.zone

                    $TTL  86400

                    @ IN SOA      hadesnet. hadesnet.(

                    42          ; serial (d. adams)

                    3H          ; refresh

                    15M         ; retry

                    1W          ; expiry

                    1D )        ; minimum

                     

                    hadesnet.                     IN NS   10.10.1.20

                    localhost                     IN A    127.0.0.1

                    orpheus.hadesnet.             IN A    10.10.1.10

                    eurydice.hadesnet.            IN A    10.10.1.20

                    orpheus-vip.hadesnet.         IN A    10.10.1.11

                    eurydice-vip.hadesnet.        IN A    10.10.1.21

                    underworld-scan.hadesnet.     IN A    10.10.1.12

                    underworld-scan.hadesnet.     IN A    10.10.1.22

                     

                     

                    I have configured my DNS in node 2 itself.

                    node1 ip = 10.10.1.10

                    node2 ip = 10.10.1.20

                    • 7. Re: nslookup scan ip not pingable in rac node
                      808880

                      Thanks Saurabh. But oracle has recommended to use DNS for separate server and not to use rac database nodes. If the dns configured node goes down entire clusters will go down. I'm just trying to identify whether the problem with existing DNS configuration  or any network issue between DNS server and rac1.

                      • 8. Re: nslookup scan ip not pingable in rac node
                        saurabh

                        There is no network issue as you can ping both the machines. There might a issue with the dns configuration. Try nslookup using ip on both node 1 and dns server.

                         

                        What i was saying configure DNS on different sever using above parameter and changes where required.

                        • 9. Re: nslookup scan ip not pingable in rac node
                          808880

                          Thanks again Saurabh. I will try your settings and will come up if any problems. Below is the ip nslookup status.

                           

                          [root@rac1 ~]# nslookup 192.168.1.27

                          ;; connection timed out; no servers could be reached

                           

                          [root@dns32 named]# nslookup 192.168.1.27

                          Server:         192.168.1.26

                          Address:        192.168.1.26#53

                           

                          27.1.168.192.in-addr.arpa       name = rac1.testenv.com.

                          • 10. Re: nslookup scan ip not pingable in rac node
                            808880

                            I have followed your config settings. But the named services itself not coming up.

                             

                            [root@dns32 etc]# service named restart

                            Stopping named:                                            [  OK  ]

                            testenv.com.zoneStarting named:

                            Error in named configuration:

                            zone testenv.com/IN: loading master file testenv.com.zone: file not found

                            _default/testenv.com/IN: file not found

                                                                                       [FAILED]

                             

                            [root@dns32 etc]# cat /var/named/chroot/etc/named.conf

                            options {

                                    directory "/var/named";

                                    dump-file "/var/named/data/cache_dump.db";

                                    statistics-file "/var/named/data/named_stats.txt";

                                    forwarders { 192.168.1.1; };

                            };

                            include "/etc/rndc.key";

                             

                             

                            zone "testenv.com" IN {

                            type master;

                            file "testenv.com.zone";

                            allow-update { none; };

                            };

                            [root@dns32 etc]# cat /var/named/chroot/etc/testenv.com.zone

                            $TTL  86400

                            @ IN SOA      testenv.com. testenv.com.(

                            42          ; serial (d. adams)

                            3H          ; refresh

                            15M         ; retry

                            1W          ; expiry

                            1D )        ; minimum

                             

                             

                            testenv.com.                    IN NS   192.168.1.26

                            localhost                       IN A    127.0.0.1

                            rac1.testenv.com.               IN A    192.168.1.27

                            rac2.testenv.com.               IN A    192.168.1.28

                            rac1-vip.testenv.com.           IN A    192.168.1.47

                            rac2-vip.testenv.com.           IN A    192.168.1.48

                            rac-scan.testenv.com.           IN A    192.168.1.57

                            rac-scan.testenv.com.           IN A    192.168.1.58

                            rac-scan.testenv.com.           IN A    192.168.1.59

                             

                            Thanks

                            • 11. Re: nslookup scan ip not pingable in rac node
                              808880

                              I have configured fresh 64 bit DNS server and installed 11.2.0.1. All looks fine now. Thanks to everyone.