Hello. I've been upgrading my 2.2 cluster to 3.4 and I've noticed that my network bonds all show as inactive in the GUI. I've double checked my 70-persistent-net-rules and my interfaces config files and everything looks good.
Checking out the bond0 and bond1 results look good as well. The network bonds are working as intended.
Gui Screenshot:
Checking out the bond0 and bond1 results look good as well. The network bonds are working as intended.
Code:
# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: slow
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 4
Actor Key: 17
Partner Key: 55190
Partner Mac Address: 00:1e:2a:ce:aa:06
Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:21:9b:92:2f:a8
Aggregator ID: 1
Slave queue ID: 0
Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:21:9b:92:2f:aa
Aggregator ID: 1
Slave queue ID: 0
Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:21:9b:92:2f:ac
Aggregator ID: 1
Slave queue ID: 0
Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:21:9b:92:2f:ae
Aggregator ID: 1
Slave queue ID: 0Gui Screenshot:
Last edited: