Release Notes
Important Notes
To visit Dell TechCenter for accessing whitepapers, blogs, wiki-articles, videos, product communities and forums, see
en.community.dell.com/techcenter/systems-management.
Known Issues
Issue 1
Newly created Dell Server HDD object’s metric are not reported.
Description: After upgrade of adapter from 1.0 to 1.1/1.2, the newly created Dell Server HDD object’s metric are not reported.
Resolution: After OpenManage Management Pack for vRealize Operations Manager Version 1.1/1.2 upgrade, you must stop data
collection and then start collecting again on the adapter instance, to reflect the correct HDD metrics. In case of multiple
instances, you need to perform the same task for individual adapters.
Versions/Systems Affected: All platforms
Issue 2
Chassis or server objects are not removed immediately after the objects are removed from the Connection profile.
Description: The server or chassis continues to exist in vROPS for almost an hour even after it is removed from the Connection
Profile.
Resolution: Wait for the next Health Metrics job to run.
Versions/Systems Affected: All platforms
Issue 3
Deleting the adapter instance times out, when there are more than 500 servers.
Description: Deleting the adapter instances from the solutions page may take longer time when the adapter is configured with
an OMIVV instance which has huge number of servers. Eventually the vROPS UI time out error occurs.
Resolution: No Resolution. In such cases, delete operations takes around 10-15 minutes to complete.
Versions/Systems Affected: All platforms
Issue 4
During manual discovery few components goes to Non_existance mode after metric collection failures.
Description: Dell highly recommends to use auto discovery. If Administrator decides to use manual discovery as the discovery
method, then whenever the extended metric collection or the health metric collection fails for any server or chassis, the
components may become Nonexistent in consecutive data collection cycles.
Resolution: User has to re-discover the server or change to auto discovery mode.
Versions/Systems Affected: All platforms
Issue 5
Few Warranty views are not localized.
Description: The warranty views might have few columns which are not localized, because some of the Instanced metrics like
Warranty metrics are not appearing in the localized languages.
Resolution: You can use the Warranty report to see the metrics.
3