Issue in Bonding during Reboot(Linux)


 
Thread Tools Search this Thread
Operating Systems Linux Issue in Bonding during Reboot(Linux)
# 1  
Old 12-20-2016
Tools Issue in Bonding during Reboot(Linux)

Respected Members,

We encountered an issue during node reboot when eth1 and eth5 of bond1 were behaving unusual(both eth1 and eth5 were in unknown states and ifdown and ifup were used to rectify). Please find the messages and configuration files as below and please let me know for any other input:

Code:
more ifcfg-bond1
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
IPV6INIT=no
ONBOOT=yes
DEVICE=bond1
BOOTPROTO=static
NETMASK=255.255.255.252
NM_CONTROLLED=no
IPADDR=192.168.0.1
USERCTL=no
BONDING_OPTS='mode=1 miimon=100 primary=eth1 primary_reselect=always'

Code:
more ifcfg-eth1
ONBOOT=yes
DEVICE=eth1
MASTER=bond1
BOOTPROTO=none
NM_CONTROLLED=no
ETHTOOL_OPTS='speed 100 duplex full autoneg off'
USERCTL=no
IPV6INIT=no
SLAVE=yes

Code:
more ifcfg-eth5
ONBOOT=yes
DEVICE=eth5
MASTER=bond1
BOOTPROTO=none
NM_CONTROLLED=no
ETHTOOL_OPTS='speed 100 duplex full autoneg off'
USERCTL=no
IPV6INIT=no
SLAVE=yes



Code:
cat /proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

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

Slave Interface: eth1
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 8
Permanent HW addr: ac:16:2d:8a:36:a5
Slave queue ID: 0

Slave Interface: eth5
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 8
Permanent HW addr: ac:16:2d:86:ab:79
Slave queue ID: 0


Code:
ifconfig eth1
eth1      Link encap:Ethernet  HWaddr AC:16:2D:8A:36:A5  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:144320945 errors:0 dropped:0 overruns:0 frame:0
          TX packets:149469477 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:59204967529 (55.1 GiB)  TX bytes:83875856927 (78.1 GiB)
          Interrupt:36

Code:
ifconfig eth5
eth5      Link encap:Ethernet  HWaddr AC:16:2D:8A:36:A5  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:64 (64.0 b)  TX bytes:640 (640.0 b)
          Interrupt:28

Code:
ifconfig bond1
bond1     Link encap:Ethernet  HWaddr AC:16:2D:8A:36:A5  
          inet addr:192.168.0.1  Bcast:192.168.0.3  Mask:255.255.255.252
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:144347534 errors:0 dropped:0 overruns:0 frame:0
          TX packets:149497311 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:59213542863 (55.1 GiB)  TX bytes:83893330646 (78.1 GiB)


Code:
ethtool -i eth1
driver: tg3
version: 3.132
firmware-version: 5719-v1.38 NCSI v1.2.46.0
bus-info: 0000:03:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

Code:
ethtool -i eth5
driver: tg3
version: 3.132
firmware-version: 5719-v1.38 NCSI v1.2.46.0
bus-info: 0000:04:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no



Code:
/var/log/messages


Dec 18 03:03:09 kernel: tg3 0000:03:00.1: eth1: Link is down
Dec 18 03:03:09 kernel: bonding: bond1: link status definitely down for interface eth1, disabling it
Dec 18 03:03:09 kernel: bonding: bond1: making interface eth5 the new active one.
Dec 18 03:03:10 kernel: tg3 0000:04:00.1: eth5: Link is down
Dec 18 03:03:10 kernel: bonding: bond1: link status definitely down for interface eth5, disabling it
Dec 18 03:03:10 kernel: bonding: bond1: now running without any active interface !
Dec 18 03:03:11 kernel: tg3 0000:03:00.1: eth1: Link is up at 100 Mbps, full duplex
Dec 18 03:03:11 kernel: tg3 0000:03:00.1: eth1: Flow control is on for TX and on for RX
Dec 18 03:03:11 kernel: tg3 0000:03:00.1: eth1: EEE is disabled
Dec 18 03:03:11 kernel: bond1: link status definitely up for interface eth1, 100 Mbps full duplex.
Dec 18 03:03:11 kernel: bonding: bond1: making interface eth1 the new active one.
Dec 18 03:03:11 kernel: bonding: bond1: first active interface up!
Dec 18 03:03:12 kernel: tg3 0000:04:00.1: eth5: Link is up at 100 Mbps, full duplex
Dec 18 03:03:12 kernel: tg3 0000:04:00.1: eth5: Flow control is on for TX and on for RX
Dec 18 03:03:12 kernel: tg3 0000:04:00.1: eth5: EEE is disabled
Dec 18 03:03:12 kernel: bond1: link status definitely up for interface eth5, 100 Mbps full duplex.
Dec 18 03:03:18 cmanicd[3252]: Entering log_iml_event(slot: 0, port: 2, code: (Other,5))
Dec 18 03:03:18 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:03:21 kernel: tg3 0000:04:00.1: eth5: Link is down
Dec 18 03:03:21 kernel: tg3 0000:03:00.1: eth1: Link is down
Dec 18 03:03:21 kernel: bonding: bond1: link status definitely down for interface eth1, disabling it
Dec 18 03:03:21 kernel: bonding: bond1: now running without any active interface !
Dec 18 03:03:21 kernel: bonding: bond1: link status definitely down for interface eth5, disabling it
Dec 18 03:03:22 kernel: tg3 0000:03:00.1: eth1: Link is up at 100 Mbps, full duplex
Dec 18 03:03:22 kernel: tg3 0000:03:00.1: eth1: Flow control is on for TX and on for RX
Dec 18 03:03:22 kernel: tg3 0000:03:00.1: eth1: EEE is disabled
Dec 18 03:03:23 kernel: tg3 0000:04:00.1: eth5: Link is up at 100 Mbps, full duplex
Dec 18 03:03:23 kernel: tg3 0000:04:00.1: eth5: Flow control is on for TX and on for RX
Dec 18 03:03:23 kernel: tg3 0000:04:00.1: eth5: EEE is disabled
Dec 18 03:03:23 kernel: bond1: link status definitely up for interface eth1, 100 Mbps full duplex.
Dec 18 03:03:23 kernel: bonding: bond1: making interface eth1 the new active one.
Dec 18 03:03:23 kernel: bonding: bond1: first active interface up!
Dec 18 03:03:23 kernel: bond1: link status definitely up for interface eth5, 100 Mbps full duplex.
Dec 18 03:03:24 cmanicd[3252]: Existing event id(0) found for the slot and port.
Dec 18 03:03:24 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:03:24 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:03:24 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:03:24 cmanicd[3252]: Trying to modify the existing IML Event.
Dec 18 03:03:24 cmanicd[3252]: Successfully updated the existing IML Event.
Dec 18 03:03:24 cmanicd[3252]: Returning from log_iml_event().
Dec 18 03:03:25 kernel: tg3 0000:03:00.1: eth1: Link is down
Dec 18 03:03:25 kernel: tg3 0000:04:00.1: eth5: Link is down
Dec 18 03:03:25 kernel: bonding: bond1: link status definitely down for interface eth1, disabling it
Dec 18 03:03:25 kernel: bonding: bond1: now running without any active interface !
Dec 18 03:03:25 kernel: bonding: bond1: link status definitely down for interface eth5, disabling it
Dec 18 03:03:26 cmanicd[3252]: Entering log_iml_event(slot: 1, port: 2, code: (Other,5))
Dec 18 03:03:26 cmanicd[3252]: Entering get_event_id(slot: 1, port: 2
Dec 18 03:03:27 cmanicd[3252]: Existing event id(7) found for the slot and port.
Dec 18 03:03:27 cmanicd[3252]: Entering read_iml_event(slot: 1, port: 2, eventid: 7)
Dec 18 03:03:27 cmanicd[3252]: Calling ioctl() to read event id: 7)
Dec 18 03:03:27 cmanicd[3252]: Successfully read the event id: 7)
Dec 18 03:03:27 cmanicd[3252]: Trying to modify the existing IML Event.
Dec 18 03:03:27 cmanicd[3252]: Successfully updated the existing IML Event.
Dec 18 03:03:27 cmanicd[3252]: Returning from log_iml_event().
Dec 18 03:03:27 kernel: tg3 0000:04:00.1: eth5: Link is up at 100 Mbps, full duplex
Dec 18 03:03:27 kernel: tg3 0000:04:00.1: eth5: Flow control is on for TX and on for RX
Dec 18 03:03:27 kernel: tg3 0000:04:00.1: eth5: EEE is disabled
Dec 18 03:03:27 kernel: bond1: link status definitely up for interface eth5, 100 Mbps full duplex.
Dec 18 03:03:27 kernel: bonding: bond1: making interface eth5 the new active one.
Dec 18 03:03:27 kernel: tg3 0000:03:00.1: eth1: Link is up at 100 Mbps, full duplex
Dec 18 03:03:27 kernel: tg3 0000:03:00.1: eth1: Flow control is on for TX and on for RX
Dec 18 03:03:27 kernel: tg3 0000:03:00.1: eth1: EEE is disabled
Dec 18 03:03:27 kernel: bonding: bond1: first active interface up!
Dec 18 03:03:27 kernel: bond1: link status definitely up for interface eth1, 100 Mbps full duplex.
Dec 18 03:03:27 kernel: bonding: bond1: making interface eth1 the new active one.
Dec 18 03:03:28 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:03:28 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:03:28 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:03:28 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:03:28 cmanicd[3252]: Entering get_event_id(slot: 1, port: 2
Dec 18 03:03:30 cmanicd[3252]: Entering read_iml_event(slot: 1, port: 2, eventid: 7)
Dec 18 03:03:30 cmanicd[3252]: Calling ioctl() to read event id: 7)
Dec 18 03:03:30 cmanicd[3252]: Successfully read the event id: 7)
Dec 18 03:03:30 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:03:30 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:03:30 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:03:30 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:03:30 cmanicd[3252]: Entering iml_log_link_up(slot: 0, port: 2)
Dec 18 03:03:30 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:03:30 cmanicd[3252]: Existing event id(0) found for the slot and port.
Dec 18 03:03:30 cmanicd[3252]: Entering repair_iml_event(slot: 0, port: 2, event: 0)
Dec 18 03:03:30 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:03:30 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:03:30 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:03:30 cmanicd[3252]: Trying to repair the existing IML Event.
Dec 18 03:03:31 cmanicd[3252]: Successfully repaired the IML Event.
Dec 18 03:03:31 cmanicd[3252]: Returning from repair_iml_event().
Dec 18 03:03:32 cmanicd[3252]: Entering get_event_id(slot: 1, port: 2
Dec 18 03:03:33 cmanicd[3252]: Entering repair_iml_event(slot: 1, port: 2, event: 7)
Dec 18 03:03:33 cmanicd[3252]: Entering read_iml_event(slot: 1, port: 2, eventid: 7)
Dec 18 03:03:33 cmanicd[3252]: Calling ioctl() to read event id: 7)
Dec 18 03:03:33 cmanicd[3252]: Successfully read the event id: 7)
Dec 18 03:03:33 cmanicd[3252]: Trying to repair the existing IML Event.
Dec 18 03:03:34 cmanicd[3252]: Successfully repaired the IML Event.
Dec 18 03:03:34 cmanicd[3252]: Returning from repair_iml_event().
Dec 18 03:03:35 cmanicd[3252]: Entering log_iml_event(slot: 1, port: 2, code: (Other,5))
Dec 18 03:03:35 cmanicd[3252]: Entering get_event_id(slot: 1, port: 2
Dec 18 03:03:37 cmanicd[3252]: Existing event id(7) found for the slot and port.
Dec 18 03:03:37 cmanicd[3252]: Entering read_iml_event(slot: 1, port: 2, eventid: 7)
Dec 18 03:03:37 cmanicd[3252]: Calling ioctl() to read event id: 7)
Dec 18 03:03:37 cmanicd[3252]: Successfully read the event id: 7)
Dec 18 03:03:37 cmanicd[3252]: Trying to modify the existing IML Event.
Dec 18 03:03:38 cmanicd[3252]: Successfully updated the existing IML Event.
Dec 18 03:03:38 cmanicd[3252]: Returning from log_iml_event().
Dec 18 03:03:39 cmanicd[3252]: Entering log_iml_event(slot: 0, port: 2, code: (Other,5))
Dec 18 03:03:39 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:03:39 cmanicd[3252]: Existing event id(0) found for the slot and port.
Dec 18 03:03:39 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:03:39 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:03:40 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:03:40 cmanicd[3252]: Trying to modify the existing IML Event.
Dec 18 03:03:40 cmanicd[3252]: Successfully updated the existing IML Event.
Dec 18 03:03:40 cmanicd[3252]: Returning from log_iml_event().
Dec 18 03:03:41 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:03:42 cmanicd[3252]: Entering repair_iml_event(slot: 0, port: 2, event: 0)
Dec 18 03:03:42 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:03:42 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:03:42 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:03:42 cmanicd[3252]: Trying to repair the existing IML Event.
Dec 18 03:03:43 cmanicd[3252]: Successfully repaired the IML Event.
Dec 18 03:03:43 cmanicd[3252]: Returning from repair_iml_event().
Dec 18 03:03:44 cmanicd[3252]: Entering get_event_id(slot: 1, port: 2
Dec 18 03:03:46 cmanicd[3252]: Entering repair_iml_event(slot: 1, port: 2, event: 7)
Dec 18 03:03:46 cmanicd[3252]: Entering read_iml_event(slot: 1, port: 2, eventid: 7)
Dec 18 03:03:46 cmanicd[3252]: Calling ioctl() to read event id: 7)
Dec 18 03:03:46 cmanicd[3252]: Successfully read the event id: 7)
Dec 18 03:03:47 cmanicd[3252]: Trying to repair the existing IML Event.
Dec 18 03:03:47 cmanicd[3252]: Successfully repaired the IML Event.
Dec 18 03:03:47 cmanicd[3252]: Returning from repair_iml_event().
Dec 18 03:03:48 cmanicd[3252]: Entering log_iml_event(slot: 0, port: 2, code: (Other,5))
Dec 18 03:03:48 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:03:49 cmanicd[3252]: Existing event id(0) found for the slot and port.
Dec 18 03:03:49 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:03:49 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:03:49 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:03:49 cmanicd[3252]: Trying to modify the existing IML Event.
Dec 18 03:03:49 cmanicd[3252]: Successfully updated the existing IML Event.
Dec 18 03:03:49 cmanicd[3252]: Returning from log_iml_event().
Dec 18 03:03:50 cmanicd[3252]: Entering log_iml_event(slot: 1, port: 2, code: (Other,5))
Dec 18 03:03:50 cmanicd[3252]: Entering get_event_id(slot: 1, port: 2
Dec 18 03:03:51 cmanicd[3252]: Existing event id(7) found for the slot and port.
Dec 18 03:03:51 cmanicd[3252]: Entering read_iml_event(slot: 1, port: 2, eventid: 7)
Dec 18 03:03:51 cmanicd[3252]: Calling ioctl() to read event id: 7)
Dec 18 03:03:51 cmanicd[3252]: Successfully read the event id: 7)
Dec 18 03:03:51 cmanicd[3252]: Trying to modify the existing IML Event.
Dec 18 03:03:51 cmanicd[3252]: Successfully updated the existing IML Event.
Dec 18 03:03:51 cmanicd[3252]: Returning from log_iml_event().
Dec 18 03:03:53 cmanicd[3252]: Entering get_event_id(slot: 1, port: 2
Dec 18 03:03:54 cmanicd[3252]: Entering repair_iml_event(slot: 1, port: 2, event: 7)
Dec 18 03:03:54 cmanicd[3252]: Entering read_iml_event(slot: 1, port: 2, eventid: 7)
Dec 18 03:03:54 cmanicd[3252]: Calling ioctl() to read event id: 7)
Dec 18 03:03:54 cmanicd[3252]: Successfully read the event id: 7)
Dec 18 03:03:54 cmanicd[3252]: Trying to repair the existing IML Event.
Dec 18 03:03:54 cmanicd[3252]: Successfully repaired the IML Event.
Dec 18 03:03:54 cmanicd[3252]: Returning from repair_iml_event().
Dec 18 03:03:55 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:03:59 cmanicd[3252]: Entering repair_iml_event(slot: 0, port: 2, event: 0)
Dec 18 03:03:59 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:03:59 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:04:01 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:04:01 cmanicd[3252]: Trying to repair the existing IML Event.
Dec 18 03:04:06 cmanicd[3252]: Successfully repaired the IML Event.
Dec 18 03:04:06 cmanicd[3252]: Returning from repair_iml_event().
Dec 18 03:06:35 kernel: tg3 0000:03:00.1: eth1: Link is down
Dec 18 03:06:35 kernel: bonding: bond1: link status definitely down for interface eth1, disabling it
Dec 18 03:06:35 kernel: bonding: bond1: making interface eth5 the new active one.
Dec 18 03:06:36 kernel: tg3 0000:04:00.1: eth5: Link is down
Dec 18 03:06:36 kernel: bonding: bond1: link status definitely down for interface eth5, disabling it
Dec 18 03:06:36 kernel: bonding: bond1: now running without any active interface !
Dec 18 03:06:37 cmanicd[3252]: Entering iml_log_link_down(slot: 0, port: 2)
Dec 18 03:06:37 cmanicd[3252]: Entering log_iml_event(slot: 0, port: 2, code: (Down,2))
Dec 18 03:06:37 cmanicd[3252]: Entering get_event_id(slot: 0, port: 2
Dec 18 03:06:37 cmanicd[3252]: Existing event id(0) found for the slot and port.
Dec 18 03:06:37 cmanicd[3252]: Entering read_iml_event(slot: 0, port: 2, eventid: 0)
Dec 18 03:06:37 cmanicd[3252]: Calling ioctl() to read event id: 0)
Dec 18 03:06:37 cmanicd[3252]: Successfully read the event id: 0)
Dec 18 03:06:37 cmanicd[3252]: Trying to modify the existing IML Event.
Dec 18 03:06:38 cmanicd[3252]: Successfully updated the existing IML Event.
Dec 18 03:06:38 cmanicd[3252]: Returning from log_iml_event().
Dec 18 03:06:39 cmanicd[3252]: Entering iml_log_link_down(slot: 1, port: 2)
Dec 18 03:06:39 cmanicd[3252]: Entering log_iml_event(slot: 1, port: 2, code: (Down,2))
Dec 18 03:06:39 cmanicd[3252]: Entering get_event_id(slot: 1, port: 2
Dec 18 03:06:40 cmanicd[3252]: Existing event id(7) found for the slot and port.
Dec 18 03:06:40 cmanicd[3252]: Entering read_iml_event(slot: 1, port: 2, eventid: 7)
Dec 18 03:06:40 cmanicd[3252]: Calling ioctl() to read event id: 7)
Dec 18 03:06:40 cmanicd[3252]: Successfully read the event id: 7)
Dec 18 03:06:40 cmanicd[3252]: Trying to modify the existing IML Event.
Dec 18 03:06:40 cmanicd[3252]: Successfully updated the existing IML Event.
Dec 18 03:06:40 cmanicd[3252]: Returning from log_iml_event().
Dec 18 03:19:22 kernel: tg3 0000:03:00.1: eth1: Link is up at 100 Mbps, full duplex
Dec 18 03:19:22 kernel: tg3 0000:03:00.1: eth1: Flow control is on for TX and on for RX
Dec 18 03:19:22 kernel: tg3 0000:03:00.1: eth1: EEE is disabled
Dec 18 03:19:22 kernel: bond1: link status definitely up for interface eth1, 100 Mbps full duplex.
Dec 18 03:19:22 kernel: bonding: bond1: making interface eth1 the new active one.
Dec 18 03:19:22 kernel: bonding: bond1: first active interface up!
Dec 18 03:19:22 kernel: tg3 0000:04:00.1: eth5: Link is up at 100 Mbps, full duplex
Dec 18 03:19:22 kernel: tg3 0000:04:00.1: eth5: Flow control is on for TX and on for RX
Dec 18 03:19:22 kernel: tg3 0000:04:00.1: eth5: EEE is disabled
Dec 18 03:19:22 kernel: bond1: link status definitely up for interface eth5, 100 Mbps full duplex.
Dec 18 03:19:25 kernel: tg3 0000:03:00.1: eth1: Link is down
Dec 18 03:19:25 kernel: bonding: bond1: link status definitely down for interface eth1, disabling it
Dec 18 03:19:25 kernel: bonding: bond1: making interface eth5 the new active one.
Dec 18 03:19:26 kernel: tg3 0000:04:00.1: eth5: Link is down
Dec 18 03:19:26 kernel: bonding: bond1: link status definitely down for interface eth5, disabling it
Dec 18 03:19:26 kernel: bonding: bond1: now running without any active interface !


To come out from this situation(at Dec 18 03:03), ifdown and ifup were performed. Please suggest what may be done here to resolve the issue.

Last edited by Mudit Bansal; 12-20-2016 at 05:59 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Network Bonding Issue

I have one production system where my customized application runs.The applications require seamless network connectivity with different machines connected in LAN and WAN. As these applications are very critical, it is very much required to have a seamless network activity.The applications are... (4 Replies)
Discussion started by: Anjan Ganguly
4 Replies

2. Red Hat

How to change bonding configuration in Linux 5.9?

I have 2 ethernet port in my linux (Red hat 5.9) machine.The 2 ethernet ports (eth0 and eth1)are bonded and are making one single ethernet port namely bond0. I have adaptive load share option selected.Now in this condition, if my eth0 port disconnected due to some failure, then will eth1 take the... (0 Replies)
Discussion started by: Anjan Ganguly
0 Replies

3. IP Networking

Is bond0 ready and a bonding interface? - 4G Bonding Router Problems (RPI)

HI all, First post on the forum, and my first proper project on the Paspberry Pi, so sorry if this is in the wrong place. I am trying to turn my Pi in to a 3G/4G Bonding router. I have been researching and trying this for a week or so now. The basic plan is to have up to 6 ZTE MF823 USB... (0 Replies)
Discussion started by: elliottlc
0 Replies

4. Red Hat

BONDING with Flapping issue!

Hi team, I'm running into a problem configuring bonding on an CentOS 64bit on DELL Server. I'm connecting eth0 and eth1 to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The ethernet address is that of the primary interface. I have tried several different modes,... (3 Replies)
Discussion started by: leo_ultra_leo
3 Replies

5. Shell Programming and Scripting

Reboot script issue

Hi guys I am troubleshooting a script that informs me when a system has rebooted. The script is placed in /etc/rc3.d folder under root. The script is as follows: . /opt/scripts/function.sh PATH=/usr/bin EMAIL_ADD=<email address> ... (2 Replies)
Discussion started by: Junaid Subhani
2 Replies

6. Solaris

vnc issue after reboot

Hi , Everytime after reboot when user tries to start vnc below error is thrown $ vncserver :5 Couldn't start Xvnc; trying default font path. Please set correct fontPath in the vncserver script. Couldn't start Xvnc process. _XSERVTransSocketCreateListener: failed to bind listener... (7 Replies)
Discussion started by: chidori
7 Replies

7. IP Networking

Channel bonding Issue - Bond0 interface not getting up in on RHEL6

Hello, I am trying to set up Channel Bonding on a RHEL6 Virtual Box VM. I have 2 ethernet cards on the machine which are set up in Internal Network mode. I followed all the steps exactly as mentioned in the RHEL6 deployment Guide, but for some reason i think results are not correct. Here are my... (13 Replies)
Discussion started by: Rohit Bhanot
13 Replies

8. Solaris

Controller Issue on X4600 after reboot

One of my X4600 server had a power loss and rebooted and now its giving me a strange problem servers internal disk controller naming has changed by itself ... the after failsafe boot md.conf file shows following c3txdx but shows internal disk at c4txdx ... what could be the reason for this and... (1 Reply)
Discussion started by: fugitive
1 Replies

9. SCO

SCO Reboot Issue

Hi, We are using SCO UNIX 7.1.3 and the server recently started rebooting by itself. Do anyone know how can i create a dump or crash dump while the server rebooots? Your quick help on this is really appreciated. Regards, Ravikumar R (1 Reply)
Discussion started by: rrb2009
1 Replies

10. HP-UX

Issue in reboot

Hi, Whenever I reboot this server remotely by using the command 'shutdown -r now' or 'reboot'. The server does not return to normal multi-user mode. It boots in single user mode. To bring back the server, someone is required to connect via console and fire 'init 3'. Please suggest on what... (1 Reply)
Discussion started by: mystition
1 Replies
Login or Register to Ask a Question