advertisement
OpenManage Integration for VMware vCenter for Desktop Client
User's Guide Version 3.2
April 2017
Rev. A00
Notes, Cautions, and Warnings
NOTE: A NOTE indicates important information that helps you make better use of your computer.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
NOTE: A WARNING indicates a potential for property damage, personal injury, or death.
Copyright © 2016 Dell Inc. All rights reserved.
This product is protected by U.S. and international copyright and intellectual property laws.
Dell ™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Contents
Chapter 3: Steps to Configure or Edit the OpenManage Integration for VMware vCenter.............14
Contents 3
4 Contents
Uploading a OpenManage Integration for VMware vCenter License to the Administration Console.... 65
Contents 5
If vCenter is idle for few hours, the OMIVV content is replaced by a "!" icon on clicking the
On running a warranty retrieval job, the warranty job status is not listed in the Warranty Job
Using OpenManage Integration for VMware vCenter to update an Intel Network card from 14.5
Why is the DNS configuration settings restored to original settings after appliance reboot if using
Even if my repository has bundles for selected 11G system, why is firmware update showing that
Why is the DNS configuration settings restored to original settings after appliance reboot if using
I Have the OMSA Agent Installed on a Dell Host System, But I Still Get an Error Message That
6 Contents
Can the OpenManage Integration for VMware vCenter Support ESXi with Lockdown Mode
The NFS Share is Set Up With the ESXi ISO, but Deployment Fails with Errors Mounting the
In the Administration Console, why the Update Repository Path is not set to default path after
Contents 7
1
Overview
Topics:
•
OpenManage Integration for VMware vCenter
•
•
How Does the OpenManage Integration for VMware vCenter Help With vCenter Administration
•
OpenManage Integration for VMware vCenter Features
•
OpenManage Integration for VMware vCenter
VMware vCenter is the primary console used by IT administrators to manage and monitor VMware vSphere ESXi hosts. In a standard virtualized environment, VMware alerts and monitoring are used to prompt an administrator to launch a separate console to resolve hardware issues. Today, using the OpenManage Integration for VMware vCenter, administrators have new capabilities to manage and monitor Dell hardware within the virtualized environment, such as:
● Alerting and environment monitoring
● Single server monitoring and reporting
● Firmware updates
● Enhanced deployment options
Key Features
Dell customers can use the OpenManage Integration for VMware vCenter to perform:
Inventory
Monitoring and
Alerting
Firmware
Updates
Deployment and
Provisioning
Service
Information
Inventory key assets, perform configuration tasks, and provide cluster and datacenter views of Dell platforms.
Detect key hardware faults and perform virtualization-aware actions (for example, migrate workloads or place host in maintenance mode).
Update Dell hardware to the most recent version of BIOS and firmware.
Create hardware profiles, hypervisor profiles, and deploy any combination of the two on bare-metal Dell
PowerEdge servers, remotely and without PXE using vCenter.
Retrieve warranty information from Dell online.
How Does the OpenManage Integration for VMware vCenter Help With vCenter Administration
OpenManage Integration for VMware vCenter provides additional virtualization functionality that supplements the current vCenter administration functions:
● Compresses tasks and adds management processes, such as firmware updates and bare-metal deployment, to the vCenter
Server Administration Console.
● Organizes deployment of multiple bare-metal servers without requiring Preboot Execution Environment (PXE).
● Provides additional intelligence (inventory, events, alarms) to diagnose server problems.
8 Overview
● Integrates with standard vCenter authentication, rules, and permissions.
OpenManage Integration for VMware vCenter
Features
The following are high-level features of the OpenManage Integration for VMware vCenter:
● Monitor Dell servers using the standard vCenter event and alarm subsystem
● Perform advanced hardware management and configuration
● Perform zero touch deployment of VMware ESXi hypervisors on bare-metal systems without using PXE
● Build hardware and VMware ESXi hypervisor profiles
● Perform firmware updates
● Troubleshoot infrastructure issues
● Generate report at the Datacenter and Cluster view—export to CSV file
● Integrate OpenManage Integration for VMware vCenter capabilities with standard vCenter roles and permissions
What's new in this release
This release of OpenManage Integration for VMware vCenter provides the following features:
● Support for Dell OpenManage Server Administrator (OMSA) version 8.5
● Support for VMware vCenter server version 6.0 U3
● Support for VMware ESXi version 6.0 U3
● Support for PowerEdge R830 platform
● Support for Non-Uniform Memory Access (NUMA) Fault Resilient Memory (FRM)
NOTE: The Auto discovery feature is not functional in this release. For more details about this, see
OMIVV cannot act as a provisioning server during the auto discovery process
on page 73
Overview 9
2
OpenManage Integration for VMware vCenter Configuration
The following sections provide step-by-step instructions for the OpenManage Integration for VMware vCenter initial configuration. Upgrade, uninstallation, and security role information are also covered in the following sections.
Topics:
•
Security Roles and Permissions
Security Roles and Permissions
The OpenManage Integration for VMware vCenter stores user credentials in an encrypted format. It does not provide any passwords to client applications to avoid any improper requests that could lead to issues. The Backup Database are fully encrypted using custom security phrases, and therefore the data cannot be misused.
By default, users in the Administrators group have all the privileges. Administrators can use all the functions of the OpenManage
Integration for VMware vCenter within VMware vSphere Client or Web Client. If you want a user with necessary privileges to manage the product, then create a role with necessary privileges, assign the role to a user, register a vCenter server using the user, and include both the Dell roles.
Data Integrity
Communication between the OpenManage Integration for VMware vCenter virtual appliance, Administration Console, and vCenter is accomplished using SSL/HTTPS. The OpenManage Integration for VMware vCenter generates an SSL certificate used for trusted communication between vCenter and the appliance. It also verifies and trusts the vCenter server's certificate before communication and the OpenManage Integration for VMware vCenter registration. The OpenManage Integration for
VMware vCenter Console tab (in VMware vCenter) uses security procedures to avoid improper requests while the keys are transferred back and forth from the Administration Console and back-end services. This type of security causes cross-site request forgeries to fail.
A secure Administration Console session has a five-minute idle timeout, and the session is only valid in the current browser window and/or tab. If the user tries to open the session in a new window or tab, a security error is created that asks for a valid session. This action also prevents the user from clicking any malicious URL that could try to attack the Administration Console session.
Figure 1. Error Message
Access Control Authentication, Authorization, And Roles
The OpenManage Integration for VMware vCenter uses the vSphere Client's current user session and the stored administration credentials for the virtual appliance to perform vCenter operations. The OpenManage Integration for VMware vCenter uses the
10 OpenManage Integration for VMware vCenter Configuration
vCenter server's built-in roles and privileges model to authorize user actions with the virtual appliance and the vCenter managed objects (hosts and clusters).
Figure 2. vCenter vSphere Client Roles and Privileges
Dell Operational Role
Contains the privileges/groups to accomplish appliance and vCenter server tasks including firmware updates, hardware inventory, restarting a host, placing a host in maintenance mode, or creating a vCenter Server task.
This role contains the following privilege groups:
Table 1. Privilege groups
Group Name
Privilege Group — Dell.Configuration
Privilege Group — Dell.Inventory
Privilege Group — Dell.Monitoring
Privilege Group — Dell.Reporting (Not used)
Description
Perform Host-Related Tasks, Perform vCenter-Related Tasks,
Configure SelLog, Configure ConnectionProfile, Configure
ClearLed, Firmware Update
Configure Inventory, Configure Warranty Retrieval, Configure
ReadOnly
Configure Monitoring, Monitor
Create a Report, Run a Report
Dell Infrastructure Deployment Role
This role contains the privileges specifically related to the hypervisor deployment features.
OpenManage Integration for VMware vCenter Configuration 11
Figure 3. Dell Infrastructure Deployment Role
The privileges that his role provides are Create Template, Configure HW Configuration Profile, Configure Hypervisor Deployment
Profile, Configure Connection Profile, Assign Identity, and Deploy.
Dell.Deploy —
Provisioning
Create Template, Configure HW Configuration Profile, Configure Hypervisor Deployment Profile,
Configure Connection Profile, Assign Identity, Deploy
Understanding Privileges
Every action performed by the OpenManage Integration for VMware vCenter is associated with a privilege. The following sections list the available actions and the associated privileges:
● Dell.Configuration.Perform vCenter-Related Tasks
○ Exit and enter maintenance mode
○ Get the vCenter user group to query the permissions
○ Register and configure alerts, for example enable/disable alerts on the event settings page
○ Post events/alerts to vCenter
○ Configure event settings on the event settings page
○ Restore default alerts on the event settings page
12 OpenManage Integration for VMware vCenter Configuration
○ Check DRS status on clusters while configuring alerts/events settings
○ Reboot host after performing update or any other configuration action
○ Monitor vCenter tasks status/progress
○ Create vCenter tasks, for example firmware update task, host configuration task, and inventory task
○ Update vCenter task status/progress
○ Get host profiles
○ Add host to data center
○ Add host to cluster
○ Apply profile to host
○ Get CIM credentials
○ Configure hosts for compliance
○ Get the compliance tasks status
● Dell.Inventory.Configure ReadOnly
○ Get all vCenter hosts to construct the vCenter tree while configuring connection profiles
○ Check if the host is a Dell server when the tab is selected
○ Get the vCenter's Address/IP
○ Get host IP/Address
○ Get the current vCenter session user based on the vSphere client session ID
○ Get the vCenter inventory tree to display the vCenter inventory in a tree structure.
● Dell.Monitoring.Monitor
○ Get host name for posting the event
○ Perform the event log operations, for example get the event count, or change the event log settings
○ Register, unregister, and configure events/alerts – Receive SNMP traps and post events
● Dell.Configuration.Firmware Update
○ Perform firmware update
○ Load firmware repository and DUP file information on the firmware update wizard page
○ Query firmware inventory
○ Configure firmware repository settings
○ Configure staging folder and perform update using the staging feature
○ Test the network and repository connections
● Dell.Deploy-Provisioning.Create Template
○ Configure HW Configuration Profile
○ Configure Hypervisor Deployment Profile
○ Configure Connection Profile
○ Assign identity
○ Deploy
● Dell.Configuration.Perform Host-Related Tasks
○ Blink LED, Clear LED, Configure OMSA URL from the Dell Server Management tab
○ Launch OMSA Console
○ Launch iDRAC Console
○ Display and clear SEL log
● Dell.Inventory.Configure Inventory
○ Display system inventory in the Dell Server Management tab
○ Get storage details
○ Get power monitoring details
○ Create, display, edit, delete, and test connection profiles on the connection profiles page
○ Schedule, update, and delete inventory schedule
○ Run inventory on hosts
OpenManage Integration for VMware vCenter Configuration 13
3
Steps to Configure or Edit the OpenManage
Integration for VMware vCenter
After you complete the basic installation of the OpenManage Integration for VMware vCenter, you can proceed to configure the appliance using one of the following methods described later in this section:
● Configuration Tasks Using the Configuration Wizard
● Configuration Tasks Using the Settings Options
The user interface in both methods is similar except in the wizard you click Save and Continue , whereas in the Settings options you click Apply .
Configuration Tasks Using the Configuration Wizard
Use these tasks when configuring the OpenManage Integration for VMware vCenter using the Configuration Wizard:
1.
Configuration Wizard Welcome Page
2.
Creating A New Connection Profile
3.
4.
5.
6.
Running A Warranty Retrieval Job
7.
Configuring The Deployment Credentials
8.
Setting The Default Firmware Update Repository
9.
Configuration Tasks Using the Settings Options
Use these tasks to set up or edit the OpenManage Integration for VMware vCenter configuration tasks:
●
Creating A New Connection Profile
●
●
●
Modifying An Inventory Job Schedule
●
●
Viewing Or Editing Deployment Credentials
●
Setting Up The Firmware Repository And Credentials
●
Topics:
•
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]
•
•
•
About Host, Bare Metal, and iDRAC Compliance Issues
•
Upgrading OpenManage Integration for VMware vCenter
•
OpenManage Integration for VMware vCenter licensing
14 Steps to Configure or Edit the OpenManage Integration for VMware vCenter
OpenManage Integration for VMware vCenter Home
Page
When you log into the OpenManage Integration for VMware vCenter home page, the navigation buttons are in the left pane, and the right pane provides useful links and information. This design provides key links into the tasks you do most often. While all these tasks are found under the left-pane navigation, you can also find them on the Overview page for ease of use. The tasks provided on this page belong to the following categories:
● Hosts and Server Deployment
This section provides more information on hosts and server deployment.
● vSphere Host and Bare Metal Server Compliance
This section provides more information and lets you view details about non-compliant hosts or bare metal servers or run the wizards to fix them.
● Inventory Schedule
In this section, you can learn more about inventory scheduling.
● Warranty Data Retrieval Schedule
This section lets you learn more or view/change warranty schedules.
● Licensing
This section lets you learn more about licensing. Use the links to go to the licensing tasks. In the host connection licenses, you can view the host connection licenses in real time. In addition, you can use the Buy Now link to purchase a full version license to manage more than one host. The Buy Now link only appears if you are using a demo license. In vCenter Connection
Licenses, you can view the VMware vCenter connection license related information.
● Events and Alarms Settings
Learn more about event and alarm settings or take the link that lets you configure them.
Configuration Wizard welcome page
After you install the OMVV, it must be configured.
1. In the vSphere Client , from Home page, under Management tab, click the Dell Management Center icon.
The first time you click on the Dell Management Center icon, it opens the Configuration Wizard . You can also access this wizard on the Dell Management Center > Settings page.
2. In the Welcome tab, review the steps, and then click Next .
Creating a new Connection Profile [Wizard]
A connection profile stores the credentials that the virtual appliance uses to communicate with Dell servers. Each Dell server must be associated with a connection profile to be managed by the OMIVV. You might assign multiple servers to a single connection profile. Creating the Connection Profile is similar between the Configuration Wizard and the Dell Management
Center, under Settings option. You can configure OMIVV to connect to iDRAC and Host using Active directory credential. Prior to using the Active Directory credentials with a connection profile, the Active Directory user’s account must exist in Active
Directory and the iDRAC and host must be configured for Active Directory based authentication. The active directory credential can be same for both iDRAC and host or it can be set as separate active directory credential. The user credential must have administrative privilege.
NOTE: With installations on hosts that are using 12th or later generation of the Dell PowerEdge servers, the OMSA agent installation is not required. For installations on 11th generation servers, OMSA agent is automatically installed during the deployment process.
NOTE: You are not allowed to create a connection profile if the number of hosts added exceeds the license limit for creating a Connection Profile.
To create a new connection profile using the wizard, perform the following steps:
1. From the Connection Profiles tab, click Create New .
Steps to Configure or Edit the OpenManage Integration for VMware vCenter 15
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
Setting Up A Proxy Server [Wizard]
Set the proxy server in the Configuration Wizard or later using the Dell Management Center, Settings > Proxy page.
To set up a proxy server:
1. In Configure HTTP Proxy , do one of the following:
● To not use a proxy server, click Save and Continue .
● To use a proxy server, under Settings enter a Proxy Server Address .
2. Enter the Proxy Port number .
3. Select the Credentials Required check box, if needed.
4. If you selected Credentials Required , do the following: a. In the Proxy User Name text box, type the proxy user name.
b. In the Proxy Password text box, type the proxy password.
c. In the Verify Password text box, re-type the proxy password.
5. Under Proxy , select the Use Proxy check box.
6. To save these options and continue, click Save and Continue .
Scheduling Inventory Jobs [Wizard]
The inventory schedule configuration is similar from the Configuration Wizard or from the Dell Management Center >
Settings option. The only difference is that the wizard provides an option to select if you want to run the inventory immediately.
NOTE: To make sure that the OMIVV continues to display updated information, it is recommended that you schedule a periodic inventory job. The inventory job consumes minimal resources and will not degrade host performance.
To schedule an inventory job:
1. In the Configuration Wizard , in the Inventory Schedule window, do one of the following:
● To run inventory schedules, click On Selected Days .
● To not run inventory schedules, select Do not run inventory on Dell hosts .
2. If you select On Selected Days , then do the following: a. Select the check box next to each day of the week that you want to run the inventory.
b. In the text box, enter the time in HH:MM format.
The time you enter is your local time. Therefore, if you want to run the inventory at the virtual appliance time zone, calculate the time difference between your local and virtual appliance time zone, and then enter the time appropriately.
3. To apply the changes and continue, click Save and Continue .
Running A Warranty Retrieval Job [Wizard]
The warranty retrieval job configuration is similar between the wizard and from the Dell Management Center > Settings option. In addition, you can run the Warranty Retrieval Job now, from Job Queue.
To run a warranty retrieval job:
1. In the Configuration Wizard , on the Warranty Schedule window, do one of the following:
● To run warranty schedules, click On Selected Days .
● To not run warranty schedules, select Do not retrieve Warranty Data .
2. If you selected On Selected Days , then do the following: a. Select the text box next to each day of the week that you want to run the warranty jobs.
b. In the text box, enter the time in HH:MM format.
The time you enter is your local time. Therefore, if you want to run the inventory at the virtual appliance time zone, calculate the time difference between your local and virtual appliance time zone, and then enter the time appropriately.
3. To apply the changes and continue, click Save and Continue .
Steps to Configure or Edit the OpenManage Integration for VMware vCenter 17
NOTE: OMIVV connects to internet to fetch the warranty information of your hosts. Depending on your network settings, you might have to configure proxy for the warranty job to run successfully.
Configuring the Deployment Credentials [Wizard]
Deployment credentials are used to communicate securely with a bare-metal system that is discovered. For secure communication with iDRAC, OMIVV uses deployment credentials from initial discovery until the end of the deployment process.
WARNING: This feature is not functional in this release for security reasons.
Setting The Default Firmware Update Repository
[Wizard]
Firmware repository settings contain the firmware catalog location used to update deployed servers. You can set up firmware repository initially here in the wizard or later from the Dell Management Center Settings option. In addition, you can run the firmware update later from the OpenManage Integration tab.
To set the default firmware update repository:
1. In the Configuration Wizard , on the Firmware Repository page, to choose the default repository for firmware updates, select one of the following:
● Dell Online
Default firmware repository (ftp.dell.com) with a staging folder. The OMIVV downloads selected firmware updates and stores them in the staging folder, and then they are applied as necessary.
NOTE: OMIVV connects to internet to get the catalog and firmware packages applicable to your hosts. Depending on your network settings, you might have to configure proxy for the firmware update task to run successfully from
Dell online.
● Local/shared repository
These are created with the Dell Repository Manager application. This local repository should be a network share. OMIVV supports both NFS and CIFS shares.
2. If you selected Local/shared repository , do the following: a. Enter the Catalog File Location using the following format:
● NFS share for xml file: host:/share/filename.xml
● NFS share for gz file: host:/share/filename.gz
● CIFS share for xml file: \\host\share\filename.xml
● CIFS share for gz file: \\host\share\filename.gz
b. If using a CIFS share, enter the User Name , Password , and Verify Password ; the passwords must match. These fields are only active when entering a CIFS share.
NOTE: The @ character is not supported for use in shared network folder user names/passwords.
c. To validate your entries click Begin Test .
3. To save this selection and continue the Configuration Wizard , click Save and Continue .
Enabling The OMSA Link [Wizard]
To launch OMSA within the OMIVV virtual appliance, the OMSA Web Server must be installed and configured. See Dell
OpenManage Server Administrator Installation Guide for instructions on how to install and configure the Web Server.
NOTE: OMSA is only required on Dell servers prior to 12 th Generation.
You can use OMSA to:
● Manage vCenter elements (detailed sensor/component-level health information).
18 Steps to Configure or Edit the OpenManage Integration for VMware vCenter
● Clear command logs and system event logs (SELs).
● Obtain NIC statistics.
● Make sure that the OMIVV captures events from a selected host.
1. In the Configuration Wizard , on the OpenManage Server Admin page, use the OMSA Web Server URL text box to enter the OMSA URL. You must include the full URL including the HTTPS.
2. To save this URL and finish the Configuration Wizard, click Finish .
Configuring NFS Shares
To use NFS shares with the OMIVV for backup and restore operations, firmware updates, and as a staging folder, there are certain configuration items that you must complete. CIFS shares do not require additional configuration.
To configure NFS shares:
1. On the Linux or Unix OS machine hosting the NFS shares, edit /etc/exports to add: /share/path <appliance IP> (rw)
*(ro) .
This allows the virtual appliance full read and write access to the share, but limits all other users to read only.
2. Start nfs services: service portmap start service nfs start service nfslock status
NOTE: The steps above may vary depending on the Linux distribution in use.
3. If any of the services were already running: exportfs -ra
Settings Overview
The OpenManage Integration for VMware vCenter Settings section:
● Lists the OpenManage Integration for VMware vCenter configuration settings.
● Starts the initial Configuration Wizard that steps you through the OpenManage Integration for VMware vCenter features necessary to manage and deploy servers in VMware vCenter.
● Starts the OpenManage Integration for VMware vCenter Administration Console that lets you perform vCenter registration, virtual appliance management, alert management, and backup/restore of the OpenManage Integration for VMware vCenter database.
General Settings Overview
General settings are used to:
● Define the OpenManage Server Administrator (OMSA) URL.
● Enable or Disable Warranty Expiration Notification.
You can perform the following tasks:
You can perform the following tasks:
●
: Set the OMSA URL that displays on the Dell Hosts tab in vCenter. You can also enable or disable Warranty
Expiration Notification.
●
: Enables or disables all hardware alarms (current alert status is displayed on the Alarms tab). Also configures incoming event and alert filtering.
●
: Enable or disable HTTP proxy usage during communication with Internet sites.
●
: Sets vCenter Host Inventory Schedule.
●
: Sets warranty information retrieval schedule for Dell hosts from Dell Online.
Steps to Configure or Edit the OpenManage Integration for VMware vCenter 19
●
: Sets up credentials to be used for communication with Dell servers during bare metal server deployment.
●
: Lets you edit where your firmware repository is stored.
●
Server Security using White List
: Provides a server white list that limits the servers that are deployed.
OMSA agent is required on Dell PowerEdge 11th generation server for the following operations:
● Detailed host inventory.
● Receive events from the host.
● Retrieve component-level health information.
● Clear command logs and system event logs (SELs)
NOTE: OMSA is only required on Dell servers prior to 12th generation of Dell PowerEdge servers.
Warranty Expiration Notification can be used to:
● Monitor the warranty expiration date.
● Set a minimum number of warranty days left threshold beyond which either a warning or critical alert is generated. The alert appears as an icon on the host's OpenManage Integration tab.
Related Tasks:
●
Enabling The OMSA Link Outside the Configuration Wizard
on page 20
●
Enable or Disable Server Warranty Expiration Notification
on page 20
Enabling The OMSA Link Outside the Configuration Wizard
To launch OpenManage Server Administrator (OMSA) within the OpenManage Integration for VMware vCenter virtual appliance, the OMSA Web Server must be installed and configured. See the Dell OpenManage Server Administrator Installation
Guide for the version of OMSA in use for instructions on how to install and configure the Web Server.
NOTE: OMSA is only required on Dell servers prior to 12th generation of Dell PowerEdge servers.
To enable the OMSA link:
1. In the Dell Management Center , Settings > General under OMSA Launcher, click Edit .
2. Use the OMSA Web Server URL text box to enter the URL for OMSA. You must include the full URL including the HTTPS and the port number 1311.
3. To save this URL, click Apply .
NOTE:
For information about setting up an OMSA trap destination, see Setting Up An OMSA Trap Destination.
Enable or Disable Server Warranty Expiration Notification
When you control the warranty settings, the server warranty information is retrieved from Dell online. Use this page to enable or disable server warranty expiration notifications for hosts and clusters. Set or edit this feature in the Dell Management Center on the Settings, General Page.
To enable or disable server warranty expiration notification:
1. In the Dell Management Center , click Settings > General.
2. In the General page, to enable notifications, click on Edit button on the right hand side.
3. Select the Enable Warranty Status Notifications check box.
4. To set the Minimum Days Threshold Alert do the following: a. To set warnings, in the Warnings drop-down list select the number of days for warnings about server warranty status.
b. To set critical warranty status, in the Critical drop-down list set the number of days for warning of critical server warranty status.
5. To apply the changes, click Apply .
20 Steps to Configure or Edit the OpenManage Integration for VMware vCenter
Creating A New Connection Profile
A connection profile stores the credentials that the virtual appliance uses to communicate with Dell servers. Each Dell server must be associated with only one connection profile to be managed by the OpenManage Integration for VMware vCenter. You may assign multiple servers to a single connection profile. Creating the Connection Profile is similar between the Configuration
Wizard and Dell Management Center, connection profiles. You can run the Configuration Wizard when you first access the Dell
Management Console, or run it later on the Connection Profiles window.
NOTE: Refer the About OpenManage Integration for VMware vCenter Licensing for more information about licensing. You are not allowed to create a connection profile if the number of hosts added exceeds the license limit.
To create a new connection profile:
1. In the OpenManage Integration for VMware vCenter , in the left pane, click Connection Profiles .
2. Click Create New link.
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 Enabled .
￭ 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 Enabled .
￭ 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.
○ In the Active Directory Password text box, type the password. The password is limited to 127 characters.
Steps to Configure or Edit the OpenManage Integration for VMware vCenter 21
○ 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 Host certificate and validate it during all future connections, select Enable .
￭ To perform no check and not store the Host certificate, select Disabled .
● To configure Host Credentials without Active Directory, do the following:
○ In the Password text box type the password for the root user. 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 Host certificate and validate it during all future connections, select Enabled .
￭ To perform no check and not store the Host certificate, select Disabled .
9. Click Next .
10. The Test Selected link is used to validate the provided iDRAC and Host Credentials for the selected servers.
● To begin the test, select the hosts and click Test Selected . The other options are inactive.
● To abort all the running connection tests,click Abort Tests .
NOTE: For servers that do not have either an iDRAC Express or iDRAC Enterprise, the iDRAC test connection result states Not Applicable for this system.
11. To complete the profile, click Save .
To manage connection profiles, see Managing Connection Profiles .
Configuring Events And Alarms
The Dell Management Center Events and Alarms page enables or disables all hardware alarms. The current alert status is displayed on the vCenter Alarms tab. A critical event indicates actual or imminent data loss or system malfunction. A warning event is not necessarily significant, but may indicate a possible future problem. Events and alarms can also be enabled using the
VMware Alarm Manager. Events are displayed on the vCenter Tasks & Events tab in the Hosts and Clusters view.
NOTE: On hosts prior to 12th generation of Dell PowerEdge servers, this feature requires that the virtual appliance is
.
You can configure events and alarms using in the Dell Management Center under the Settings option for Events and Alarms.
To configure events and alarms:
1. In the Dell Management Center , under Settings > Events and Alarms , click Edit .
2. Under Event Posting Levels , select one of the following:
● Do not post any events - Block hardware events.
● Post All Events - Post all hardware events.
● Post only Critical and Warning Events - Post only critical or warning level hardware events.
● Post only Virtualization-Related Critical and Warning Events - Post only virtualization-related critical and warning events; this is the default event posting level.
3. To enable all hardware alarms and events, select the Enable Alarms for Dell Hosts check box.
NOTE: Dell hosts that have alarms enabled respond to critical events by entering maintenance mode.
4. In the dialog box that displays, click Continue to accept this change, or click Cancel .
5. To restore the default vCenter alarm settings for all managed Dell servers, click Restore Default Alarms .
It may take up to a minute before the change takes effect.
6. To save, click Save .
22 Steps to Configure or Edit the OpenManage Integration for VMware vCenter
About Proxy Configuration
The proxy settings define the HTTP proxy and any required credentials used to retrieve information from the Web (including from Dell online), such as:
● Enable or disable the proxy server
● Enter the proxy server and port number needed
● Define any required credentials - user name and password
Related Tasks:
●
●
Using The HTTP Proxy For Retrieving Web Based Data
●
Setting Up The HTTP Proxy Using The Administration Console
Setting Up A Proxy Server
Depending on your network settings, OMIVV might need the proxy information to reach the internet. If applicable, Proxy settings used for the following tasks :
● To retrieve the host's warranty information
● To retrieve the firmware catalog and the applicable firmware components from Dell online
● To connect to Dell online during appliance upgrade.
Set up the proxy server in the Configuration Wizard or later using the Settings option, HTTP Proxy.
NOTE: Proxy passwords cannot exceed 31 characters.
To set the proxy details in OMIVV:
1. In the Dell Management Center , select Settings > HTTP Proxy , and then click Edit .
2. Enter the Proxy Port number .
3. Select the Credentials Required check box, if needed.
4. If you selected Credentials Required , do the following: a. In the Proxy User Name text box, enter the proxy user name.
b. In the Proxy Password text box, enter the proxy password.
c. In the Verify Password text box, re-enter the proxy password you just typed.
5. Under Proxy , select the Use Proxy check box.
6. To save these options, click, Apply .
Using The HTTP Proxy For Retrieving Web Based Data
To use the HTTP proxy for retrieving Web based data:
1. In the Dell Management Center , select Settings > HTTP Proxy , and then click Edit .
2. Select the Use Proxy check box.
3. Click Apply .
4. To validate settings, click Test Connectivity .
Running Inventory Jobs
To run the inventory job:
1. Once the Configuration Wizard is complete, Inventory triggers automatically for all hosts which are added to a Connection
Profile. For a subsequent inventory run on-demand, click Job Queue > Inventory > Run Now to run an inventory job.
2. To see the status of the inventory job, click Refresh .
3. Navigate to the Host and Cluster view, click on any Dell host , then click the OpenManage Integration tab. The following info should be available:
● Overview Page
● System Event Log
Steps to Configure or Edit the OpenManage Integration for VMware vCenter 23
● Hardware Inventory
● Storage
● Firmware
● Power Monitoring
NOTE: Inventory job for hosts exceeding the license limit will be skipped and marked as Failed.
The following host commands work within the OpenManage Integration tab:
● Blink Indicator Light
● Run Firmware Update Wizard
● Launch Remote Access
● Launch OMSA
● Launch CMC
Scheduling a Warranty job
You can run the Warranty job schedule at any time from the Dell Management Center > Settings > Warranty Schedule page. Warranty Retrival page is disable now. You can run the Warranty Retrieval job now from the Job Queue > Warranty
History page.
To schedule a warranty retrieval job:
1. In the Dell Management Center , select Settings > Warranty Schedule.
2. In the Warranty Schedule window, click Edit .
3. To configure the schedule, do one of the following: a. To run Warranty Schedules, click On Selected Days .
b. Not to run Warranty Schedules, select Do not retrieve Warranty Data .
4. If you selected On Selected Days , then do the following: a. Select the check box next to each day of the week that you want to run the warranty jobs.
b. In the text box, enter the time in HH:MM format.
The time you enter is your local time. Calculate the time difference you need to run the warranty jobs at the proper time.
5. To run the warranty jobs now, navigate to Job Queue > Warranty History and then click Run Now .
NOTE: OMIVV connects to internet to fetch the warranty information of your hosts. Depending on your network settings, you might have to configure proxy for the warranty job to run successfully.
Viewing or Editing Deployment Credentials
In Dell Management Center, you can edit the deployment credentials. Deployment credentials are used to securely communicate with the Dell bare-metal server, until the OS deployment is completed.
WARNING: This feature is not functional in this release for security reasons
Setting Up The Firmware Repository
To set up the firmware repository and credentials:
1. In the OpenManage Integration for VMware vCenter , select Settings > Firmware Repository and then click Edit .
2. On the Firmware Repository page, to choose the default repository for firmware updates, select one of the following:
● Dell Online
This uses the default firmware update repository of Dell online (ftp.dell.com) with a required staging folder. The
OpenManage Integration for VMware vCenter downloads selected firmware updates and stores them in the staging folder, and then they are applied as necessary.
● Shared Network Folder
24 Steps to Configure or Edit the OpenManage Integration for VMware vCenter
Hosts using Lifecycle Controller can update from a custom repository which is hosted on a accessible network shared folder. To create a custom repository, Dell recommends using Dell Repository Manager to create it and then save it to a shared location where the hosts and OpenManage Integration can access it. Enter the location of the repository's catalog file below.
3. If you select Shared Network Folder enter the full the of catalog file in the Catalog File Location field
4. Click Begin Test .
5. Click Apply .
Server Security using White list
Restrict the set of deployable servers using a white list. If a server is in the white list, it is provided with credentials during the
Auto-Discovery and handshake process and is displayed in the list of servers that are used for deployment. The white list is maintained by manually adding server service tags, deleting service tags, or importing a list of service tags from a CSV file.
WARNING: This feature is not functional in this release for security reasons.
About Host, Bare Metal, and iDRAC Compliance Issues
To manage hosts, bare metal servers, and iDRAC with the OpenManage Integration for VMware vCenter each must meet certain minimum criteria. If not compliant, then they are not managed properly by the OpenManage Integration for VMware vCenter. Use the Fix Non-Compliant Hosts, Bare Metal Server, and iDRAC compliance links to see which host/bare metal servers/iDRACs in your configuration are not compliant and fix them. This wizard displays hosts/bare metal servers/iDRACs where:
● Hosts have not been assigned to a connection profile.
If a connection profile is not assigned to a host, a dialog box is offered to take you to the Connection Profile screen. This configuration is outside this wizard. Return later to run this wizard.
● Collect System Inventory on Reboot (CSIOR) is disabled or has not been run, which requires a manual reboot.
● The OMSA agent (Host Root credentials ) is not installed, is out of date, or not configured properly.
● Bare metal servers have outdated Integrated Dell Remote Access Controller (iDRAC) firmware, Lifecycle Controller (LC) firmware, or BIOS versions.
CAUTION: Hosts in Lockdown Mode will not appear in compliance checks even if they are non-compliant. They do not display because their compliance status cannot be determined. Make sure to check the compliance of these systems manually. When this is the case a warning displays.
In each case, you need to fix the compliance issues by running one of the following:
● To fix vSphere host compliance issues, see
Running The Fix Non-Compliant vSphere Hosts Wizard
● To fix bare metal servers that have compliance issues, see
Running The Fix Non-Compliant Bare Metal Server Wizard
●
To fix iDRAC compliance issues: iDRAC License Compliance
Related Information :
●
Re-Checking Bare Metal Server Compliance
Running The Fix Non-Compliant vSphere Hosts Wizard
Run the Fix Non-Compliant vSphere Hosts Wizard to fix non-compliant hosts. For information about compliance, see
Host And Bare Metal Compliance Issues
. Some non-compliant ESXi hosts require reboots. An ESXi host reboot is required if
OpenManage Server Administrator (OMSA) must be installed or updated. In addition, a reboot is required on any host that has never run CSIOR. If you select to automatically reboot an ESXi host, the following actions take place:
● For a CSIOR status fix:
If CSIOR is not enabled on the host, you can enable CSIOR on the host, and then the host is set into maintenance mode and rebooted.
● For an OMSA status fix:
1. OMSA is installed on the host.
2. The host is set to maintenance mode and rebooted.
3. After the reboot completes, OMSA is configured for the changes to take effect.
Steps to Configure or Edit the OpenManage Integration for VMware vCenter 25
4. The host comes out of maintenance mode.
5. Inventory is run to refresh data.
To run the Fix Non-Compliant vSphere Hosts Wizard:
1. In the Dell Management Center , in the left pane, click Compliance > vSphere Hosts .
2. In the vSphere Host Compliance window, view the noncompliant hosts, then click Fix Non-Compliant vSphere Hosts .
3. In the Fix Non-Compliant vSphere Hosts wizard, select the check boxes for the hosts you want to fix.
4. Click Next .
5. If there is a server without a connection profile, you are given the option to exit the wizard and fix these systems from the
Connection Profile page, or continue with this wizard. See
Creating A New Connection Profile
. When done, return to this wizard.
6. In the Turn On CSIOR window, select the check boxes to turn on CSIOR for the selected hosts.
7. Click Next .
8. In the Fixing OMSA window, select the check boxes to fix OMSA for the selected hosts.
9. Click Next .
10. In the Reboot Hosts window, view the ESXi hosts that must be rebooted. An ESXi host reboot is required if OMSA must be installed or updated. In addition, a reboot is required on any host that has never run CSIOR. Do one of the following:
● If you want to automatically put hosts in maintenance mode and reboot when required, select the Automatically put hosts in maintenance mode and reboot whenever required check box.
● If you want to reboot manually, you must do the following: a. Once the Install OMSA task is completed for a host, reboot the host.
b. Once the host is up and if OMSA is not configured, configure OMSA manually or use the Compliance Wizard.
c. Re-run inventory, see
.
11. Click Next .
12. In the Summary window, review the actions that take place on the non-compliant hosts. Manual reboots are required for these to take effect.
13. Click Finish .
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 are removed from the list. If not, the non-compliant system remains on the list.
6. When finished, click Done .
26 Steps to Configure or Edit the OpenManage Integration for VMware vCenter
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.
Upgrading OpenManage Integration for VMware vCenter
The following is the upgrade scenario for the OpenManage Integration for VMware vCenter:
●
Upgrading From Trial Version To Full Product Version
NOTE: Perform an appliance backup before you begin the upgrade. See
Performing An Immediate Backup
.
Upgrading From a Trial Version To a Full Product Version
To upgrade from trial version to a full product versions:
1. Go to the Dell Website and purchase the full product version.
You may also access the Dell website in the OpenManage Integration for VMware vCenter using one of the Buy Now links, like the one located in the Administration Portal on the Licensing window. This is applicable only when you are using evaluation license.
2. The download includes the new full version product, and a new license file.
3. Launch a browser window and enter the Administration Console URL displayed in the vSphere vCenter Console tab for the virtual machine you want to configure or use the link from the Dell Management Console > Settings page. The URL uses the following format and is case insensitive: https://<ApplianceIPAddress>
4. In the Administration Console login window , enter the password and click Login .
5. To upload the license file, click Upload .
6. In the Upload License window, click Browse to navigate to the license file.
7. Select the license file and then click Upload .
Steps to Configure or Edit the OpenManage Integration for VMware vCenter 27
OpenManage Integration for VMware vCenter licensing
The OpenManage Integration for VMware vCenter has two types of licenses:
● Evaluation license—when the OMIVV version 3.2 appliance is powered on for the first time, an evaluation license is automatically installed. The trial version contains an evaluation license for five hosts (servers) managed by the OpenManage
Integration for VMware vCenter. This is applicable only for 11th and later generations of the Dell servers and is a default license, which is for a 90 days trial period.
● Standard license—the full product version contains a standard license for up to 10 vCenter servers and you can purchase any number of host connections managed by OMIVV.
When you upgrade from an evaluation license to a full standard license, you will receive an email about the order confirmation, and you can download the license file from the Dell Digital store that is available at http://www.dell.com/support/licensing .
Save the license .XML file to your local system, and upload the new license file by using the Administration Console .
Licensing presents the following information:
● Maximum vCenter Connection Licenses—up to 10 registered and in-use vCenter connections are allowed.
● Maximum Host Connection Licenses—the number of host connections that were purchased.
● In Use—the number of vCenter connection or host connection licenses in use. For host connection, this number represents the number of hosts (or servers) that have been discovered and inventoried.
● Available—the number of vCenter connections or host connection licenses available for future use.
NOTE: The standard license period is for three or five years only, and the additional licenses are appended to the existing license and not over written.
When you purchase a license, the .XML file (license key) is available for download through the Dell Digital store that is available at http://www.dell.com/support/licensing . If you are unable to download your license key(s), contact Dell Support by going to www.dell.com/support/softwarecontacts to locate the regional Dell Support phone number for your product.
28 Steps to Configure or Edit the OpenManage Integration for VMware vCenter
4
End-To-End Hardware Management
The goal of end-to-end hardware management is to provide the system health status and up-to-date infrastructure information that an administrator needs to respond to critical hardware events without leaving the Dell Management Center or vCenter.
End-to-end hardware management within the OpenManage Integration for VMware vCenter is divided into four separate parts:
● Monitoring
● Inventory
● Advanced host management
● Warranty retrieval
Topics:
•
Monitoring the Datacenter And Host System
•
•
•
•
•
Displaying The Entire Datacenter Hardware Configuration
•
•
Understanding System Event Logs In vSphere Client Host View
•
•
Advanced Host Management Using vCenter
Monitoring the Datacenter And Host System
Datacenter and host system monitoring lets an administrator monitor infrastructure health by displaying hardware (server and storage) and virtualization-related events on the Tasks & Events tab in vCenter. Additionally, critical hardware alerts can trigger the OpenManage Integration for VMware vCenter alarms. Few alarms defined for Dell virtualization-related events can move the managed host system to maintenance mode.
To perform monitoring:
1. Configure the Event and Alarm settings.
2. Configure SNMP OMSA trap destinations , if needed.
3. Use the Tasks & Events tab in vCenter to review event information.
Understanding Events And Alarms
You can edit events and alarms from the OpenManage Integration for VMware vCenter within Manage > Settings tab. From here you can select the Event Posting Level, enable Alarms for Dell Hosts, or Restore Default Alarms. You can configure events and alarms for each vCenter or all at once for all registered vCenters.
There are four event posting levels.
Table 2. Event Posting Level Descriptions
Event
Do not post any Events
Post all Events
Description
Do not have the OpenManage Integration for VMware vCenter forward any events or alerts into related vCenters.
Post all events, including informal events, that the
OpenManage Integration for VMware vCenter receives from managed Dell hosts into related vCenters.
End-To-End Hardware Management 29
Table 2. Event Posting Level Descriptions (continued)
Post only Critical and Warning Events
Post only Virtualization-Related Critical and Warning Events
Posts only events with either Critical or Warning criticality into related vCenters.
Post Virtualization related events received from hosts into related vCenters. Virtualization related events are those that
Dell has selected to be most critical to hosts running virtual machines.
When you configure your events and alarms, you can enable them. When enabled, critical hardware alarms can trigger the
OpenManage Integration for VMware vCenter to put the host system into a maintenance mode, and in certain cases, migrate the virtual machines to another host system. The OpenManage Integration for VMware vCenter forwards events received from managed Dell hosts, and creates alarms for those events. Use these alarms to trigger actions from vCenter, like a reboot, maintenance mode, or migrate. For example, when a dual power supply fails and an alarm is created, the resulting action is to migrate the virtual machine on that machine to a new one.
A host enters or leaves maintenance mode only as when you request it. If the host is in a cluster when it enters maintenance mode, you are given the option to evacuate powered-off virtual machines. If this option is selected, each powered-off virtual machine is migrated to another host, unless there is no compatible host available for the virtual machine in the cluster. While in maintenance mode, the host does not allow deployment or power-on of a virtual machine. Virtual machines that are running on a host entering maintenance mode need to be either migrated to another host or shut down, either manually or automatically by
VMware Distributed Resource Scheduling (DRS).
Any hosts outside of clusters, or in clusters without VMware Distributed Resource Scheduling (DRS) enabled, could see virtual machines being shut down due to a critical event. DRS continuously monitors usage across a resource pool and intelligently allocates available resources among virtual machines according to business needs. Use clusters with DRS configured in conjunction with Dell Alarms to make sure that virtual machines are automatically migrated on critical hardware events. Listed in the details of the on screen message are any clusters on this vCenter instance that may be impacted. Confirm that the clusters are impacted before enabling Events and Alarms.
If you ever need to restore the default alarm settings, you can do so with the Reset Default Alarm button. This button is a convenience to restore the default alarm configuration without uninstalling and reinstalling the product. If any Dell alarm configurations have been changed since install, those changes are reverted using this button.
NOTE: To receive Dell events, you must enable the events.
NOTE: The OpenManage Integration for VMware vCenter pre-selects the virtualization-related events that are the essential to hosts successfully running virtual machines. Dell host alarms are disabled by default. If Dell alarms are enabled, the clusters should use the VMware Distributed Resource Scheduler to make sure that the virtual machines that send critical events are automatically migrated.
Understanding OMSA For 11th Generation Dell PowerEdge Hosts
On PowerEdge servers earlier than 12th generation, it is mandatory to install OMSA to work with the OpenManage Integration for VMware vCenter. OMSA is installed automatically on 11th generation Dell PowerEdge hosts during deployment, or if you want to install it manually, you may still do so.
NOTE: When deploying the OMSA agent using the OpenManage Integration for VMware vCenter starts the httpClient service and enables port 8080 on and releases after ESXi 5.0 to download OMSA VIB and install it. Once the OMSA installation is completed, the service automatically stops and the port is closed.
To configure OMSA on 11th generation Dell PowerEdge servers, choose from the following:
●
Deploying an OMSA Agent Onto ESXi System
●
Setting Up An OMSA Trap Destination
Deploying The OMSA Agent Onto An ESXi System
Install the OMSA VIB on an ESXi system to gather inventory and alert information from the systems.
NOTE: OpenManage agents are required on Dell hosts earlier than Dell PowerEdge 12th generation servers. Install OMSA using the OpenManage Integration for VMware vCenter or install manually to hosts prior to installing the OpenManage
30 End-To-End Hardware Management
Integration for VMware vCenter. Details on manually installing the agents are at http://en.community.dell.com/ techcenter/systems-management/w/wiki/1760.openmanage-server-administrator-omsa.aspx.
1. If not already installed, install the vSphere command line tool (vSphere CLI) from http://www.vmware.com
.
2. Enter the following command:
Vihostupdate.pl -server <IP Address of ESXi host> -i -b <OMSA version X.X>
NOTE: It can take a few minutes for OMSA to install. This command requires a reboot of the host after it completes.
Setting Up An OMSA Trap Destination
All 11th generation of hosts must have OMSA configured.
NOTE: OMSA is only required on Dell servers earlier than 12th generation Dell PowerEdge servers.
To set up an OMSA trap destination:
1. Either use the link to the OMSA user interface found in Settings > General , or navigate to the OMSA agent from a Web browser ( https://<HostIP>:1311/ ).
2. Log in to the interface, and select the Alert Management tab.
3. Select Alert Actions and make sure that any events to be monitored have the Broadcast Message option set, so that the events will be sent out.
4. Select the Platform Events option at the top of the tab.
5. Click the grey Configure Destinations button, and click the Destination link.
6. Select the Enable Destination check box.
7. Enter the OpenManage Integration for VMware vCenter appliance IP address in the Destination IP Address field.
8. Click Apply Changes .
9. Repeat step 1 to step 8 to configure additional events.
Viewing Events
To view events, do one of the following:
● Navigate to the virtual machine and right-click to display the vCenter > Tasks & Events tab and click Events so that the selected level of events is displayed.
● Click on the parent node (cluster or datacenter) of the host or the root folder of the vCenter.
Events appear only on those nodes in the vSphere tree.
vSphere Client Host Overview
The Overview provides information on key host server attributes, including individual component health, identification, hypervisor, and firmware information.
Hardware Component Health
Component health is a graphical representation of the status of all major host server components: system chassis, power supply, temperature, fans, voltage, processors, batteries, intrusion, hardware log, power management, and memory. The available status states are:
● Healthy (green check mark) — component operating normally
● Warning (yellow triangle with exclamation point) — component has a non-critical error
● Critical (red X) — component has a critical failure
● Unknown (question mark) — status is unknown for the component
A global health status is displayed in the upper-right header bar.
Server Information
Server information provides identification, hypervisor, and firmware information, such as:
● Host name, power state, iDRAC IP, Management IP, connection profile in use, model, service tag and asset tag numbers, number of days left on the warranty, and when the last inventory scan was performed.
End-To-End Hardware Management 31
● Hypervisor, BIOS firmware, and iDRAC firmware versions.
● Ten most recent system event log entries. Click Details to launch the System Event Log window that displays additional log details.
Host Information
In the left pane of the Host Overview, you can find the links to the following types of Host information:
● System Event Log
Displays hardware system event log information. See Understanding System Event Logs .
● Hardware Inventory
Displays information about the following hardware devices:
○ Field Replaceable Units (FRUs) such as DIMMs, system planar, power supplies, backplanes, controller cards, and others.
○ Memory — Number of slots available and in use, maximum capacity and amount of memory in use, and details on individual DIMMs.
○ Network Interface Cards (NICs) — Number of installed cards and details on individual NICs.
○ PCI Slots — Total available and number in use and details on individual slots.
○ Power Supplies — Number present and details on individual PSUs.
○ Processors — Number present and details on individual CPUs.
○ Remote Access Card — IP address information and RAC type and Web interface URL.
See
.
● Storage
The host system storage provides a graphical and detailed view of the capacity and type of physical and logical storage for storage connected to a host-based storage controller, including:
○ Host system total storage, unconfigured, configured, and both global and dedicated hot spare disks capacity
○ List of how many of each storage component is present in the system component data table that contains detailed information on that component
● Firmware
Run the Firmware Update Wizard or view your firmware version. See Firmware Updates .
● Power Monitoring
The host system power monitoring provides general power information, energy statistics, and reserve power information, including:
○ Current power budget, profile, warning and failure thresholds
○ Energy consumption, system peak power, and amperage statistics
○ Reserve power and peak reserve capacity
NOTE: Not all power supplies support this feature and blade enclosure power supplies are not supported.
● Warranty
Warranty retrieval provides the following information for Dell servers:
○ Updated service warranty information, while only transmitting the host service tag
○ Warranty information updated at scheduled intervals
○ Secure transmission using a proxy server and credentials
○ Information through a tested, secure connection
See
.
Host Actions
The Host actions are commands you performed on the current host server, such as:
● Use the Blink Indicator Light to blink the LCD front indicator light. See
Setting Up Physical Server Front Indicator Lights .
● Use the Run Firmware Update Wizard to display the Firmware Update wizard and update the host server firmware. See
Running the Firmware Update Wizard .
● Use the iDRAC Reset to reset iDRAC without rebooting the host.
See
.
Management Consoles
The management consoles are used to launch external system management consoles, such as:
32 End-To-End Hardware Management
● Click Remote Access Console to launch the Integrated Dell Remote Access Controller (iDRAC) Web user interface.
● Click OMSA Console to launch the OpenManage Server Administrator (OMSA) user interface if it has been configured. See
● Click Blade Chassis Console to launch the Chassis Management Controller (CMC) Web user interface.
Resetting iDRAC
iDRAC sometimes might not response to the requests coming from the OpenManage Integration for VMware vCenter. The only way to recover from this state is to reset iDRAC. An iDRAC reset performs a normal reboot of the iDRAC. This reboot does not reboot the host. After you perform a reset, it takes 1 or 2 minutes for iDRAC to return to a usable state.
While iDRAC is rebooting, you may see:
● Some delay or a communication error while the OpenManage Integration for VMware vCenter obtains its health status.
● All open sessions with iDRAC close.
● DHCP address for iDRAC may change. If iDRAC uses DHCP for its IP address, then there is a chance that the IP address will change. If this happens, rerun the host inventory job to capture the new iDRAC IP in the inventory data
NOTE: A soft reset of iDRAC may not always work to get iDRAC back to reusable state. You may need a hard reset. To do a hard reset, on the server, power off server, remove the power cable for 2 minutes and connect it back. For more information on resetting iDRAC, refer to your version of iDRAC User’s Guide.
NOTE: Dell recommends that you place the host in maintenance mode before resetting iDRAC.
1. In vSphere Client , under the Inventory heading, select Hosts and Clusters .
2. From Hosts and Clusters , select the host system in the tree view and select the OpenManage Integration tab.
3. Under Host Actions , select iDRAC Reset .
4. On the iDRAC Rest dialog box, select the Continue iDRAC Reset , and click OK .
About Inventory Schedule
The inventory schedule sets the time/day for running inventory jobs, such as:
● Weekly at a specific time and on selected days
● At a set time interval
Most of the OpenManage Integration for VMware vCenter features require that an inventory is completed first to gather required data. An inventory of all host systems must be collected to display this information. To perform an inventory on host systems, create a connection profile that provides communication and authentication information. Once the inventory is complete, you can view the inventory results for an individual host system.
NOTE: To make sure that the inventory contains up-to-date information, schedule the inventory job to run a minimum of once a week. The inventory job consumes minimal resources and does not degrade host performance.
Related Tasks:
●
●
Modifying An Inventory Job Schedule
●
Displaying The Inventory For A Single Host System
●
Displaying The Datacenter Hardware Configuration And Status
Modifying An Inventory Job Schedule
The Inventory Schedule sets the time/day for running inventory jobs, such as:
● Weekly at a specific time and on selected days.
● At a set time interval a completed inventory is required to gather the data needed by the majority of the OpenManage
Integration for VMware vCenter features.
NOTE: To make sure that the inventory contains up-to-date information, the inventory job should run a minimum of once a week. The inventory job consumes minimal resources and does not degrade host performance.
End-To-End Hardware Management 33
To modify the inventory job schedule:
1. From the Dell Management Center, select Settings > Inventory Schedule .
2. To change the current schedule, click Edit .
3. Select the On Selected Days option button, and then select the check box for the day of the week and enter the time.
Click Clear to clear the entries.
4. To change the inventory schedule, click Apply , or to cancel the inventory schedule, click Cancel .
5. To run the job now, from the management center, select Job Queue and the Inventory History tab.
6. Click Run Now .
7. To update the Details of Last Inventory Job , click Refresh .
Displaying The Inventory For A Single Host System in vCenter
To display the inventory for a single host system:
1. From the vSphere Client's Home, select Hosts and Clusters .
2. From Hosts and Clusters , in the left pane, select the host system, and then select the OpenManage Integration tab.
3. An overview of the selected host is displayed.
The overview provides information on key host server attributes, including individual component health, identification, hypervisor, and firmware information.
● Hardware Component Health is a graphical representation of the status of all major host server components: system chassis, power supply, temperature, fans, voltage, processors, batteries, intrusion, hardware log, power management, and memory. The available status states are:
○ Healthy (green check mark) - component operating normally
○ Warning (yellow triangle with exclamation point) - component has a non-critical error
○ Critical (red X) - component has a critical failure
○ Unknown (question mark) - status is unknown for the component
A global health status is displayed in the upper-right header bar.
● Server Information provides identification, hypervisor, and firmware information, such as:
○ Host name, power state, iDRAC IP address, Management IP address, connection profile in use, model, service tag and asset tag numbers, number of days left on the warranty, and when the last inventory scan was performed
○ Hypervisor, BIOS firmware, and iDRAC firmware versions
○ Fault Resilient Memory (FRM): This is a BIOS attribute and is enabled in the BIOS during initial setup of the sever and displays the memory operational mode of the server. You need to restart your system when you change memory operational mode value. This is applicable for R620, R720, T620, M620 and 13th generation servers with ESXi 5.5 or later version. The four different values are:
￭ Enabled and Protected: This value indicates that the system is supported and the operating system version is ESXi
5.5 or later, and the memory operational mode in BIOS is set to FRM.
￭ Enabled and Not Protected: This value indicates that the memory operational mode in BIOS is set to FRM, but the operating system does not have support for this feature.
￭ Disabled: This value indicates that it supports valid systems with any operating system version and here memory operational mode in BIOS is not set to FRM.
￭ Blank: If memory operational mode in BIOS is not supported the FRM attribute is not displayed.
○ Non-Uniform Memory Access (NUMA) Fault Resilient Memory (FRM): NUMA FRM is a new memory operating mode available on the BIOS settings of high-end Dell’s 13th generation of PowerEdge systems with at least two or four processors. This mode establishes an area of memory that is fault-resilient on all CPUs, providing the same protection to the hypervisor against uncorrectable memory errors that would affect it, as well as maintaining NUMA memory functionality and performance. The four different values are:
￭ NUMA Enabled and Protected: This value indicates that the system is supported and the operating system version is ESXi 5.5 or later, and the memory operational mode in BIOS is set to NUMA FRM.
￭ NUMA Enabled and Not Protected: This value indicates that the memory operational mode in BIOS is set to NUMA
FRM, but the operating system does not have support for this feature.
￭ Disabled: This value indicates that it supports valid systems with any operating system version and here memory operational mode in BIOS is not set to NUMA FRM.
￭ Blank: If memory operational mode in BIOS is not supported the NUMA FRM attribute is not displayed.
● Recent System Log Entries provide the 10 most recent system event log entries. To launch the System Event Log window that displays additional log details, click Details .
34 End-To-End Hardware Management
4. Under Host Information , click Hardware Inventory to display a list and further details on all components installed in host system, including:
● Field-replaceable units (FRUs) - DIMMS, system planar, power supplies, backplanes, controller cards, and so on.
● Memory - Number of slots available and in use, maximum capacity and amount of memory in use, and details on individual
DIMMs.
● Network Interface Cards (NICs) - Number of installed cards and details on individual NICs.
● PCI Slots - Total available and number in use, and details on individual slots.
● Power Supplies - Number present and details on individual PSUs.
● Processors - Number present and details on individual CPUs.
● Remote Access Card - IP address information, RAC type, and Web interface URL.
5. Under Host Information , click Storage to display a graphic and detailed view of the capacity and type of physical and virtual storage, including:
● Host system total storage, unconfigured, configured, and global hot spare disk capacity.
● List of how many of each storage component is present in the system.
● Component data table that contains detailed information on that component.
6. Under Host Information , click Firmware to display all Dell Lifecycle Controller firmware information including:
● Update name - BIOS, Dell Lifecycle Controller, power supply, and so on.
● Update type - BIOS, firmware, or application.
● Individual update details - Version, installation time, if an update is in progress or the update status, and the update version. The update status and version only have data when an update is scheduled, and the update version is the firmware version to which the system will be updated.
7. Under Host Information , click Power Monitoring to display general power information, energy statistics, and reserve power information, including:
● Current power budget, profile, warning and failure thresholds.
● Energy consumption, system peak power, and amperage statistics.
● Reserve power and peak reserve capacity.
8. Under Host Information , click Warranty to display system warranty information including:
● Warranty provider name and description of the warranty.
● Start and end dates and how many days are left on the warranty.
● Status of the warranty (Active, Expired) and when the warranty information was last updated.
Inventory And Licensing
If server data cannot be retrieved and displayed, there are several possible causes:
● The server was not associated with a connection profile, and therefore an inventory task cannot be completed.
● An inventory task was not run on the server to collect the data, therefore there is nothing to display.
● The number of host licenses is exceeded, and you must have additional licenses available in order for the inventory task to complete.
● The server does not have the correct iDRAC license required for 12th and later generation servers and you must purchase the correct iDRAC license.
The Buy Now link is for purchasing the product for the first time and not for upgrades. The Buy Now link only appears if you are using a evaluation license.
Related Tasks:
●
Viewing And Editing An Existing Connection Profile
●
Modifying An Inventory Job Schedule
The OpenManage Integration for VMware vCenter has two types of licenses:
● Evaluation license—when the OMIVV version 3.2 appliance is powered on for the first time, an evaluation license is automatically installed. The trial version contains an evaluation license for five hosts (servers) managed by the OpenManage
Integration for VMware vCenter. This is applicable only for 11th and later generations of the Dell servers and is a default license, which is for a 90 days trial period.
● Standard license—the full product version contains a standard license for up to 10 vCenter servers and you can purchase any number of host connections managed by OMIVV.
Related Tasks:
●
About OpenManage Integration for VMware vCenter Licensing
End-To-End Hardware Management 35
●
Uploading OpenManage Integration for VMware vCenter License To The Administration Console
Standard Licensing Scenarios
Licensing presents the following information:
● Maximum vCenter Connection Licenses—up to 10 registered and in-use vCenter connections are allowed.
● Maximum Host Connection Licenses—the number of host connections that were purchased.
● In Use—the number of vCenter connection or host connection licenses in use. For host connection, this number represents the number of hosts (or servers) that have been discovered and inventoried.
● Available—the number of vCenter connections or host connection licenses available for future use.
NOTE: The standard license period is for three or five years only, and the additional licenses are appended to the existing license and not over written.
When you purchase a license, the .XML file (license key) is available for download through the Dell Digital store that is available at http://www.dell.com/support/licensing . If you are unable to download your license key(s), contact Dell Support by going to www.dell.com/support/softwarecontacts to locate the regional Dell Support phone number for your product.
Viewing Storage Inventory
The host system storage provides a graphical and detailed view of the capacity and type of physical and logical storage for storage connected to a host-based storage controller, including:
● Host system total storage, unconfigured, configured, and global hot spare disks capacity
● List of how many of each storage component is present in the system
● Component data table that contains detailed information on that component
To view storage data:
1. In vSphere Client , select a host and then select the OpenManage Integration Tab .
2. In the left pane, under Host Information , click Storage .
3. In the Storage page, view the graphical summary or use the table and View and Filter drop-down lists to sort your inventory information.
Viewing Host Power Monitoring
The host system power monitoring provides general power information, energy statistics, and reserve power information, including:
● Current power budget, profile, warning and failure thresholds
● Energy consumption, system peak power, and amperage statistics
● Reserve power and peak reserve capacity
To view host power monitoring:
1. In vSphere Client , select your host, then select the OpenManage Integration tab.
2. In the left pane, under Host Information , click Power Monitoring .
3. In the Power Monitoring page, view the power for this host.
Displaying The Entire Datacenter Hardware
Configuration
You must complete an inventory job prior to displaying the entire datacenter hardware configuration. Once the inventory is run, you can view any of the following:
● Hardware: Field Replaceable Units
● Hardware: Processors
● Hardware: Power Supplies
● Hardware: Memory
36 End-To-End Hardware Management
● Hardware: NICs
● Hardware: PCI Slots
● Hardware: Remote Access Card
● Storage: Physical Disks
● Storage: Virtual Disks
● Firmware
● Power Monitoring
● Warranty
To display the entire datacenter hardware configuration:
1. From the vSphere Client , under the Inventory heading select Hosts and Clusters .
2. In Hosts and Clusters , select a datacenter in the tree view and select the OpenManage Integration tab.
3. An overview of all hosts in the datacenter is displayed. Use the View drop-down list to view an inventory category.
4. Use the Filter text box to enter a filter for the inventory data.
5. To refresh the displayed inventory, click Refresh .
Managing Connection Profiles
Connection profiles associate access and deployment credentials with a set of host systems and typically contain:
● Profile name and unique description (to help with profile management)
● A list of hosts associated with the connection profile
● iDRAC credentials
● Host credentials
● Date Created
● Date Modified
● Last Modified User
After you run the Configuration Wizard , you manage credential profiles from the OpenManage Integration for VMware vCenter Manage tab > Templates & Profiles using the following:
●
●
Viewing And Editing An Existing 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.
End-To-End Hardware Management 37
○ 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.
○ 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 Host certificate and validate it during all future connections, select Enable .
￭ To perform no check and not store the Host certificate, select Disabled .
● To configure Host Credentials without Active Directory, do the following:
○ In the User Name text box, type the user name. The user name must be root.
○ In the Password text box type the password. The password is limited to 127 characters.
NOTE: For servers that do not have either an iDRAC Express or Enterprise card, the iDRAC test connection result states Not Applicable for this system.
NOTE: The OMSA credentials are the same credentials used for ESXi hosts.
○ 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 Host certificate and validate it during all future connections, select Enable .
￭ To perform no check and not store the Host certificate, select Disabled .
9. Click Save .
10. To close the window, click X (upper-right corner).
Deleting A Connection Profile
You can remove a connection profile from the OpenManage Integration for VMware vCenter.
38 End-To-End Hardware Management
To delete a connection profile:
1. From the OpenManage Integration for VMware vCenter , click Connection Profiles .
2. Under Available Profiles , select the profile to delete and then click Delete .
3. On the message that displays, to remove the profile, click Delete , or click Cancel to cancel the delete action.
Testing A Connection Profile
To test a connection profile:
1. In the OpenManage Integration for VMware vCenter , select Connection Profiles .
2. Under Available Profiles , to test the entered iDRAC and host root credentials on the selected servers, select the connection profile and then click Test Connection .
3. Use the check boxes to select the hosts you want tested, and then click Test Selected .
4. To abort all selected tests and cancel the testing, click Abort All Tests .
5. To exit, click Done .
Refreshing A Connection Profile
In the OpenManage Integration for VMware vCenter, on the Manage > Connection Profiles tab, up in the VMware vSphere
Web Client title bar, click the Refresh icon.
NOTE: If a host is removed from vCenter, then it is removed from the connection profile automatically.
Understanding System Event Logs In vSphere Client
Host View
The System Event Log provides status information for hardware discovered by the OpenManage Integration for VMware vCenter.
System Event Logs provide information based on the following criteria:
Status There are several status icons: Informational (blue exclamation point), Warning (yellow triangle with exclamation point), Error (red X).
Indicates the time and date the event occurred.
Time (Server
Time)
Search this page Displays the specific message, server names, configuration settings, and so on.
The severity levels are defined as:
Info
Warning
Error
Security
The OpenManage Integration for VMware vCenter operation completed successfully.
The OpenManage Integration for VMware vCenter operation partially failed, and was partially successful.
The OpenManage Integration for VMware vCenter operation failed.
Contains information on system security.
You can save the log as an external CSV file.
Related Information :
●
Displaying The System Event Logs For An Individual Host
Displaying Logs in Dell Management Center
Dell Management Center logs include status information for discovered hardware and a history of user actions.
To display logs in Dell Management Center:
1. From the Dell Management Center , in the left pane, select Log .
End-To-End Hardware Management 39
2. To update the log with the most recent data, click Refresh .
3. To select a severity category to filter the log data, in the All Categories drop-down list select one of the following: All
Categories, Info, Warning, Error, or Security.
4. To select a date range for filtering log data, click the Last Week drop-down list and select one of the following: Last week,
Last Month, Last Year, or Custom Range.
If Custom Range is selected, then the Start Date and Stop Date drop-down lists are displayed.
5. If you selected custom date range: a. Click the calendar to populate the Start date.
b. Click the calendar to populate End date.
c. To save your configuration, click Apply .
6. To control how the log is displayed, use the display controls to set the Records per screen , go to a desired Page , and use the forward and backward page controls.
7. To export the Log contents to a comma-separated value (CSV) file, click Export .
8. In the download location window, browse to the location to save the log and click Save .
Displaying The Event Logs For An Individual Host
System HardwareEvent Logs provide information based on the following criteria:
● Status
There are several status icons: Informational (blue exclamation point), Warning (yellow triangle with exclamation point), Error
(red X).
● Time (Server Time)
Displays the time and date the event occurred.
● Search this page
Displays the specific message, server names, configuration settings, and so on.
To display the system event log for an individual host:
1. From the vSphere Client , under the Inventory heading select Hosts and Clusters .
2. In the tree view, select the host system.
3. Select the OpenManage Integration tab.
4. From Recent System Log Entries , to launch the System Event Log window, click Details .
5. To update the System Event Log , click Refresh Log .
6. To limit (filter) the number of event log entries, choose one of the following:
● In the search filter text box, and enter a text string to dynamically filter the log entries.
● To clear the filter text box, click X and all the event log entries display.
7. To clear all event log entries, click Clear Log . A message displays stating that all log entries are deleted after they are cleared and select one of the following:
● To agree to clear log entries, click OK .
● To cancel, click Cancel .
8. To export the event log to a CSV file, click Export .
9. Browse to the location to save the system event log and click Save .
About Firmware Updates
The location where servers receive firmware updates is a global setting that is available in the OpenManage Integration for
VMware vCenter on the Settings tab.
Firmware repository settings contain the firmware catalog location used to update deployed servers. There are two location types:
Dell
(ftp.dell.com)
Uses the firmware update repository of Dell ( ftp.dell.com
). The OpenManage Integration for VMware vCenter downloads selected firmware updates from Dell repository.
40 End-To-End Hardware Management
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
● Apply updates and force reboot without entering maintenance mode.
The update is applied, and a reboot occurs even if the host is not in maintenance mode. This method is not recommended.
6. Click Finish .
7. To verify that the update was successful, in Dell Management Center, select Job Queue > Inventory History > Run Now , and review the Dell Management Center Overview page to see the new versions.
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. 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.
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
.
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 a 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.
42 End-To-End Hardware Management
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.
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.
9. Click Next .
10. In the Select the Systems/Components to Update page, use the check boxes to select the components to upgrade or downgrade. If you want to downgrade, select the Allow components to be downgraded check box.
NOTE: If you select all components and some remain unselected, that means that there are no upgrades available for those components. You may select those components for a downgrade.
11. Click Next .
12. In the Firmware Update Information page, review the components you have selected for an upgrade or downgrade.
13. Click Next .
14. In the Schedule Firmware Updates page, under Job Name, do the following: a. In the Firmware Update Job Name text box, type the firmware update job name .
This is a mandatory field. If this is not filled in, this upgrade is not scheduled. Do not use a name that is already in use. If your purge this name, you may reuse it again.
b. In the Firmware Update Description, type the description .
15. Under Job Schedule, do one of the following:
NOTE: Selecting an option is mandatory. If one is not selected, the upgrade is blocked.
● If you want to run the update job now, click Update Now , and then click Finish .
● If you want to run the update job later, click Schedule Update , and then do the following: a. In the Calendar box, select the month and day .
b. In the Time text box, type the time in HH:MM, and then click Finish .
NOTE: The time is the local timezone where your client is physically located. Invalid time values result in a blocked update.
Viewing Firmware Update Status for Clusters and Datacenters
For information to display on this page, run a firmware update for a cluster or a datacenter. This page only displays information
.
On this page you can refresh, purge, or abort your firmware update jobs.
1. From the Dell Management Center, select Job Queue > Firmware Update Jobs .
2. To display the most recent information, click Refresh .
3. View the status in the datagrid. This grid offers the following information about firmware update jobs:
● Status
● Scheduled Time
● Name
● Description
● Collection Size
The collection size is the number of servers on this firmware inventory job.
● Progress Summary
The progress summary lists the progress details of this firmware update.
End-To-End Hardware Management 43
4. To see more details about a particular job, in the datagrid for a particular job, click Details .
Here you can find the following details:
● Service Tag
● iDRAC IP
● Status
● Warnings
● Firmware Update Job Details
● Start Time
● End Time.
5. If you want to abort a scheduled firmware update that is not running, in the same line as the job you want to abort, click
Abort .
6. If you want to purge scheduled firmware updates, click Purge Job Queue .
You can only purge jobs that are completed or scheduled.
7. Select the Older than date and job Status , and click Apply . The selected jobs are then cleared from the queue.
Advanced Host Management Using vCenter
The advanced host management tasks are host system-based actions that let an administrator identify a physical server in the datacenter environment, launch server-based management tools, and display server warranty information. All of these actions are initiated from the OpenManage Integration tab in vCenter or by right-clicking the host in Host & Clusters view for an individual host system.
Setting Up Physical Server Front Indicator Light
To assist in locating a physical server in a large datacenter environment, you can set the front indicator light to blink for a set time period.
To set up a physical server's front indicator light:
1. In vSphere Client , under the Inventory heading, select Hosts and Clusters .
2. From Hosts and Clusters , select the host system in the tree view and select the OpenManage Integration tab.
3. Under Host Actions , select Blink Indicator Light .
4. Choose one of the following:
● To turn the blink on and set the time period, in the Indicator Light dialog box, click Blink On , and use the Timeout drop-down list to select the timeout increment, and then click OK .
● To turn the blink off, in the Indicator Light dialog box, click Blink Off , and then click OK .
Server Based Management Tools
There are two server-based management tools, iDRAC and OMSA, that can be launched from the vSphere Client >
OpenManage Integration tab. Under the Management Consoles link in the left pane you can access:
● Launch Remote Access.
Use this option to launch the iDRAC user interface
● Launch OMSA
Use this option to launch the OpenManage Server Administrator user interface URL that was entered into the management center either during the initial Configuration Wizard or using Settings > General . You must install the URL for the server administrator Web server on a Windows-based management station.
● If you are on a blade system, launch the CMC to launch the Chassis Management Controller user interface. If you are not on a blade system, this does not display.
44 End-To-End Hardware Management
Warranty Retrieval
Warranty retrieval provides the following information for Dell servers:
● Updated service warranty information, while only transmitting the host service tag
● Warranty information updated at scheduled intervals
● Secure transmission using a proxy server and credentials
NOTE: Dell does not store transmitted service tag information.
Related Tasks:
●
Running A Warranty Retrieval Job
●
Viewing Server Warranty Information For A Single Host
●
Viewing Warranty Information For An Entire Data Center
Viewing Server Warranty Information For An Entire Data Center
Once the warranty job completes, you can view server warranty information in vSphere Client, on the Datacenter View page.
To view the server warranty information for an entire datacenter:
1. From the vSphere Client, under the Inventory heading select Hosts and Clusters .
2. From Hosts and Clusters , select the datacenter in the tree view and select the OpenManage Integration tab.
3. An overview of all hosts in the datacenter is displayed. In the View drop-down list select Warranty .
4. In the Filter text box, enter a filter for the warranty data.
5. To refresh the displayed inventory, click Refresh .
6. To export the inventory as a CSV file, click Export . In the Download Location window, browse to the location to save the inventory and click Save .
Viewing Server Warranty Information For A Single Host
Once a warranty job completes you can view the warranty information for a single host in vSphere Client on the Hosts View page.
To view the server warranty information for a single host:
1. From the vSphere client, under the Inventory heading select Hosts and Clusters .
2. From Hosts and Clusters , select the host system in the tree view and select the OpenManage Integration tab.
3. To display system warranty information, select Warranty . The information on the Warranty Status page includes:
● Warranty provider name and description of the warranty
● The start and end dates and how many days are left on the warranty
● The warranty status (active or inactive) and when warranty information was last updated
End-To-End Hardware Management 45
5
Hardware Prerequisites
To successfully perform hardware provisioning and deployment, the physical servers must appear in the Deployment Wizard. All physical servers must meet the following prerequisites:
● See the Dell Management Plug-In for VMWare vCenter Release Notes for specific hardware support information.
● The server must have the minimum supported versions of iDRAC firmware, Lifecycle controller and BIOS. See the Dell
Management Plug- in for VMWare vCenter Release Notes for specific hardware support information.
NOTE: If the firmware versions are outdated, a two step upgrade process could be required. See the firmware documentation for detailed upgrade instructions.
● The Dell Management Plug-in supports deployment using only embedded/integrated LOMs. You can configure NICs in PCI slots manually after the deployment. If using add-on NICs, the system must have the host LOMs enabled.
● The Dell Management Plug-in allows deployment onto Internal Dual SD Module (hypervisor only) or local hard drives. Before you install hypervisor to an Internal Dual SD Module, it must have a maximum of 1 or 2 GB of storage. The Internal Dual SD
Module must be enabled from BIOS before you deploy the hypervisor with the Dell Management Plug-in. You can change the management NIC manually, and add the system to vCenter.
● If the iDRAC is in dedicated mode, its NIC must be enabled to communicate with the Dell Management Plug-in.
● If the Dell Management Plug-in is not used for hardware configuration, then make sure the following conditions are met prior to initiating hypervisor deployment:
○ Enable the VT (Virtualization Technology) flag in the BIOS.
○ Set the system's boot order to either a bootable Virtual Disk or an Internal Dual SD Module for operating system installation.
● If the Dell Management Plug-in is used for hardware configuration, the BIOS setting for VT is automatically enabled, even if
BIOS configuration is not part of the hardware profile. Express/Clone RAID configuration is required if a virtual disk is not already present on the target system.
● If your servers are from versions prior to 12G, then the deployment process installs the OpenManage Server Administrator package on the target system, and automatically configures the SNMP trap destination to point to the Dell Management
Plug-in.
● Custom ESXi images that contain all the Dell drivers are required for deployment. You can find the correct images by going to the Dell Drivers & Downloads page and saving the custom images to a location you can access during the deployment process. For the most up-to date list of supported ESXi versions for this release, see the Release Notes.
Topics:
•
•
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
•
•
Building A New Deployment Template
•
Provisioning Overview
Once a physical inventory of the datacenter is complete, all discovered bare-metal systems are available to the OpenManage
Integration for VMware vCenter for zero touch hardware provisioning and hypervisor deployment. To prepare for provisioning and deployment, you must:
Create a
Hardware Profile
Contains the hardware settings gathered from a reference server that is used to deploy new servers. See
Creating A New Hardware Profile
.
46 Hardware Prerequisites
Create a
Hypervisor
Profile
Create a
Deployment
Template
Contains the hypervisor installation information needed for ESXi deployment. See
.
Optionally contains a hardware profile, a hypervisor profile, or both. You can save and reuse these profiles as needed for all available datacenter servers. See
.
Once the deployment template is created, use the Deployment Wizard to gather the information necessary to create a scheduled job that provisions server hardware and deploys new hosts in vCenter. For information about running the Deployment
Wizard, see
. Lastly, use the Job Queue to view job status and make changes to pending deployment jobs.
NOTE: No more than two deployment jobs should be scheduled to run consecutively. Multiple jobs should use the scheduling feature to stagger deployment execution.
Understanding Deployment Job Times
Provisioning and deploying bare-metal servers can take between 30 minutes to several hours to complete, depending on certain factors. When starting a deployment job, it is recommended that you plan your deployment time according to the guidelines provided. The amount of time it takes to complete provisioning and deployment varies with deployment type, complexity, and number of deployment jobs running simultaneously. The table below gives guidelines of the approximate time a deployment job may take. Deployment jobs are run in batches of up to five concurrent servers, to improve time for the overall deployment job.
The exact number of concurrent jobs depends on resources available.
Table 3. Approximate Deployment Time Scenarios
Deployment Type
Hypervisor only
Hardware only
Hypervisor and Hardware profiles
Approximate Time Per Deployment
Between 30 minutes to 130 minutes
Up to 2 hours depending on the complexity and the RAID,
BIOS, and boot options to configure
1 to 4 hours
Server States Within The Deployment Sequence
When an inventory job is run, discovered bare-metal systems are classified in different states to help determine if the server is new to the datacenter or has a pending deployment job scheduled. Administrators can use the following states to determine if a server should be included in a deployment job. The states are:
Unconfigured
Configured
The server has contacted the OpenManage Integration for VMware vCenter and is waiting to be configured. See
Understanding Deployment Job Times
.
The server is configured with all hardware information required for a successful hypervisor deployment.
Downloading Custom Dell ISO Images
Custom ESXi images that contain all Dell drivers are required for deployment.
NOTE: The OpenManage Integration for VMware vCenter ISO does not contain the required ESXi ISO images for deployment. You must download these images to a location that is accessible during deployment or your deployment may fail.
1. Navigate to support.dell.com
.
2. Browse to the Drivers & Downloads page in your language, and then do one of the following:
● To select the drivers using the Service Tag or Express Service Code, under Yes , in the text box enter the service tag or express service code, and then click Submit .
● To select the drivers using another option, under No , select one of the following:
○ Automatically detect my Service Tag for me
Hardware Prerequisites 47
○ Choose from My Products and Services List
○ Choose from a list of all Dell products
Then click Continue and follow the directions for the option selected.
3. On the page for the server selected, scroll down to Refine your results and under Operating System , use the drop-down list to select the ESXi system you want.
4. Click Enterprise Solutions .
5. In the Enterprise Solutions list, select the version of ISO required, and then click Download File .
NOTE: Embedded ISOs are used for hypervisor installs on to Dual Internal SD Modules. Installable ISOs are for installs on to hard disks.
6. In the dialog box, select For Single File Download via Browser , and then click Download Now .
7. In the dialog box, browse to the location to store the ISO images for deployment.
Understanding How To Configure A Hardware Profile
To configure server hardware settings, you must create a hardware profile. A hardware profile is a configuration template you can apply to newly-discovered infrastructure components and it requires the following information:
Boot Order The boot order is the boot device sequence and hard drive sequence, which you can edit only if the boot mode is set to BIOS.
BIOS Settings The BIOS settings include: memory, processor, SATA, integrated devices, serial communications, embedded server management, power management, system security, and miscellaneous settings.
iDRAC Settings iDRAC settings include: Network, user list, and user configuration (IPMI/iDRAC privileges).
NOTE: For systems that have iDRAC Express, the iDRAC configuration cannot be extracted; therefore, the server should not be used as a reference server. If it is used as a target system, then no iDRAC configuration from the reference server is applied.
RAID
Configuration
The RAID configuration displays the current RAID topology on the reference server at the time the hardware profile was extracted.
NOTE: There are two RAID configuration options configured in the Hardware Profile:
● Apply RAID1 + create a dedicated hot spare, applicable . Use this option if you want to apply default RAID configuration settings to the target server. The RAID configuration task defaults to
RAID1 on the first two drives of the integrated controller that are RAID1 capable. Additionally, a dedicated hot-spare for the RAID1 array is created if a candidate drive meeting the criteria exists
● Clone RAID configuration from the reference Server as shown below . Use this option if you want to clone the reference server setting. See
Creating A New Hardware Profile
.
NOTE: The OpenManage Integration for VMware vCenter enables certain BIOS settings under the
Processor group in the BIOS on all deployed servers, regardless of the settings on the reference server. Before using a reference server to create a new hardware profile, it must have the Collect
System Inventory On Reboot (CSIOR) setting enabled and be rebooted to provide accurate inventory and configuration information.
The tasks for creating hardware profiles include:
●
Enabling CSIOR On A Reference Server
●
Creating A New Hardware Profile
●
Cloning A Hardware Profile on page 50
●
About Managing Hardware Profiles
Creating A New Hardware Profile
To create a new hardware profile:
1. In the Dell Management Center, select Deployment > Deployment Templates > Hardware Profiles .
48 Hardware Prerequisites
2. Click Create New .
3. In the New Hardware Profile page, do the following:
● In the Profile Name text box, enter the profile name.
● In the Description text box, type an optional description.
4. Click Save .
5. To continue, in the left pane, click Reference Server .
6. In the Reference Server window, click Edit .
7. To find a reference server that is compliant, managed by vCenter, and successfully inventoried by the OpenManage
Integration for VMware vCenter, click Browse .
8. In the Servers dialog box, scroll down the list to find the right reference server, and click Select .
9. To customize the reference server settings as defaults, click Customize Settings from Reference Server , and then click
Save .
10. A dialog box that states extracting the settings takes several minutes is displayed. To populate settings, click Continue . The selected server’s name, iDRAC IP address, and service tag are displayed in the Reference Server window .
11. In the left pane, select Boot Order . To include boot order information in the profile, select the Include Boot Order in this
Hardware Profile check box.
12. To display the boot order options, expand Boot Order , and then click Edit to make updates:
NOTE: For Dell 13th generation PowerEdge Servers, only the current boot mode details are displayed for the hardware profiles.
NOTE: Operating system deployment from OpenManage Integration for VMware and vCenter fails if the BOOT mode in the target machine is set to UEFI a. In the Boot Mode drop-down list to select either BIOS or UEFI.
b. In the View/Configure drop-down list, under Boot Device Sequence , to make changes to the boot device sequence displayed, select the device and click either Move Up or Move Down .
c. In the Boot Retry Sequence drop-down list, select Enabled so that the server automatically retries the boot sequence, or select Disabled to not retry the sequence.
d. Click Save to save the changes, or Cancel to cancel the changes.
13. If the BIOS boot mode was selected, you can expand Hard Drive Sequence to display the hard drive sequence options, and click Edit to make updates:
● To make changes to the hard drive sequence displayed, select the device and click either Move Up or Move Down .
● Click Save to save the changes, or Cancel to cancel the changes.
14. In the left pane, select BIOS Settings . To include BIOS setting information in the profile, select the Include BIOS Settings in this Hardware Profile check box. Expand a category to display the setting options, and click Edit to make updates to one of the following:
● Memory Settings
● Processor Settings
● SATA Settings
● Integrated Devices
● Serial Communication
● Embedded Server Management
● Power Management
● System Security
● Miscellaneous Settings
Once all updates are made for a category, click Apply to save the changes or click Cancel to cancel the changes.
NOTE: For detailed BIOS information, including setting options and explanations, refer to the Hardware Owner’s Manual for the selected server.
15. In the left pane, select iDRAC Settings and then select Network .
16. To include network setting information in the profile, select the Include Network Settings in this Hardware Profile check box. Expand a category to display the setting options, and click Edit to make updates to one of the following:
● Network
● Network Settings
● Virtual Media
Hardware Prerequisites 49
Once all updates are made for a category, click Apply to save the changes or click Cancel to cancel the changes.
NOTE: For detailed iDRAC information, including setting options and explanations, refer to the iDRAC User’s Guide for the selected server.
17. In the left pane, select iDRAC Settings > User List . To include user list information in the profile, select the Include User
List in this Hardware Profile check box. Under iDRAC Local User List, do one of the following: a.
Add User : Manually enter an iDRAC user and the required information. When finished, click Save to save your changes or Cancel to cancel.
b.
Delete User : Delete the selected user. Select the check box for the user and click Delete , or click Cancel to cancel.
c.
Edit User : Manually edit an iDRAC user’s information. When finished, click Save to save your changes or Cancel to cancel.
NOTE: For detailed iDRAC information, including setting options and explanations, refer to the iDRAC User’s Guide for the selected server.
18. In the left pane, select RAID Configuration . To include RAID configuration information in the profile, select the Include
RAID Configuration in this Hardware Profile check box. Then select one of the following:
● Apply RAID1 + create a dedicated hot spare, applicable.
Use this option if you want to apply default RAID configuration settings to the target server. The RAID configuration task defaults to RAID1 on the first two drives of the integrated controller that are RAID1 capable. Additionally, a dedicated hot-spare for the RAID1 array is created if a candidate drive meeting the criteria exists.
● Clone RAID configuration from the reference Server .
Use this option if you want to clone the reference server setting.
The profile is automatically saved, and displays in the Hardware Profiles window under Available Profiles
Enabling CSIOR On A Reference Server
Before creating a hardware profile using a reference server, enable the Collect System Inventory On Reboot (CSIOR) setting and reboot the server to provide accurate inventory and configuration information. There are two methods for enabling CSIOR:
Locally
Remotely
This uses an individual host using the Dell Lifecycle Controller United Server Configurator (USC) user interface.
This uses a WS-Man script. For more information on scripting this functionality, see the Dell Tech Center and the DCIM Lifecycle Controller Management Profile .
To enable CSIOR locally on a reference server:
1. Power on the system, and during POST press <F10> to launch USC.
2. Select Hardware Congfiguration > Part Replacement Configuration .
3. Enable the Collect System Inventory on Reboot setting, and exit USC.
Cloning A Hardware Profile
To clone a new hardware profile:
1. In the Dell Management Center, select Deployment > Deployment Templates > Hardware Profiles .
2. Click Create New .
3. In the New Hardware Profile page, do the following:
● In the Profile Name text box, enter the profile name
● In the Description text box, enter an optional description.
4. Click Save .
5. In the left pane, click Reference Server .
6. In the Reference Server window, click Edit .
7. To extract all hardware settings from the reference server, click the Clone Reference Server Settings option button.
8. Click Save .
50 Hardware Prerequisites
9. A dialog box that states extracting the settings will take several minutes is displayed, then click Continue . The settings are populated, and the selected server’s name, iDRAC IP address, and service tag are displayed in the Reference Server window.
The profile is saved, and displays in the Hardware Profiles window under Available Profiles .
About Managing Hardware Profiles
Hardware profiles define a server's hardware configuration using a reference server. From the Dell Management Center, there are several management actions you can perform on existing hardware profiles, including:
●
Viewing Or Editing Hardware Profiles
on page 51
●
●
●
●
Viewing Or Editing Hardware Profiles
To view or edit a hardware profile:
1. In the Dell Management Center, select Deployment > Deployment Templates > Hardware Profiles .
2. Select a profile and click View/Edit .
3. In the Hardware Profile window, to make any changes, click Edit .
4. Click Save to apply changes, or click Cancel to cancel changes.
Duplicating Hardware Profiles
To duplicate a hardware profile:
1. In the Dell Management Center, select Deployment > Deployment Templates > Hardware Profiles .
2. On the Hardware Profile page, select a profile, and then click Duplicate .
3. In the Duplicate dialog box, enter a unique hardware profile name.
4. Click Apply to create a copy of the profile with the new name, or click Cancel to cancel.
Renaming Hardware Profiles
To rename a hardware profile:
1. In the Dell Management Center, select Deployment > Deployment Template > Hardware Profiles .
2. On the Hardware Profile page, select a profile and click Rename .
3. In the Rename dialog box, enter a unique hardware profile name.
4. Click Apply to use the new name, or click Cancel to cancel.
Deleting Hardware Profiles
To delete a hardware profile:
NOTE: Deleting a hardware profile that is part of a running deployment task can cause the task to fail.
1. In the Dell Management Center, select Deployment > Deployment Templates > Hardware Profiles .
2. Select a profile and click Delete .
3. In the message dialog box, to remove the profile click Delete , or click Cancel to cancel.
Refreshing Hardware Profiles
To refresh an updated hardware profile:
1. In the Dell Management Center, select Deployment > Deployment Templates > Hardware Profiles .
Hardware Prerequisites 51
2. Click Refresh .
The updated hardware profile information displays.
Creating A New Hypervisor Profile
To deploy and configure ESXi to a server, a hypervisor profile must be created. A hypervisor profile requires the following information:
● The scriptable Reference ISO software media location on an NFS or CIFS share
● vCenter instance that manages the deployed hosts, plus an optional host profile
● The destination cluster or datacenter where the plug-in deploys servers in vCenter
NOTE: Use one of the following naming conventions for the Reference ISO file name:
NFS format: host:/share/hypervisor_image.iso
CIFS format:\\host\share\hypervisor.iso
To create a new hypervisor profile:
1. In the Dell Management Center , select Deployment > Deployment Templates > Hypervisor Profile .
2. In the Hypervisor Profiles page, click Create New .
3. In the New Hypervisor Profile page, do the following:
● In the Profile Name text box, enter the profile name.
● In the Description text box, enter an optional description.
4. In the left pane, click Reference ISO , and then click Edit , and on the Hypervisor Installation Source dialog box, enter the following information:
● In the Installation Source ISO text box, type the path to your hypervisor share location. A copy of this hypervisor image is modified to permit a scripted installation. The reference ISO location must be in one of the following format:
NFS format: host:/share/hypervisor_image.iso
CIFS format: \\host\share\hypervisor.iso
● In the Select a Version drop-down list, select an ESXi version.
All servers deployed using this Hypervisor Profile will have this image, and if the servers are versions prior to 12G, the latest recommended version of OpenManage Server Administrator is installed.
5. If using a CIFS share, enter the User Name , Password , and Verify Password . The passwords must match.
6. To add the settings to the profile, click Save .
7. In the left pane, click vCenter Settings , and then edit where required:
● vCenter Instance : Displays the server instance that manages a host after deployment.
● vCenter Version : Displays the current version.
● vCenter Destination Container : Datacenter or cluster that hosts the new physical servers; click Browse to search for vCenter destinations.
● vCenter Host Profile : Select a profile that encapsulates host configuration and helps to manage host configuration.
8. To add the information to the profile, click Save .
For information on Managing Hypervisor Profiles, see Managing Hypervisor Profiles .
Managing Hypervisor Profiles
There are several management actions you can perform on existing hypervisor profiles, including:
●
●
Viewing Or Editing Hypervisor Profiles
●
Duplicating Hypervisor Profiles
●
●
●
Refreshing Hypervisor Profiles
52 Hardware Prerequisites
VLAN Support
The OpenManage Integration for VMware vCenter supports hypervisor deployment to a routable VLAN. Configure VLAN support in the Deployment Wizard. In this portion of the Deployment Wizard, there is an option to specify use of VLANs and to specify a VLAN ID. When a VLAN ID is provided, it is applied to the hypervisor's management interface during deployment and tags all traffic with the VLAN ID.
Make sure that the VLAN provided during deployment communicates with both the virtual appliance and the vCenter server.
The deployment of a hypervisor to a VLAN that cannot communicate to one or both of these destinations causes the deployment to fail.
If you have selected multiple bare-metal servers in a single deployment job and want to apply the same VLAN ID to all the servers then on the Server Identification portion of the Deployment Wizard, under Default Settings, use the Apply settings to all selected servers button. This option lets you apply the same VLAN ID along with the other network settings to all the servers in that deployment job.
NOTE: The OpenManage Integration for VMware vCenter does not support a multi-homed configuration. Adding a second network interface to the appliance for communication with a second network causes problems for the work flows involving hypervisor deployment, server compliance, and firmware updates.
Figure 4. Example VLAN network.
In this example network, the OpenManage Integration for VMware vCenter is on VLAN 5, while the vCenter and the VMkernal of the ESXi hosts being deployed are on VLAN 10. Because the OpenManage Integration for VMware vCenter does not support multi-VLAN homing, VLAN 5 must route to VLAN 10 for all systems to communicate to each other correctly. If routing is not enabled between these VLANs, then the deployment fails.
Viewing Or Editing Hypervisor Profiles
To view or edit hypervisor profiles:
1. In the Dell Management Center, select Deployment > Deployment Template > Hypervisor Profiles window.
2. Select a profile and click View/Edit .
3. In the Hypervisor Profiles: Profile Name window, select the profile section to display or change, and make any necessary changes.
4. Click Save to apply changes, or click Cancel to cancel changes.
Hardware Prerequisites 53
Duplicating Hypervisor Profiles
To duplicate a hypervisor profile:
1. In the Dell Management Center, select Deployment > Deployment Template > Hypervisor Profiles .
2. On the Hypervisor Profiles page, select a profile and click Duplicate .
3. In the Duplicate dialog box, enter a unique hypervisor profile name.
4. Click Apply to create a copy of the profile with the new name, or click Cancel to cancel.
Renaming Hypervisor Profiles
To rename a hypervisor profile:
1. In the Dell Management Center, select Deployment > Deployment Templates > Hypervisor Profiles.
2. On the Hypervisor Profiles page, select a profile and click Rename .
3. In the Rename dialog box, enter a unique hypervisor profile name.
4. Click Apply to use the new name, or click Cancel to cancel.
Deleting Hypervisor Profiles
To delete a hypervisor profile:
NOTE: Deleting a hypervisor profile that is part of a running deployment task can cause the task to fail.
1. In the Dell Management Center, select Deployment > Deployment Templates > Hypervisor Profiles .
2. Select a profile and click Delete .
3. In the message dialog box, click Delete to remove the profile, or click Cancel to cancel.
Refreshing Hypervisor Profiles
To refresh an updated hypervisor profile:
1. In the Dell Management Center, select Deployment > Deployment Templates > Hypervisor Profiles .
2. Click Refresh .
The updated hypervisor profile information displays.
Building A New Deployment Template
A deployment template contains either a hardware profile, a hypervisor profile, or both. The Deployment Wizard uses this template to provision server hardware and deploy hosts within vCenter.
To build a new deployment template:
1. In the Dell Management Center, select Deployment > Deployment Templates .
2. Under Available Profiles , click Create New .
3. In the Create New window, enter a name for the template, and then click Save .
4. To complete the template, click Edit .
5. In the right pane, in the Profile drop-down list, choose a profile, and then do one of the following:
● To display the hardware/hypervisor profile settings for the selected profile, click View .
● To create a new hardware/hypervisor profile, click Create New .
6. Enter an optional Description for the deployment template that is helpful for managing the template.
7. To apply profile selections and save changes, click Save . To cancel, click Cancel .
54 Hardware Prerequisites
Managing Deployment Templates
From the Dell Management Center, there are several management actions you can perform on existing deployment templates, including:
●
●
Duplicating Deployment Templates
●
●
Duplicating Deployment Templates
To duplicate a deployment template:
1. In the Dell Management Center, select Deployment > Deployment Templates .
2. On the Deployment Templates page, select a template, and then click Duplicate .
3. Enter the template's new name and click Apply . The template must have a unique name.
Deleting Deployment Templates
To delete a deployment template:
1. In the Dell Management Center, select Deployment > Deployment Templates .
2. On the Deployment Templates page, select a template and click Delete .
3. Click Delete on the message box to delete the template, or click Cancel to cancel.
Renaming Deployment Templates
To rename deployment template:
1. In the Dell Management Center, select Deployment > Deployment Templates .
2. On the Deployment Templates page, select a template, click Rename .
3. Enter the template's new name and click Apply . The template must have a unique name.
4. To display all deployment templates, from the Dell Management Center select Deployment > Deployment Templates and click Refresh .
Running The Deployment Wizard
The Deployment Wizard steps you through the bare metal server deployment process of:
● Selecting undeployed servers.
When you deploy hypervisor, you can deploy to an Internal Dual SD Module with a minimum of 1 GB of storage. The Internal
Dual SD Module must be enabled from the BIOS before you deploy the hypervisor with the OpenManage Integration for
VMware vCenter.
● Using a deployment template (hardware and hypervisor profiles combination).
● Setting up global settings. This page lets you choose to deploy hypervisor to a hard disk or Internal Dual SD Module.
● Assigning identification to the deployed servers.
● Matching a desired connection profile to each server.
● Scheduling the server deployment jobs to run.
● Displaying the Job Queue where you can manage deployment jobs.
NOTE: If you’re deploying a hardware profile only, then the new Global Settings, Server Identification, and Connection
Profile pages are skipped and you go directly to the Schedule Job page.
NOTE: For trial/evaluation license, you can use Deployment wizard as long as license is not expired.
Related Tasks:
●
Deployment Wizard Step 1: Select Servers
Hardware Prerequisites 55
●
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: Schedule Jobs
Deployment Wizard - Step 1: Select Servers
This page covers server deployment. If you want to deploy hypervisor to an Internal Dual SD Module, this page displays whether that option is available or unavailable. For more information about Internal Dual SD Modules see,
. If the server you want to deploy does not display in the list for step 2, you can manually add a server to have it display in
the list for this step, see Adding A Server Manually
.
To select servers:
1. In the Dell Management Center , select Deployment > Deployment Wizard .
2. In the Select Servers window, to assign non-deployed servers to this deployment job, use the check boxes to select
Servers .
3. Click Next .
To continue with the task to step two, click
Deployment Wizard Step 2: Deployment Templates
Deployments to a hardware profile differ from hypervisor deployments. If you are deploying to a hardware profile, click
.
To select a deployment template:
1. Deployment Template selects/creates a deployment template in one of several ways:
● Select an existing deployment template under Available Templates . Information for the selected template populates the right pane.
● Select an existing deployment template, and then click Edit to change one or both associated profiles.
● Click Create New to define a new template.
2. Select one of the following:
● If you are deploying to a hardware profile, click Next
, which jumps you to Deployment Wizard Step 6
.
● If you are deploying to a hypervisor profile, click Next , which takes you to
Deployment Wizard Step 3: Global Settings
You can deploy hypervisor to either a hard drive or an Internal Dual SD Module. If an Internal Dual SD Module is available on at least one of the servers selected, the Internal Dual SD Module option is enabled by default. If not, both the Hard Disk and
Internal Dual SD Module options are not selected.
To deploy the hypervisor, perform the following steps:
1. In the Global Settings page, select one of the following options:
● Hard Disk — Deploys the hypervisor on the hard disk drive.
● Internal Dual SD Module — Deploys the hypervisor on the Internal Dual SD Module.
2. If any of the selected servers do not support an Internal Dual SD Module, or an Internal Dual SD Module is not present during deployment, perform one of the following actions:
● Select the Deploy the hypervisor to the first hard disk for servers that do not have an available Internal Dual
SD Module check box if you want to deploy the hypervisor on the first hard disk of the servers.
CAUTION: If you select this option and deploy the hypervisor on the first hard disk drive of the servers, all the data on the disk drives will be erased.
● Clear the Deploy the hypervisor to the first hard disk for servers that do not have an available Internal Dual SD
Module check box to skip the deployment on those servers and continue hypervisor deployment on the next server.
56 Hardware Prerequisites
3. Click Next .
To continue with the task to Step 4, click
Deployment Wizard Step 4: Server Identity
.
Deployment Wizard Step 4: Server Identification
Server identification can be provided in two ways:
● Enter networking information (IP address, subnet mask and gateway); a fully-qualified domain name for the hostname is mandatory. The use of localhost for the FQDN is not supported. The FQDN is used when adding the host to vCenter.
● Use the Dynamic Host Configuration Protocol (DHCP) to configure IP addresses, subnet mask, gateway IP, hostname and preferred/alternate DNS servers. The DHCP assigned IP address will be used when adding the host to vCenter. When using
DHCP, it is highly recommended that an IP reservation for selected NIC MAC addresses be used.
NOTE: Use a Fully Qualified Domain Name (FQDN) for hostname instead of localhost. Starting with ESXi 5.1, a value of localhost impairs OpenManage Integration for VMware vCenter from processing events sent from the host. Create a DNS record that resolves the IP address to the FQDN. For SNMP alerts from ESXi 5.1 to be identified correctly, configure the
DNS server to support reverse lookup requests. The DHCP reservations and DNS host names must be in place and verified before the deployment job is scheduled to run.
This screen provides the option to specify a VLAN ID. When a VLAN ID is provided, it is applied to the hypervisor’s management interface during deployment and tags all traffic with the VLAN ID.
To identify your server:
1. Server Identification assigns deployed servers new names and network identification. To display a list of servers that do not meet the minimum requirements for firmware, BIOS, or have other issues, click Non-Compliant Servers .
2. For additional information, click Details .
3. Once the systems are updated, click Check Compliance to retest and verify fixes. To refresh the list, click Refresh , and click Abort All Test to cancel the testing.
4. Click ^ to expand and view individual server information.
5. Under Host Name and NIC , enter a Fully Qualified Host Name for the server.
6. In the NIC Management Tasks drop-down list, select the NIC that will be used for managing the server.
7. Enter IP addresses , subnet mask , and other network information, or select the Obtain using DHCP check box.
8. If deploying to a network that requires a VLAN ID, select the VLAN check box and then enter the VLAN ID.
For the VLAN ID, use the numbers 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
9. Repeat for all servers to deploy, or select the Apply settings to all selected servers check box.
10. Click Next .
To continue with the task to Step 5, click
.
Deployment Wizard Step 5: Connection Profile
Connection profiles are used to establish connection credentials for hosts by associating them with iDRAC or Host Root
Credentials. The Connection Profiles window allows you to:
● Display or edit a current connection profile
● Delete a connection profile
● Refresh the connection profile list to reflect vCenter host changes
To create a connection profile:
1. Connection Profile automatically assigns servers to connection profiles after the deployment job completes.
Once a connection profile is selected, click Next .
2. Select the Assign all servers to the same connection profile option button, and select the connection profile from the drop-down list to assign all servers to the same existing profile.
3. To create a new profile, click New and to view or edit the selected profile click View/Edit .
4. To display the selected connection profile settings, click View .
5. Select the Select a Connection Profile for each Server option button, and then select an individual connection profile for each server from the drop-down list.
6. Once a connection profile is selected, click Next .
To continue with the task to Step 6, click
Hardware Prerequisites 57
Deployment Wizard Step 6: Scheduling Jobs
Schedule sets the schedule for the deployment job. There are several options of when to run the deployment job: immediately, schedule the deployment job to run on a selected date and time, hold deployment job and manually start it.
To set up scheduling:
1. Determine when to run a deployment job by entering a date and time: a. Click Schedule server(s) for deployment .
b. Use the calendar control to select the date.
c. Enter the time of day:
● Immediately: Click Deploy server(s) now .
● Postpone job: Click Create deployment job .
● Put on hold: With this option, only the schedule can be modified and all other deployment job options cannot be changed.
2. Enter a Job Name and Job Description.
3. Click Finish .
4. Now that the deployment wizard is complete, you can manage deployment jobs using the Job Queue .
5. To display a list of non-compliant servers that must have a firmware update before the wizard can be completed, click
Non-Compliant Servers .
Related Tasks:
●
Managing Deployment Jobs Using Deployment JobQueue
Understanding Job Queue
The Job Queue manages server deployment and inventory retrieval jobs, such as:
● Displaying the submitted server deployment jobs.
● Refreshing the Deployment Jobs or Inventory/Warranty History queues.
● Scheduling an inventory job to update the Dell server attributes found in the current vCenter.
● Purging the deployment job queue entries.
● Managing firmware updates for clusters and databases.
NOTE: To make sure the inventory/warranty contains up-to-date information, schedule the inventory/warranty job to run a minimum of once a week. The inventory/warranty job consumes minimal resources and does not degrade host performance.
Tasks on this page include:
●
Managing Deployment Jobs Using Deployment Job Queue
●
●
Modifying An Inventory Job Schedule
●
Viewing Firmware Update Status for Clusters and Datacenters
Managing Deployment Jobs Using The Deployment Job Queue
To manage deployment jobs using the deployment job queue:
1. From the Dell Management Center , select Job Queue > Deployment Jobs .
2. To update Deployment Jobs Details , click Refresh .
3. To display a Deployment Job Details dialog, which contains detailed information on the servers included in the deployment job, click Details . This displays the following details:
● Service tag
● iDRAC IP address
● Server status
● If any warnings occurred
● Deployment job details
● Start and End time
58 Hardware Prerequisites
To display full information for each item in the dialog’s table, hover over the item and an additional text pop-up is displayed.
4. To either put a selected job on hold or to enter an updated schedule, click Modify .
5. Click Abort to abort the deployment job.
6. When the message displays, click Abort Job to abort, or click Do Not Abort Job to cancel.
NOTE: Any deployment jobs that are in progress cannot be aborted.
7. To display the Purge Deployment Job Queue window, click Purge Job Queue . Select the Older than date and job Status , and click Apply . The select jobs are then cleared from the queue.
Adding A Server Manually
You can manually add a server that has not been added by the discovery process. Once it is added, the server shows up in the list of servers in the Deployment Wizard.
1. In the Dell Management Center, Deployment , and then click Deployment Wizard .
2. On the Select Server tab, click Add Server .
3. In the Add Server dialog box, do the following: a. In the iDRAC IP Address text box, enter the iDRAC IP Address.
b. In the User Name text box, enter the user name.
c. In the Password text box, enter the password.
4. Click Add Server . This could take a few minutes.
Removing A Bare Metal Server
You can manually remove a server that has been added.
1. In Dell Management Center, under Deployment click Deployment Wizard .
2. On the Select Servers tab, click Remove Servers .
3. In the Remove Servers dialog box, select the check box of the server to remove.
4. Click Remove Selected Servers .
5. On the Select Servers tab, view the servers listed in the table to confirm it was removed.
Hardware Prerequisites 59
6
Console Administration
Administration of the OpenManage Integration for VMware vCenter and its virtual environment is achieved by using two additional administration portals:
● Web-based Administration Console
● Console view for an individual server (the appliance virtual machine console).
Through the use of these two portals, global settings for vCenter management, OpenManage Integration for VMware vCenter database backup and restore, and reset/restart actions can be entered and used across all vCenter instances.
Topics:
•
Web-based Administration Console
•
Using the Administration Console
•
•
•
•
Understanding the vSphere Client Console
Web-based Administration Console
The Web-based Administration Console provides several key pieces of functionality: vCenter server registration and management, virtual appliance management, global vCenter alert settings, and backup and restore settings.
Using the Administration Console
From the vCenter Registration window in the Administration Console, you can register a vCenter server, and upload or buy a license. If you are using a demo license, a Buy Software link displays from which you can purchase a full-version license for managing multiple hosts. In this section you can also modify, update, and unregister a server.
Related Tasks:
●
Registering a vCenter server by a non-administrator user with necessary privileges on page 60
●
○
○
Updating the SSL Certificates for Registered vCenters
○
Uninstalling OpenManage Integration for VMware vCenter from vCenter
●
Uploading a OpenManage Integration for VMware vCenter License
Registering a vCenter server by a non-administrator user with necessary privileges
You can register vCenter servers for the OMIVV appliance with vCenter administrator credentials of the vCenter server or a non-administrator user with the necessary privileges.
Perform the following steps to enable a user with the required privileges to register a vCenter server:
1. Add a role and select the required privileges for the role or modify an existing role to change the privileges selected for that role. See VMware vSphere documentation for the steps required to create or modify a role and select privileges in the vSphere client. See
on page 61 to select all the required privileges for the role.
NOTE: The vCenter administrator should add or modify a role.
60 Console Administration
2. After you define a role and select privileges for the role, assign a user to the newly created role. See VMware vSphere documentation for more information on assigning permissions in the vSphere client. A vCenter server non-administrator user with the required privileges can now register and/or unregister vCenter, modify credentials, or update the certificate.
NOTE: The vCenter administrator should assign permissions in the vSphere client.
3. Register a vCenter server by using a non-administrator user with the required privileges. See
Registering a vCenter server by a non-administrator user with the required privileges
on page 62.
on page 62.
Now, a non-administrator user with the required privileges can use the OMIVV features with Dell hosts.
Defining privileges
To enable a non-administrator user with the required privileges to register a vCenter server, select the following privileges:
● Alarms
○ Create alarm
○ Modify alarm
○ Remove alarm
● Extension
○ Register extension
○ Unregister extension
○ Update extension
● Global
○ Cancel task
○ Log event
○ Settings
● Host
○ CIM
￭ CIM Interaction
○ Configuration
￭ Advanced settings
￭ Connection
￭ Maintenance
￭ Query patch
￭ Security profile and firewall
○ Inventory
￭ Add host to cluster
￭ Add standalone host
● Host profile
○ Edit
○ View
● Permissions
○ Modify permission
○ Modify role
● Sessions
○ Validate session
● Task
○ Create task
○ Update task
NOTE: While registering a vCenter server by a non-administrator user with the necessary privileges, an error message is displayed if the mentioned privileges are not assigned.
Console Administration 61
Registering a vCenter server by a non-administrator user with the required privileges
You can register a vCenter server for the OMIVV appliance by using a non-administrator user with the required privileges. See
on page 62 for more information on registering a vCenter server.
Assigning Dell privileges to the role
You can edit an existing role to assign the Dell privileges.
NOTE: Ensure that you are logged in as a user with Administrator privileges.
To assign the Dell privileges to an existing role, perform the following:
1. Log in to the vSphere client with administrative rights.
2. On the vSphere client Home page, click Roles .
3. Right-click the role to edit and select Edit Role .
4. Select the following privileges and click OK .
● Dell
○ Dell.Configuration
○ Dell.Deploy-Provisioning
○ Dell.Inventory
○ Dell.Monitoring
○ Dell.Reporting
See
Security Roles and Permissions
on page 10 for more information on the available OMIVV roles within vCenter.
The changes to permissions and roles take effect immediately. The non-administrator user with necessary privileges can now perform the OpenManage Integration for VMware vCenter operations.
NOTE: For all vCenter operations, OMIVV uses the privileges of the registered user and not the privileges of the logged-in user.
Registering a vCenter Server
You can register the OpenManage Integration for VMware vCenter after the OpenManage Integration for VMware vCenter is installed. OpenManage Integration for VMware vCenter uses the admin user account or a non-administrator user account with necessary privileges for vCenter operations. OpenManage Integration for VMware vCenter currently supports 10 vCenters per
OMIVV appliance that can be changed later.
1. Open Administration Console .
2. To register a new vCenter server, in the left pane, click VCENTER REGISTRATION , and then click Register New vCenter
Server .
3. In the Register a New vCenter dialog box, under vCenter Name do the following: a. In the vCenter Server IP or Hostname text box, enter the vCenter IP address or FQDN of the host.
NOTE: Registering OMIVV with the VMware vCenter by using Fully Qualified Domain Name (FQDN) is highly recommended. For all registrations, the host name of vCenter should be properly resolvable by the DNS server. The following are the recommended practices for using the DNS server:
● Assign a static IP address and host name when you deploy an OMIVV appliance with a valid DNS registration. A static IP address ensures that during the system restart, the IP address of the OMIVV appliance remains same.
● Ensure that OMIVV host name entries are present in both forward and reverse lookups.
b. In the Description text box, enter an optional description.
4. Under vCenter User Account , do the following: a. In the vCenter User Name text box, enter the administrator’s user name or a non-administrator user name with the required privileges.
b. In the Password text box, enter the password.
c. In the Verify Password text box, enter the password again.
62 Console Administration
5. Click Register .
NOTE: For all vCenter operations, OMIVV uses the privileges of the registered user and not the privileges of the logged-in user.
For example: Suppose, a user X with the necessary privileges registers OMIVV with vCenter and user Y has only Dell privileges.
The user Y can now log in to the vCenter and can trigger a firmware update task from OMIVV. While performing the firmware update task, OMIVV uses the privileges of user X to put the host into maintenance mode or reboot the host.
OpenManage Integration for VMware vCenter Requirements
The OpenManage Integration for VMware vCenter (OMIVV) requires information from OpenManage on older generation servers, and more current platforms are restricted to start at the version of vSphere that understands the newer chipset.
Due to this, there are limits on the version of vSphere that a given version of OMIVV works with.
Table 4. Supported ESXi versions on managed hosts
ESXi version support v5.0
11G
Y
12G
Server generation
Y
13G
N v5.0 U1 Y Y N v5.0 U2
Y Y N v5.0 U3
Y Y N v5.1
Y Y N v5.1 U1
Y Y N v5.1 U2
Y Y Y v5.1 U3
N Y Y v5.5
Y Y
(except M830, FC830, and
FC430)
N v5.5 U1
Y Y N v5.5 U2
Y Y Y v5.5 U3
Y Y Y v6.0
Y Y Y v6.0 U1 Y Y Y v6.0 U2 Y Y Y v6.0 U3 Y Y Y
Table 5. Supported vCenter Server versions for release 3.2
vCenter version Desktop client support v5.1 U2
Y v5.1 U3
Y
Web client support
N
N
Console Administration 63
Table 5. Supported vCenter Server versions for release 3.2 (continued)
v5.5 U1 vCenter version Desktop client support
Y v5.5 U2
Y v5.5 U3
Y v6.0
Y v6.0 U1 Y v6.0 U2 Y v6.0 U3 Y
Web client support
Y
Y
Y
Y
Y
Y
Y
Modifying the vCenter Login
The vCenter login credentials can be modified by a user with administrative privileges or a non-administrator user with necessary privileges.
1. In OpenManage Integration for VMware vCenter, on the Summary tab, use the link to open the Administration Console .
2. In the Login dialog box, type your password.
3. In the left pane, click VCENTER REGISTRATION . The registered vCenters are displayed in the right pane. To open the
Modify vCenter Acct window, under Credentials , click Modify .
4. Enter the vCenter User Name , Password , and Verify Password ; the passwords must match.
5. To change the password, click Apply , or to cancel the change click Cancel .
NOTE: An error message is displayed if the necessary privileges are not assigned to a non-administrator user who is modifying the vCenter login credentials.
Updating The SSL Certificates For Registered vCenter Servers
If the SSL certificate is changed on a vCenter server, then use the following steps to import the new certificate for the
OpenManage Integration for VMware vCenter. The OpenManage Integration for VMware vCenter uses this certificate to make sure the vCenter server it is talking to is the correct vCenter server and not an impersonator.
OpenManage Integration for VMware vCenter uses the openssl API to create the Certificate Signing Request (CSR) using the
RSA encryption standard with a 2048 bit key length. The CSR generated by the OpenManage Integration for VMware vCenter is used to get a digitally signed certificate from a trusted Certification Authority. The OpenManage Integration for VMware vCenter uses the digital certificate to enable SSL on the Web server for secure communication.
1. Launch a web Browser then enter https://<ApplianceIPAdrdress>
2. In the left pane, click VCENTER REGISTRATION . The registered vCenters are displayed in the right pane. To update the certificates, click Update .
Uninstalling the OpenManage Integration for VMware vCenter
To remove the OpenManage Integration for VMware vCenter, it must be unregistered from the vCenter server using the
Administration Console.
1. Launch a web browser then enter https://<ApplianceIPAdrdress>
2. In the vCenter Registration page, under the vCenter server table, unregister the OpenManage Integration for VMware vCenter by clicking Unregister .
You may have more than one vCenter, so be sure select the right one.
3. In the Unregister vCenter dialog box that asks if you really want to unregister this server, click Unregister .
64 Console Administration
Uploading a OpenManage Integration for VMware vCenter License to the Administration Console
1. In OpenManage Integration for VMware vCenter, on the Summary tab, use the link to open the Administration Console.
2. In the Login dialog box, type your password.
3. In the left pane, click VCENTER REGISTRATION . The registered vCenters are displayed in a table. To display the upload license dialog box, click Upload License .
4. To navigate to the license file, click the Browse button, to navigate to the license file, and then click Upload .
NOTE: If the license file is modified or edited in any way, the appliance views it as corrupted and the file will not work.
NOTE: You can add licenses if you need to add more hosts. Follow the process mentioned above to add more licenses.
NOTE: If the number of successfully inventoried 11th, 12th, and 13th generation servers equals the number of purchased licenses. Edit existing connection profiles by removing few 11th, 12th, or 13th generation servers. Create a new connection profile for the removed 11th, 12th, or 13th generation servers.
Virtual Appliance Management
Virtual appliance management contains the OpenManage Integration for VMware vCenter network, version, NTP, and HTTPS information, and lets an administrator:
● Restart the virtual appliance
● Update the virtual appliance, and configure an update repository location
● Generate a troubleshooting bundle that contains appliance logging information.
● Enter Network Time Protocol (NTP) settings
● Upload and manage HTTPS certificates
Related Tasks:
●
Restarting The Virtual Appliance
●
Updating A Repository Location And Updating An Appliance
●
Downloading Troubleshooting Bundle
●
Restarting the Virtual Appliance
Restarting the virtual appliance logs you out from the Administration Console, and the OpenManage Integration for VMware vCenter is unavailable until the virtual appliance and its services are active.
1. In OpenManage Integration for VMware vCenter, under Administrative Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click APPLIANCE MANAGEMENT .
4. To restart the OpenManage Integration for VMware vCenter, click Restart the Virtual Appliance .
5. On the Restart Virtual Appliance dialog box, to restart the virtual appliance click Apply or click Cancel to cancel.
Updating a Repository Location and Virtual Appliance
Perform a backup prior to an update of the virtual appliance to make sure all data is protected. See,
1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click APPLIANCE MANAGEMENT .
4. Next to Appliance Update, click Edit .
Console Administration 65
5. In the Appliance Update window, enter the Repository Location URL , and then click Apply .
NOTE: If the update location is on an external network, such as the Dell FTP site, then a proxy must be entered in the
HTTP Proxy area.
Updating the Virtual Appliance Software
To prevent data loss, perform an appliance backup prior to beginning the software update.
1. Launch a web Browser then enter https://<ApplianceIPAddress>.
2. In the left pane, click APPLIANCE MANAGEMENT .
3. To update the virtual appliance to the software version listed under Appliance Update , click Update Virtual Appliance .
4. In the Update Appliance dialog box, the current and available versions are listed. To begin the update, click Update .
5. The system is locked down and put into maintenance mode. When the update is complete, the Appliance page displays showing the newly installed version.
Downloading the Troubleshooting Bundle
Use this information to assist in troubleshooting issues, or send to Technical Support.
1. Launch a web Browser then enter https://<ApplianceIPAddress>.
2. In the left pane, click APPLIANCE MANAGEMENT .
3. To generate the troubleshooting bundle dialog box, click Generate Troubleshooting Bundle .
4. Click the Download Troubleshooting Bundle link.
5. To exit, click Close .
Setting Up The HTTP Proxy
You can set up the HTTP proxy settings using the Administration Console.
1. In OpenManage Integration for VMware vCenter, on the Summary tab, use the link to open the Administration Console.
2. In the Login dialog box, type your password.
3. In the left pane, click APPLIANCE MANAGEMENT .
4. In the Appliance Management page, scroll down to the HTTP Proxy Settings , and then click Edit .
5. In the Edit page, do the following: a. To enable the use of HTTP Proxy Settings, next to Use HTTP Proxy Settings , select Enable .
b. In the Proxy Server Address text box, enter the proxy server address.
c. In the Proxy Server Port text box, enter the proxy server port.
d. To use proxy credentials, next to Use Proxy Credentials , select Yes .
e. If you are using credentials, in the User Name text box, enter the user name.
f. In the Password text box, type the password.
6. Click Apply .
Setting Up the NTP Servers
Use the Network Time Protocol (NTP) to synchronize the virtual appliance clocks to that of a NTP server.
1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click APPLIANCE MANAGEMENT .
4. Click Edit under NTP Settings .
5. Select the Enabled check box. Enter the host name or IP address for a Preferred and Secondary NTP Server and click
Apply .
6. To exit, click Cancel .
66 Console Administration
NOTE: It might take around 10 minutes for the virtual appliance clocks to synchronize with the NTP server.
Generating a Certificate Signing Request
NOTE: You must upload the certificate before registering the OpenManage Integration for VMware vCenter with the vCenter.
Generating a new Certificate Signing Request prevents certificates that are created with the previously generated CSR from being uploaded to the appliance.
1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click APPLIANCE MANAGEMENT .
4. Click Generate Certificate Signing Request for HTTPS Certificates . A message displays stating that if a new request is generated, then certificates created using the previous CSR can no longer be uploaded to the appliance. To continue with the request, click Continue , or Cancel to cancel.
5. Enter the Common Name , Organizational Name , Organizational Unit , Locality , State Name , Country and Email for the request. Click Continue .
6. Click Download , and then save the resulting certificate request to an accessible location.
Uploading an HTTPS Certificate
You can use HTTPS Certificates for secure communication between the virtual appliance and host systems. To set up this type of secure communication, a certificate signing request must be sent to a certificate authority and then the resulting certificate is uploaded using the Administration Console. There is also a default certificate that is self-signed and can be used for secure communication; this certificate is unique to every installation.
NOTE: You can use Microsoft Internet Explorer , Firefox, Crome to upload certificates.
1. In OpenManage Integration for VMware vCenter, on the Summary tab, use the link to open the Administration Console.
2. In the Login dialog box, type your password.
3. In the left pane, click APPLIANCE MANAGEMENT .
4. Click Upload Certificate for HTTPS Certificates .
5. In the Upload Certificates dialog box, click OK .
6. To select the certificate to upload, click Browse , and then click Upload .
7. If you want to abort the upload, click Cancel .
NOTE: The certificate must use PEM format.
Restoring the Default HTTPS Certificate
NOTE: If you want to upload a custom certificate for your appliance, you need to upload the new certificate prior to vCenter registration. If you upload the new custom certificate after vCenter registration, communication errors are displayed in the Web client. To fix this issue, you need to unregister and reregister the appliance with the vCenter.
1. In OpenManage Integration for VMware vCenter, on the Summary tab, use the link to open the Administration Console.
2. In the Login dialog box, type your password.
3. In the left pane, click APPLIANCE MANAGEMENT .
4. Click Restore Default Certificate link under HTTPS Certificates .
5. In the restore default certificate dialog box, click Apply .
Setting up Global Alerts
Alert management lets you enter global settings for how alerts are stored for all vCenter instances.
Console Administration 67
1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click ALERT MANAGEMENT . To enter new vCenter alert settings, click Edit .
4. Enter numeric values for the following items:
● Maximum number of alerts
● Number of days to retain alerts
● Timeout for duplicate alerts (seconds)
5. To save your settings, click Apply , or click Cancel to cancel.
Managing Backup And Restore
Managing backup and restore is accomplished from the Administrative Console. Tasks on this page include:
●
Configuring Backup And Restore
●
●
Performing An Immediate Backup
●
Restoring The Database From Backup
Configuring Backup And Restore
The backup and restore function backs up the OpenManage Integration for VMware vCenter database to a remote location from which it can be restored later. Profiles, templates, and host information are included in the backup. It is recommended that you schedule automatic backups to guard against data loss. After this procedure, you must configure a backup schedule.
NOTE: NTP Settings are not saved and restored.
1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click BACKUP AND RESTORE .
4. To edit the current backup and restore settings, click Edit .
5. In the Settings and Details page, do the following: a. In the Backup Location text box, type the path to the backup files.
b. In the User Name text box, type the user name.
c. In the Password text box, type the password.
d. Under Enter the password used to encrypt backups , type the encrypted password in the text box.
The encryption password can contain alpha numeric characters and the following special characters: !@#$%*. There is no length restriction.
e. In the Verify Password text box, retype the encrypted password.
6. To save these settings, click Apply .
7. Configure the backup schedule. For more information, see Scheduling Automatic Backups .
Scheduling Automatic Backups
This is the second part of configuring backup and restore. For detailed information on configuring the backup location and credentials, see
Configuring Backup And Restore
.
To schedule an automatic backup:
1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click BACKUP AND RESTORE .
4. To edit the backup and restore settings, click Edit Automatic Scheduled Backup (this makes fields active).
5. To enable the backups, click Enabled .
68 Console Administration
6. Select the check boxes for the days of the week for which you want to run the backup.
7. In the Time for Backup (24 Hour Time Format, HH:mm) text box, enter the time in HH:mm format.
The Next Backup populates with the date and time of the next scheduled backup.
8. Click Apply .
Performing An Immediate Backup
1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click BACKUP AND RESTORE .
4. Click Backup Now .
5. To use location and encryption password from the Backup settings, in the Backup Now dialog box, select that check box.
6. Enter a Backup Location , User Name , Password , and Encryption Password .
The encryption password can contain alpha numeric characters and the following special characters: !@#$%*. There is no length restriction.
7. Click Backup .
Restoring the Database from a Backup
NOTE: The restore operation causes the virtual appliance to reboot after it has completed.
1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration
Console.
2. In the Login dialog box, type your password.
3. In the left pane, click BACKUP AND RESTORE and the current backup and restore settings are displayed.
4. Click Restore Now .
5. In the Restore Now dialog box, enter a File Location along with the backup .gz file (CIFS/NFS Format).
6. Enter the User Name , Password , and Encryption Password for the backup file.
The encryption password can contain alpha numeric characters and the following special characters: !@#$%*. There is no length restriction.
7. To save your changes, click Apply .
The appliance reboots or restarts once Apply is clicked.
Understanding the vSphere Client Console
The vSphere Client Console is found within the vSphere Client on a virtual machine. The Console works hand in hand with the Administration Console. The Console provides the ability to:
●
●
Change the virtual appliance password
●
●
●
Reset the virtual appliance to factory settings
●
●
●
●
Upgrading OpenManage Integration Plugin from 3.0 version to the current version
on page 71
Console Administration 69
●
Migration Path to migrate from 2.x to 3.1
on page 72
Use the arrow keys to navigate up or down. Once you have selected the option you want, press <ENTER> . After you access the Console screen, VMware vSphere Client takes control of your cursor. To escape from that control, press <CTRL> +
<ALT> .
Configuring Network Settings
Changes to the network settings are done in the vSphere Client Console.
1. In vSphere Web Client, in the Navigator, select vCenter .
2. In the Navigator, select the Virtual Machine that you want to manage.
3. Do one of the following:
● On the Object tab, select Action > Open Console .
● Right-click the virtual machine that you selected and select Open Console .
4. In the Console window, select Configure Network , then press <ENTER> .
5. Enter the desired network settings under Edit Devices or under Edit DNS configuration, then click Save & Quit . To abort any changes, click Quit .
Changing The Virtual Appliance Password
The virtual appliance password can be changed in the vSphere Client using the appliance console.
To change the virtual appliance password:
1. Log in to the vCenter/ESXi host where the OpenManage Integration for VMware vCenter is deployed. Select the
OpenManage Integration for VMware vCenter virtual machine and click the Console tab.
2. Log in to the appliance using username as admin and password which was set earlier.
3. In the OpenManage Integration for VMware vCenter Virtual Appliance Setup window, click on Change Admin Password .
4. In the Change Password Window, enter the Current Password
5. In the New Password enter the new password.
6. In the Confirm New Password enter the new password for confirmation.
7. Click on Change Password Button
A message, Password was updated successfully is displayed.
8. Click OK .
Setting The Local Time Zone
To set the local time zone:
NOTE: You can only edit the timezone and not the current time and date.
1. In vSphere Client , select the OpenManage Integration for VMware vCenter virtual machine, and then click the Console tab.
2. Select Set Time Zone and press <ENTER> .
3. In the Timezone Selection window, select the desired time zone and click OK . To cancel changes click Cancel . The time zone is updated.
Rebooting Virtual Appliance
To reboot the virtual appliance:
1. In vSphere Client , select the OpenManage Integration for VMware vCenter virtual machine, and then click the Console tab.
2. Select Reboot this Virtual Appliance and press <ENTER> .
70 Console Administration
3. The following message is displayed:
If there are any processes running on this appliance they will be terminated by this action. Are you sure you wish to do this?
4. Enter y to reboot or n to cancel. The appliance is rebooted.
Resetting The Virtual Appliance To Factory Settings
To reset the virtual appliance to factory settings:
1. In vSphere Client , select the OpenManage Integration for VMware vCenter virtual machine, and click the Console tab.
2. Select Reset this Virtual Appliance to Factory Settings and press <ENTER> .
3. The following notice is displayed:
This operation is completely Irreversible if you continue you will completely reset
*this* appliance to its original settings. All changes you have made to this appliance will be Lost. Are you sure you wish to Reset this Appliance to Factory
Settings?
4. Enter y to reset or n to cancel.
The appliance is reset to the original factory settings and all the all others settings and saved data will be lost.
NOTE: When the virtual appliance is reset to factory settings, any updates made to the Network Configuration are preserved; these settings are not reset.
Refreshing the Console View
To refresh the Console view, select Refresh and press <ENTER> .
Logging out from the console
To log out from the console, click Log out in the top right corner against your logged-in account.
Read-only User Role
There is an unprivileged user role called readonly with shell access for diagnostic purposes. The read-only user has limited privileges to run the mount. The readonly user's password is set as readonly . The readonly user’s password has changed from admin password (for OMIVV v1.0 to v3.2) for security purposes.
Upgrading OpenManage Integration Plugin from 3.0 version to the current version
To upgrade OpenManage Integration plug-in from version 3.0 to the current version, perform the following steps:
1. Open a web browser and enter the Administration Console URL displayed in the vSphere vCenter Console tab for the virtual machine you want to configure. You can also use the link displayed on the Help and Support page in the Dell Management
Console. The URL is represented in the following format and is case-insensitive: https://<ApplianceIPAddress>
2. In the left pane of the ADMINISTRATION CONSOLE window, click APPLIANCE MANAGEMENT .
3. Depending on your network settings, enable proxy and provide proxy settings if your network needs proxy.
4. To upgrade OpenManage Integration plug-in from version 3.0 to the current version, do one of the following:
● Ensure that Update Repository Path is set to http://linux.dell.com/repo/hardware/vcenter-plugin-x64/latest/ path.
If the path is different, in the Appliance Management window, in the APPLIANCE UPDATE section, click Edit to update the path to http://linux.dell.com/repo/hardware/vcenter-plugin-x64/latest/ in the Update
Repository Path text box. Click Apply to save the updates.
Console Administration 71
● If there is no internet connectivity, download all the files and folders from the http://linux.dell.com/repo/ hardware/vcenter-plugin-x64/latest/ path and copy them to an HTTP share. In the Appliance Management window, in the APPLIANCE UPDATE section, click Edit , and then in the Update Repository Path text box, update the path to the offline HTTP share, and click Apply .
5. Compare the available virtual appliance version and current virtual appliance version and ensure that the available virtual appliance version is greater than the current virtual appliance version.
6. To apply the update to the virtual appliance, under Appliance Settings , click Update Virtual Appliance .
7. In the UPDATE APPLIANCE dialog box, click Update . After you click Update , you are logged off the ADMINISTRATION
CONSOLE window.
NOTE: While upgrading OMIVV from 3.0 to the current version, the custom certificate is not migrated and you must reapply the settings that you had applied for the certificate.
Migration Path to migrate from 2.x to 3.1
Do the following to migrate from older version to the OMIVV 3.1 version:
1. Take a backup of the database for the older release.
2. Power off the older appliance from the vCenter.
NOTE: Do not unregister the plug-in from the vCenter. Unregistering the plug-in from the vCenter removes all the
Alarms registered on the vCenter by the plug-in and all the customization that is performed on the alarms, such as actions and so on, on the vCenter.
3. Deploy the new OpenManage Integration version 3.1 OVF.
4. Power on the OpenManage Integration version 3.1 appliance.
5. Set up the network, time zone, and so on, to the appliance. It is mandatory that the new OpenManage Integration version 3.1
appliance has the same IP address as the old appliance.
NOTE:
The plug-in might not work properly if the IP address for the 3.1 appliance is different from the IP address of the older appliance. In such a scenario, you should unregister and re-register all the vCenter instances.
6. Restore the database to the new appliance.
7. Verify the appliance. For more information, see Installation Verification in this guide to ensure the database migration is successful.
8. Run the Inventory on all the registered vCenter.
NOTE:
It is recommended that you run the inventory on all the hosts managed by the plug-in again after the upgrade. For more information, see Running Inventory Jobs in OpenManage Integration for VMware vCenter User’s Guide available at dell.com/support/manuals for steps to run the inventory on demand.
If the IP address of the new OpenManage Integration version 3.1 appliance has changed from that of the old appliance, the trap destination for the SNMP traps must be configured to point to the new appliance. For 12th generation and higher generation servers, this is fixed by running the Inventory on these hosts. For hosts earlier than 12th generation that were compliant with earlier versions, this IP change shows up as noncompliant and requires you to configure OMSA.
72 Console Administration
7
Troubleshooting
Use this section to find answers to troubleshooting questions. This section includes:
●
Frequently asked questions (FAQ)
●
●
●
Topics:
•
Frequently Asked Questions (FAQ)
•
•
•
OpenManage Integration for VMware vCenter Related Information
Frequently Asked Questions (FAQ)
This section contains some common questions and solutions.
OMIVV cannot act as a provisioning server during the auto discovery process
If OMIVV IP address is used as a provisioning server in the iDRAC settings for the newly added Dell servers, these Dell servers will not be auto discovered. The auto discovery process fails as OMIVV 3.2 does not support MD5 encrypted SSL certificate signatures to enhance more secure encryption.
Resolution: None.
Intermittent Inventory failure for 1st time after OSD
In case of intermittent inventory failure post first time deployment, user might observe the error "No inventory record found for the host <IP / Host name>"
Resolution: Intermittent inventory failure post first time OSD can be resolved by running the inventory manually.
Test connection for iDRAC in the connection profile page fails in
DNC once OSD is successful
After OS deployment, immediate test connection to iDRAC fails and shows an error, "Fail - Unable to connect to iDRAC" in the connection profile page.
Resolution: This issue occurs since BMC is unable to obtain an IP address. To resolve this issue, you must restart the management network. If the issue still persist, user will have to restart the ESXi host.
Troubleshooting 73
Dell privileges that are assigned while registering the OMIVV appliance are not removed after unregistering OMIVV
After registering vCenter with an OMIVV appliance, several Dell privileges are added to the vCenter privilege list. Once you unregister vCenter from the OMIVV appliance, the Dell privileges are not removed.
NOTE: Although the Dell privileges are not removed, there is no impact to any OMIVV operations.
Version Affected: 3.1
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?
If vCenter is idle for few hours, the OMIVV content is replaced by a "!" icon when you click the OpenManage Integration tab of an inventoried host and Dell Management Center icon to perform any actions.
Resolution: You can resume the session by closing the current session and logging in again.
Version Affected: 3.1, vCenter 6.0 and later
Dell Management Center does not display all the relevant logs when trying to filter a severity category. How can I view all the logs?
When you select a severity category to filter the log data by choosing All Categories from the drop-down, all the logs belonging to specific category are displayed accurately. However, if you filter by choosing Info from the drop-down, the
Firmware update logs are not displayed and only the task initiation logs are displayed.
Resolution: To view all the logs in Dell Management Center, select All Categories from the Filter drop-down.
Version Affected: 3.1
How can I change the status of the OMIVV plug-in to Enabled?
After OMIVV is installed and registered with the vCenter Server, the status of OMIVV plug-in might not display the Enabled status in some situations. The Download and Install status is displayed instead of the Enabled status.
To change the status of OMIVV plug-in to Enabled, perform the following steps:
1. Log out from vSphere Client, and vSphere Web Client.
2. Boot the OMIVV appliance into a single User mode.
3. Edit the /etc/hosts file: <vCenterIP> <myvCenter.mydomain.com> <myvCenter> and add a DNS entry for the vCenter Server.
For example, 10.35.210.126 myvCenter.us.dell.com myvCenter
4. Reboot the OMIVV appliance. Perform either of the following steps depending on the usage of vCenter appliance.
a. If you use Windows vCenter Server, edit the hosts file at c:\system\window32\drivers\etc\hosts and add a DNS entry for the OMIVV appliance.
For example, 10.35.210.120 myomivv.us.dell.com myomivv.
Execute the following command to flush DNS: ipconfig /flushdns b. If you use vCenter appliance, edit the /etc/hosts file and add a DNS entry for the OMIVV appliance.
For example, 10.35.210.120 myomivv.us.dell.com myomivv.
Reboot the vCenter appliance.
5. Click Unregister to unregister OMIVV.
6. Re-log into vSphere Client and vSphere Web Client to verify that the OMIVV plug-in displays the Enabled status.
74 Troubleshooting
Version Affected: 3.0
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?
While restoring from a backup created previously, OpenManage Integration for VMware vCenter might not display the Dell
Management Center icon.
Resolution: You can resolve this issue by unregistering the vCenter server from the OMIVV appliance and registering the vCenter server again.
Version Affected: This issue might be only seen when restoring a backup from OMIVV 3.0.0.173 build number to OMIVV
3.0.0.197 build number.
OMIVV version for is not updated from About Screen after the
Appliance is updated
This is a known issue with the Internet Explorer where it is still using the old cache values. Clearing the IE's cache would show the correct version.
Using OpenManage Integration for VMware vCenter to update an
Intel Network card with the firmware version of 13.5.2 is not supported.
There is a known issue with Dell PowerEdge 12th generation servers and some Intel Network cards with the firmware version of
13.5.2. Updating some models of Intel network cards at this version of firmware fails when the firmware update is applied using the Lifecycle Controller. Customers with this version of firmware must update the network driver software using an operating system. If the Intel Network card has a version of firmware other than 13.5.2, you can update using OpenManage Integration for VMware vCenter. For more information, see http://en.community.dell.com/techcenter/b/techcenter/archive/2013/03/20/ intel-network-controller-card-with-v13-5-2-firmware-cannot-be-upgraded-using-lifecycle-controller-to-v13-5-6.aspx
NOTE: Note: When using the one-to-many firmware update, avoid selecting Intel network adapters that are at version
13.5.2, as the update will fail and stop the update task from updating remaining servers.
On running a warranty retrieval job, the warranty job status is not listed in the Warranty Job Queue page
If your network needs proxy details to connect to the internet and the proxy is not set on the OMIVV appliance, the warranty retrieval job fails and the job is not listed under warranty job queue.
Resolution: Set the proxy details and trigger the warranty job again.
Version Affected: All
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
This is a known issue with NIC 14.5 and 15.0. You must use the custom catalog to update the firmware to 15.5.0 first before updating the firmware to 16.x.
Version Affected: All
Troubleshooting 75
On trying a firmware update with an invalid DUP, the hardware update job status on the vCenter console neither fails nor timesout for hours, though the job status in LC says ‘FAILED’. Why is this happening?
When the invalid DUP is picked for firmware update, the status of the task in the vCenter console window remains ‘In Progress’ but the message is changed to the reason of failure. This is a known VMware defect and will be fixed in the future releases of
VMware vCenter.
Resolution: The task has to be cancelled manually.
Version Affected: All
Administration Portal is still showing the unreachable Update
Repository location.
If the user provided a unreachable Update Repository path, the error message “Failed: Error while connecting to the URL …. ” is displayed on the top of the Appliance Update view, however the Update Repository Path is not cleared out to the value before update.
Resolution: Move out of this page to another page and make sure the page is refreshed.
Version Affected: All
Why is the DNS configuration settings restored to original settings after appliance reboot if using DHCP for appliance IP and DNS settings overwritten
There is a known defect where statically assigned DNS settings are replaced by values from DHCP. This can happen when
DHCP is used to obtain IP settings, and DNS values are assigned statically. When the DHCP lease is renewed or the appliance is restarted the statically assigned DNS settings are removed. Resolution: Statically assign IP settings when the DNS server settings will be different from DHCP.
Version Affected: All
Why did my system not enter maintenance mode when I performed a one-to-many firmware update?
Some firmware updates do not require rebooting the host. In that case, the firmware update is performed without putting the host into maintenance mode.
Even if my repository has bundles for selected 11G system, why is firmware update showing that I have no bundles for Firmware
Update?
When I added a host to the connection profile in lockdown mode, the inventory kicked off but failed stating that “No Remote
Access Controller was found or Inventory is not supported on this host.” Inventory is supposed to work for a host in lockdown mode, right?
If you put the host in lockdown mode or remove a host from lockdown mode, you must wait 30–minutes before performing the next operation. If you use a 11G host for firmware update, the firmware update wizard will not show any bundles even if the repository provided has bundles for that system. This occurs because the 11G host might have not been configured for OMSA to send traps to OpenManage Integration.
76 Troubleshooting
Resolution: Ensure that the host is compliant using the host Compliance screen of OpenManage Integration desktop client. If it is not compliant, use the fix Host Compliance to get it compliant.
Version Affected: 2.2 and later
Why Does My ESXi Deployment Fail on Servers Having a PERC
S300 Boot Controller?
Deployments of OpenManage Integration for VMware vCenter using different ESXi versions on Dell PowerEdge servers with the
PERC S300 boot controller failed. The Dell customized ESXi operating systems do not carry the driver for the PERC S300 boot controller, which causes the boot controller/HDD not to be recognized during operating system installation. Servers with PERC
S300 boot controllers are not supported for OpenManage Integration for VMware vCenter deployments.
How Come I See An Error Message Displayed After Clicking The
Firmware Link?
If you have a slow network speed (9600BPS), you may get a Communication Error Message. This error message may display when you click the Firmware link in the vSphere Client for the OpenManage Integration for VMware vCenter. It happens when the connection times out while trying to obtain the Software Inventory list. Microsoft Internet Explorer initiates this timeout. For
Microsoft Internet Explorer versions 9/10, the default “Receive Time out” value is set to 10 seconds. Fix this issue by using the following steps.
Figure 5. Firmware link communication error
1. Open Microsoft Registry Editor (Regedit).
2. Navigate to the following location:
KHEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
3. Add a DWORD value for ReceiveTimeout.
4. Set the value to 30 seconds (30000) [This value may need to be a higher value in your environment].
5. Exit Regedit.
6. Restart Internet Explorer.
NOTE: Just opening a new Internet Explorer window is not enough. Restart the Internet Explorer browser.
What generation of Dell servers does the OpenManage Integration for VMware vCenter configure and support for SNMP traps?
OpenManage Integration for VMware vCenter supports OMSA SNMP traps on pre-12th generation servers and iDRAC traps on
12th generation servers.
Troubleshooting 77
How does the OpenManage Integration for VMware vCenter support more than three vCenters in Linked Mode?
Each virtual appliance supports a maximum of three vCenters in Linked Mode. If you have more than ten vCenters, you need a new instance of the appliance for every ten vCenters with associated licensing.
Does OpenManage Integration for VMware vCenter support vCenter in linked mode?
Yes , OpenManage Integration for VMware vCenter supports up to 10 vCenters either in a linked mode or not in a linked mode also. For more information on how OpenManage Integration for VMware vCenter works in linked mode, see the white paper,
OpenManage Integration for VMware vCenter: Working in Linked Mode on www.Dell.com.
What are required port settings for OMIVV?
NOTE: When deploying the OMSA agent by using the Fix non-compliant vSphere hosts link available from the
Compliance window in OMIVV, OMIVV starts the http client service and enables port 8080 on releases after ESXI 5.0
to download the OMSA VIB and install it. After the OMSA VIB installation is complete, the service automatically stops and the port is closed.
Use the following port settings for OMIVV:
Table 6. Virtual appliance ports
Port number Protocols Port type Direction Usage Configurable
21 FTP TCP
Max.
Encryption
Level
None Out
53
80
80
162
11620
443
443
4433
2049
4001–4004
11620
DNS
HTTP
HTTP
SNMP Agent
SNMP Agent
HTTPS
WSMAN
HTTPS
NFS
NFS
SNMP Agent
TCP
TCP
TCP
UDP
UDP
TCP
TCP
TCP
UDP
UDP
UDP
None
None
None
None
None
128–bit
128–bit
128–bit
None
None
None
Out
Out
In
In
In
In
In/Out
In
In/Out
In/Out
In
FTP command client
DNS client
Dell Online Data
Access
Administration
Console
SNMP Agent
(server)
No
No
No
No
No
SNMP Agent
(server)
HTTPS server
No iDRAC/OMSA communication
No
No
Auto Discovery No
Public Share No
Public Share
SNMP Agent
(server)
No
No
Table 7. Managed nodes
78 Troubleshooting
Table 7. Managed nodes
Port number Protocols
50
51
5353
631
69
111
162, 11620
443
2049
4001–4004
443
4433
8080
68
RMCP
IMP mDNS
IPP
TFTP
NFS
SNMP
WSMAN
NFS
NFS
HTTPS
HTTPS
HTTP
BOOTP
Port type
UDP
TCP
UDP
UDP
TCP
TCP
TCP
UDP/TCP
UDP/TCP
UDP/TCP
UDP/TCP
UDP
UDP/TCP
UDP
Max.
Encryption
Level
None
128–bit
None
None
128–bit
128–bit
128–bit
N/A
None
128–bit
128–bit
None
Direction
Out
In
In/Out
In/Out
In
Out
In
Out
N/A
In/Out
Out
In/Out
In
Out
Usage Configurable
Hardware events iDRAC/OMSA communication
Public Share
No
No
No
Public Share
HTTPS server
No
No
Auto Discovery No
HTTP server; downloads the
OMSA VIB and fixes noncompliant vSphere hosts
No
Remote Mail
Check Protocol
IMP Logical
Address
Maintenance
No
No
Multicast DNS No
No Internet Printing
Protocol (IPP)
Trivial File
Transfer
No
SUN Remote
Procedure Call
(Portmap)
Bootstrap
Protocol Client
No
No
What are the Minimum requirements for successful installation and operation of the virtual appliance?
The following settings outline the minimum appliance requirements:
● Google Chrome, version 28 and later
.
● Microsoft Internet Explorer, version 9 and 10
● Mozilla Firefox, version 22 and later
● Reserved Memory: 2 GB
NOTE: For optimal performance Dell recommends 3 GB.
● Disk: 43.5 GB.
● CPU: 2 virtual CPUs.
Troubleshooting 79
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?
The password of the user used from discovery is not changed to the new credential if only hardware profile template is selected for deployment. This is done intentionally so that the plugin is able to communicate with the iDRAC future use in deployment needs.
Why is the processor version “Not Applicable” in Processor view in the System overview page?
In case of PowerEdge 12 th Generation Dell Servers and higher generations, the processor version is in the Brand column. In case of lower generation servers processor version is shown in the Version column.
Why is the DNS configuration settings restored to original settings after appliance reboot if using DHCP for appliance IP and DNS settings overwritten
There is a known defect where statically assigned DNS settings are replaced by values from DHCP. This can happen when
DHCP is used to obtain IP settings, and DNS values are assigned statically. When the DHCP lease is renewed or the appliance is restarted the statically assigned DNS settings are removed. Resolution: Statically assign IP settings when the DNS server settings will be different from DHCP.
Version Affected: All
How come I do not see my new iDRAC version details listed on the vCenter Hosts & Clusters page?
After the successful completion of a firmware update task in the vSphere Desktop client’s recent tasks pane, refresh the
Firmware Update page and verify the firmware versions. If the page shows the old versions, then go to Host Compliance page in OpenManage Integration for VMware vCenter and check the CSIOR status of that host. If CSIOR is not enabled, then enable
CSIOR and reboot host. If the CSIOR was already enabled, then login to the iDRAC console, reset iDRAC, wait for few minutes, and then refresh the Firmware Update page in vSphere Desktop client.
How Do I Test Event Settings by Using OMSA to Simulate a
Temperature Hardware Fault?
To make sure that events are functioning correctly:
1. In the OMSA user interface, navigate to Alert Management > Platform Events .
2. Select the Enable Platform Event Filter Alerts check box.
3. Scroll down to the bottom, and click Apply Changes .
4. To make sure that a specific event is enabled, such as temperature warning, from the tree on the left, select Main System
Chassis .
5. Under Main System Chassis , select Temperatures .
6. Select the Alert Management tab, and select Temperature Probe Warning .
7. Select the Broadcast a Message check box, and select Apply Changes .
8. To cause the temperature warning event, from the tree view on the left, select Main System Chassis .
9. Select Temperatures under Main System Chassis .
10. Select the System Board Ambient Temp link, and select the Set to Values option button.
80 Troubleshooting
11. Set the Maximum Warning Threshold to below the current listed reading; for example if the current reading is 27, set the threshold to 25 .
12. Select Apply Changes , and the temperature warning event is generated. To cause another event, restore the original settings using the same Set to Values option. Events are generated as warnings, and then to a normal state. If everything is working properly, navigate to the vCenter Tasks & Events view; a temperature probe warning event should be displayed.
NOTE: There is a filter for duplicate events; if you try to trigger the same event too many times in a row, you will only receive one event. Allow at least 30 seconds between events to see all events.
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?
To resolve this issue on an 11th generation server:
1. Install OMSA with the Remote Enablement component on the host system.
2. If you are using the command line to install OMSA, make sure to specify the -c option . If OMSA is already installed, reinstall it with the -c option and restart the service: srvadmin-install.sh -c srvadmin-services.sh restart
For an ESXi host, you must install OMSA VIB using the VMware Remote CLI tool , and reboot the system.
Can the OpenManage Integration for VMware vCenter Support
ESXi with Lockdown Mode Enabled?
Yes. Lockdown Mode is supported in this release on hosts ESXi 5.0 and above.
When I tried to use lockdown mode, it failed.
When I added a host to the connection profile in lockdown mode, the inventory kicked off but failed stating that “No Remote
Access Controller was found or Inventory is not supported on this host.” Inventory is supposed to work for a host in lockdown mode, right?
If you put the host in lockdown mode or remove a host from lockdown mode, you must wait 30–minutes before performing the next operation on the OpenManage Integration for VMware vCenter.
On trying a firmware update with an invalid DUP, the hardware update job status on the vCenter console neither fails nor timesout for hours, though the job status in LC says ‘FAILED’. Why is this happening?
When the invalid DUP is picked for firmware update, the status of the task in the vCenter console window remains ‘In Progress’ but the message is changed to the reason of failure. This is a known VMware defect and will be fixed in the future releases of
VMware vCenter.
Resolution: The task has to be cancelled manually.
Version Affected: All
Troubleshooting 81
What Setting Should I Use For UserVars.CIMoeMProviderEnable
With ESXi 4.1 U1?
Set UserVars.CIMoemProviderEnabled
to 1.
I Am Using A Reference Server to Create a Hardware Profile But it
Failed. What Should I Do?
Check to make sure that minimum recommended versions of iDRAC firmware, Lifecycle Controller firmware, and BIOS are installed.
To make sure that the data retrieved from the reference server is current, enable Collect System Inventory On Restart
(CSIOR)
.
I Am Attempting to Deploy ESXi on a Blade Server and it Failed.
What Should I Do?
1. Make sure the ISO location (NFS path) and staging folder paths are accurate.
2. Make sure the NIC selected during assignment of server identity is on the same network as the virtual appliance.
3. If using static IP address , make sure the network information provided (including subnet mask and default gateway) is accurate. In addition, , make sure the IPaddress is not already assigned on the network.
4. Make sure at least one Virtual Disk is seen by the system. ESXi also installs to an internal RIPS SD card.
Why Are My Hypervisor Deployments Failing On R210 II Machines?
A timeout issue on R210 II systems produces a hypervisor deployments failure error due to the failure of the BIOS to boot from attached ISO. To resolve this issue, manually install hypervisor on the machine.
The NFS Share is Set Up With the ESXi ISO, but Deployment Fails with Errors Mounting the Share Location.
To find the solution:
1. Make sure the iDRAC is able to ping the appliance.
2. Make sure your network is not running too slow.
3. Make sure the ports: 2049, 4001 - 4004 are open and the firewall is set accordingly.
How Do I Force Removal of the Virtual Appliance?
1. Go to https://<vcenter_serverIPAddress>/mob
2. Enter the VMware vCenter admin credentials.
3. Click Content .
4. Click ExtensionManager .
5. Click UnregisterExtension .
6. Enter the extension key com.dell.plugin.openManage_integration_for_VMware_vCenter
, and then click
Invoke method .
7. Enter the extension key com.dell.plugin.openManage_integration_for_VMware_vCenter_WebClient
, and then click Invoke method .
8. Turn off the OpenManage Integration for VMware vCenter virtual appliance and delete it.
82 Troubleshooting
Entering a Password in the Backup Now Screen Receives an Error
Message
If you are using a low resolution monitor, the Encryption Password field is not visible from the BACKUP NOW window. You must scroll down the page to enter the encryption password.
My Firmware Update Failed. What Do I Do?
Check the virtual appliance logs to see if the tasks timed out. If so, iDRAC needs to be reset by performing a cold reboot. Once the system is up and running, check to see if the update was successful by either running an inventory or using the Firmware tab.
My vCenter Registration Failed. What Can I Do?
vCenter registration can fail due to communication issues, therefore if you are experiencing these issues one solution is to use a static IP address. To use a static IP address, in the Console tab of the OpenManage Integration for VMware vCenter and select
Configure Network > Edit Devices and enter the correct gateway and FQDN (Fully Qualified Domain Name). Enter the DNS server name under Edit DNS Config.
NOTE: Make sure that the virtual appliance can resolve the DNS server you entered.
Performance during Connection Profile Test Credentials is extremely slow or unresponsive.
The iDRAC on a server has only one user (for example, only root ) and the user is in a disabled state, or all users are in a disabled state. Communicating to a server in a disabled state causes delays. To fix this issue, you can either fix the disable state of the server, or reset iDRAC on the server to re-enable the root user to default setting.
To fix a server in a disabled state:
1. Open the Chassis Management Controller console and select the disabled server.
2. To automatically open the iDRAC console, click Launch iDRAC GUI .
3. Navigate to the user list in iDRAC console, and choose one of the following:
● iDRAC 6 : Select iDRAC settings > Network/Security tab > Users tab .
● iDRAC 7 : Select iDRAC settings > Users tab .
● iDRAC 8 : Select iDRAC settings > Users tab .
4. To edit the settings, in the User ID column, click the link for the admin (root) user.
5. Click Configure User , and then click Next .
6. In the User Configuration page for the selected user, select the check box next to Enable user, and then and click Apply .
Does the OpenManage Integration for VMware vCenter support the
VMware vCenter Server appliance?
Yes, the OpenManage Integration for VMware vCenter supports the VMware vCenter Server appliance.
Does the OpenManage Integration for VMware vCenter support the vSphere Web Client?
Yes, the OpenManage Integration for VMware vCenter supports the VMware vSphere Web client.
Troubleshooting 83
In the Administration Console, why the Update Repository Path is not set to default path after I reset the appliance to factory settings?
After you reset the appliance, go to the Administration Console, and then click APPLIANCE MANAGEMENT in the left pane. In the Appliance Settings page, the Update Repository Path is not changed to default path.
Resolution: In the Administration Console, manually copy the path in the Default Update Repository field to Update
Repository Path field.
After backup and restore of OpenManage Integration for VMware vCenter, why alarm settings are not restored?
Restoring the OpenManage Integration for VMware vCenter appliance backup does not restore all the Alarm settings. However, in the OpenManage Integration for VMware GUI, the Alarms and Events field displays the restored settings.
Resolution: In the OpenManage Integration for VMware GUI, in the Manage > Settings tab, manually change the Events and
Alarms settings.
Bare Metal Deployment Issues
This section deals with issues found during the deployment process.
Hardware Configuration Failure
● Before initiating a deployment task, make sure the system has completed CSIOR and is not in the process of rebooting.
● It is highly recommended that BIOS configuration be run in Clone mode, so that the reference server is an identical system.
● Some controllers do not allow creation of a RAID 0 array with one drive. This feature is supported only on high-end controllers, and the application of such a hardware profile can cause failures.
OS deployment failure on PowerEdge servers running iDRAC version 2.35.35.35
● While deploying the ESXi operating system, the host fails to load all the ESXi packages from the OMIVV appliance, displaying the following message:
Fatal error: 33 (Inconsistent data)
● It is recommended that you update the iDRAC firmware to version 2.40.40.40 or later.
Contacting Dell
NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog.
Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues:
1. Go to dell.com/support
2. Select your support category.
3. Verify your country or region in the Choose a Country/Region drop-down list at the bottom of the page.
4. Select the appropriate service or support link based on your need.
OpenManage Integration for VMware vCenter Related
Information
● View or download Dell server documentation for PowerEdge™ Servers: Dell PoweEdge manuals
● Dell OpenManage System Administrator documents: Dell OMSA documents
84 Troubleshooting
● Dell Lifecycle Controller documentation: DLCI documentation
Troubleshooting 85
8
Virtualization-related Events For Dell
PowerEdge Servers
The following table contains virtualization-related critical and warning events, including event name, description and severity level for 11th, 12th, and 13th generation of PowerEdge servers.
Table 8. Virtualization-related Events of 11th, 12th, and 13th Generation PowerEdge Servers
Event Name
Dell-Current sensor detected a warning value
Description
A current sensor in the specified system exceeded its warning threshold.
Severity
Warning
Recommended action
No action
Dell-Current sensor detected a failure value
Put the system into maintenance mode
Dell-Current sensor detected a non-recoverable value
Dell-Redundancy regained
Dell-Redundancy degraded
Dell - Redundancy lost
Dell - Power supply returned to normal
Dell - Power supply detected a warning
Dell - Power supply detected a failure
Dell - Power supply sensor detected a non-recoverable value
Dell - Memory Device Status warning
A current sensor in the specified system exceeded its failure threshold.
A current sensor in the specified system detected an error from which it cannot recover
Sensor Returned to Normal
Value
Error
Error
Info
A redundancy sensor in the specified system detected that one of the components of the redundancy unit has failed but the unit is still redundant.
A redundancy sensor in the specified system detected that one of the components in the redundant unit has been disconnected, has failed, or is not present.
Warning
Error
Info Sensor Returned to Normal
Value
A power supply sensor reading in the specified system exceeded a user definable warning threshold.
A power supply has been disconnected or has failed.
A power supply sensor in the specified system detected an error from which it cannot recover.
A memory device correction rate exceeded an acceptable value.
Warning
Error
Error
Warning
No action
No action
No action
Put the system into maintenance mode
No action
No action
Put the system into maintenance mode
No action
No action
86 Virtualization-related Events For Dell PowerEdge Servers
Table 8. Virtualization-related Events of 11th, 12th, and 13th Generation PowerEdge Servers (continued)
Event Name
Dell - Memory Device error
Description
A memory device correction rate exceeded an acceptable value, a memory spare bank was activated, or a multibit
ECC error occurred.
Severity
Error
Recommended action
Put the system into maintenance mode
No action Dell - Fan enclosure inserted into system
Dell - Fan enclosure removed from system
Dell - Fan enclosure removed from system for an extended amount of time
Dell - Fan enclosure sensor detected a non-recoverable value
Sensor returned to normal value.
A fan enclosure has been removed from the specified system.
A fan enclosure has been removed from the specified system for a user-definable length of time.
A fan enclosure sensor in the specified system detected an error from which it cannot recover.
Sensor Returned to Normal
Value.
Info
Warning
Error
Error
Dell - AC power has been restored
Dell - AC power has been lost warning
Dell - An AC power cord has lost its power
Dell - Processor sensor returned to a normal value
Dell - Processor sensor detected a warning value
Info
An AC power cord has lost its power, but there is sufficient redundancy to classify this as a warning.
An AC power cord has lost its power, and lack of redundancy requires this to be classified as an error.
Warning
Error
Info Sensor Returned to Normal
Value
A processor sensor in the specified system is in a throttled state.
Warning
Error Dell - Processor sensor detected a failure value
A processor sensor in the specified system is disabled, has a configuration error, or experienced a thermal trip.
A processor sensor in the specified system has failed.
Dell - Processor sensor detected a non-recoverable value
Dell - Device configuration error
Dell - Battery sensor returned to a normal value
Dell - Battery sensor detected a warning value
A configuration error was detected for a pluggable device in the specified system.
Sensor Returned to Normal
Value
A battery sensor in the specified system detected that a battery is in a predictive failure state.
Error
Error
Info
Warning
No action
No action
No action
No action
No action
No action
No action
No action
No action
No action
No action
No action
No action
Virtualization-related Events For Dell PowerEdge Servers 87
Table 8. Virtualization-related Events of 11th, 12th, and 13th Generation PowerEdge Servers (continued)
Event Name
Dell - Battery sensor detected a failure value
Dell - Battery sensor detected a nonrecoverable value
Dell - Thermal shutdown protection has been initiated
Description
A battery sensor in the specified system detected that a battery has failed.
Severity
Error
A battery sensor in the specified system detected that a battery has failed.
This message is generated when a system is configured for thermal shutdown due to an error event. If a temperature sensor reading exceeds the error threshold for which the system is configured, the operating system shuts down and the system powers off. This event may also be initiated on certain systems when a fan enclosure is removed from the system for an extended period of time.
Error
Error
Recommended action
No action
No Action
No action
Info No action Dell - Temperature sensor returned to a normal value
Dell - Temperature sensor detected a warning value
Dell - Temperature sensor detected a failure value
Dell - Temperature sensor detected a non-recoverable value
Dell - Fan sensor returned to a normal value
Dell - Fan sensor detected a warning value
Dell - Fan sensor detected a failure value
Dell - Fan sensor detected a nonrecoverable value
Dell - Voltage sensor returned to a normal value
Sensor Returned to Normal
Value.
A temperature sensor on the backplane board, system board, CPU, or drive carrier in the specified system exceeded its warning threshold.
A temperature sensor on the backplane board, system board, or drive carrier in the specified system exceeded its failure threshold value.
A temperature sensor on the backplane board, system board, or drive carrier in the specified system detected an error from which it cannot recover.
Sensor Returned to Normal
Value
Fan Sensor reading in the host <x> exceeded a warning threshold value.
A fan sensor in the specified system detected the failure of one or more fans.
A fan sensor detected an error from which it cannot recover.
Sensor Returned to Normal
Value
Warning
Error
Error
Info
Warning
Error
Error
Info
No action
Put the system into maintenance mode
No action
No action
No Action
Put the system into maintenance mode
No action
No action
88 Virtualization-related Events For Dell PowerEdge Servers
Table 8. Virtualization-related Events of 11th, 12th, and 13th Generation PowerEdge Servers (continued)
Event Name
Dell - Voltage sensor detected a warning value
Description
A voltage sensor in the specified system exceeded its warning threshold
Dell - Voltage sensor detected a failure value
A voltage sensor in the specified system exceeded its failure threshold.
Dell - Voltage sensor detected a nonrecoverable value
A voltage sensor in the specified system detected an error from which it cannot recover.
Severity
Warning
Error
Error
Recommended action
No action
Put the system into maintenance mode
No action
Info No action Dell - Current sensor returned to a normal value
Dell - Storage: storage management error
Sensor Returned to Normal
Value.
Storage management has detected a device independent error condition.
Dell - Storage: Controller warning
Dell - Storage: Controller failure
Controller warning. Refer to the Tasks & Events tab on the vSphere client for details.
Controller failure. Refer to the
Tasks & Events tab on the vSphere client for details.
Dell - Storage: Channel Failure Channel failure.
Error
Warning
Error
Error
Put the system into maintenance mode
No action
Put the system into maintenance mode
Put the system into maintenance mode
No action Dell - Storage: Enclosure hardware information
Dell - Storage: Enclosure hardware warning
Dell - Storage: Enclosure hardware failure
Dell - Storage: Array disk failure
Dell - Storage: EMM failure
Dell - Storage: power supply failure
Dell - Storage: temperature probe warning
Enclosure hardware information.
Info
Enclosure hardware warning.
Warning
Enclosure hardware error.
Array disk failure.
EMM failure.
Power supply failure.
Error
Error
Error
Error
No action
Put the system into maintenance mode
Put the system into maintenance mode
Put the system into maintenance mode
Put the system into maintenance mode
No action
Dell - Storage: temperature probe failure
Dell - Storage: Fan failure
Physical disk temperature probe warning, too cold or too hot
Physical disk temperature probe error, too cold or too hot.
Fan failure.
Warning
Error
Error
Put the system into maintenance mode
Battery warning.
Warning
Put the system into maintenance mode
No action Dell - Storage: Battery warning
Dell - Storage: Virtual disk degraded warning
Dell - Storage: Virtual disk degraded failure
Virtual disk degraded warning. Warning
Virtual disk degraded failure Error
No action
Put the system into maintenance mode
Virtualization-related Events For Dell PowerEdge Servers 89
Table 8. Virtualization-related Events of 11th, 12th, and 13th Generation PowerEdge Servers (continued)
Event Name
Dell - Storage: Temperature probe information
Description
Temperature probe information
Severity
Info
Recommended action
No action
Array disk warning.
Warning No action Dell - Storage: Array disk warning
Dell - Storage: Array disk information
Dell - Storage: Power supply warning
Dell - Chassis Intrusion -
Array disk information.
Power supply warning.
Chassis Intrusion - Physical
Info
Warning
Error
No action
No action
No Action
Dell - Chassis
Intrusion( Physical Security
Violation) Event Cleared
Dell - CPU Presence
(Processor Presence detected)
Chassis Intrusion ( Physical
Security Violation) Event
Cleared
CPU Presence (Processor
Presence detected)
Info
Info
Dell - System Event Log
(SEL) Full (Logging Disabled)
System Event Log (SEL) Full
(Logging Disabled)
Dell - System Event Log
(SEL) Cleared
Dell - SD Card redundancy
Has Returned to Normal
Dell - SD Card Redundancy has been Lost
Dell - SD Card Redundancy
Degraded
Dell - Module SD Card
Present (SD Card Presence
Detected)
Dell - Module SD Card Failed
(Error)
Dell - Module SD Card Write
Protect(Warning)
Dell - Module SD Card not
Present
System Event Log (SEL)
Cleared
SD Card redundancy Has
Returned to Normal
SD Card Redundancy has been Lost
SD Card Redundancy
Degraded
Module SD Card Present (SD
Card Presence Detected)
Module SD Card Failed (Error) Error
Module SD Card Write
Protect (Warning)
Error
Info
Info
Error
Warning
Info
Warning
Module SD Card not Present Info
Error Dell - Watchdog Timer
Expired
Dell - Watchdog Reset
Watchdog Timer Expired
Watchdog Reset
Dell - Watchdog Power Down Watchdog Power Down
Dell - Watchdog Power cycle Watchdog Power cycle
Dell - System Power Exceeds
PSU Wattage
Dell - System Power Exceeds
Error Cleared
System Power Exceeds PSU
Wattage
System Power Exceeds Error
Cleared
Dell - Power Supply Inserted Power Supply Inserted
Error
Error
Error
Error
Info
Info
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
90 Virtualization-related Events For Dell PowerEdge Servers
Table 8. Virtualization-related Events of 11th, 12th, and 13th Generation PowerEdge Servers (continued)
Event Name
Dell - Internal Dual SD Module is present
Description
Internal Dual SD Module is present
Severity
Info
Recommended action
No Action
Info No Action Dell - Internal Dual SD Module is online
Dell - Internal Dual SD Module is operating normally
Dell - Internal Dual SD Module is write protected
Dell - Internal Dual SD Module is writable
Dell - Integrated Dual SD
Module is absent
Dell - Integrated Dual SD
Module redundancy is lost
Dell - Internal Dual SD Module is redundant
Dell - Internal Dual SD Module is not redundant
Dell - Integrated Dual SD
Module failure
Dell - Internal Dual SD Module is offline
Dell - Integrated Dual
SD Module redundancy is degraded
Dell - SD card device has detected a warning
Dell - SD card device has detected a failure
Dell - Integrated Dual SD
Module warning
Dell - Integrated Dual SD
Module information
Dell - Integrated Dual
SD Module redundancy information
Dell - Network failure or critical event
Dell - Network warning
Dell - Network information
Dell - Physical disk failure
Dell - Physical disk warning
Dell - Physical disk information
Dell - An error was detected for a PCI device
Internal Dual SD Module is online
Internal Dual SD Module is operating normally
Internal Dual SD Module is write protected
Internal Dual SD Module is writable
Integrated Dual SD Module is absent
Integrated Dual SD Module redundancy is lost
Internal Dual SD Module is redundant
Internal Dual SD Module is not redundant
Integrated Dual SD Module failure
Internal Dual SD Module is offline
Integrated Dual SD Module redundancy is degraded
SD card device has detected a warning
SD card device has detected a failure
Integrated Dual SD Module warning
Integrated Dual SD Module information
Integrated Dual SD Module redundancy information
Network failure or critical event
Network warning
Network information
Physical disk failure
Physical disk warning
Physical disk information
An error was detected for a
PCI device
Info
Warning
Info
Error
Error
Info
Info
Error
Warning
Warning
Warning
Error
Warning
Info
Info
Error
Warning
Info
Error
Warning
Info
Error
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
Virtualization-related Events For Dell PowerEdge Servers 91
Table 8. Virtualization-related Events of 11th, 12th, and 13th Generation PowerEdge Servers (continued)
Event Name
Dell - A warning event was detected for a PCI device
Description
A warning event was detected for a PCI device
Severity
Warning
Recommended action
No Action
No Action Dell - An informational event was detected for a PCI device
An informational event was detected for a PCI device
Virtual Disk Partition failure.
Dell - Virtual Disk Partition failure.
Dell - Virtual Disk Partition warning.
Virtual Disk Partition warning.
Info
Error
Warning
Dell - Cable failure or critical event
Dell - Chassis Management
Controller detected an error.
Cable failure or critical event Error
Error
Dell - IO Virtualization failure or critical event.
Dell - Link status failure or critical event.
Dell - System: Software configuration failure.
Dell - Storage Security failure or critical event.
Dell - Chassis Management
Controller audit failure or critical event.
Dell - Power Supply audit failure or critical event.
Chassis Management
Controller detected an error.
IO Virtualization failure or critical event.
Link status failure or critical event.
System: Software configuration failure.
Storage Security failure or critical event.
Chassis Management
Controller audit failure or critical event.
Power Supply audit failure or critical event.
Error
Error
Error
Error
Error
Error
Dell - Power usage audit failure or critical event.
Dell - Configuration: Software configuration failure.
Power usage audit failure or critical event.
Configuration: Software configuration failure.
Error
Error
Dell - Chassis Management
Controller detected a warning.
Chassis Management
Controller detected a warning.
Warning
Dell - Link status warning.
Dell - Security warning.
Dell - System: Software configuration warning.
Link status warning.
Security warning.
System: Software configuration warning.
Storage Security warning.
Warning
Warning
Warning
Warning Dell - Storage Security warning.
Dell - Software change update warning
Dell - Chassis Management
Controller audit warning.
Dell - PCI device audit warning.
Dell - Power Supply audit warning.
Software change update warning
Chassis Management
Controller audit warning.
PCI device audit warning.
Power Supply audit warning.
Warning
Warning
Warning
Warning
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
Put the system into maintenance mode
No Action
92 Virtualization-related Events For Dell PowerEdge Servers
Table 8. Virtualization-related Events of 11th, 12th, and 13th Generation PowerEdge Servers (continued)
Event Name
Dell - Power usage audit warning.
Description
Power usage audit warning.
Severity
Warning
Recommended action
No Action
Warning No Action Dell - Security configuration warning.
Dell - Configuration: Software configuration warning.
Security configuration warning.
Configuration: Software configuration warning.
Warning No Action
Virtualization-related Events For Dell PowerEdge Servers 93
94
Topics:
•
Disabling Administrative Accounts on iDRAC Servers
Disabling Administrative Accounts on iDRAC Servers
NOTE: Refer to the iDRAC documentation for information about disabling administrative accounts in iDRAC Servers.
A
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Key Features
- Manage and monitor physical and virtual infrastructure from a single console
- Automate hardware inventory and firmware updates
- Monitor events and alerts for proactive issue resolution
- Enhance security with role-based access control
- Simplify deployment and configuration with intuitive wizards
- Gain visibility into power consumption and thermal status
Related manuals
Frequently Answers and Questions
What are the benefits of using Dell OpenManage Integration for VMware vCenter?
What types of devices can be managed with this product?
How does this product improve security?
advertisement