1 2 Previous Next 19 Replies Latest reply: Feb 9, 2010 12:48 AM by 721050 RSS

    vip resolving

    721050
      hi

      i am trying to install grid infra with DNS settings.but its not accepting/resolving the VIP during installation although my VIP is declared in db.domain-name.de file.what else to do?

      regards
        • 1. Re: vip resolving
          506787
          install it with a correct vip.

          of course that's nonsense.

          please, please, start with operating system, version, 32/64, oracle version, 32/64, public ip address and dns names, private ip address and dns names, and vip address and dns names.
          then, describe the exact error and messages you received.

          try to put some effort in your question. it will be rewarded with effort from the community.
          • 2. Re: vip resolving
            721050
            frits hoogland wrote:
            install it with a correct vip.

            of course that's nonsense.

            please, please, start with operating system, version, 32/64, oracle version, 32/64, public ip address and dns names, private ip address and dns names, and vip address and dns names.
            then, describe the exact error and messages you received.

            try to put some effort in your question. it will be rewarded with effort from the community.
            i can post anything,but it will post junk of log.hope some specific steps from commu members.
            db.sayantan-chakraborty.de
            $ORIGIN .
            sayantan-chakraborty.de               SOA     rac-1.sayantan-chakraborty.de. rac-1.sayantan-chakraborty.de. (
             22         ; serial
             900        ; refresh (15 minutes)
             600        ; retry (10 minutes)
             86400      ; expire (1 day)
             3600       ; minimum (1 hour)
             )
             NS      rac-1.sayantan-chakraborty.de.
             NS      rac-2.sayantan-chakraborty.de.
            $ORIGIN sayantan-chakraborty.de.
            router                A      192.168.1.1
            rac-1                    A       192.168.1.2
            rac-2                    A       192.168.1.3
            rac1vip                A       192.168.1.25
            rac2vip                A       192.168.1.35
            rac-1-priv               A       192.168.181.10
            rac-2-priv               A       192.168.181.20
            rac-scan                 A       192.168.1.31
            rac-scan                 A       192.168.1.23
            rac-scan           A      192.168.1.45
            ifconfige -a
            [root@rac-1 ~]# /sbin/ifconfig -a
            eth0      Link encap:Ethernet  HWaddr 00:00:E8:F7:02:B0  
                      inet addr:192.168.1.25  Bcast:192.168.1.255  Mask:255.255.255.0
                      inet6 addr: fe80::200:e8ff:fef7:2b0/64 Scope:Link
                      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                      RX packets:2616 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:1521 errors:0 dropped:0 overruns:0 carrier:0
                      collisions:0 txqueuelen:1000 
                      RX bytes:699703 (683.3 KiB)  TX bytes:263787 (257.6 KiB)
                      Interrupt:177 Base address:0x8400 
            
            eth1      Link encap:Ethernet  HWaddr 00:26:18:59:EE:49  
                      inet addr:192.168.181.10  Bcast:192.168.181.255  Mask:255.255.255.0
                      inet6 addr: fe80::226:18ff:fe59:ee49/64 Scope:Link
                      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:0 errors:0 dropped:0 overruns:0 carrier:1
                      collisions:0 txqueuelen:1000 
                      RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
                      Memory:fe9c0000-fea00000 
            
            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:2162 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:2162 errors:0 dropped:0 overruns:0 carrier:0
                      collisions:0 txqueuelen:0 
                      RX bytes:3587802 (3.4 MiB)  TX bytes:3587802 (3.4 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)
            
            virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
                      inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
                      inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
                      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
                      collisions:0 txqueuelen:0 
                      RX bytes:0 (0.0 b)  TX bytes:11064 (10.8 KiB)
            
            [root@rac-1 ~]# 
            i have declared vip under alias of eth0 with nick name rac1vip

            named.conf
            // Enterprise Linux BIND Configuration Tool
            // 
            // Default initial "Caching Only" name server configuration
            //
            
            // Enterprise Linux BIND Configuration Tool
            // 
            // Default initial "Caching Only" name server configuration
            //
            
            options {
                 directory "/var/named";
                 dump-file "/var/named/data/cache_dump.db";
                    statistics-file "/var/named/data/named_stats.txt";
                 /*
                  * If there is a firewall between you and nameservers you want
                  * to talk to, you might need to uncomment the query-source
                  * directive below.  Previous versions of BIND always asked
                  * questions using port 53, but BIND 8.1 uses an unprivileged
                  * port by default.
                  */
                  // query-source address * port 53;
                 //directory "/var/named";
                  listen-on-v6 { none; };
                 // allow-query { sayantan-; };
                 //forwarders { 218.248.240.208 ; 218.248.240.135 ; }; #IP of upstream ISP nameserver(s)
                 //forward only; #rely completely on our upstream nameservers
                 //notify no;
                 max-cache-size unlimited;
                 recursive-clients 1000;
                 
                    
            };
            
            logging {
             # Log queries to a file limited to a size of 100 MB.
             channel query_logging {
             file "/var/named/named_querylog"
             versions 3 size 100M;
             print-time yes;                 // timestamp log entries
             };
             category queries {
             query_logging;
             };
            
             # Or log this kind alternatively to syslog.
             channel syslog_queries {
             syslog user;
             severity info;
             };
             category queries { syslog_queries; };
            
             # Log general name server errors to syslog.
             channel syslog_errors {
             syslog user;
             severity error;
             };
             category default { syslog_errors;  };
            
            
             # Don't log lame server messages.
             category lame-servers { null; };
            };
            
            
            #zone "." IN {
            #     type hint;
            #     file "named.root";
            #};
            
            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 "127.0.0.zone";
            };
            
            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; };
            };
            
            include "/etc/rndc.key";
            
            # Forward Zone for sayantan-chakraborty domain
            zone "sayantan-chakraborty.de" IN {
            type master;
             file "db.sayantan-chakraborty.de";
             allow-transfer { acl_transf; };
            };
            
            # Reverse Zone for sayantan-chakraborty domain
            #zone "1.168.192.in-addr.arpa" IN {
            #        type master;
            #        file "192.168.1.zone";            
            # };
            
            acl acl_transf { 192.168.1.3/24; };
            
            acl acl_name { any; };
            
            //acl sayantan-chakraborty { 192.168.1.3/24; 127.0/8; };
            //options {
                    
            //};
            127.0.0.zone
            $TTL 1W
            @               IN SOA          localhost.   root.localhost. (
             42              ; serial (d. adams)
             2D              ; refresh
             4H              ; retry
             6W              ; expiry
             1W )            ; minimum
            
             IN NS           localhost.
            1               IN PTR          localhost.
            localhost.zone
            $TTL     86400
            @          IN SOA     @       root (
                                     42          ; serial (d. adams)
                                     3H          ; refresh
                                     15M          ; retry
                                     1W          ; expiry
                                     1D )          ; minimum
            
                         IN NS          @
                       IN A          127.0.0.1
                      IN AAAA          ::1
            named_querylog
            03-Feb-2010 16:04:11.685 client 192.168.1.3#1031: query: rac-2.sayantan-chakraborty.de.sayantan-chakraborty.de IN AAAA +
            03-Feb-2010 16:04:11.685 client 192.168.1.3#1031: query: rac-2.sayantan-chakraborty.de IN A +
            03-Feb-2010 16:04:15.273 client 192.168.1.2#36398: query: safebrowsing.clients.google.com IN AAAA +
            03-Feb-2010 16:04:15.337 client 192.168.1.2#45085: query: safebrowsing.clients.google.com IN A +
            03-Feb-2010 16:04:15.372 client 192.168.1.2#38963: query: safebrowsing.clients.google.com IN A +
            03-Feb-2010 16:05:25.156 client 127.0.0.1#48580: query: rac-1.sayantan-chakraborty.de IN A +
            03-Feb-2010 16:05:29.427 client 192.168.1.2#51713: query: safebrowsing.clients.google.com IN AAAA +
            03-Feb-2010 16:05:29.464 client 192.168.1.2#25503: query: safebrowsing.clients.google.com IN A +
            03-Feb-2010 16:05:29.501 client 192.168.1.2#25404: query: safebrowsing.clients.google.com IN A +
            03-Feb-2010 16:05:33.505 client 127.0.0.1#46741: query: rac-2.sayantan-chakraborty.de IN A +
            03-Feb-2010 16:05:46.444 client 127.0.0.1#13142: query: rac-scan.sayantan-chakraborty.de IN A +
            03-Feb-2010 16:06:51.272 client 192.168.1.2#61463: query: api.mywot.com IN AAAA +
            03-Feb-2010 16:06:51.309 client 192.168.1.2#65298: query: api.mywot.com.localdomain IN AAAA +
            03-Feb-2010 16:06:51.309 client 192.168.1.2#61001: query: api.mywot.com IN A +
            03-Feb-2010 16:06:51.507 client 192.168.1.2#54724: query: pagead2.googlesyndication.com IN AAAA +
            03-Feb-2010 16:06:51.544 client 192.168.1.2#9305: query: pagead2.googlesyndication.com IN A +
            03-Feb-2010 16:06:51.588 client 192.168.1.2#47898: query: pagead2.googlesyndication.com IN A +
            03-Feb-2010 16:06:51.642 client 192.168.1.2#10951: query: googleads.g.doubleclick.net IN AAAA +
            03-Feb-2010 16:06:51.700 client 192.168.1.2#30104: query: googleads.g.doubleclick.net IN A +
            03-Feb-2010 16:06:51.743 client 192.168.1.2#35986: query: googleads.g.doubleclick.net IN A +
            03-Feb-2010 16:08:45.036 client 192.168.1.3#1024: query: sayantan-chakraborty.de IN SOA -E
            03-Feb-2010 16:08:45.037 client 192.168.1.3#52716: query: sayantan-chakraborty.de IN AXFR -
            03-Feb-2010 16:09:11.873 client 192.168.1.3#1031: query: rac-2.sayantan-chakraborty.de IN AAAA +
            03-Feb-2010 16:09:11.874 client 192.168.1.3#1031: query: rac-2.sayantan-chakraborty.de.rac-1.sayantan-chakraborty.de IN AAAA +
            03-Feb-2010 16:09:11.874 client 192.168.1.3#1031: query: rac-2.sayantan-chakraborty.de.sayantan-chakraborty.de IN AAAA +
            03-Feb-2010 16:09:11.875 client 192.168.1.3#1031: query: rac-2.sayantan-chakraborty.de IN A +
            03-Feb-2010 16:09:20.373 client 192.168.1.2#29298: query: api.mywot.com IN AAAA +
            03-Feb-2010 16:09:20.439 client 192.168.1.2#14382: query: api.mywot.com.localdomain IN AAAA +
            03-Feb-2010 16:09:20.439 client 192.168.1.2#19745: query: api.mywot.com IN A +
            03-Feb-2010 16:10:29.491 client 192.168.1.2#38404: query: googleads.g.doubleclick.net IN AAAA +
            03-Feb-2010 16:10:29.536 client 192.168.1.2#41452: query: googleads.g.doubleclick.net IN A +
            03-Feb-2010 16:10:29.584 client 192.168.1.2#58206: query: googleads.g.doubleclick.net IN A +
            03-Feb-2010 16:10:29.626 client 192.168.1.2#21586: query: pagead2.googlesyndication.com IN AAAA +
            03-Feb-2010 16:10:29.665 client 192.168.1.2#38827: query: pagead2.googlesyndication.com IN A +
            03-Feb-2010 16:10:29.701 client 192.168.1.2#27072: query: pagead2.googlesyndication.com IN A +
            03-Feb-2010 16:10:29.737 client 192.168.1.2#31994: query: safebrowsing.clients.google.com IN AAAA +
            03-Feb-2010 16:10:29.773 client 192.168.1.2#36189: query: safebrowsing.clients.google.com IN A +
            03-Feb-2010 16:10:29.816 client 192.168.1.2#26381: query: safebrowsing.clients.google.com IN A +
            03-Feb-2010 16:11:43.028 client 192.168.1.2#32139: query: 2.1.168.192.in-addr.arpa IN PTR +
            03-Feb-2010 18:07:30.726 client 192.168.1.25#6786: query: rac-2.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:21:34.210 client 192.168.1.25#4964: query: rac2vip.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:21:44.066 client 192.168.1.25#46360: query: rac1vip.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:22:31.443 client 192.168.1.25#44686: query: rac-2.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:22:39.740 client 192.168.1.25#53353: query: rac-1.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:22:55.149 client 192.168.1.25#57401: query: rac2vip.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:28:53.333 client 192.168.1.25#41752: query: rac-scan.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:35:35.278 client 192.168.1.25#30897: query: rac-scan.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:36:23.084 client 192.168.1.25#37050: query: rac1vip.sayantan-chakraborty.de IN A +
            03-Feb-2010 18:36:34.354 client 192.168.1.25#47063: query: rac2vip.sayantan-chakraborty.de IN A +
            03-Feb-2010 21:43:53.016 client 192.168.1.25#27374: query: rac-1.sayantan-chakraborty.de IN A +
            http://www.desiupload.com/show.php/397278_hi.jpeg.html
            http://www.desiupload.com/show.php/397279_network.jpeg.html

            i am getting INS:- 40910 error during installation.
            what to do now?
            • 3. Re: vip resolving
              506787
              the VIP needs to be resolvable (thus name must be resolvable to an IP address). I guess (can not really tell) this is the case. (use ping/dig/nslookup to determine on every host).
              Also, please read the documentation and installation manual carefully. (!!)

              the VIP must be an IP address which is not used (the clusterware brings up the VIP itself)
              • 4. Re: vip resolving
                721050
                hi

                /etc/sysconfig/network-scripts/ifcfg-eth0
                # Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express
                DEVICE=eth0
                BOOTPROTO=none
                HWADDR=00:1d:72:39:3a:e4
                ONBOOT=yes
                TYPE=Ethernet
                USERCTL=no
                IPV6INIT=no
                PEERDNS=no
                IPADDR=192.168.1.3
                NETMASK=255.255.255.0
                GATEWAY=192.168.1.1
                ~                                                                               
                ~                                                                               
                ~                                                                               
                ~                                                                               
                ~                                                                               
                ~                                                                               
                ~                                                                               
                ~                                                                               
                ~                                                                               
                ~                                                                               
                "/etc/sysconfig/network-scripts/ifcfg-eth0" 13L, 275C
                do you think i need to add this to named.conf?
                forwarders { xxx.xxx.xxx.xxx; xxx.xxx.xxx.xxx; }; #IP of upstream ISP nameserver(s)
                     forward only; #rely completely on our upstream nameservers
                do i need any /etc/hosts modification?
                # Do not remove the following line, or various programs
                # that require network functionality will fail.
                127.0.0.1               rac-1.sayantan-chakraborty.de rac-1 localhost.localdomain localhost
                ::1             localhost6.localdomain6 localhost6
                ~                                                         
                the documentation says it looks in dns and hosts file for vip.thats why i am asking?

                ping/dig/nslookuup for rac-2.
                [root@localhost ~]# ping rac-2.sayantan-chakraborty.de.
                PING rac-2.sayantan-chakraborty.de (192.168.1.3) 56(84) bytes of data.
                64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.350 ms
                64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.286 ms
                64 bytes from 192.168.1.3: icmp_seq=3 ttl=64 time=0.264 ms
                64 bytes from 192.168.1.3: icmp_seq=4 ttl=64 time=0.264 ms
                
                [2]+  Stopped                 ping rac-2.sayantan-chakraborty.de.
                [root@localhost ~]# 
                [root@localhost ~]# dig @192.168.1.2 rac-2.sayantan-chakraborty.de
                
                ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> @192.168.1.2 rac-2.sayantan-chakraborty.de
                ; (1 server found)
                ;; global options:  printcmd
                ;; Got answer:
                ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56983
                ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1
                
                ;; QUESTION SECTION:
                ;rac-2.sayantan-chakraborty.de. IN      A
                
                ;; ANSWER SECTION:
                rac-2.sayantan-chakraborty.de. 3600 IN  A       192.168.1.3
                
                ;; AUTHORITY SECTION:
                sayantan-chakraborty.de. 3600   IN      NS      rac-2.sayantan-chakraborty.de.
                sayantan-chakraborty.de. 3600   IN      NS      rac-1.sayantan-chakraborty.de.
                
                ;; ADDITIONAL SECTION:
                rac-1.sayantan-chakraborty.de. 3600 IN  A       192.168.1.2
                
                ;; Query time: 21 msec
                ;; SERVER: 192.168.1.2#53(192.168.1.2)
                ;; WHEN: Thu Feb  4 11:13:37 2010
                ;; MSG SIZE  rcvd: 113
                
                [root@localhost ~]# 
                [root@localhost ~]# nslookup rac-2.sayantan-chakraborty.de
                Server:         192.168.1.2
                Address:        192.168.1.2#53
                
                Name:   rac-2.sayantan-chakraborty.de
                Address: 192.168.1.3
                
                [root@localhost ~]# 
                [root@localhost ~]# nslookup rac-scan.sayantan-chakraborty.de
                Server:         192.168.1.2
                Address:        192.168.1.2#53
                
                Name:   rac-scan.sayantan-chakraborty.de
                Address: 192.168.1.23
                Name:   rac-scan.sayantan-chakraborty.de
                Address: 192.168.1.31
                Name:   rac-scan.sayantan-chakraborty.de
                Address: 192.168.1.45
                dig/nslookup for vip
                [root@localhost ~]# nslookup rac1vip.sayantan-chakraborty.de
                Server:         192.168.1.2
                Address:        192.168.1.2#53
                
                Name:   rac1vip.sayantan-chakraborty.de
                Address: 192.168.1.25
                
                [root@localhost ~]# dig @192.168.1.2 rac1vip.sayantan-chakraborty.de
                
                ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> @192.168.1.2 rac1vip.sayantan-chakraborty.de
                ; (1 server found)
                ;; global options:  printcmd
                ;; Got answer:
                ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28249
                ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
                
                ;; QUESTION SECTION:
                ;rac1vip.sayantan-chakraborty.de. IN    A
                
                ;; ANSWER SECTION:
                rac1vip.sayantan-chakraborty.de. 3600 IN A      192.168.1.25
                
                ;; AUTHORITY SECTION:
                sayantan-chakraborty.de. 3600   IN      NS      rac-1.sayantan-chakraborty.de.
                sayantan-chakraborty.de. 3600   IN      NS      rac-2.sayantan-chakraborty.de.
                
                ;; ADDITIONAL SECTION:
                rac-1.sayantan-chakraborty.de. 3600 IN  A       192.168.1.2
                rac-2.sayantan-chakraborty.de. 3600 IN  A       192.168.1.3
                
                ;; Query time: 0 msec
                ;; SERVER: 192.168.1.2#53(192.168.1.2)
                ;; WHEN: Thu Feb  4 11:16:39 2010
                ;; MSG SIZE  rcvd: 137
                
                [root@localhost ~]# dig @192.168.1.2 rac2vip.sayantan-chakraborty.de
                
                ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> @192.168.1.2 rac2vip.sayantan-chakraborty.de
                ; (1 server found)
                ;; global options:  printcmd
                ;; Got answer:
                ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42106
                ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
                
                ;; QUESTION SECTION:
                ;rac2vip.sayantan-chakraborty.de. IN    A
                
                ;; ANSWER SECTION:
                rac2vip.sayantan-chakraborty.de. 3600 IN A      192.168.1.35
                
                ;; AUTHORITY SECTION:
                sayantan-chakraborty.de. 3600   IN      NS      rac-2.sayantan-chakraborty.de.
                sayantan-chakraborty.de. 3600   IN      NS      rac-1.sayantan-chakraborty.de.
                
                ;; ADDITIONAL SECTION:
                rac-1.sayantan-chakraborty.de. 3600 IN  A       192.168.1.2
                rac-2.sayantan-chakraborty.de. 3600 IN  A       192.168.1.3
                
                ;; Query time: 0 msec
                ;; SERVER: 192.168.1.2#53(192.168.1.2)
                ;; WHEN: Thu Feb  4 11:16:48 2010
                ;; MSG SIZE  rcvd: 137
                
                [root@localhost ~]# 
                [root@localhost ~]# nslookup rac2vip.sayantan-chakraborty.de
                Server:         192.168.1.2
                Address:        192.168.1.2#53
                
                Name:   rac2vip.sayantan-chakraborty.de
                Address: 192.168.1.35
                
                [root@localhost ~]# 
                error screen during grid installation
                http://www.desiupload.com/show.php/397372_man.jpeg.html

                regards
                • 5. Re: vip resolving
                  506787
                  what I meant is the VIP is the ip address of eth0. that is not correct. the vip must be an unused IP address. the clusterware must be able to bring up the ip address itself, without conflicting with an existing up address.
                  • 6. Re: vip resolving
                    721050
                    frits hoogland wrote:
                    what I meant is the VIP is the ip address of eth0. that is not correct. the vip must be an unused IP address. the clusterware must be able to bring up the ip address itself, without conflicting with an existing up address.
                    so i followed http://www.webnms.com/simulator/help/sim_network/netsim_conf_virtual_ip.html
                    [root@rac-1 ~]# ip address show
                    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
                        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
                        inet 127.0.0.1/8 scope host lo
                        inet6 ::1/128 scope host 
                           valid_lft forever preferred_lft forever
                    2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
                        link/ether 00:26:18:59:ee:49 brd ff:ff:ff:ff:ff:ff
                        inet 192.168.181.10/24 brd 192.168.181.255 scope global eth1
                        inet6 fe80::226:18ff:fe59:ee49/64 scope link 
                           valid_lft forever preferred_lft forever
                    3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
                        link/ether 00:00:e8:f7:02:b0 brd ff:ff:ff:ff:ff:ff
                        inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
                        inet6 fe80::200:e8ff:fef7:2b0/64 scope link 
                           valid_lft forever preferred_lft forever
                    4: sit0: <NOARP> mtu 1480 qdisc noop 
                        link/sit 0.0.0.0 brd 0.0.0.0
                    5: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
                        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
                        inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
                        inet6 fe80::200:ff:fe00:0/64 scope link 
                           valid_lft forever preferred_lft forever
                    [root@rac-1 ~]# /sbin/ip addr del 192.168.1.25/24 eth0
                    Error: either "local" is duplicate, or "eth0" is a garbage.
                    [root@rac-1 ~]# /sbin/ip addr del 192.168.1.25/24 eth0
                    and now getting
                    [root@rac-1 ~]# /sbin/ip addr add 192.168.1.25/24 eth0
                    Error: either "local" is duplicate, or "eth0" is a garbage.
                    [root@rac-1 ~]# /sbin/ip addr del 192.168.1.25/24 eth0
                    Error: either "local" is duplicate, or "eth0" is a garbage.
                    [root@rac-1 ~]# 
                    AND during oracle clusterware installation i am getting:
                    Cause - None of the locally defined network interfaces has a subnet matching the SCAN VIP subnet.  Action - Define a public interface with a subnet matching the SCAN VIP or choose a SCAN VIP with a subnet matching the public interface.
                    http://httpd.apache.org/docs/1.3/misc/vif-info.html
                    any suggestion ??

                    regards
                    • 7. Re: vip resolving
                      506787
                      your answer did not respond to what answered.

                      for every RAC node, you need to have two ip addresses setup, one is called the public interface, one is called the private interface.
                      both ip addresses must have a separate ip address and separate subnet.
                      if you use hostnames instead of ip addresses, the hostnames must be resolvable. (you posted a great deal about configuring that, but that is not a problem as far as I see it)

                      you also need to setup a third hostname/ip address, which needs to be in the subnet mask of the public ip address.
                      this ip address may not be the public or private ip address, because the clusterware brings it up itself.
                      • 8. Re: vip resolving
                        721050
                        frits hoogland wrote:
                        your answer did not respond to what answered.

                        for every RAC node, you need to have two ip addresses setup, one is called the public interface, one is called the >private interface.
                        you also need to setup a third hostname/ip address, which needs to be in the subnet mask of the public ip address.
                        this ip address may not be the public or private ip address, because the clusterware brings it up itself.
                        to resolve it i did "ip addr add 192.168.1.25 eth0" which resulted an error what posted in the previous post.
                        "AND during oracle clusterware installation i am getting":
                        Cause - None of the locally defined network interfaces has a subnet matching the SCAN VIP subnet.  Action - Define a public interface with a subnet matching the SCAN VIP or choose a SCAN VIP with a subnet matching the public interface.
                         
                        then i tried to refix it with "ip addr 192.168.1.25/32 eth0" i got an error during this command execution :
                        [root@rac-1 ~]# /sbin/ip addr add 192.168.1.25/24 eth0
                        Error: either "local" is duplicate, or "eth0" is a garbage.
                        [root@rac-1 ~]# /sbin/ip addr del 192.168.1.25/24 eth0
                        Error: either "local" is duplicate, or "eth0" is a garbage.
                        [root@rac-1 ~]# 
                         
                        to re-fix it i tried ifconfig 192.168.1.25/24 eth0:0 " command but it resulted an error: INS:-40910 again.so i am requesting you:
                        can you put some command over here for that?

                        regards
                        • 9. Re: vip resolving
                          661723
                          hi

                          if i am not interrupting.....
                          http://www.cyberciti.biz/tips/howto-configure-linux-virtual-local-area-network-vlan.html

                          probably you are looking for this.but wait for frits to comment

                          HTH

                          [looked like duplication|http://forums.oracle.com/forums/thread.jspa?threadID=1025159&tstart=0]
                          • 10. Re: vip resolving
                            Hans Forbrich
                            Assuming you have 2 or more network cards:

                            1) Which Network card is to be used for Public IP
                            2) What is the IP address assigned to that card (ifconfig eth0)
                            3) Since VIP must be reserved but not assigned, what is the /etc/hosts entry for the VIP
                            (cat /etc/hosts)
                            4) Make sure the VIP is not assigned (ping vip's address MUST fail)
                            • 11. Re: vip resolving
                              721050
                              Hans Forbrich wrote:
                              Assuming you have 2 or more network cards:
                              Exactly two NICs.
                              >
                              1) Which Network card is to be used for Public IP
                              192.168.1.x/24 so i want the VIP as 192.168.1.25/24 eth0.
                              2) What is the IP address assigned to that card (ifconfig eth0)
                              ifconfig -a is already posted.
                              3) Since VIP must be reserved but not assigned, what is the /etc/hosts entry for the VIP
                              ping failing always.
                              (cat /etc/hosts)
                              its also posted.
                              4) Make sure the VIP is not assigned (ping vip's address MUST fail)
                              failing for PING.

                              i am confused abit do i really need /etc/hosts entry as i am using bind,chroot approach to configure DNS?
                              • 12. Re: vip resolving
                                Hans Forbrich
                                dork wrote:
                                i am confused abit do i really need /etc/hosts entry as i am using bind,chroot approach to configure DNS?
                                Yes. MOS note 264847.1 specifically indicates that the VIP address must be in /etc/hosts and also in DNS.

                                In fact, all 3 addresses - public, VIP and private need to be in /etc/hosts as there mseem to assumptions about that in the various check routines.
                                • 13. Re: vip resolving
                                  Hans Forbrich
                                  dork wrote:
                                  Hans Forbrich wrote:
                                  Assuming you have 2 or more network cards:
                                  Exactly two NICs.
                                  1) Which Network card is to be used for Public IP
                                  192.168.1.x/24 so i want the VIP as 192.168.1.25/24 eth0.
                                  2) What is the IP address assigned to that card (ifconfig eth0)
                                  That will end up being eth0:0 and the assignment, start & stop must be under clusterware control.

                                  >
                                  ifconfig -a is already posted.
                                  And could have changed since you are working to resolve your problem.
                                  • 14. Re: vip resolving
                                    506787
                                    it's best to configure networking using
                                    system-config-network
                                    .
                                    first setup the hostnames in /etc/hosts. (just as hans suggests)

                                    You need two ip addresses set in a different subnet mask, and one ip address not set (which the clusterware will bring online) in the subnet mask of the public ip address.

                                    the errormessage you've posted states you've assigned the VIP address in different subnet than you public ip address, which is mandatory. so I suggest to fix that first.
                                    1 2 Previous Next