- Notes, cautions, and warnings
- Release summary
- Compatibility
- New and enhanced features
- Fixes
- Bandwidth and port details
- Single Sign-On with CSR
- Storage sled and storage IOM updates
- Root password application
- FCoE virtual MAC addresses
- OME-Modular unresponsive
- HTTPS firmware catalog share
- Compute sled firmware updates in member chassis
- Compute sled updates
- Failure of compute sled updates in MCM
- FIPS enabled systems
- Deployment and configuration job
- Migrating profiles
- Firmware update failure
- Login failure
- OME-Modular version information for member chassis
- Failure of compute sled updates in MCM
- Firmware update job status
- Single management module connectivity
- Important Notes
- Known issues
- Unable to restore network configuration attributes
- Fault list does not contain HWC2131
- Chassis KVM output may be lost after AC power outage in chassis
- ISL Cabling Diagram not shown correctly in Microsoft Edge and Internet Explorer
- Unable to view details of template created from a reference device
- Firmware catalog may be deleted automatically after editing
- Error displayed when creating a local user account under certain conditions
- Cannot perform a graceful shut down of all compute sleds
- Check Compliance operation fails to run and no error message is displayed
- Unable to deploy chassis profile after removing syslog or SNMP destinations
- Unable to edit firmware catalog in specific scenarios
- Unable to restore iDRAC from the lead chassis
- Unable to export chassis profile using hostname or FQDN
- Request to join a group fails when using Microsoft Edge or Internet Explorer
- Devices may not appear after being moved from the lead chassis to a member chassis
- Set Proxy operation fails when using a hostname ending with a numeric character
- Using special characters while setting iDRAC password causes error
- Descriptive error not displayed when compute sled is in lockdown mode and VLAN settings are changed
- Last run date for some jobs may be displayed incorrectly after firmware update
- Unable to start MM Update when IOMs or storage components are selected as chassis components while updating firmware from baselines
- IOM firmware updates fail intermittently when IOMs are selected as part of chassis component while updating firmware from baselines
- Multiple Firmware Update jobs start for IOMs or storage devices when IOMs or storage devices are selected while updating firmware from baselines
- OME - Modular slows down while deploying many compute sleds in 20 chassis setup
- PowerEdge MX 10GbT PTM is not displayed on chassis Group Topology page
- MCM Lead chassis does not display alerts from chassis components
- Bandwidth settings are not deployed on IOMs in fabric mode when an imported template is used
- Alerts are not received through SYSLOG, SNMP, or EMAIL after downgrading OME-Modular firmware
- Limitations
- Installation
- Resources and support
- Contacting Dell EMC
Dell EMC OpenManage Enterprise-Modular Edition Version 1.00.10 for PowerEdge MX7000 Chassis Release Notes
Last run date for some jobs may be displayed incorrectly after firmware update
- Description
- After firmware update, some jobs may display the last run date as "1970". The issue is only seen when NTP servers are configured as the time source. After a firmware update, the public network takes some time to get established, which delays synchronizing the system time with the NTP server. Any jobs run before the system time synchronizes to the NTP server, display the year as 1970.
- Workaround
- The date and time are fixed automatically when the next job is run.
- Systems affected
- PowerEdge MX7000
- Tracking number
- 115338
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: <>()\