Are Cisco Fabric Extender (FEX) devices supported by Discovery?Cisco Nexus Switches are sometimes used with Nexus 2000 Series Fabric Extenders (FEX) units. These separate units provide additional Ports for some Nexus 5000, 7000 or 9000 series switches, and have an up-link connection to the main Switch. They are not managed devices themselves, but are visible in the Cisco vendor MIB SNMP OIDs of the Switch, and so their attributes are theoretically discover-able. At the time of writing (updated Aug 2022) Discovery probes and patterns do not create CIs for the FEX units or their Ports. The main Switch unit is discovered, and a CI will be created for that and its ports. Support for Cisco FEX devices will require an enhancement of the Network Switch pattern. If you need this supporting, please provide feedback to our developers by up-voting and commenting with your specific requirement on the existing Enhancement request in the Idea Portal. In August 2022 this was "under consideration" so it stands a good chance:Fexes data is not getting discovered under Cisco Nexus primary switch Note: This switch architecture is not the same as "Stacked Switches", for example Cisco Catalyst switches, where several identical Switch units act as Primary or Secondary depending on how they are configured. Stacked Switches are supported, and IP Switch Cis created for each Switch in the stack. In the past, the Network Switch pattern has mistakenly created multiple CIs when discovering Nexus switches, when OIDs relating to the FEX units were mistaken for Stacked Switches. These additional CIs wrongly had the same Model as the actual switch, as would have been correct if this had really been a stacked switch. If support is added for FEX units in future, it is unlikely that the IP Switch table will be used for them, and it is possible they may only appear as additional ports of the Switch CI. Known problems: PRB1594667 A Switch CI is created for Cisco Fabric Extender (FEX) units, as if it were a Stacked Switch