ISG LAG interface become 'inactive' or 'backup' instead of active.
Article ID: 260990
Updated On:
Products
Issue/Introduction
The LAG configuration is done on the ISG interface and using the ISG's CLI.
For example, using interface 2:0 and 2:2 for the LAG.
Interface 2:0 become "inactive" and "backup".
localhost(config-lag)# view interfaces
Physical-interface Duplex Speed State LAG
----------------------------------------------------------------
0:0 full 1G up None
2:0 full 1G up 0(inactive)
2:1 full 1G up None
2:2 full 1G up 0(active)
2:3 full 1G up None
localhost(config-lag)# view id 0
Group-id: 0
App-Interface: 9:0
Mode: 802.3ad 4
Xmit hash policy: layer2 0
MAC address: 00:e0:ed:d9:ee:22
Duplex: full
Speed: 1G
State: up
Total Tx Bytes: 3508
Total Rx Bytes: 9367
Total Tx Errors: 0
Total Rx Errors: 0
Host-Interfaces: 2:0, 2:2
2:0
Actor operation port state: (77) active,aggr,synced,default
Aggregator id: 1
Partner operation port state: (1) active
Link failure count: 0
MII status: up
Hardware address: 00:e0:ed:d9:ee:22
Operational state: backup
Tx bytes: 2628
Rx bytes: 14319
Tx errors: 0
Rx errors: 0
2:2
Actor operation port state: (61) active,aggr,synced,accept,send
Aggregator id: 2
Partner operation port state: (61) active,aggr,synced,accept,send
Link failure count: 0
MII status: up
Hardware address: 00:e0:ed:d9:ee:24
Operational state: active
Tx bytes: 1600
Rx bytes: 18396
Tx errors: 0
Rx errors: 0
The aggregate speed is showing only 1G instead of 2G.
localhost(config-lag)# view
Group-id Interfaces Duplex Speed State App-Interface
-----------------------------------------------------------------------------------------
0 2:0, 2:2 full 1G up 9:0
Cause
Based on the messages log from the ISG diagnostics log shows an issue with the LAG or LACP protocol handshake.
Feb 22 18:41:05 localhost cli_register.py[19070]: 2023-02-22 18:41:05,039:776019.197941 DEBUG:network_nic_utils.py:194:set_master Interface nic2_0 is successfully added to Lag lag0
Feb 22 18:41:04 localhost cli_register.py[19070]: 2023-02-22 18:41:04,358:775338.037014 DEBUG:lag_action.py:37:add_interface add lag 0 interface 2:0
Feb 22 18:41:08 localhost kernel: lag0: link status definitely up for interface nic2_0, 1000 Mbps full duplex
Feb 22 18:41:08 localhost kernel: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
Feb 22 18:41:08 localhost kernel: lag0: first active interface up!
Feb 22 18:41:09 localhost cli_register.py[19070]: 2023-02-22 18:41:09,914:780894.232035 DEBUG:network_nic_utils.py:67:get_speed Successfully read speed (1000) from interface nic2_0
Feb 22 18:41:09 localhost cli_register.py[19070]: 2023-02-22 18:41:09,918:780897.84193 DEBUG:network_nic_utils.py:89:get_duplex Successfully read duplex (full) from interface nic2_0
Feb 22 18:41:09 localhost cli_register.py[19070]: 2023-02-22 18:41:09,918:780898.042917 DEBUG:nfrm_lags.py:334:add_interface Partner: speed=1G, duplex=full
Resolution
There is an issue on the switch side in regards to the LAG or LACP configuration. Fixing this on the switch side resolved the issue.
Feedback
