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
- _
● Creating A Connection Profile
● Viewing And Editing An Existing Connection Profile
● Deleting A Connection Profile
● Testing A Connection Profile
● Refreshing A Connection Profile
Viewing Or Editing An Existing Connection Profile
After you have configured a connection profile, you can edit the profile name, description, associated hosts, and iDRAC and
OMSA Agent credentials.
To view or edit an existing connection profile:
1. From the OpenManage Integration for VMware vCenter, select Connection Profiles.
2. Under Available Profiles, select the profile to view or edit and then click Edit/View.
3. In the Profile Name and Description page, enter the Connection Profile Name and an optional Connection Profile
Description that are used to help manage custom connection profiles.
4. In the Associated Hosts page, select the hosts for the connection profile and click Next.
5. In the Credentials page, read the information and click Next.
6. In the iDRAC page, under Credentials, do one of the following:
NOTE: The iDRAC account requires administrative privileges for updating firmware, applying hardware profiles, and
deploying hypervisor.
● 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 skip down to configure the iDRAC credentials.
○ In the Active Directory User Name text box, type the user name. Type the username in one of these formats:
domain\username or domain/username or username@domain. The user name is limited to 256 characters. Refer to
Microsoft Active Directory documentation for user name restrictions.
○ In the Active Directory Password text box, type the password. The password is limited to 127 characters.
○ In the Verify Password text box, type the password again.
○ In the Certificate Check drop-down list, select one of the following:
■ To download and store the iDRAC certificate and validate it during all future connections, select Enable .
■ To perform no check and not store the certificate, select Disabled.
● To configure iDRAC credentials without Active Directory, do the following:
○ In the User Name text box, type the user name. The user name is limited to 16 characters. Refer to the iDRAC
documentation for information about user name restrictions for your version of iDRAC.
NOTE:
The local iDRAC account requires administrative privileges for updating firmware, applying hardware
profiles, and deploying hypervisor.
○ In the Password text box type the password. The password is limited to 20 characters.
○ In the Verify Password text box, type the password again.
○ In the Certificate Check drop-down list, select one of the following:
■ To download and store the iDRAC certificate and validate it during all future connections, select Enable.
■ To perform no check and not store the iDRAC certificate, select Disabled.
7. Click Next.
8. In the Host Credentials page, under Credentials, do one of the following:
● For hosts already configured and enabled for Active Directory on which you want to use Active Directory, select the Use
Active Directory check box; otherwise skip down to configure your Host Credentials.
○ In the Active Directory User Name text box, type the user name. Type the username in one of these formats:
domain\username or domain/username or username@domain. The user name is limited to 256 characters. Refer to
Microsoft Active Directory documentation for user name restrictions.
38
End-To-End Hardware Management