Find the answer to your Linux question:
Results 1 to 2 of 2
Hi, I have installed Centos 6.2 in IBM X 3610 server with two Ethernet ports. I have bonded the ethernet ports and the output as folows: Every 0.1s: cat /proc/net/bonding/bond0 ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jan 2013
    Posts
    32

    Post IP address clash issue in network


    Hi,

    I have installed Centos 6.2 in IBM X 3610 server with two Ethernet ports. I have bonded the ethernet ports and the output as folows:


    Every 0.1s: cat /proc/net/bonding/bond0 Fri Jun 21 15:31:39 2013

    Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

    Bonding Mode: fault-tolerance (active-backup)
    Primary Slave: None
    Currently Active Slave: eth0
    MII Status: up
    MII Polling Interval (ms): 100
    Up Delay (ms): 0
    Down Delay (ms): 0

    Slave Interface: eth0
    MII Status: up
    Speed: 100 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 00:21:5e:38:4b:f1
    Slave queue ID: 0

    Slave Interface: eth1
    MII Status: up
    Speed: 100 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 00:21:5e:38:4b:f0
    Slave queue ID: 0


    whenever I restart network service it gives the following error:

    Shutting down interface bond0: [ OK ]
    Shutting down loopback interface: [ OK ]
    Bringing up loopback interface: [ OK ]
    bringing up bond0 [ failed ]
    error: someother host already uses address 10.20.79.101

    If I restart the server and restart the service it's throwing the same error. But When I unplug the cable, restart the service{lo & bond0 ok} , am not getting the error and plug the cable back its pinging.


    dmesg output
    Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
    bonding: bond0 is being created...
    bonding: cannot add bond bond0; already exists
    bonding: Bond creation failed.
    bonding: bond0: setting mode to active-backup (1).
    bonding: bond0: Setting MII monitoring interval to 100.
    ADDRCONF(NETDEV_UP): bond0: link is not ready
    bonding: bond0: Adding slave eth0.
    alloc irq_desc for 24 on node -1
    alloc kstat_irqs on node -1
    tg3 0000:08:00.0: irq 24 for MSI/MSI-X
    bonding: bond0: enslaving eth0 as a backup interface with a down link.
    bonding: bond0: Adding slave eth1.
    alloc irq_desc for 25 on node -1
    alloc kstat_irqs on node -1
    tg3 0000:09:00.0: irq 25 for MSI/MSI-X
    bonding: bond0: enslaving eth1 as a backup interface with a down link.
    tg3 0000:08:00.0: eth0: Link is up at 100 Mbps, full duplex
    tg3 0000:08:00.0: eth0: Flow control is on for TX and on for RX
    tg3 0000:09:00.0: eth1: Link is up at 100 Mbps, full duplex
    tg3 0000:09:00.0: eth1: Flow control is on for TX and on for RX
    bond0: link status definitely up for interface eth0, 100 Mbps full duplex.
    bonding: bond0: making interface eth0 the new active one.
    bonding: bond0: first active interface up!
    bond0: link status definitely up for interface eth1, 100 Mbps full duplex.
    ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    bond0: no IPv6 routers present
    readahead-collector: starting delayed service auditd
    readahead-collector: sorting
    readahead-collector: finished
    tg3 0000:08:00.0: eth0: Link is down
    bonding: bond0: link status definitely down for interface eth0, disabling it
    bonding: bond0: making interface eth1 the new active one.
    tg3 0000:09:00.0: eth1: Link is down
    bonding: bond0: link status definitely down for interface eth1, disabling it
    bonding: bond0: now running without any active interface !
    bonding: bond0: Removing slave eth0
    bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:21:5e:38:4b:f1 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
    bonding: bond0: releasing backup interface eth0
    tg3 0000:08:00.0: PME# enabled
    bonding: bond0: Removing slave eth1
    bonding: bond0: releasing backup interface eth1
    tg3 0000:09:00.0: PME# enabled
    lo: Disabled Privacy Extensions
    bonding: bond0: setting mode to active-backup (1).
    bonding: bond0: Setting MII monitoring interval to 100.
    ADDRCONF(NETDEV_UP): bond0: link is not ready
    bonding: bond0: Adding slave eth0.
    tg3 0000:08:00.0: irq 24 for MSI/MSI-X
    bonding: bond0: enslaving eth0 as a backup interface with a down link.
    bonding: bond0: Adding slave eth1.
    tg3 0000:09:00.0: irq 25 for MSI/MSI-X
    bonding: bond0: enslaving eth1 as a backup interface with a down link.
    tg3 0000:08:00.0: eth0: Link is up at 100 Mbps, full duplex
    tg3 0000:08:00.0: eth0: Flow control is on for TX and on for RX
    bond0: link status definitely up for interface eth0, 100 Mbps full duplex.
    bonding: bond0: making interface eth0 the new active one.
    bonding: bond0: first active interface up!
    ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
    tg3 0000:09:00.0: eth1: Link is up at 100 Mbps, full duplex
    tg3 0000:09:00.0: eth1: Flow control is on for TX and on for RX
    bond0: link status definitely up for interface eth1, 100 Mbps full duplex.
    bond0: no IPv6 routers present

    Any help will be highly appreciated. Thanks in advance.

  2. #2
    Just Joined!
    Join Date
    Jan 2013
    Posts
    32
    Hi,

    I apologize for the delay in replying. The issue was resolved after NetworkManager service was started. Is there any specific reason for this. I shall be happy to know how it got resolved by starting NetworkManager service.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •