ProLiant Servers (ML,DL,SL)

Bonding not working with non-HP switch

 
Nizam28
New Member

Bonding not working with non-HP switch

Hi HP,

    Ethernet Bonding  is not working with non-HP switch.

HP DL380 gen9 to non-HP switch.

1. Both ports indivdiually working fine. But when, one of the bonded ethernet port disabled secondary port not coming up (As we configure, Bonding Mode: fault-tolerance (active-backup))

2. Secondary interface MII Status is showing down, Only it comes UP, once config changed to Active-Active at switch end.

Please find the below mentioned output for reference and suggest.

===================MII Status: down==============================

cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

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

Slave Interface: eno2
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 7
Permanent HW addr:  xxxxxxxxxx2
Slave queue ID: 0

Slave Interface: eno1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr:  xxxxxxxxxx1
Slave queue ID: 0

================================================

==============MII Status: up==========================

cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

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

Slave Interface: eno2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 6
Permanent HW addr: xxxxxxxxxx2
Slave queue ID: 0

Slave Interface: eno1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: xxxxxxxx1
Slave queue ID: 0

======================================

Some configs and output for reference. Is it any parameter missing in configuration at server side ?

$ ifconfig eno1

eno1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether xxxxxxxxxxxx1 txqueuelen 1000 (Ethernet)
RX packets 505090 bytes 96640736 (92.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 468645 bytes 185166132 (176.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16

---------------------------------------

$ ifconfig eno2
eno2: flags=6147<UP,BROADCAST,SLAVE,MULTICAST> mtu 1500
ether xxxxxxxxxxxx2 txqueuelen 1000 (Ethernet)
RX packets 2894 bytes 372821 (364.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1020 bytes 335840 (327.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17

------------------------------------------

$ ifconfig bond0
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet xxxxxxxx netmask xxxxxxxx broadcast xxxxxxxxx
inet6 xxxxxxxxxxxxxx prefixlen 64 scopeid 0x20<link>
ether 94:18:82:80:22:d0 txqueuelen 1000 (Ethernet)
RX packets 508026 bytes 97018703 (92.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 469696 bytes 185510046 (176.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

------------------------------------------------


cat ifcfg-bond0
DEVICE=bond0
NAME=bond0
TYPE=Bond
NM_CONTROLLED=no
BONDING_MASTER=yes
IPADDR=xxxxxxxxxxxx
PREFIX=28
GATEWAY=xxxxxxxxxxx
IPV6INIT=no
DEFROUTE=yes
ONBOOT=yes
BOOTPROTO=none
BONDING_OPTS="mode=active-backup miimon=100"
[network-scripts]$

------------------------------------------

[network-scripts]$ cat ifcfg-eno1
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
NAME=eno1
UUID=xxxxxxxxxxxx
DEVICE=eno1
ONBOOT=yes
NM_CONTROLLED=no
MASTER=bond0
SLAVE=yes

--------------------------------------
[network-scripts]$ cat ifcfg-eno2
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
NAME=eno2
UUID=xxxxxxxxxxxx
DEVICE=eno2
ONBOOT=yes
NM_CONTROLLED=no
MASTER=bond0
SLAVE=yes

=================================

 

 

2 REPLIES 2
parnassus
Honored Contributor

Re: Bonding not working with non-HP switch

What is the configuration of peer ports on the non-HP Switch? ...are those ports set as autonomous (not aggregated into a bond logical interface, switch side)?

Can't you use bonding mode 4 (4 = 802.3ad = LACP) instead? I mean Server side AND Switch side? ...clearly you need that someone make for you an aggregated interface (using LACP) with the two actual switch members ports but the outcome is better (because peers negotiate and exchange information each others by means of LACP)...sometime this approach is not possible (maybe the Switch doesn't support LACP or OS has some restrictions)...but if it is possible it's worth a try.

A good reference here (Linux bonding modes) and here (Switch ports configuration).


I'm not an HPE Employee
Kudos and Accepted Solution banner
ksram
HPE Pro

Re: Bonding not working with non-HP switch

Hi,

Any update on the information asked / if the reference links were useful?

Thank you

KSRam


I work for HPE

Accept or Kudo