Users Guide
1 | 71 | | | |
1 | 72 | | | |
1 | 73 | | | |
1 | 74 | | | |
1 | 75 | | | |
1 | 76 | | | |
1 | 77 | | | |
1 | 78 | SP0012 | SP0012 | up |
1 | 79 | | | |
1 | 80 | | | |
1 | 81 | | | |
1 | 82 | | | |
3 Congure the unit ID of the Fabric Expander with the service tag (provision name) in CONFIGURATION mode.
OS10(config)# unit-provision node/unit-id provision_name
• node/unit-id — Enter 1 for node with an unassigned unit ID from the show unit-provision output.
• provision_name — Enter the service tag of the Fabric Expander from the Chassis-service-tag eld in the show
discovered-expanders output.
4 Verify the discovered Fabric Expander and its virtual slot ID in EXEC mode.
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 71
Expander Module
When the Fabric Switching Engine discovers the Fabric Expander, it creates virtual ports by mapping each 8x25GE FEM breakout
interface in port groups 1 to 9 to a Fabric Expander virtual port.
Example: Fabric Expander virtual port mapping
Fabric Expander
service tag
Fabric Engine
QSFP28-DD port
group
Fabric Engine QSFP28-
DD 8x25GE interfaces
Fabric Expander
assigned unit ID
(virtual slot)
Fabric Expander virtual
ports
SKY003Q 1/1/1 1/1/17:1 71 1/71/1
1/1/17:2 1/71/2
1/1/17:3 1/71/3
1/1/17:4 1/71/4
1/1/18:1 1/71/5
1/1/18:2 1/71/6
1/1/18:3 1/71/7
1/1/18:4 1/71/8
80 PowerEdge MX Ethernet I/O modules