Troubleshooting Guide

Table Of Contents
Fabric Attach troubleshooting example
Troubleshooting FA Server rejection of I-SID-to-VLAN
assignments using trace
Consider an FA solution where the FA Server receives I-SID-to-VLAN assignment requests from a
proxy device and some of these assignment requests are rejected by the FA Server. Use this
procedure to help you troubleshoot the cause of the rejection.
Note:
When the FA Server rejects an I-SID-to-VLAN assignment request, the error message in the log
file lists a generic reason for the failure, such as rejected due to application error
(status 9). To troubleshoot further, you must use trace.
This procedure also demonstrates how you can configure trace for enhanced troubleshooting.
Procedure
Begin troubleshooting on the FA Server
1. Enter Privileged EXEC mode:
enable
2. Verify that router IS-IS is enabled. This is required for proper FA operation.
show isis
Note:
I-SID-to-VLAN assignments are always rejected if router IS-IS is disabled.
3. Verify that FA is enabled on the interface on which I-SID-to-VLAN assignments are
expected.
show fa interface [disabled-auth] [enabled-auth] [mlt <1–512>] [port
{slot/port[/sub-port] [-slot/port[/sub-port]] [,...]}]
4. Verify the discovery and authentication status of the proxy device, on the interface.
show fa elements [{slot/port[/sub-port] [-slot/port[/sub-port]]
[,...]}]
5. Determine the I-SID-to-VLAN assignments received on the interface and which ones are
rejected.
show fa assignment [{slot/port[/sub-port] [-slot/port[/sub-port]]
[,...]}]]
6. View the log file to determine the cause of the assignment rejection.
show log file module fa
Troubleshooting Fabric Attach
January 2017 Troubleshooting 334
Comments on this document? infodev@avaya.com