Last Modified: Aug 21, 2022
Opened: Jan 18, 2022
If LACP interfaces are configured and used by the tenant, after the partition is disabled/enabled, the LACP interface may not work properly due to wrong interface LACP state, which is caused by the disable/enable process. Symptoms: interface state lacp_state is LACP_DEFAULTED For example: interface 2/1.0 is one of member of an LACP interface, which works fine before the partition is disabled/enabled. After the partition is disabled/enabled, run "show interfaces interface 2/1.0 state" command; the output is lacp_state LACP_DEFAULTED. lacp_state LACP_DEFAULTED is wrong which will cause vlan-listeners missing on the blade. vlan-listeners missing on the blade will cause tenant interface failure.
Tenant will not be able to send/receive user traffic and it will not recover automatically.
1. LACP interface is used. 2. LACP interface is configured correctly and up before the partition is disabled/enabled. 3. Disable/enable the partition.
Remove the ethernet interface from the aggregation and re-attach it to the aggregation. This will recover the interface state and resolve the problem. Example: commands to recover the interface (interface 2/1.0 belongs to the LACP interface lag1 and 2/1.0 has a wrong lacp_state). 1. In the partition CLI, remove the aggregate-id for the interface. Entering configuration mode terminal default-1(config)# no interfaces interface 2/1.0 ethernet config aggregate-id ;commit Commit complete. default-1(config)# 2. Re-add the aggregate-id. default-1(config)# interfaces interface 2/1.0 ethernet config aggregate-id lag1 ;commit 3. Reboot the blade (optional step -- use only if step 1 and 2 did not fix the problem).