OEL 6.2 network bonding

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

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

Similar Messages

  • Network bonding

    Hello,
    I have two connections. One wireless (wlan0) and one wired (eth0).
    They are a bit slow, so I thought that I could use both to have a faster internet connection (this is load-balancing, isn't it?).
    Is mode balance-tlb right for me?
    Also a problem:
    $ netcfg bonded
    :: bonded up [ BUSY ]
    > Slave eth0 is down and timeout reached
    > Slave wlan0 is down and timeout reached
    > No slaves up, aborting
    configs:
    /etc/network.d/bonded:
    #CONNECTION="bond"
    #DESCRIPTION='Bond Interface'
    #INTERFACE='bond0'
    #IP='static'
    #ADDR="10.0.0.1"
    #NETMASK="255.0.0.0"
    #SLAVE_INTERFACES=("eth0" "wlan0")
    #SKIPNOCARRIER="yes"
    CONNECTION="bonding"
    INTERFACE="bond0"
    SLAVES="eth0 wlan0"
    IP="dhcp"
    DHCP_TIMEOUT=10
    SLAVE_TIMEOUT=5
    /etc/network.d/home:
    CONNECTION='ethernet'
    DESCRIPTION='A basic static ethernet connection using iproute'
    INTERFACE='eth0'
    IP='static'
    ADDR='192.168.1.95'
    #ROUTES=('192.168.0.0/24 via 192.168.1.2')
    GATEWAY='192.168.1.1'
    DNS=('8.8.8.8', '8.8.4.4')
    ## For IPv6 autoconfiguration
    #IP6=stateless
    ## For IPv6 static address configuration
    #IP6='static'
    #ADDR6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
    #ROUTES6=('abcd::1234')
    #GATEWAY6='1234:0:123::abcd'
    /etc/network.d/wifi:
    CONNECTION='wireless'
    DESCRIPTION='A simple WEP encrypted wireless connection'
    INTERFACE='wlan0'
    SECURITY='wep'
    ESSID='wifi'
    KEY='abcd'
    IP='dhcp'
    # Uncomment this if your ssid is hidden
    #HIDDEN=yes
    ## Uncomment if you are using an ad-hoc connection
    #ADHOC=1
    #IP="static"
    #IFOPTS="0.0.0.0"
    #PRE_UP="ifenslave bond0 wlan0"
    #PRE_DOWN="ifenslave -d bond0 wlan0"
    /etc/modprobe.d/bonding.conf:
    options bonding mode=balance-tlb
    options bonding miimon=100
    options bonding primary=eth0
    /etc/conf.d/bonding:
    empty (only comments)
    /etc/conf.d/netcfg:
    # Enable these netcfg profiles at boot time.
    # - prefix an entry with a '@' to background its startup
    # - set to 'last' to restore the profiles running at the last shutdown
    # - set to 'menu' to present a menu (requires the dialog package)
    # Network profiles are found in /etc/network.d
    #NETWORKS=(last)
    NETWORKS=(bonded wifi)
    # Specify the name of your wired interface for net-auto-wired
    #WIRED_INTERFACE="eth0"
    # Specify the name of your wireless interface for net-auto-wireless
    #WIRELESS_INTERFACE="wlan0"
    # Array of profiles that may be started by net-auto-wireless.
    # When not specified, all wireless profiles are considered.
    #AUTO_PROFILES=("profile1" "profile2")
    NOTE: I use systemd
    resources to set all these up: http://www.codekoala.com/blog/2012/bond … rch-linux/, https://wiki.archlinux.org/index.php/Co … ng_Network
    please tell me if you want an y more info.
    Thank you in advance!
    Last edited by ttouch (2012-10-28 14:11:35)

    I created a script with the output of your script as I get errors when running it as root. Here is the script:
    #!/bin/bash
    /usr/sbin/ip route flush table ISP1 2>/dev/null
    /usr/sbin/ip rule del fwmark 101 table ISP1 2>/dev/null
    /usr/sbin/ip route add table ISP1 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.31 metric 202 2>/dev/null
    /usr/sbin/ip route add table ISP1 default via 192.168.178.1 dev eth0
    /usr/sbin/ip rule add fwmark 101 table ISP1
    /usr/sbin/ip route flush table ISP2 2>/dev/null
    /usr/sbin/ip rule del fwmark 102 table ISP2 2>/dev/null
    /usr/sbin/ip route add table ISP2 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.31 metric 202 2>/dev/null
    /usr/sbin/ip route add table ISP2 default via 192.168.1.1 dev wlan0
    /usr/sbin/ip rule add fwmark 102 table ISP2
    /usr/sbin/iptables -t mangle -F
    /usr/sbin/iptables -t mangle -X
    /usr/sbin/iptables -t mangle -N MARK-gw1
    /usr/sbin/iptables -t mangle -A MARK-gw1 -m comment --comment 'send via 192.168.178.1' -j MARK --set-mark 101
    /usr/sbin/iptables -t mangle -A MARK-gw1 -j CONNMARK --save-mark
    /usr/sbin/iptables -t mangle -A MARK-gw1 -j RETURN
    /usr/sbin/iptables -t mangle -N MARK-gw2
    /usr/sbin/iptables -t mangle -A MARK-gw2 -m comment --comment 'send via 192.168.1.1' -j MARK --set-mark 102
    /usr/sbin/iptables -t mangle -A MARK-gw2 -j CONNMARK --save-mark
    /usr/sbin/iptables -t mangle -A MARK-gw2 -j RETURN
    /usr/sbin/iptables -t mangle -A PREROUTING -j CONNMARK --restore-mark
    /usr/sbin/iptables -t mangle -A PREROUTING -m comment --comment "this stream is already marked; escape early" -m mark ! --mark 0 -j ACCEPT
    /usr/sbin/iptables -t mangle -A PREROUTING -m comment --comment 'prevent asynchronous routing' -i eth0 -m state --state NEW -j MARK-gw1
    /usr/sbin/iptables -t mangle -A PREROUTING -m comment --comment 'prevent asynchronous routing' -i wlan0 -m state --state NEW -j MARK-gw2
    /usr/sbin/iptables -t mangle -N DEF_POL
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'default balancing' -p tcp -m state --state ESTABLISHED,RELATED -j CONNMARK --restore-mark
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'default balancing' -p udp -m state --state ESTABLISHED,RELATED -j CONNMARK --restore-mark
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'balance gw1 tcp' -m mark --mark 0 -p tcp -m state --state NEW -m statistic --mode nth --every 2 --packet 0 -j MARK-gw1
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'balance gw1 tcp' -m mark --mark 0 -p tcp -m state --state NEW -m statistic --mode nth --every 2 --packet 0 -j ACCEPT
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'balance gw2 tcp' -m mark --mark 0 -p tcp -m state --state NEW -m statistic --mode nth --every 2 --packet 1 -j MARK-gw2
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'balance gw2 tcp' -m mark --mark 0 -p tcp -m state --state NEW -m statistic --mode nth --every 2 --packet 1 -j ACCEPT
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'balance gw1 udp' -m mark --mark 0 -p udp -m state --state NEW -m statistic --mode nth --every 2 --packet 0 -j MARK-gw1
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'balance gw1 udp' -m mark --mark 0 -p udp -m state --state NEW -m statistic --mode nth --every 2 --packet 0 -j ACCEPT
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'balance gw2 udp' -m mark --mark 0 -p udp -m state --state NEW -m statistic --mode nth --every 2 --packet 1 -j MARK-gw2
    /usr/sbin/iptables -t mangle -A DEF_POL -m comment --comment 'balance gw2 udp' -m mark --mark 0 -p udp -m state --state NEW -m statistic --mode nth --every 2 --packet 1 -j ACCEPT
    /usr/sbin/iptables -t nat -A POSTROUTING -m comment --comment 'snat outbound eth0' -o eth0 -s 192.168.0.0/16 -m mark --mark 101 -j SNAT --to-source 192.168.178.95
    /usr/sbin/iptables -t nat -A POSTROUTING -m comment --comment 'snat outbound wlan0' -o wlan0 -s 192.168.0.0/16 -m mark --mark 102 -j SNAT --to-source 192.168.1.95
    /usr/sbin/ip route flush cache
    And here is the output:
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.
    WARNING: The state match is obsolete. Use conntrack instead.

  • OEL 5.2 network configuration

    Hi:
    I am new to linux and I have a PC( Acer Veriton X275) . I have installed OEL 5.2 on it. but I cannot connect to the internet. I already create a network from my Network Configuration interface. but its Inactive. once I press the Activate button I do have this error :
    /sbin/ifup: line 17: ./network-functions: No such file or directory
    /sbin/ifup: line 28:need_config: command not found
    /sbin/ifup: configuration for eth0 not found.
    usage: ifup<device name>
    I am using cable connection to the router and it's using the DHCP ( My boss told me the connection is DHCP , I'm not sure about it)..
    Do you have any solution for this problem?
    Thanks in advanced
    sincerely
    farshad zamani
    Edited by: 922700 on Apr 2, 2012 6:59 PM

    ok, also I got this comment from another of my friend. but I want to use the oracle database 11g R2 on linux. As I read the guideline for the database its support the Oracle Linux 5 updat 2. I scared whether I format the OS and the network problem solved but I get another problem with oracle db. do you know oracle db is supported by Oracle linux 6.2 or 5.8 or not?
    anyway thanks for your reply

  • OEL 6.0 network installation

    Why Oracle doesn't have CD image for network installation?
    We have old IBM servers where still only CD drive.
    And can't to boot from USB sticks.
    But same RHEL distros have it!

    Perhaps you will find the following interesting.
    Oracle Linux 6 - boot.iso file.
    http://forums.oracle.com/forums/thread.jspa?messageID=9406260
    http://www.linuxforums.org/forum/red-hat-fedora-linux/173121-how-install-rhel6-via-pxe-boot.html

  • X4500 and network bonding

    Dear sirs,
    in past few days I've been in touch to older x4500. I runs SUSE and we have two RAID5 arrays on it.
    My problem is that I'm not able to get more performance that 2 Gbps (gigabits per second). I've looked into documentation and found some notice that is confusing to me and my colleague (as we aren't native speakers).
    I read: There are two chips each one supports 1 Gbps on two interfaces (means 2 Gbps in four RJ-45 holes)
    My colleague read: There are two cards with four chips each one supports 1 Gbps (means 4 Gbps in four RJ-45 holes)
    Before starting hard digging to our kernel and modules I'd like to have confirmed that x4500 supports more than 2 Gbps on intergrated LAN controllers.
    Bond is set to 802.3ad (configured well on our CISCO 6500 side) and load is balanced on basis of L4 (IP + port).
    Any help is really appreciated.
    M

    IIRC (I haven't checked recently), Mac OS X supports bonding, but uses the standard LACP link aggregation in which all links are simultaneously active (traffic is balanced across all active links).
    This usually (but not always) is not possible across multiple switches.
    If you want an active/standby port configuration then you may have to roll your own - a simple script that ifconfig up's an interface when the primary fails would be relatively easy to construct.

  • Network bond (link aggregate) failing

    I have a D-Link DGS-1224T. I have set up a trunk between ports 5 and 6. I have connected cat6 cables between my macpro and those ports. I have gone in and successfully created a bond and given it manual IP settings.
    It works great for a little while, then it fails saying that there is no partner. If I recreate, again it works for a short period of time.
    Any thoughts?

    There are a lot of factors, look at N for wireless. Even IEEE has some issues after something is released. FYI: It was originally called IEEE 802.1AX-2008 and before that it was IEEE 802.3-2005 Ethernet. So depending on which format Dlink used they are not incorrect. I suspect you thought it did as did this person:
    http://discussions.apple.com/thread.jspa?threadID=361809
    Again this is not a manufacture issue.

  • How to create network teaming or channel bond

    hi
    how to create bond0 and bon1 for RAC installation between two nodes??
    node1
    [grid1@rac-1 ~]$ /sbin/ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:00:E8:F7:02:B0 
              inet addr:192.168.1.2  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:20571 errors:0 dropped:0 overruns:0 frame:0
              TX packets:19190 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:10508240 (10.0 MiB)  TX bytes:9218545 (8.7 MiB)
              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.63  Mask:255.255.255.192
              inet6 addr: fe80::226:18ff:fe59:ee49/64 Scope:Link
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:49 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:23
              collisions:0 txqueuelen:1000
              RX bytes:18391 (17.9 KiB)  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:16332 errors:0 dropped:0 overruns:0 frame:0
              TX packets:16332 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:16738217 (15.9 MiB)  TX bytes:16738217 (15.9 MiB)
    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:47 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 b)  TX bytes:10062 (9.8 KiB)
    [grid1@rac-1 ~]$ node2
    [root@rac-2 ~]# ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:1D:72:39:3A:E4 
              inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::21d:72ff:fe39:3ae4/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:6765 errors:0 dropped:0 overruns:0 frame:0
              TX packets:7040 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:3922791 (3.7 MiB)  TX bytes:1079834 (1.0 MiB)
              Interrupt:169
    eth2      Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
              inet addr:192.168.181.20  Bcast:192.168.181.63  Mask:255.255.255.192
              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:24 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:7029 (6.8 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:4970 errors:0 dropped:0 overruns:0 frame:0
              TX packets:4970 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:7648305 (7.2 MiB)  TX bytes:7648305 (7.2 MiB)
    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:54 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 b)  TX bytes:10706 (10.4 KiB)
    [root@rac-2 ~]# ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:1D:72:39:3A:E4 
              inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::21d:72ff:fe39:3ae4/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:6767 errors:0 dropped:0 overruns:0 frame:0
              TX packets:7044 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:3923027 (3.7 MiB)  TX bytes:1080210 (1.0 MiB)
              Interrupt:169
    eth2      Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
              inet addr:192.168.181.20  Bcast:192.168.181.63  Mask:255.255.255.192
              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:37 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:9982 (9.7 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:4970 errors:0 dropped:0 overruns:0 frame:0
              TX packets:4970 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:7648305 (7.2 MiB)  TX bytes:7648305 (7.2 MiB)
    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:54 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 b)  TX bytes:10706 (10.4 KiB)
    [root@rac-2 ~]# i have done till now....
    Configure Network Bonding
    In /etc/modprobe.conf add line:
    alias bond0 bonding
    alias bond1 bonding
    options bonding miimon=100 mode=1 max-bonds=2
    (“mode=1? means active/passive failover… see “bonding.txt” in kernel sources for more options)
    /etc/sysconfig/network-scripts/ifcfg-bond0 looks like:
    DEVICE=bond0
    BOOTPROTO=none
    ONBOOT=yes
    NETWORK=192.168.181.10
    NETMASK=255.255.255.192
    IPADDR=192.168.181.20
    USERCTL=no
    /etc/sysconfig/network-scripts/ifcfg-eth0 looks like:
    DEVICE=eth0
    BOOTPROTO=none
    ONBOOT=yes
    MASTER=bond0
    SLAVE=yes
    USERCTL=yes1)what to do get my access to adsl modem?
    2)what to do on node2?
    i am facing some error when i am installing clusterware bcz the interface names are different in each node.and public and private ip NICs are in different order.
    will this bonding solute out this issue?
    regards
    Edited by: you on Apr 25, 2010 2:00 AM
    following the steps from here(but its done on vm-ware):
    http://blog.ronnyegner-consulting.de/2009/09/14/oracle-11g-release-2-install-guide-%E2%80%93-grid-infrastructure-installation/

    Why do you want to use bonding? If this is not a real RAC, what do you want to achieve by bonding?
    I do not see a dedicated Interconnect interface. Node 1 has NIC eth1 and node 2 has NIC eth2. One of the basics for RAC is to have the same configuration on each node. So if node 1 uses eth1 for public/virtual/private networking, then so should every other node in the cluster.
    If you bond eth0 and eth1, then what do you want to use for your Interconnect? The same bond0 interface that is now used for your RAC's public and virtual interface configuration?
    Make sure you understand the basic requirements for a RAC configuration. Make sure you adhere to these - even in a virtualised environment.

  • Oracle RAC HAIP vs network interface bonding

    Hi,
    Oracle intruduced new feature called HAIP (11gR2 Grid Infrastructure Redundant Interconnect and ora.cluster_interconnect.haip [ID 1210883.1] ) in Oracle 11.2.0.2 or later. Oracle GI natively supports HAIP so that user does not need to configure Interconnect network interface bonding anymore.
    It seems to me that HAIP will provide better performance than network bonding. Using HAIP, you can have up to four interconnect at work at same time whereas bonding really present as one interconnect IP (ofcause you can have two bondings configured, but still is 1/2 of what HAIP can potentially up to).
    Any thought on this?

    I have implemented this at my site on a two node RAC.
    We did test the same by bringing the newly added interfaces down and the failover did happen as expected.
    I personally think that OS bonding will be better considering the number of bugs we run into as when the complexity and involvement of Oracle features increases.
    Not saying that Oracle is unreliable, but just a personal opinion.
    There is already a situation, you may face, wherein after the failover (and failback following the failover) the IPs returned are not correct due to ARP caching if the IPs fall under same network.
    This can be avoided by using proven OS bonding (not that I'm aware of any issues with OS bonding :) ).

  • OS level load balancing in OEL

    Hi,
    Would like to know if we can do OS level load balancing with OEL?
    I know in Windows there is Network Load Balancing NLB, that would do this, so I am hoping is there something similar in OEL?
    Thanks.

    Optimus prime wrote:
    Would like to know if we can do OS level load balancing with OEL?Any kernel automatically "+load balances+" processing across the resources (e.g. CPUs) available to the kernel. The 2.6 kernel uses the Completely Fair Scheduler
    I know in Windows there is Network Load Balancing NLB, that would do this, so I am hoping is there something similar in OEL?Kind of. There are a number of clustering options for Linux. Including commercial products like Oracle Grid.
    I think the one of the oldest (and well known) Linux clustering s/w projects is Beowulf.
    For networking specifically (comparing it with what I read in Microsoft's FAQ for NLB) is Linux Virtual Server. Quote:
    "<i>The Linux Virtual Server as an advanced load balancing solution can be used to build highly scalable and highly available network services, such as scalable web, cache, mail, ftp, media and VoIP services.</i>"
    There are also other options - such a network devices (in addition to standard switches and routers) that specifically provides load balancing for networking. Though personally, I did not like this approach much for Oracle RAC and we rolled our own load balancing using NAT and iptables.
    Bonding, as mentioned above, is one of many technical considerations when implementing a load balancer. This is (in my experience) primarily for high availability - and provides redundant paths from the server to a resource. Does not need to be IP based - it can be Infiniband based too (e.g. like used by Oracle Database Machine for redundant storage fabric paths to the Exadata Storage Server).
    Typically 2 separate interfaces/dual ports will be wired into separate switches that in turn will be wired into the greater network or storage system or whatever. This is then bonded on the server as a single logical interface. If an interface, port, cable or even switch fail, that logical interface still have a secondary path providing full connectivity. Bonding is discussed at http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding.
    This is however a very low level of dealing with load balancing (and redundancy). It alone should not be considered as a load balancing solution.

  • Network bridging two cable connections. Worth it?

    I tend to be a bit (okay excessively) power hungry. My apartment complex provides a free shared wireless cable connection. I found it to be not reliable with uptime and was forced to get a dedicated cable line for myself.
    Then I had this thought: when there are times when this wireless and free connection is up and running, would it be worth it to bridge the two connections on my desktop? One would be wired, the other wireless. I haven't yet purchased the wireless card since I'd like some input on this first. Both are cable connections at around 6 mbps (Comcast). I'm fairly savvy with networks however not so much on this concept of bridging in home computing. I use the Internet for large downloads, FTP, SSH, and web design, and I'm just power hungry , so I'm curious what the bandwidth and speed increases would be on this.
    My desktop is very powerful and new, if that were to at all be a concern. Any thoughts, experiences, or input on this?
    Last edited by jskier (2007-08-15 12:22:37)

    Lone_Wolf wrote:
    It sounds like you want to combine both physical nics into 1 virtual, this is called bonding.
    Download the kernel sources and check Documentation/networking/bonding.txt .
    I've done a bit of searching and it seems that downloading large files , ftp and such don't benefit from this as they only can make one connection.
    Everyhting that uses multiple connections like p2p should benefit from it.
    If you're going to use this, you should consider installing a downloadmanager like prozilla or aria / aria2.
    Hmm, me thinks I'll play around with it, thanks!

  • Oracle VM 3.1.1 Manager: Configuraing NIC Bonding?

    Each of the two OVM 3.1.1 servers in the OVMM 3.1.1 server pool has three Gigabit Ethernet NIC's:
    <ol>
    <li>One for the Management + VM + Heartbeat Networks (eth0) and
    <li>The other two (eth1 + eth2) should be bonded for redundancy and performance and connected to the Live Migration + Storage Networks.
    </ol>
    However, OVMM 3.1.1 doesn't seem to have the ability to configure the bonding for NIC's. Am I overlooking something?
    Eric Pretorious
    Truckee, CA

    Refer to the Oracle VM User's Guide for Release 3.1.1:
    <li>Chapter 5.4, Network Bonding discusses bonding Management interfaces.
    <li>Chapter 5.8, Managing Bonded Interfaces discusses bonding non-Management interfaces.
    Eric Pretorious
    Truckee, CA
    REFERENCE
    http://docs.oracle.com/cd/E27300_01/E27309/html/vmusg-network-bonding.html
    http://docs.oracle.com/cd/E27300_01/E27309/html/vmusg-network-bondintfce.html

  • Help with netowork bonding

    I need help... i had the network bond setup properly until the last update of netcfg: Since then, i cannot start the bonded interface: It gives an error saying that eth0 and eth1 are down and cannot make the bonding... I tried to fix it myself but failed to.... someone can give me a hand? The wiki is outdated because the configuration from /etc/rc.conf on this matter should be commented and configured somewhere else....
    EDIT: Sorry, i kind of panicked... i will collect all the info i can to ellaborate a bit more the case and post an answer.... BWT.... i had to FORCE the update of netcfg because while installing it was complaining that /etc/network.d/examples/bonding already existed....
    As said... i will post back with more info.... but basically, when i try to bring the bonding profile up, bonding eth0 and eth1, /etc/rc.d/network-profiles complains that those interfaces are down.....
    Last edited by Xi0N (2012-05-31 15:21:40)

    Ok, the setup is as follows:
    De-activated network daemon and using net-profiles daemon in /etc/rc.conf
    Added the bonding module in /etc/rc.conf
    Then, I created a profile under /etc/network.d/bonded
    CONNECTION="bonding"
    INTERFACE="bond0"
    SLAVES="eth0 eth1"
    IP="static"
    ADDR="192.168.1.245"
    GATEWAY="192.168.1.155"
    DNS=("192.168.1.2")
    /etc/conf.d/netcfg has only one line enabled:
    NETWORKS=(bonded)
    The other ones are commented out
    If I run /etc/rc.d/net-profiles start, i get the message:
    bonded up
    > Slave eth0 is down and timeout reached
    > Slave eth1 is down and timeout reached
    > No slaves up, aborting
    > No profile Started
    That profile used to work until the upgrade.......... if any more info is needed, ask me and i will post it ASAP...
    Last edited by Xi0N (2012-05-31 15:41:23)

  • Bonding in oracle vm

    I created a bonding interface as described in metalink article: Enabling Network Bonding in Oracle VM for x86 [ID 738269.1]
    Question:
    brctl show is showing that eth0 was replaced by bond0 --> thats fine.
    But I created my brigde interface with interfaces eth0 and eth4
    But brctl show is still showing interface for xen bridge xenbr4 is eth4.
    Shouldnt that be modified to xenbr0 as well ?

    Chris,
    The metalink OVM networking notes are a little rough and incomplete, please check your configuration against http://itnewscast.com/chapter-7-oracle-vm-networking-8021q
    I'm sure the link will assist.
    Respectfully,
    Roddy

  • Recommendations for XenServer network configuration on B200M2

    We are just starting a XenApp / XenDesktop / VDI project at our company.  I'm very familiar with VMware as that is the hypervisor we primarily use on UCS.  I'll be using XenServer for this project though as the licensing comes with the Citrix licensing.  Does anybody have a recommended configuration for the nics in a XenServer running on UCS B200M2's.  The adapters in the B200M2's are the M81KR's so I was going to setup them up similar to how I setup and ESXi server.
    That would be the following:
    Management network (this would use the same native vlan that I use for the management network of my ESXi hosts)
    1 nic on fabric A that doesn't failover for the management network (bonded with nic listed below)
    1 nic on fabric B that doesn't failover for the management network (bonded with nic listed above)
    XenMotion (this would use the same native vlan that I use for VMotion in VMware)
    1 nic on fabric B that can failover to fabric A
    Guest / VM Network (this I would use vlan tagging to add the appropriate networks for my desktops)
    1 nic on fabric A that doesn't failover for guest / vm network connectivity (bonded with nic listed below)
    1 nic on fabric B that doesn't failover for guest / vm network connectivity (bonded with nic listed above)
    Could somebody offere some suggestions / recommendations on how they have setup there XenServers in UCS for VDI / XenDesktop?

    Hey Russ, I have deployed XenServer on UCS a lot and here is our standard config that has worked for my customers.
    2 vNICs for management, 1 on Fabric A and 1 on Fabric B
    2 vNICs for VM traffic, 1 on Fabric A and 1 on Fabric B
    If using IP storage then 2 additional vNIC for that, 1 on Fabric A and 1 on Fabric B
    2 vHBAs for FC SAN, 1 on Fabric A and 1 on Fabric B
    Make sure you have a BIOS policy that disables all of the Intel C-States

  • Exadata network freeze

    I have a layer 2 problem (network looping) in my network some days ago and this problem was solved when I removed all exadata data connection from my external network switches. Somebody have similar problem here ?

    This sounds like a misconfigured active-active bonding configuration. With an active-active bond, both the switch and the database server must have link aggregation properly configured on the right ports, unlike active-passive bonding where no switch configuration is required.
    You can test this by disabling bonding in your network configuration, and seeing if your network loop goes away.
    There's some brief network channel bonding documentation in chapter 2 of the Exadata Owner's Guide. The official (if somewhat technical) documentation would be in the Linux kernel's bonding.txt though: https://www.kernel.org/doc/Documentation/networking/bonding.txt
    Marc

Maybe you are looking for