FEX (Fabric Extender) Ports on CISCO Nexus
search cancel

FEX (Fabric Extender) Ports on CISCO Nexus

book

Article ID: 331903

calendar_today

Updated On:

Products

VMware Smart Assurance VMware Telco Cloud Service Assurance

Issue/Introduction

Access ports being managed in IP

Environment

10.x / 2.x 

Resolution

On a CISCO NEXUS, Fabric Extender Cards(FEX), ports on these cards and manage these ports by default

In the scenario below we have a NEXUS 5K or 7K connected to a NEXUS 2K.

In a Nexus Switch the Nexus2K are represented as a FEX(Fabric Extender) Card. These cards will have the FC ports on it.  As the 2K is not a managed entity on its own (i.e no SNMP Agent present) it will not show its CDP or LLDP data.  The ports from the Nexus5k/7k Switch are connected to the Nexus2k. As the Nexus2K is not a managed entity so there will never be a connection between these two entities (no ConnectedVia).

Smarts uses the following OID to determine if the ports are FEX ports Smarts uses OID cefexBindingExtenderIndex {".1.3.6.1.4.1.9.9.691.1.1.1.1.2"}.  The standard MIB2 is used to determine AdminStatus and OperStatus.

If FEX is set, Smarts will by default EXPLICITLY_MANAGE the ports and be monitored.