-
Notifications
You must be signed in to change notification settings - Fork 429
Open
Description
Non-sequential interface assignment causes interface issue
Description
When a non-sequential interface is assigned (skipping one or more ports in the sequence), the interface remains operationally down despite being administratively up. No traffic passes, packet capture shows nothing leaving the interface, and any protocol configured on it (LAG, etc.) will fail as a result.
Example
On my lab interface 1/1/1-1/1/3 are configured. LAG configured on the interface.
If I want to use the interface 1/1/5 without using the 1/1/4 I will have an issue.
Nothing will leave the interface, no packet capture from wireshark
Operational state stay down
A:lab@NCAKE101# show lag 20
===============================================================================
Lag Data
===============================================================================
Lag-id Adm Opr Weighted Threshold Up-Count MC Act/Stdby
name
-------------------------------------------------------------------------------
20 up down No 0 0 N/A
lag-20
===============================================================================
[/]
A:lab@NCAKE101#
As soon as I switch to interface 1/1/4 and redeploy the lab, everything works fine and the operational state is up. The configuration is identical.
A:lab@NCAKE101# show lag 20
===============================================================================
Lag Data
===============================================================================
Lag-id Adm Opr Weighted Threshold Up-Count MC Act/Stdby
name
-------------------------------------------------------------------------------
20 up up No 0 1 N/A
lag-20
===============================================================================
[/]
A:lab@NCAKE101#
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels