Troubleshooting Guide

Table Of Contents
1 out of 1 Total Num of fabric attach interfaces displayed
----------------------------------------------------------------------
View the FA interfaces that have authentication disabled:
Switch:1#show fa interface disabled-auth
=======================================================================
Fabric Attach Interfaces
=======================================================================
INTERFACE SERVER MGMT MGMT MSG AUTH MSG AUTH
STATUS ISID CVID STATUS KEY
-----------------------------------------------------------------------
Port2/10 enabled 0 0 disabled ****
Port4/6 disabled 0 0 disabled ****
Mlt2 enabled 0 0 disabled ****
-----------------------------------------------------------------------
3 out of 3 Total Num of fabric attach interfaces displayed
-----------------------------------------------------------------------
Related links
Troubleshooting Fabric Attach on page 309
Verify LLDP port-level transmission and reception
Viewing port-based LLDP statistics
Use this procedure to verify port-based LLDP statistics.
About this task
LLDP operates at the interface level. Enabling FA on a port automatically enables LLDP
transmission and reception on the port. It also enables traffic tagging and disables spanning tree on
that port.
Enabling FA on an MLT enables LLDP transmission and reception on all ports in the MLT.
Note:
When FA is enabled on ports in an MLT or LACP MLT, tagging is enabled and spanning tree is
disabled on those ports.
When a port is removed from an MLT, LLDP transmission on that port stops and spanning tree
is enabled. Any I-SID-to-VLAN mappings on that port are removed, if not already learned on any
other port in the MLT. This also causes the Switched UNI I-SID to be deleted from the MLT. If
however, the mappings are learned on another port on the MLT, then the Switched UNI I-SID
continues to exist for that MLT.
Procedure
1. Enter Privileged EXEC mode:
enable
2. Verify LLDP statistics:
show lldp stats
Troubleshooting Fabric Attach
January 2017 Troubleshooting 312
Comments on this document? infodev@avaya.com