API Guide

Eth 1/1/21:1 down 0 auto A 1 -
Eth 1/1/21:2 down 0 auto A 1 -
Eth 1/1/21:3 down 0 auto A 1 -
Eth 1/1/21:4 down 0 auto A 1 -
Eth 1/1/22:1 down 0 auto A 1 -
Eth 1/1/22:2 down 0 auto A 1 -
Eth 1/1/22:3 down 0 auto A 1 -
Eth 1/1/22:4 down 0 auto A 1 -
...
Virtual ports
A virtual port is a logical OS10 port that connects to a downstream server and has no physical hardware location on the switch.
Virtual ports are created when an MX9116n Fabric Switching Engine onboards an MX7116n Fabric Expander Module. The
onboarding process consists of discovery and configuration.
Fabric Expander discovery
A Fabric Expander functions as an unmanaged Ethernet repeater with sixteen 25GE server-facing ports and two QSFP28-DD
uplink ports. An attached Fabric Switching Engine in Full Switch mode automatically discovers the Fabric Expander when these
conditions are met:
● The Fabric Expander is connected to the Fabric Engine by attaching a cable between a QSFP28-DD port on each device.
● On the Fabric Engine, the QSFP28-DD port-group connected to the Fabric Expander is in 25g-8x fabric-expander-
mode mode.
● At least one compute sled is installed in the MX7000 chassis containing the Fabric Expander.
NOTE:
If you move a Fabric Expander by cabling it to a different QSFP28-DD port on the Fabric Engine, all software
configurations on virtual ports are maintained. Only the QSFP28-DD breakout interfaces that map to the virtual ports
change.
NOTE: If the servers in the MX7000 chassis have dual-port NICs, connect the Fabric Engine only to QSFP28-DD port 1 on
the Fabric Expander. Do not connect to QSFP28-DD port 2.
To verify the auto-discovered Fabric Expanders, enter the show discovered-expanders command.
OS10# show discovered-expanders
Service-tag Model Type Chassis-service-tag Chassis-slot Port-group Virtual-Slot-
Id
-----------------------------------------------------------------------------------------
-
403RPK2 MX7116n Fabric 1 SKY003Q A2 port-
group1/1/2
Expander Module
Fabric Expander virtual slot configuration
If the Fabric Switching Engine is in SmartFabric mode, an attached Fabric Expander is automatically configured:
● Virtual ports on the Fabric Expander and a virtual slot ID are created and mapped to 8x25GE breakout interfaces in FEM
mode on the Fabric Engine.
● The unit ID is automatically discovered.
● Server traffic is transmitted through the QSFP28-DD uplink on the Fabric Expander to the Fabric Engine.
If the Fabric Switching Engine is in Full Switch mode, you can perform the same switch configuration using the CLI as in
SmartFabric mode using the graphical user interface, except that you must manually configure the unit ID of the Fabric
Expander. The unit ID is also called the virtual slot ID.
1. Locate the service tag of the Fabric Expander in the show discovered-expanders output.
2. Display the unassigned unit IDs reserved for Fabric Expanders in EXEC mode. The service tags of provisioned Fabric
Expanders are displayed in the Provision Name column of the show unit-provision output.
OS10# show unit-provision
Node ID | Unit ID | Provision Name | Discovered Name | State |
--------+---------+----------------+-----------------+-------|
1 | 71 | | | |
1 | 72 | | | |
316
PowerEdge MX Ethernet I/O modules