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
- _
Updating Older Firmware Versions
Firmware must be at a minimum level for the Firmware Update Wizard to run. When it is not, you are offered options to help
update your firmware, prior to running the Firmware Update Wizard. Typically, firmware installed earlier than July 29, 2009
requires you to download and run an ISO file, see Firmware Updates. For firmware installed between July 29, 2009 and prior
to Oct. 14, 2010, you are offered an ISO bundle to automatically install from the OpenManage Integration for VMware vCenter.
Firmware updated after October 14th, 2010 runs the Firmware Update Wizard. Firmware updates are run from vSphere Client on
the host OpenManage Integration tab. To set up the repository, see Setting Up The Firmware Repository .
To update older firmware versions:
1. In vSphere Client, on the OpenManage Integration tab, under Host Actions, click Run Firmware Update Wizard.
The Update Required dialog displays when your host is at a lower level of firmware than the wizard supports. You will either
be asked to download and run an ISO file or be given a bundle of updates to run.
2. In the Update Required dialog box, do one of the following:
● To automatically exit maintenance mode after the firmware update, select the Exit maintenance mode after firmware
update completes check box.
● To enter maintenance mode to examine and/or test the machine before adding it back to the cluster, do not check the
check box.
3. Click Update.
4. The Success dialog box tells you that an update is now in progress.
If you chose to Exit maintenance mode after firmware update completes, the firmware update puts the host into
maintenance mode and then reboots automatically. Otherwise, it stays in maintenance mode.
5. Refer to the Recent Tasks area of the vSphere Client to watch the update progress.
After this procedure, run the Firmware Update Wizard again to make sure your firmware is completely updated.
Running the Update Firmware Wizard for Clusters and Datacenters
This functionality is only available for 11th and later generations of Dell servers that have either an iDRAC Express or iDRAC
Enterprise. If your firmware was installed on or after October 14th, 2010, you can automatically update your firmware versions
using the Firmware Update Wizard. This wizard only updates hosts that are part of a connection profile and compliant in terms
of firmware, CSIOR status, hypervisor, and OMSA status (11th generation servers only). If your host is not listed, run the
Compliance Wizard for vSphere Hosts from the OpenManage Integration for VMware vCenter or select the host that is not
listed from the Hosts and Clusters view and use the Firmware Update Wizard. It typically takes from 30 to 60 minutes to update
firmware components for each host. Enable DRS on a cluster so that virtual machines can be migrated when a host enters/exits
maintenance mode during the firmware update process. You can only schedule or run one firmware update task at a time.
If you want to export from the wizard, use the Export to CSV button. Search is available for locating a specific cluster,
datacenter, host, or any topic item from the datagrid except for Date Applied.
NOTE: Always update firmware together as part of the repository bundle: BIOS, iDRAC, and Lifecycle Controller.
NOTE: For information on changing the default timeout setting, see How Come I see an Error Message Displayed After
Clicking the Firmware Update Link in the Troubleshooting section of the User’s Guide.
You can view the status and manage Firmware update jobs from the Job Queue page. See, Viewing Firmware Update Status for
Clusters and Datacenters.
1. In the vSphere Client, under the Inventory heading select Hosts and Clusters.
2. In Hosts and Clusters, in the tree view, select a datacenter or a cluster and then select the OpenManage Integration
tab.
3. Click Update Firmware.
If this link is not enabled or if you get an popup message when you click this option, then there is a firmware update job in
progress or scheduled, close the dialog box, wait and try this again later. View the status of all jobs on the Firmware Update
Jobs tab in Job Queues.
4. In the Welcome page, review the information about the update before proceeding with the wizard.
5. Click Next.
6. In the Firmware Inventory page, review the components that are already installed on the systems.
7. Click Next.
8. In the Select Updated Bundles page, select the update bundles using the check boxes.
9. Click Next.
End-To-End Hardware Management
43