Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter for Desktop Client User's Guide Version 3.0
- Overview
- OpenManage Integration for VMware vCenter Configuration
- Steps to Configure or Edit the OpenManage Integration for VMware vCenter
- OpenManage Integration for VMware vCenter Home Page
- Configuration Wizard welcome page
- Creating a new Connection Profile [Wizard]
- Configuring Events And Alarms [Wizard]
- Setting Up A Proxy Server [Wizard]
- Scheduling Inventory Jobs [Wizard]
- Running A Warranty Retrieval Job [Wizard]
- Configuring the Deployment Credentials [Wizard]
- Setting The Default Firmware Update Repository [Wizard]
- Enabling The OMSA Link [Wizard]
- Configuring NFS Shares
- Settings Overview
- About Host, Bare Metal, and iDRAC Compliance Issues
- Upgrading OpenManage Integration for VMware vCenter
- About OpenManage Integration for VMware vCenter Licensing
- End-To-End Hardware Management
- Monitoring the Datacenter And Host System
- vSphere Client Host Overview
- About Inventory Schedule
- Viewing Storage Inventory
- Viewing Host Power Monitoring
- Displaying The Entire Datacenter Hardware Configuration And Status
- Managing Connection Profiles
- Understanding System Event Logs In vSphere Client Host View
- About Firmware Updates
- Advanced Host Management Using vCenter
- Hardware Management
- Provisioning Overview
- Understanding Deployment Job Times
- Server States Within The Deployment Sequence
- Downloading Custom Dell ISO Images
- Understanding How To Configure A Hardware Profile
- About Managing Hardware Profiles
- Creating A New Hypervisor Profile
- Managing Hypervisor Profiles
- Building A New Deployment Template
- Running The Deployment Wizard
- Deployment Wizard - Step 1: Select Servers
- Deployment Wizard Step 2: Deployment Templates
- Deployment Wizard Step 3: Global Settings
- Deployment Wizard Step 4: Server Identification
- Deployment Wizard Step 5: Connection Profile
- Deployment Wizard Step 6: Scheduling Jobs
- Understanding Job Queue
- Adding A Server Manually
- Removing A Bare Metal Server
- Console Administration
- Web-based Administration Console
- Managing vCenter Server Connections
- Virtual Appliance Management
- Setting up Global Alerts
- Managing Backup And Restore
- Understanding the vSphere Client Console
- Troubleshooting
- Frequently Asked Questions (FAQ)
- How can I change the status of the OMIVV plug-in to Enabled?
- How do I resolve error code 2046/2048?
- OMIVV version for is not updated from About Screen after the Appliance is updated
- Using OpenManage Integration for VMware vCenter to update an Intel Network card with the firmware version of 13.5.2 is not supported.
- Using OpenManage Integration for VMware vCenter to update an Intel Network card from 14.5 or 15.0 to 16.x fails due to staging requirement from DUP
- On trying a firmware update with an invalid DUP, the hardware update job status on the vCenter console neither fails nor times-out for hours, though the job status in LC says ‘FAILED’. Why is this happening?
- Administration Portal is still showing the unreachable Update Repository location.
- Why is the DNS configuration settings restored to original settings after appliance reboot if using DHCP for appliance IP and DNS settings overwritten
- Why did my system not enter maintenance mode when I performed a one-to-many firmware update?
- Even if my repository has bundles for selected 11G system, why is firmware update showing that I have no bundles for Firmware Update?
- Why Does My ESXi Deployment Fail on Servers Having a PERC S300 Boot Controller?
- How Come I See An Error Message Displayed After Clicking The Firmware Link?
- What generation of Dell servers does the OpenManage Integration for VMware vCenter configure and support for SNMP traps?
- How does the OpenManage Integration for VMware vCenter support more than three vCenters in Linked Mode?
- Does OpenManage Integration for VMware vCenter support vCenter in linked mode?
- What are the Required Port Settings for the OpenManage Integration for VMware vCenter?
- What are the Minimum requirements for successful installation and operation of the virtual appliance?
- Why is the password not changed for the user used for bare-metal discovery after successfully applying the hardware profile that has the same user with new changed credentials in the iDRAC user list?
- Why is the processor version “Not Applicable” in Processor view in the System overview page?
- Why is the DNS configuration settings restored to original settings after appliance reboot if using DHCP for appliance IP and DNS settings overwritten
- How come I do not see my new iDRAC version details listed on the vCenter Hosts & Clusters page?
- How Do I Test Event Settings by Using OMSA to Simulate a Temperature Hardware Fault?
- I Have the OMSA Agent Installed on a Dell Host System, But I Still Get an Error Message That OMSA is Not Installed. What Should I Do?
- Can the OpenManage Integration for VMware vCenter Support ESXi with Lockdown Mode Enabled?
- When I tried to use lockdown mode, it failed.
- On trying a firmware update with an invalid DUP, the hardware update job status on the vCenter console neither fails nor times-out for hours, though the job status in LC says ‘FAILED’. Why is this happening?
- What Setting Should I Use For UserVars.CIMoeMProviderEnable With ESXi 4.1 U1?
- I Am Using A Reference Server to Create a Hardware Profile But it Failed. What Should I Do?
- I Am Attempting to Deploy ESXi on a Blade Server and it Failed. What Should I Do?
- Why Are My Hypervisor Deployments Failing On R210 II Machines?
- Why Do I See Auto-discovered Systems Without Model Information in the Deployment Wizard
- The NFS Share is Set Up With the ESXi ISO, but Deployment Fails with Errors Mounting the Share Location.
- How Do I Force Removal of the Virtual Appliance?
- Entering a Password in the Backup Now Screen Receives an Error Message
- My Firmware Update Failed. What Do I Do?
- My vCenter Registration Failed. What Can I Do?
- Performance during Connection Profile Test Credentials is extremely slow or unresponsive.
- Does the OpenManage Integration for VMware vCenter support the VMware vCenter Server appliance?
- Does the OpenManage Integration for VMware vCenter support the vSphere Web Client?
- In the Administration Console, why the Update Repository Path is not set to default path after I reset the appliance to factory settings?
- After backup and restore of OpenManage Integration for VMware vCenter, why alarm settings are not restored?
- After performing a restore of OpenManage Integration for VMware vCenter, what should I do if the Dell Management Center icon is not displayed in the vSphere Client?
- Bare Metal Deployment Issues
- Contacting Dell
- OpenManage Integration for VMware vCenter Related Information
- Frequently Asked Questions (FAQ)
- Virtualization-related Events For Dell PowerEdge Servers
- _
Running The Fix Non-Compliant Bare Metal Server Wizard
Run the Fix Non-Compliant Bare Metal Server Wizard to fix non-compliant bare metal servers. For information about
compliance, see About Host And Bare Metal Compliance Issues.
To run the Fix Non-Compliant Bare Metal Server Wizard:
1. In the Dell Management Center, in the left pane, click Compliance > Bare Metal Servers.
2. In the Bare Metal Servers window, view the non-compliant hosts, then click Fix Non-Compliant Bare Metal Servers.
3. In the Fix Bare Metal Servers wizard, select the check boxes for the hosts you want to fix.
4. Click Next.
5. In the Summary window, review the actions that take place on the non-compliant bare metal servers.
6. Click Finish.
Re-checking Bare Metal Server Compliance
For servers you have fixed outside of the OpenManage Integration for VMware vCenter, you must run this manual server
compliance re-check. You can find this on the Dell Management Center, Compliance, Bare Metal Servers page.
To re-check bare metal server compliance:
1. In the Dell Management Center > Compliance > Bare Metal Servers page, click Re-check Compliance.
2. In the Non-Compliant Servers window, to refresh the list, click Refresh.
3. To run the re-check, click Check Compliance.
4. To abort the re-check, click Abort All Tests.
5. If you successfully fixed your system, the list refreshes and your system is removed from the list. If not, the non-compliant
system remains on the list.
6. When finished, click Done.
NOTE:
OMIVV requires the BIOS, LC and iDRAC firmwares to be at least at a minimal compliant level for the OMIVV to function
properly. For the Dell Servers which has BIOS, LC or iDRAC firmwares below the compliant level, see Using Dell™
Repository Manager to Create a Deployment Media (Bootable ISO) to Perform Systems Updates to manually update
the firmware.
iDRAC License Compliance
When you select the iDRAC License Compliance page, it runs a compliance test. This test lasts for a few minutes. The vSphere
hosts and bare metal servers listed on this page are non-compliant because they do not have a compatible iDRAC license. The
table displays the status of the iDRAC license. On this page you can see how many days remain on your license and update it
as required. If your Run inventory job link is disabled, that means there are no vSphere hosts that are non-compliant due to the
iDRAC license. If the Recheck Bare Metal Server Compliance link is disabled, that means there are no bare metal servers that
are non-compliant due to the iDRAC license.
1. In Dell Management Center, in the left pane, click Compliance.
2. Expand Compliance, and click iDRAC License.
Once you arrive to this page the compliance test runs. This is the same test that runs when you click Refresh.
3. If your license is out of date, click Purchase/Renew iDRAC License.
4. Log into the Dell License Management page and update or purchase a new iDRAC license.
Use the information on this page to identify and update your iDRAC.
5. After you install an iDRAC license, run an inventory job for vSphere hosts and return to this page after the inventory job
completes. For bare metal servers, recheck licensed bare metal server compliance.
28
Steps to Configure or Edit the OpenManage Integration for VMware vCenter