Users Guide
Table Of Contents
- 1 Introduction
- 2 SmartFabric Services for PowerEdge MX: An overview
- 3 SmartFabric mode requirements, guidelines, and restrictions
- 3.1 Create multi-chassis management group
- 3.2 Upstream network requirements
- 3.3 VLAN scaling guidelines
- 3.4 Configuring port speed and breakout
- 3.5 Switch slot placement for SmartFabric mode
- 3.6 Switch-to-Switch cabling
- 3.7 NIC teaming guidelines
- 3.8 Maximum Transmission Unit (MTU) behavior
- 3.9 Other restrictions and guidelines
- 4 Creating a SmartFabric
- 4.1 Physically cable MX chassis and upstream switches
- 4.2 Define VLANs
- 4.3 Create the SmartFabric
- 4.4 Configure uplink port speed or breakout, if needed
- 4.5 Create Ethernet uplink
- 4.6 Configure Fibre Channel universal ports
- 4.7 Create Fibre Channel uplinks
- 4.8 Configuring the upstream switch and connect uplink cables
- 5 Deploying a server
- 6 SmartFabric operations
- 7 Switch operations
- 8 Validating the SmartFabric deployment
- 9 SmartFabric troubleshooting
- 9.1 Troubleshooting errors encountered for port group breakout
- 9.2 Troubleshooting Spanning Tree Protocol (STP)
- 9.3 Verify VLT/vPC configuration on upstream switches
- 9.4 Discovery of FEM and compute sleds
- 9.5 Troubleshooting uplink errors
- 9.6 Troubleshooting FC/FCoE
- 9.7 SmartFabric Services – Troubleshooting commands
- 10 Uplink configuration scenarios
- 10.1 Scenario 1 - SmartFabric deployment with Dell EMC PowerSwitch Z9100-ON upstream switches
- 10.2 Scenario 2 - SmartFabric connected to Cisco Nexus 3232C switches
- 10.3 Scenario 3: Connect MX9116n FSE to Fibre Channel storage - NPIV Proxy Gateway mode
- 10.4 Scenario 4: Connect MX9116n FSE to Fibre Channel storage - FC Direct Attach
- 10.5 Scenario 5: Connect MX5108n to Fibre Channel storage - FSB
- 10.6 Scenario 6: Configure Boot from SAN
- A Hardware used in this document
- B Dell EMC Unity information
- C Additional information
- D Validated components
- E Technical resources
- F Support and feedback
54 Dell EMC PowerEdge MX SmartFabric Configuration and Troubleshooting Guide
Note: Any configuration not completed by the OME-M console is lost when switching between IOM operating
modes.
6.8 Module replacement process in SmartFabric
Dell EMC PowerEdge MX platform gives you an option to replace the I/O Modules in a SmartFabric mode in
case of any errors or failures. MX9116n FSE and MX5108n can be replaced with another same type of I/O
Module. In case of errors or failures, replace the old IOM with the new IOM using Linux command.
For Module Replacement process, follow the steps:
1. Physically replace the IOM.
2. Identify the master IOM in a fabric.
3. Execute the process of module replacement from the master IOM using the module replacement
command.
6.8.1 Physically replace the IOM
Follow the below instructions to physically replace IOM:
• Identify the faulty IOM to replace. Disconnect the cables connected to faulty IOM.
• Insert the new IOM in the same slot as the failed IOM. The IOM should be in SmartFabric and must
be up and running.
• The model of the IOM should be same.
• The new IOM should have the same version of SmartFabric OS10 as the old IOM.
• Confirm if the new IOM has been recognized by OME-M before proceeding further.
6.8.2 Identify the master IOM in a fabric
To identify the master IOM in the fabric, run sfs_master_details.py command on the Linux shell prompt
the IOM. To run the above command, follow the instructions below:
1. Login to the Linux shell
OS10# system bash
admin@MX9116n-A1#:~$
2. Go to the bin directory on SmartFabric OS10 by running cd /opt/dell/os10/bin command. This
directory will have all the python scripts to run for the module replacement process.
• Identify the master IOM by running sfs_master_details.py.
admin@MX9116N-A1:/opt/dell/os10/bin$sfs_master_details.py
• If you run the command on master IOM, the output will be I am the Master. If you run the
command on other member IOMs it will return the IPv6 address of master IOM.
For Example:
The console displays the following output on Master IOM:
admin@MX9116N-A1:/opt/dell/os10/bin$sfs_master_details.py
I am the Master