Users Guide
Table Of Contents
- Dell EMC OpenManage Enterprise-Modular Edition for PowerEdge MX7000 Chassis User's Guide
- Contents
- 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
- Exporting chassis profiles
- Managing chassis failover
- Troubleshooting in chassis
- Blinking LEDs
- Interfaces to access OME-Modular
- Viewing chassis hardware
- Viewing chassis alerts
- Viewing chassis hardware logs
- Configuring OME–Modular
- Viewing current configuration
- Configuring users and user settings
- Configuring login security settings
- Configuring alerts
- 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
- Creating validated firmware solution baseline using Dell Repository Manager
- Upgrading networking switch using different OS10 DUP versions
- Upgrading networking switch using CLI
NOTE: Setting Auto Negotiation to false and choosing a network port speed may result in the chassis losing link
to the network switch in Top of Rack, or to the neighbor chassis, if running MCM. It is recommended that the Auto
Negotiation is set to true for most use cases.
Table 9. Top of the Rack Support Matrix for management module and management module uplink
Top of the Rack Switch
Configuration
Management Module
Configuration
Supported for Management Module Uplink (YES
or NO)
100 Mbps (Auto negotiation
OFF)
100 Mbps (Auto negotiation OFF) YES
10 Mbps (Auto negotiation
OFF)
10 Mbps (Auto negotiation OFF) YES
Auto Neg ON Auto Negotiation ON YES
100 Mbps (Auto negotiation
OFF)
Auto Negotiation ON NO
10 Mbps (Auto negotiation
OFF)
Auto Negotiation ON NO
Auto Negotiation ON 100 Mbps (Auto negotiation OFF) NO
Auto Negotiation ON 10 Mbps (Auto negotiation OFF) NO
5. In the IPv4 Settings section, configure the following:
● Enable IPv4
● Enable DHCP
● IP Address
● Subnet Mask
● Gateway
● Use DHCP to Obtain DNS Server Addresses
● Static Preferred DNS Server
● Static Alternate DNS Server
6. In the IPv6 Settings section, configure the following:
● Enable IPv6
● Enable Autoconfiguration
● IPv6 Address
● Prefix Length
● Gateway
● Use DHCPv6 to Obtain DNS Server Addresses
● Static Preferred DNS Server
● Static Alternate DNS Server
NOTE:
The static IPv6 IP address that is already configured is applied and displayed in OME–Modular when the
configuration is changed from static to DHCP IP.
7. Enable or disable the VLAN for the chassis. You can configure the VLAN settings only if the Register with DNS check box
is cleared.
You can change from a VLAN network to a non-VLAN network, or move from a non-VLAN network to a VLAN network, only
if Register with DNS check box is cleared.
By default, the IPv4 settings are enabled and the DNS registration is disabled with a default name. You can modify the name
using any local interfaces such as OpenManage Mobile.
NOTE:
Ensure that the network cable is plugged to the correct port when you modify the VLAN state for the change to
be effective.
Isolate the chassis management from the data network as the uptime of a chassis that is improperly integrated into your
environment cannot be supported or guaranteed. Due to the potential of traffic on the data network, the management
interfaces on the internal management network are saturated by traffic that is intended for servers. It results in OME–
Modular and iDRAC communication delays. These delays may cause unpredictable chassis behavior, such as OME–Modular
displaying iDRAC as offline even when it is up and running, which in turn causes other unwanted behavior. If physically
Logging in to OME-Modular
39