- Notes, cautions, and warnings
- Revision history
- Overview
- Updating firmware for PowerEdge MX solution
- MX7000 Solution Baselines
- Upgrading Ethernet switch using DUP
- OME-Modular licenses
- Logging in to OME-Modular
- Logging in to OME–Modular as local, Active Directory, or LDAP user
- Logging in to OME-Modular using OpenID Connect
- OME-Modular home page
- Viewing device health
- Setting up chassis
- Initial configuration
- Configuring chassis settings
- Managing chassis
- Chassis groups
- Controlling chassis power
- Backing up chassis
- Restoring chassis
- Ethernet switch backup instructions
- Exporting chassis profiles
- Managing chassis failover
- Troubleshooting in chassis
- Extracting logs
- Blinking LEDs
- Interfaces to access OME-Modular
- Viewing chassis hardware
- Viewing chassis alerts
- Viewing chassis hardware logs
- Configuring OME–Modular
- Managing compute sleds
- Managing Profiles
- Managing storage
- Managing templates
- Managing identity pools
- Ethernet IO Modules
- MX Scalable Fabric architecture
- SmartFabric Services
- Managing networks
- Managing Fibre Channel IOMs
- Managing firmware
- Monitoring alerts and logs
- Monitoring audit logs
- Use case scenarios
- Troubleshooting
- Storage
- Firmware update is failing
- Storage assignment is failing
- SAS IOM status is downgraded
- SAS IOM health is downgraded
- Drives on compute sled are not visible
- Storage configuration cannot be applied to SAS IOMs
- Drives in OpenManage are not visible
- iDRAC and OpenManage drive information do not match
- The assignment mode of storage sled is unknown
- Unable to access OME-Modular using Chassis Direct
- Troubleshooting lead chassis failure
- Storage
- Recommended slot configurations for IOMs
- Updating components in phased update order through manual orchestration
- Creating validated firmware solution baseline using Dell Repository Manager
- Upgrading networking switch using different OS10 DUP versions
- Upgrading networking switch using CLI
- CLI commands not part of chassis backup
- VMware ESXi/MX Baseline Validation Matrix
- MX7000 Solution Baselines for previous versions
- OME-Modular firmware update matrix for previous versions
Dell OpenManage Enterprise-Modular Edition Version 2.00.00 for PowerEdge MX7000 Chassis User's Guide
Upstream network switch requirements
It is recommended, but not required, that PowerEdge MX switches are connected to a pair of redundant upstream switches. When you are connecting a pair of switches in Fabric mode to an upstream switch pair, ensure that:
- Both upstream switches must be connected to each other using technologies such as VLT or VPC.
- The upstream switch ports must be in a port channel using LACP.
NOTE: The LACP option is supported on Ethernet uplinks only.
- A compatible Spanning Tree Protocol is configured. For more information, see the section, Spanning Tree Protocol.
Spanning Tree Protocol
OpenManage Modular v1.20.00 and OS10 versions later than 10.5.0.5 include a new Ethernet uplink type that does not require STP. The No STP Ethernet uplink is now the recommended uplink type for all SmartFabric installations. See the Dell PowerEdge MX Networking Deployment Guide for upstream switch configuration instructions.
The legacy Ethernet uplink type that does require STP is still supported. If you are creating a legacy Ethernet uplink, ensure that the correct STP type is selected.
OS10 defaults to RPVST+ as the Spanning Tree protocol. To change STP modes, use the spanning-tree mode command. Use the spanning-tree mode command to change STP modes. For steps, see the OS10 Enterprise Edition User Guide.
NOTE: During MX deployment, if the Spanning Tree is enabled, assign the Top of Rack (ToR) switch as root bridge to avoid traffic drop during convergence.
NOTE: If the upstream network is running RSTP, change from RPVST+ to RSTP before physically connecting the switches to the upstream network. Failure to do so may cause a network outage.
For more information about SmartFabric uplinks, see the PowerEdge MX SmartFabric Configuration and Troubleshooting Guide.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\