Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter for Desktop Client User's Guide Version 3.1
- 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
- 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
- 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)
- 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 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?
- Bare Metal Deployment Issues
- Contacting Dell
- OpenManage Integration for VMware vCenter Related Information
- Frequently Asked Questions (FAQ)
- Virtualization-related Events For Dell PowerEdge Servers
- _
2. In the Profile Name and Description panel, enter the profile name, and a description that is optional that are used to help
manage custom connection profiles, and then click Next.
3. In the Associated Hosts section, select the hosts to be associated with the Connection Profile, and then click Next.
4. View the information about credentials and connection protocols and click Next.
5. In the iDRAC panel, type the iDRAC credential information.
a. For iDRACs already configured and enabled for Active Directory on which you want to use Active Directory, select the
Use Active Directory check box; otherwise configure the iDRAC local credentials. Enter User Name, Password, and
Verify Password. The user name can contain up to 16 characters including white space. The passwords must match and
use ASCII-printable characters only.
b. For Certificate Check, select Enable to download and store the iDRAC certificate and validate it during all future
connections, or select Disable to perform no check and not store the certificate.
6. Click Next.
7. In the Host panel, do the following:
a. You must select the Use Active Directory check box to enable active directory credentials. Enter the User Name,
Password, and Verify Password.
b. If you do not select Use Active Directory, enter the Password, for the root user and verify password. The passwords
must match.
c. For Certificate Check, select Enable to download and store the OMSA/ESXi certificate and validate it during all future
connections, or select Disable to perform no check and not store the certificate.
8. Click Next.
9. The Test Connection window tests the entered iDRAC and Host root Credentials on the selected servers. Test connection
is optional but is recommended.
● To begin the test, select the hosts, and click Test Selected. The other options are disabled.
● To abort all the tests before completion, click Abort All Tests.
10. To complete the profile, click Save.
11. To continue on to configure Events and Alarms, click Save and Continue.
Configuring Events And Alarms [Wizard]
Configure events and alarms using the Configuration Wizard or from the Dell Management Center, Settings option for Events
and Alarms. In order to receive the events from the servers, OMIVV is configured as the trap destination. For 12th generation
hosts and later, the SNMP trap destination is set in iDRAC. For hosts prior to 12th generation, trap generation is set in OMSA.
NOTE:
OMIVV supports SNMP v1 and v2 alerts for 12th generation hosts and later. For hosts prior to 12th generation,
OMIVV supports only SNMP v1 alerts.
To configure events and alarms, perform the following steps:
1. In the Configuration Wizard, under Event Posting Levels, select one of the following:
● Do not post any events — Blocks hardware events.
● Post All Events — Posts all hardware events.
● Post only Critical and Warning Events — Posts only critical or warning level hardware events.
● Post only Virtualization-Related Critical and Warning Events — Posts only virtualization-related critical and warning
events; this is the default event posting level.
2. To enable all hardware alarms, select the Enable Alarms for Dell Hosts check box.
NOTE: Dell hosts that have alarms enabled respond to critical events by entering maintenance mode.
3. In the dialog box that is displayed, click Continue to accept this change, or click Cancel.
NOTE: This step is only seen if Enable Alarms For Dell Hosts is selected.
4. To restore the default vCenter alarm settings for all managed Dell servers, click Restore Default Alarms.
It might take up to a minute before the change takes effect.
5. To continue the wizard, click Save and Continue.
NOTE:
Restoring the OMIVV appliance backup does not restore all the Alarm settings. However, in the OMIVV GUI, the
Alarms and Events field displays the restored settings. To resolve this issue, in the OMIVV GUI, in the Manage > Settings
tab, manually change the Events and Alarms settings.
16 Steps to Configure or Edit the OpenManage Integration for VMware vCenter