Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter for Desktop Client User's Guide Version 3.2
- 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
- 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
- Managing Connection Profiles
- Understanding System Event Logs In vSphere Client Host View
- About Firmware Updates
- Advanced Host Management Using vCenter
- Hardware Prerequisites
- 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
- Using the Administration Console
- Virtual Appliance Management
- Setting up Global Alerts
- Managing Backup And Restore
- Understanding the vSphere Client Console
- Configuring Network Settings
- Changing The Virtual Appliance Password
- Setting The Local Time Zone
- Rebooting Virtual Appliance
- Resetting The Virtual Appliance To Factory Settings
- Refreshing the Console View
- Logging out from the console
- Read-only User Role
- Upgrading OpenManage Integration Plugin from 3.0 version to the current version
- Migration Path to migrate from 2.x to 3.1
- Troubleshooting
- Frequently Asked Questions (FAQ)
- OMIVV cannot act as a provisioning server during the auto discovery process
- Intermittent Inventory failure for 1st time after OSD
- Test connection for iDRAC in the connection profile page fails in DNC once OSD is successful
- Dell privileges that are assigned while registering the OMIVV appliance are not removed after unregistering OMIVV
- If vCenter is idle for few hours, the OMIVV content is replaced by a "!" icon on clicking the OpenManage Integration tab and Management Center. What should I do to resume the session?
- Dell Management Center does not display all the relevant logs when trying to filter a severity category. How can I view all the logs?
- How can I change the status of the OMIVV plug-in to Enabled?
- 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?
- 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.
- On running a warranty retrieval job, the warranty job status is not listed in the Warranty Job Queue page
- 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 required port settings for OMIVV?
- 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?
- 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?
- Bare Metal Deployment Issues
- Contacting Dell
- OpenManage Integration for VMware vCenter Related Information
- Frequently Asked Questions (FAQ)
- Virtualization-related Events For Dell PowerEdge Servers
- _
Shared Network
Folder
Created with Dell Repository Manager™. These local repositories are on CIFS or NFS file share.
NOTE: Once the repository is created, save it to a location that the registered hosts can access. Repository passwords
cannot exceed 31 characters. Do not use any of the following characters in a password: @, &, %, ', ", ,(comma), <, >
The Firmware Update Wizard always checks for the minimum firmware levels for iDRAC, BIOS, and Lifecycle Controller, and
attempts to update them to required minimum versions. Once iDRAC, Lifecycle Controller, and BIOS firmware versions meet
minimum requirements, the Firmware Update wizard allows updates for all firmware including: iDRAC, Lifecycle Controller, RAID,
NIC/LOM, Power Supply, BIOS, and so on.
Related Information:
●
Setting Up The Firmware Repository on page 24
Running The Firmware Update Wizard
This functionality is only available for 11th and later generations Dell servers that have either an iDRAC Express or Enterprise
card.
NOTE: To safeguard against browser timeout issues, change the default timeout to 30 seconds. 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.
NOTE: For trial/evaluation license, you can use Firmware wizard as long as license is not expired.
To run the Firmware Update Wizard:
1. In vSphere Client > OpenManage Integration tab > Host Information, click Firmware > Run Firmware Update
Wizard.
2. To use the Load a single firmware update from a file option:
a. Enter the file path in the following format:
CIFS: \\<host accessible share path>\<FileName>.exe or
NFS: host:/share/filename.exe
b. If you have NFS, skip to step 7 or enter the User Name and Password in a domain format that has access to the share
drive.
c. Continue to step 7.
Alternatively, to use the Update from repository option:
a. Select Update from repository.
b. Make sure that you have a network connection to ftp.dell.com.
c. Click Next.
3. Select the bundle for your host and click Next.
NOTE:
● 64-bit bundles are not supported for 12th generation hosts with iDRAC version 1.51 and earlier.
● 64-bit bundles are not supported for 11th generation hosts on all iDRAC versions.
4. Select the desired firmware updates and click Next. The components that are either a downgrade, already up-to-date,
or currently scheduled for update are not selectable. If you select the Allow Components to be Downgraded check
box, select the options that are listed as Downgrade. Selecting this option is only recommended to advanced users who
understand the implications of downgrading firmware.
5. Select the desired restart option.
● Enter maintenance mode, apply updates, and restart.
Host goes into maintenance mode. If the host cannot enter maintenance mode, then the host is not restarted and the
update is applied during the next reboot. Select the Exit maintenance mode after firmware update completes check
box, to exit maintenance mode after the update.
● Apply updates on next reboot.
To avoid a service interruption, it is recommended that the host enters maintenance mode before the reboot.
End-To-End Hardware Management
41