- 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
Chassis Direct
The Chassis Direct feature in OME-Modular enables users to access management consoles such as iDRAC and management module of devices on the chassis. The MX7000 chassis has several USB ports. The Right Control Panel (RCP) on the front of the chassis has three USB ports. Two ports are regular sized USB-A ports, for keyboards and mouse used for the chassis level KVM. The third port is a Micro-AB port that supports USB OTG. To use Chassis Direct, connect the USB OTG port to a laptop. The processor on the management module emulates a USB network interface and provides a network bridge into the management VLAN. The network is same that Quick Sync 2 bridges for OpenManage Mobile Wi-Fi access.
When network time protocol setting is not enabled, RCP replacement does not restore system time. The real-time clock on the new RCP is used as system time of the lead chassis and the same gets synced to all member chassis. This action may result in member OME-Modular reboot and MM redundancy loss for some time. Redundancy should be restored successfully after few minutes.
Remove the USB cable that is connected to the front panel and perform complete AC or DC power cycle the chassis.
With the system that is connected to the USB OTG port on the chassis, you can access the MM user interface and iDRAC user interface or KVM. You can get access by launching a browser on the laptop and entering the URL, https://ome-m.local. A chassis phonebook page which contains a list of entries to the available devices on the chassis, is displayed. This option provides a better experience than the front panel KVM, which provides access only the command-line prompt access for OME-Modular.
Select the check box to enable accessing the MX7000 chassis from a host such as a laptop or server, using a USB On-The-Go (OTG) cable. Connect the USB OTG cable from the host to the micro USB port on the front panel (right control panel) of the MX7000 chassis. On successful connection, LED under the micro-USB on the right control panel of MX7000 chassis turns green and USB Ethernet adapter is displayed on the host. The chassis is automatically configured with an IPV4 and IPV6 address. After ensuring that the addresses are configured, open a web browser and enter the URL, https://ome-m.local in the address bar.
On laptops running Windows, if the IPV6 traffic is blocked, check the Remote Network Driver Interface Specification (RNDIS) interface for IPv6 address. You may be able to access chassis phonebook page through IPv4, but iDRAC and OME-Modular web consoles are inaccessible. In that case, enable IPv6 traffic flow on the system.
When you enable or disable the Chassis Direct feature in OME-Modular, the following error codes are displayed:
The Chassis Direct feature in OME-Modular has a mutual exclusivity with the Quick Sync feature. Before downgrading the management module firmware from 1.10.00 version to an earlier version, remove the USB cable that is connected to the front panel of chassis. If USB cable is not removed and 1.10.00 firmware is downgraded, the Quick Sync feature may be degraded. Perform complete AC or DC power cycle of chassis to restore Quick Sync back to health.
| Error code | Chassis Direct LED blink status | Description and resolution |
|---|---|---|
| 1 | Amber | The USB network link is down as the Chassis Direct feature is disabled.
Resolution—Enable the Chassis Direct and reattach the USB cable to access the chassis phonebook. |
| 2 | Amber | The USB network link does not come up as the chassis internal USB operation failed.
Resolution—If the issue persists, reattach the USB cable to the laptop or perform complete AC or DC power cycle of the chassis. |
| 3 | Amber | The USB network link fails to come up owing to an issue on the host laptop.
Resolution—If the issue persists, reattach the USB cable. |
| 4 | Turned off | The USB network link is down as the USB cable is disconnected.
Resolution—Reattach the USB cable for the link to come up. |
If the Chassis Direct feature is disabled and the USB cable is inserted, the Chassis Direct LED turns amber and the alert, USR0197, is displayed on the OME-Modular web interface. You can see the alert only if you have logged in to OME-Modular using the public network. If you repeat the action within a short interval, the alert is not displayed. However, the Chassis Direct LED remains amber as the MM suppresses consecutive duplicate alerts.
NOTE: While using Internet Explorer to access the phonebook page, a custom certificate larger than 46 Kb results in TLS error. Change the certificate or use a different browser.
NOTE: If you have a custom certificate that is uploaded on 1.40.xx and you downgrade the OME-Modular to earlier version, downgraded chassis restores the self-signed certificate. Manually upload a custom certificate in the chassis.
Diagnose Chassis Direct connection
If you are unable to establish a secure connection with ome-m.local from your web browser using Chassis Direct, it may be because of your web browser safety features. For example, macOS integrated security settings prevents you from accessing a website that it does not consider it as secured. The error messages can vary depending on the browser, it may display "can't establish a secure connection to the server" on Safari, and "Revoked Certificate" on Google Chrome. You can resolve this issue either by uploading a trusted SSL web certificate to the Management Module UI or accepting the SSL certificate of the ome-m.local.Obtaining the SSL certificate of the ome-m.local.
- Go to the ome-m.local and click lock icon on the address bar.
- Select View/Show Certificate and then click Details.
- Verify and save the certificate on your device.
Installing SSL certificate of the ome-m.local to Keychain Access application on the macOS.
- Go to the Keychain Access application on the macOS and click Certificates.
- Drag and drop the downloaded certificate into the Keychain Access Certificates screen.
Setting preference on the
Keychain Access application to accept the SSL certificate of the
ome-m.local .
- Double-click the downloaded certificate to set the system preference.
- Expand the Trust option and select Always Trust preference for the certificate.
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: <>()\