Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter Version 4.2 Web Client User's Guide
- Introduction
- About Administration Console
- Using Administration Portal
- Registering vCenter Server by nonadministrator user
- Registering vCenter server
- Uploading license to Administration Portal
- Managing the virtual appliance
- Restarting virtual appliance
- Changing host name of virtual appliance
- Updating virtual appliance repository location and virtual appliance
- Upgrading OMIVV from existing version to current version
- Updating appliance through backup and restore
- Downloading the troubleshooting bundle
- Setting up HTTP proxy
- Setting up Network Time Protocol servers
- Configuring deployment mode
- Generating Certificate Signing Request
- Uploading HTTPS certificate
- Setting up global alerts
- Managing backup and restore
- About vSphere client console
- Using Administration Portal
- Managing multiple appliances
- Accessing OpenManage Integration from web client
- OpenManage Integration for VMware vCenter licensing
- Appliance configuration for VMware vCenter
- Using Baseline tab
- Profiles
- Inventory and warranty management
- Events, alarms, and health monitoring
- About firmware updates
- Chassis management
- Deploying hypervisor
- Device discovery
- Provisioning
- System profiles
- Managing System profiles
- Configuring hardware profile
- Creating hypervisor profile
- Creating deployment templates
- About deployment wizard
- Deployment job timing
- Downloading custom Dell EMC ISO images
- About host, bare-metal, and iDRAC compliance
- Security roles and permissions
- Frequently Asked Questions-FAQ
- Frequently Asked Questions-FAQ
- Export All button fails to export to .CSV file in Google chrome
- iDRAC license type and description are displayed incorrectly for non-compliant vSphere hosts
- Dell EMC icon is not displayed after unregistering vCenter from earlier OMIVV version and then registering same vCenter with later OMIVV version
- Dell provider is not displayed as health update provider
- Inventory failing when performing firmware update task on ESXi 5.x host
- Host inventory or test connection fails due to invalid or unknown iDRAC IP.
- On running fix noncompliant vSphere hosts wizard, the status of a specific host is displayed as Unknown
- Dell privileges that are assigned while registering the OMIVV appliance are not removed after unregistering OMIVV
- OMIVV does not display all the relevant logs when trying to filter a severity category
- How do I resolve error code 2000000 caused by VMware Certificate Authority-VMCA
- In Administration Console, Update Repository Path is not set to default path after I reset appliance to factory settings
- Warranty and inventory schedule for all vCenters is not applying when selected from the job queue page
- What should I do when a web communication error in the vCenter web client appears after changing the DNS settings in OMIVV
- The settings page fail to load, if I navigate away and again go back to the settings page
- Task cannot be scheduled for the time in the past- error in inventory schedule and warranty schedule page of Initial Configuration Wizard appear
- Installation date appears as 12-31-1969 for some of the firmware on the firmware page
- Successive global refresh cause exception to be thrown in the recent task window.
- Why is web client UI distorted for few Dell screens in IE 10
- I am not seeing OpenManage Integration icon in web client even if registration of plug-in to vCenter was successful
- Even if repository has bundles for selected 11G system, firmware update displaying that there are no bundles for firmware update
- Why is DNS configuration settings restored to original settings after appliance reboot if appliance IP and DNS settings are overwritten with DHCP values
- Using OMIVV to update the Intel network card with firmware version of 13.5.2 is not supported
- Using OMIVV to update Intel network card from 14.5 or 15.0 to 16.x fails due to staging requirement from DUP
- Why trying firmware update with invalid DUP, hardware update job status on vCenter console neither fails nor times-out for hours, although job status in LC prompts as FAILED
- Why does Administration Portal display unreachable update repository location
- Why did system not enter maintenance mode when I performed one-to-many firmware update
- Chassis global health still healthy when some of power supply status has changed to critical
- Processor version is displayed as “Not Applicable” in processor view in system overview page
- Does OMIVV support vCenter in linked mode
- What are required port settings for OMIVV
- Password is not changed for user used for bare-metal discovery after successfully applying hardware profile or system profile that has same user with new changed credentials in iDRAC user list
- Unable to view new iDRAC version details listed on vCenter hosts and clusters page
- How can I test event settings by using OMSA to simulate temperature hardware Fault
- Although OMSA agent is installed on OMIVV host system, I still get error message that OMSA is not installed.
- Can OMIVV support ESXi with lockdown mode enabled
- When I tried to use lockdown mode, it fails
- Creation of hardware profile fails if I am using reference server
- Attempting to deploy ESXi on server fails
- Hypervisor deployments failing on Dell PowerEdge R210 II machines
- Auto discovered systems are displayed without model information in Deployment wizard
- NFS share is set up with ESXi ISO, but deployment fails with errors mounting share location
- How do I force remove virtual appliance from vCenter
- Entering a Password in the Backup Now Screen Receives an Error Message
- In vSphere web client, clicking Dell server management portlet or Dell icon returns 404 error
- What should I do as firmware update failed
- What should I do as vCenter registration failed
- Performance during connection profile test credentials is slow or unresponsive
- Does OMIVV support VMware vCenter server appliance
- Firmware level not updated when I have performed firmware update with Apply on Next reboot option and system was rebooted
- Host still displayed under chassis even after removing host from vCenter tree
- In Administration Console, Update Repository Path is not set to default path after I reset appliance to factory settings
- After backup and restore of OMIVV, alarm settings are not restored
- Hypervisor deployment fails when NPAR is enabled on a target node and disabled in System Profile
- Available virtual appliance version displays wrong information when the available version is lesser than the current version
- The 267027 exception is thrown while adding a 12G bare-metal server with an Express license
- During OS deployment on 14G, hardware profile apply fails due to iDRAC error
- OMIVV RPM upgrade fails when proxy is configured with domain user authentication
- Unable to apply System Profile that has PCIe card in the FX chassis
- Bare-metal deployment issues
- Frequently Asked Questions-FAQ
- Related Documentation
- System specific attributes
- Customization attributes
- Additional information
- Component vs. baseline version comparison matrix
5. After you install an iDRAC license, run an inventory job for the vSphere host and return to this page after the inventory job is
successfully complete for the host to be compliant.
Viewing baseline compliance
The Baseline Compliance page displays the baseline compliance status based on the drift detection for all OMIVV-managed
vSAN hosts associated with the Cluster profile.
● Configuration Compliance—Displays the drift in attributes between the System profile used in the Cluster profile and the
associated vSAN hosts.
●
Firmware and Driver Compliance—Displays the firmware and driver version drift between the Firmware and/or Driver
Repository Profiles used in the Cluster profile and the associated vSAN hosts.
1. On the OpenManage Integration for VMware vCenter page, click Manage > Compliance > Baseline Compliance.
A table is displayed that lists the non-compliant hosts that are associated with the baseline along with the host IP or FQDN,
vCenter IP or FQDN, cluster name, cluster profile name, configuration compliance status, firmware compliance status, and
driver compliance status.
NOTE: Only non-compliant hosts are displayed on the Baseline Compliance page.
The compliance categories are:
● Compliant—Indicates that the components in the host comply with the associated profiles in baseline.
● Non-compliant—Indicates that the components in the host do not comply with the associated profiles in baseline.
● Not Applicable—Indicates that firmware, or driver, or System profiles are not associated to the cluster profile.
a. To view further details of a host, select a desired host.
You can view the HostName and Last Drift Detection Time in the bottom pane.
b. To swap the columns within the table, drag columns within the data grid.
c. To filter the content of the data grid, use Filter.
NOTE:
You can view the following information about the Baseline Compliance page:
● Total number of non-compliant hosts
● Total number of non-compliant clusters
● Total number of hosts and clusters that are associated with the baseline
● Total number of non-compliant hosts distributions of drift type
2. After a successful drift detection job, the hosts that are associated with the baseline are listed in the table. To view the drift
details, select a desired host, and click Show Drift Details.
The Drift Details dialog box is displayed.
3. In the Drift Details dialog box, you can view the following:
● If the compliance drift detection job fails, the compliance status is displayed as "non-compliant" along with the reason for
failure. Use the reason indicated to resolve the issue.
● If the drift detection job is successful, the compliance status is displayed as "non-compliant" and the following details are
displayed on the Drift Details page:
For Hardware:
○ Instance—Indicates the hardware component name.
○ Group—Indicates the group name of the attributes.
○ Attribute Name—Indicates the attribute name.
○ Current Value—Indicates the host value.
○ Baseline Value—Indicates the baseline value.
○ Drift Type—Indicates the reason for non-compliance. For more information about the drift type, see Component vs.
baseline version comparison matrix on page 159.
For Firmware and Driver:
○ Component Name—Indicates the name of the component.
○ Current Value—Indicates the host value.
○ Baseline Value—Indicates the baseline value.
○ Drift Type—Indicates the reason for non-compliance. For more information about the drift type, see Component vs.
baseline version comparison matrix on page 159.
○ Criticality(for firmware)—Indicates the importance level of updating the version of an identified component.
○ Recommendation(for driver)—Indicates the importance level of updating the version of an identified component.
126
About host, bare-metal, and iDRAC compliance