The MIB module for configuring one or more fabric
extenders to connect into a core switch.  Since fabric 
extenders might not be manageable entities, this MIB is
assumed to be instrumented on the core switch.  A fabric
extender may be hardwired or preconfigured with a list of 
uplink ports.  These uplink ports are used to connect to a 
core switch.  A fabric extender is assumed to be directly 
connected to its core switch. Each physical interface on 
the core switch is assumed to be connected to one and only
one fabric extender.  

When an extender powers up, it runs a link local discovery 
protocol to find core switches.  The extender puts all 
available self identification in its discovery report.  
The core switch, depending on configuration, uses the 
extenders identification to accept or deny an extender 
from connecting. A fabric extender may be connected to 
different core switches via different uplink ports. In 
that case, each core switch's instance of the MIB may 
refer to the same extender.

Ports on core switch used to connect to extenders
are known as Fabric ports.  A fabric port may be a physical
interface or a logical interface such as an EtherChannel.
An extender may connect into a core switch via more than 
one fabric port.  Non fabric ports on an extender are 
typically used to connect hosts/servers.

Imported Objects

TEXTUAL-CONVENTION, RowStatus, TimeStamp, TruthValueSNMPv2-TC
ciscoEthernetFabricExtenderMIBNotifs .
ciscoEthernetFabricExtenderObjects .
cefexConfig .
cefexBindingTable .
cefexBindingEntry .
cefexBindingInterfaceOnCoreSwitch .
cefexBindingExtenderIndex .
cefexBindingCreationTime .
cefexBindingRowStatus .
cefexConfigTable .
cefexConfigEntry .
cefexConfigExtenderName .
cefexConfigSerialNumCheck .
cefexConfigSerialNum .
cefexConfigPinningFailOverMode .
cefexConfigPinningMaxLinks .
cefexConfigCreationTime .
cefexConfigRowStatus .
ciscoEthernetFabricExtenderMIBConformance .
cEthernetFabricExtenderMIBCompliances .
cEthernetFabricExtenderMIBGroups .