1 2 Previous Next 18 Replies Latest reply: Jun 11, 2012 2:29 AM by __OUTSIDER___ RSS

    OEL 6.2 network bonding

    __OUTSIDER___
      Hi all,

      I am trying create and test network bonding in OEL6.2 (2.6.32-300.25.1.el6uek.x86_64). OEL6 installed as Oracle VM 3.1.1 Virtual machine.

      Problem is that when I created second bond (bond1) I lost my old (bond0) interface IP address.
      Now all 4 interfaces linked to bond1 and respectively two of them have wrong IPs.

      Please help

      ./thanks

      My confs
      [root@c1n1 ~]# cat /etc/modprobe.d/bonding.conf
      alias bond0 bonding
      alias bond1 bonding
      
      [root@c1n1 ~]# cat  /etc/sysconfig/network-scripts/ifcfg-bond0
      DEVICE=bond0
      IPADDR=199.199.10.11
      NETMASK=255.255.255.0
      ONBOOT=yes
      BOOTPROTO=none
      USERCTL=no
      BONDING_OPTS="miimon=100 mode=balance-rr"
      
      
      [root@c1n1 ~]# cat  /etc/sysconfig/network-scripts/ifcfg-bond1
      DEVICE=bond1
      IPADDR=10.10.10.11
      NETMASK=255.255.255.0
      ONBOOT=yes
      BOOTPROTO=none
      USERCTL=no
      BONDING_OPTS="miimon=100 mode=balance-rr"
      
      [root@c1n1 ~]# cat  /etc/sysconfig/network-scripts/ifcfg-eth0
      DEVICE=eth0
      USERCTL=no
      ONBOOT=yes
      MASTER=bond0
      SLAVE=yes
      BOOTPROTO=none
      HWADDR=00:21:F6:00:00:11
      [root@c1n1 ~]#
      
      
      [root@c1n1 ~]# cat  /etc/sysconfig/network-scripts/ifcfg-eth1
      DEVICE=eth1
      USERCTL=no
      ONBOOT=yes
      MASTER=bond0
      SLAVE=yes
      BOOTPROTO=none
      WADDR=00:21:F6:00:00:01
      [root@c1n1 ~]#
      
      DEVICE=eth2
      USERCTL=no
      ONBOOT=yes
      MASTER=bond1
      SLAVE=yes
      BOOTPROTO=none
      TYPE=Ethernet
      HWADDR=00:21:F6:00:00:0c
      [root@c1n1 ~]#
      
      [root@c1n1 ~]# cat  /etc/sysconfig/network-scripts/ifcfg-eth3
      DEVICE=eth3
      USERCTL=no
      ONBOOT=yes
      MASTER=bond1
      SLAVE=yes
      BOOTPROTO=none
      HWADDR=00:21:F6:00:00:06
      [root@c1n1 ~]#
      [root@c1n1 ~]# ifconfig
      bond0 Link encap:Ethernet HWaddr 00:21:F6:00:00:11
      inet addr:*199.199.10.11* Bcast:199.199.10.255 Mask:255.255.255.0
      inet6 addr: fe80::221:f6ff:fe00:11/64 Scope:Link
      UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
      RX packets:1523 errors:0 dropped:0 overruns:0 frame:0
      TX packets:1505 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:107167 (104.6 KiB) TX bytes:127301 (124.3 KiB)

      bond1 Link encap:Ethernet HWaddr 00:21:F6:00:00:0C
      inet addr:*10.10.10.11* Bcast:10.10.10.255 Mask:255.255.255.0
      inet6 addr: fe80::221:f6ff:fe00:c/64 Scope:Link
      UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
      RX packets:108 errors:0 dropped:0 overruns:0 frame:0
      TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:12087 (11.8 KiB) TX bytes:12115 (11.8 KiB)

      eth0 Link encap:Ethernet HWaddr 00:21:F6:00:00:11
      inet addr:*10.10.10.11* Bcast:10.10.10.255 Mask:255.255.255.0
      UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
      RX packets:757 errors:0 dropped:0 overruns:0 frame:0
      TX packets:760 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:54078 (52.8 KiB) TX bytes:63464 (61.9 KiB)
      Interrupt:5

      eth1 Link encap:Ethernet HWaddr 00:21:F6:00:00:11
      inet addr:*10.10.10.11* Bcast:10.10.10.255 Mask:255.255.255.0
      UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
      RX packets:766 errors:0 dropped:0 overruns:0 frame:0
      TX packets:745 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:53089 (51.8 KiB) TX bytes:63837 (62.3 KiB)
      Interrupt:4

      eth2 Link encap:Ethernet HWaddr 00:21:F6:00:00:0C
      inet addr:*10.10.10.11* Bcast:10.10.10.255 Mask:255.255.255.0
      UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
      RX packets:53 errors:0 dropped:0 overruns:0 frame:0
      TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:5963 (5.8 KiB) TX bytes:6292 (6.1 KiB)
      Interrupt:3

      eth3 Link encap:Ethernet HWaddr 00:21:F6:00:00:0C
      inet addr:*10.10.10.11* Bcast:10.10.10.255 Mask:255.255.255.0
      UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
      RX packets:55 errors:0 dropped:0 overruns:0 frame:0
      TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:6124 (5.9 KiB) TX bytes:5823 (5.6 KiB)
      Interrupt:2
        • 1. Re: OEL 6.2 network bonding
          Catch-22
          Did you copy and paste the information?
          WADDR=00:21:F6:00:00:01
          I'm sure that should rather read HWADDR

          Have you tried to shutdown all interfaces and restart the network?
          • 2. Re: OEL 6.2 network bonding
            __OUTSIDER___
            >

            Thanks Dude for reply.
            Did you copy and paste the information?
            WADDR=00:21:F6:00:00:01
            I am just create HWADDR line for all interfaces according to Oracle VM information.
            I'm sure that should rather read HWADDR

            Have you tried to shutdown all interfaces and restart the network?
            YES
            I even rebooted machine :(


            ./thanks
            • 3. Re: OEL 6.2 network bonding
              __OUTSIDER___
              >
              Did you copy and paste the information?
              WADDR=00:21:F6:00:00:01
              OK I understand. I corrected this mistyping but its no helped.

              Do you know need I add HWADDR lines in bonding interface ?

              ./thanks
              • 4. Re: OEL 6.2 network bonding
                __OUTSIDER___
                I tried to find something here but nothing.
                bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
                Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-bond0 instead
                bonding: bond0: Setting MII monitoring interval to 100.
                bonding: bond0: setting mode to balance-rr (0).
                ADDRCONF(NETDEV_UP): bond0: link is not ready
                bonding: bond0: Adding slave eth0.
                bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
                bonding: bond0: enslaving eth0 as an active interface with an up link.
                ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
                bonding: bond0: Adding slave eth1.
                bonding: bond0: Warning: failed to get speed and duplex from eth1, assumed to be 100Mb/sec and Full.
                bonding: bond0: enslaving eth1 as an active interface with an up link.
                bond0: IPv6 duplicate address fe80::221:f6ff:fe00:11 detected!
                Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-bond1 instead
                bonding: bond1 is being created...
                bonding: bond1: Setting MII monitoring interval to 100.
                bonding: bond1: setting mode to balance-rr (0).
                ADDRCONF(NETDEV_UP): bond1: link is not ready
                bonding: bond1: Adding slave eth2.
                bonding: bond1: Warning: failed to get speed and duplex from eth2, assumed to be 100Mb/sec and Full.
                bonding: bond1: enslaving eth2 as an active interface with an up link.
                ADDRCONF(NETDEV_CHANGE): bond1: link becomes ready
                bonding: bond1: Adding slave eth3.
                bonding: bond1: Warning: failed to get speed and duplex from eth3, assumed to be 100Mb/sec and Full.
                bonding: bond1: enslaving eth3 as an active interface with an up link.
                bond1: IPv6 duplicate address fe80::221:f6ff:fe00:c detected!
                • 5. Re: OEL 6.2 network bonding
                  Catch-22
                  Since this is under OVM, perhaps you should check http://itnewscast.com/chapter-7-oracle-vm-networking-8021q

                  Apparently there are different options required for Xen.
                  • 6. Re: OEL 6.2 network bonding
                    Avi Miller-Oracle
                    __OUTSIDER___ wrote:
                    I am trying create and test network bonding in OEL6.2 (2.6.32-300.25.1.el6uek.x86_64). OEL6 installed as Oracle VM 3.1.1 Virtual machine.
                    You shouldn't be configuring bonding inside a virtual guest: bond at the Dom0/Oracle VM Server level and just use virtual interfaces attached to the guest.
                    • 7. Re: OEL 6.2 network bonding
                      __OUTSIDER___
                      Dude wrote:
                      Since this is under OVM, perhaps you should check http://itnewscast.com/chapter-7-oracle-vm-networking-8021q

                      Apparently there are different options required for Xen.
                      Thank for link but don't you think if bond0 is working bond1 also must work.....?

                      I try to find something about Virtual guest bonding but I found only VM server bonding related
                      information(bare metal).
                      • 8. Re: OEL 6.2 network bonding
                        __OUTSIDER___
                        Avi Miller wrote:
                        You shouldn't be configuring bonding inside a virtual guest: bond at the Dom0/Oracle VM Server level and just use virtual interfaces attached to the guest.
                        Thank Avi for joining.

                        Yes I know but I want just to try how it works. My bond0 is working but not second(bond1).
                        Can you confirm that bonding configuration inside VM guest is differ then physical NIC bonding ?
                        • 9. Re: OEL 6.2 network bonding
                          Avi Miller-Oracle
                          __OUTSIDER___ wrote:
                          Can you confirm that bonding configuration inside VM guest is differ then physical NIC bonding ?
                          There are no physical characteristics to the netfront NIC, so I doubt it would work: the bonding drivers use various hardware manipulation techniques to change the MAC address on-the-fly, etc. If you really want to play with bonding inside a guest, you may need to run a fully hardware-virtualized guest and use the emulated Realtek NICs instead.
                          • 10. Re: OEL 6.2 network bonding
                            __OUTSIDER___
                            Avi Miller wrote:
                            There are no physical characteristics to the netfront NIC, so I doubt it would work: the bonding drivers use various hardware manipulation techniques to change the MAC address on-the-fly, etc. If you really want to play with bonding inside a guest, you may need to run a fully hardware-virtualized guest and use the emulated Realtek NICs instead.
                            Thanks for explanation. Now everything is clear for me except one thing .... why in my case one bond is still working?
                            [root@c1n1 oramedia]# cat /etc/modprobe.d/bonding.conf
                            alias bond0 bonding
                            
                            
                            [root@c1n1 oramedia]# cat  /etc/sysconfig/network-scripts/ifcfg-bond0
                            DEVICE=bond0
                            IPADDR=199.199.10.11
                            NETMASK=255.255.255.0
                            ONBOOT=yes
                            BOOTPROTO=none
                            USERCTL=no
                            BONDING_OPTS="miimon=100 mode=balance-rr"
                            
                            
                            
                            [root@c1n1 oramedia]# cat  /etc/sysconfig/network-scripts/ifcfg-eth0
                            DEVICE=eth0
                            USERCTL=no
                            ONBOOT=yes
                            MASTER=bond0
                            SLAVE=yes
                            BOOTPROTO=none
                            HWADDR=00:21:F6:00:00:11
                            
                            [root@c1n1 oramedia]# cat  /etc/sysconfig/network-scripts/ifcfg-eth1
                            DEVICE=eth1
                            USERCTL=no
                            ONBOOT=yes
                            MASTER=bond0
                            SLAVE=yes
                            BOOTPROTO=none
                            HWADDR=00:21:F6:00:00:01
                            
                            
                            bond0     Link encap:Ethernet  HWaddr 00:21:F6:00:00:11
                                      inet addr:199.199.10.11  Bcast:199.199.10.255  Mask:255.255.255.0
                                      inet6 addr: fe80::221:f6ff:fe00:11/64 Scope:Link
                                      UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
                                      RX packets:1598 errors:0 dropped:0 overruns:0 frame:0
                                      TX packets:1359 errors:0 dropped:0 overruns:0 carrier:0
                                      collisions:0 txqueuelen:0
                                      RX bytes:114369 (111.6 KiB)  TX bytes:123828 (120.9 KiB)
                            
                            eth0      Link encap:Ethernet  HWaddr 00:21:F6:00:00:11
                                      inet addr:199.199.10.11  Bcast:199.199.10.255  Mask:255.255.255.0
                                      UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
                                      RX packets:806 errors:0 dropped:0 overruns:0 frame:0
                                      TX packets:688 errors:0 dropped:0 overruns:0 carrier:0
                                      collisions:0 txqueuelen:1000
                                      RX bytes:58041 (56.6 KiB)  TX bytes:62192 (60.7 KiB)
                                      Interrupt:5
                            
                            eth1      Link encap:Ethernet  HWaddr 00:21:F6:00:00:11
                                      inet addr:199.199.10.11  Bcast:199.199.10.255  Mask:255.255.255.0
                                      UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
                                      RX packets:792 errors:0 dropped:0 overruns:0 frame:0
                                      TX packets:671 errors:0 dropped:0 overruns:0 carrier:0
                                      collisions:0 txqueuelen:1000
                                      RX bytes:56328 (55.0 KiB)  TX bytes:61636 (60.1 KiB)
                                      Interrupt:4
                            • 11. Re: OEL 6.2 network bonding
                              Catch-22
                              Obviously your bonding configuration did not work and you have received the answer why. If you are just playing around, well ok, but what else are you going to achieve with your setup attempt?
                              • 12. Re: OEL 6.2 network bonding
                                __OUTSIDER___
                                Dude wrote:
                                How do you really know if things are working and won't have an adverse affect now or later, or in combination with something else? Obviously your bonding configuration did not work and you have received the answer why. If you are just playing around, well ok, but what else are you going to achieve with your setup attempt?
                                Thanks.
                                Well ... I will try to explain. I am planning installation of G.I. 11r2 ,RAC + Data Guard(MAA). I have tested my old G.I. with RACcheck tool and I have list of recommendations. So regarding that list I need to configure network bonding for Public and Privat interconnect networks.
                                Do you know which is best method to test bonding configuration ?
                                • 13. Re: OEL 6.2 network bonding
                                  Catch-22
                                  If you need to setup network bonding I suggest to set it up according to the documentation.

                                  Network bonding obviously relies on physical network interfaces. So apparently under OVM you can either use virtual interfaces using hardware virtualization, or configure bonding on Dom0. I think setting up network bonding with virtual interfaces does not really make sense and cannot be really tested because of a single point of failure or resource. The Oracle Virtualization forum should be the appropriate forum to discuss such questions.
                                  • 14. Re: OEL 6.2 network bonding
                                    __OUTSIDER___
                                    Dear Dude , Avi thanks for your time and for you answers.
                                    This forum is a great place because guys like you.
                                    ./thanks
                                    1 2 Previous Next