Release Notes

OME-Modular takes up to 30 minutes to fetch
network IOM inventory
Description When you insert a new network IOM into a chassis and do not refresh inventory, OME-Modular may take
up to 30 minutes to fetch inventory data.
Workaround Refresh inventory on the new IOM manually or wait until the next default inventory task is complete.
Systems affected All systems supported in this release
Tracking number 146808
Member chassis storage sleds inventory for all drives
displayed as encryption capable in lead chassis
Description Member chassis storage sled inventory for all drives is displayed as Encryption Capable in the lead
chassis though the drives do not support encryption.
Workaround In the MCM environment, you can get the correct Encryption Capable information directly from the
member chassis.
Systems affected No physical systems affected. Information may be displayed incorrectly for storage sleds installed on
member chassis, from the lead chassis web interface.
Tracking number 147384
HTTPS custom port in OME-Modular does not work
after upgrading to 1.10.00 or later
Description
Automatic redirection to HTTPS custom port does not work after updating to the OME-Modular
firmware.
Workaround Enter the hostname and custom port, for example, 10.10.10.10:1234, manually in the address bar of the
browser to access OME-Modular. Reconfiguring the custom port after the firmware update helps resolve
the issue.
Systems affected OME-Modular with customized HTTPS port that is updated to the OME-Modular 1.10.00 or later.
Tracking number 146489
Identity pool options missing in Edit Network view and
during deployment
Description
The identity pool options are not displayed when the name of a template or NIC teaming is changed after
restoring configuration to a new lead after retiring the existing lead. The identity pool options are not
displayed during deployment and in the Edit Network view. However, this does not affect deployed
identities that are displayed on the Identity Pools page.
Workaround
Clone the template and use the clone for all new device deployments.
Delete the old template, if it is not deployed.
If the old template is deployed, it works for the existing devices and can be retained.
Systems affected All systems supported in this release.
Tracking number 147605
14 Known issues