OpenManage Integration for VMware vCenter for Desktop Client User's Guide Version 2.
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. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2013 Dell Inc.
Contents 1 Overview.......................................................................................................................................9 OpenManage Integration for VMware vCenter .......................................................................................................9 Key Features.............................................................................................................................................................
Running The Fix Non-Compliant vSphere Hosts Wizard..................................................................................34 Running The Fix Non-Compliant Bare Metal Server Wizard............................................................................35 iDRAC License Compliance..............................................................................................................................36 Upgrading OpenManage Integration for VMware vCenter........................................
Creating A New Hardware Profile................................................................................................................... 64 Cloning A Hardware Profile..............................................................................................................................66 About Managing Hardware Profiles.......................................................................................................................67 Viewing Or Editing A Hardware Profile................
Setting up Global Alerts.......................................................................................................................................... 84 Managing Backup And Restore..............................................................................................................................84 Configuring Backup And Restore.....................................................................................................................84 Scheduling Automatic Backups............
How Do I Test Event Settings by Using OMSA to Simulate a Temperature Hardware Fault?......................... 97 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?................................................................................................................. 97 Can the OpenManage Integration for VMware vCenter Support ESX/ESXI with Lockdown Mode Enabled?.......................................................
1 Overview OpenManage Integration for VMware vCenter VMware vCenter is the primary console used by IT administrators to manage and monitor VMware vSphere ESX/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.
• Integrates with standard vCenter authentication, rules, and permissions.
OpenManage Integration for VMware vCenter Configuration 2 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. Security Roles and Permissions The OpenManage Integration for VMware vCenter stores user credentials in an encrypted format.
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 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.
Figure 3. Dell Infrastructure Deployment Role The privileges this role provides are Create Template, Configure HW Configuration Profile, Configure Hypervisor Deployment Profile, Configure Connection Profile, Assign Identity, and Deploy. Dell.
• • • • • Dell.Configuration.
• – 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.
Understanding How To Configure or Edit the OpenManage Integration for VMware vCenter 3 After you complete the basic installation of the OpenManage Integration for VMware vCenter, you can proceed to configure the appliance using one of two methods. Although using the Configuration Wizard is the most common method used, you can also accomplish this through the appliance's Settings page in the Dell Management Center.
• 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.
5. 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.
7. 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.
To configure events and alarms: 1. In the Configuration Wizard, 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. • 2. Post only Virtualization-Related Critical and Warning Events - Post only virtualization-related critical and warning events; this is the default event posting level.
To schedule an inventory job: 1. In the Configuration Wizard, in the Inventory Schedule window, do one of the following: • 2. To run inventory schedules, click On Selected Days. • To not run inventory schedules, select Do not run inventory on Dell hosts. 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.
3. To save the specified credentials and continue with the Configuration Wizard, click Save and Continue. 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.
• Make sure that the OpenManage Integration for VMware vCenter 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 and the port number. For example, https:\ \:1311. 2. To save this URL and finish the Configuration Wizard, click Finish.
General Settings Overview General settings are used to: • Define the OpenManage Server Administrator (OMSA) URL. • Enable or Disable Warranty Expiration Notification. The OMSA software can be used to: • Manage vCenter elements (detailed sensor, component-level health information). • Clear command logs and system event logs (SELs). • Obtain NIC statistics. • Make sure that the OpenManage Integration for VMware vCenter captures events from a selected host.
3. 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 license status, in the Critical drop-down list set the number of days for warning of critical server warranty status. 4. To apply the changes, click Apply. Creating A New Connection Profile A connection profile stores the credentials that the virtual appliance uses to communicate with Dell servers.
5. 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.
7. 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.
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. • 3.
5. 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. 6. Under Proxy, select the Use Proxy check box. 7. To save these options, click, Save. Using The HTTP Proxy For Retrieving Web Based Data To use the HTTP proxy for retrieving Web based data: 1.
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. To not run Warranty Schedules, select Do not run inventory on Dell hosts. 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.
Setting Up The Firmware Repository To set up the firmware repository and credentials: 1. In the Dell Management Center, 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.
To enable a server white list: 1. In the Dell Management Center, in the left pane, select Settings. 2. In the right-pane, select Security. 3. In the Security window, click Edit. 4. To use the white list to restrict server deployment, select the Enforce Server White List check box. 5. Click Apply, and the server white setting changes to ENABLED. Adding Deployable Servers To A White List For information about security settings for deployable servers, see Server Security Settings For Deployment.
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.
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.
Downloading An ISO For Manual Firmware Updates The OpenManage Integration for VMware vCenter automatically fixes most compliance issues. Sometimes, a manual ISO installation is required. .You can download the required ISO to manually fix compliance using the following steps: 1. In the Dell Management Center → Compliance → Bare Metal Servers page, to download an ISO, click Download ISO. 2. In the Download ISO dialog box, to find the location of the ISO, click Download.
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.
End-To-End Hardware Management 4 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.
Post all Events Post all events, including informal events, that the OpenManage Integration for VMware vCenter receives from managed Dell hosts into related vCenters. Post only Critical and Warning Events Posts only events with either Critical or Warning criticality into related vCenters. Post only Virtualization-Related Critical and Warning Events Post Virtualization related events received from hosts into related vCenters.
• Setting Up An OMSA Trap Destination Deploying the OMSA Agent onto an ESX System Install the OMSA tar.gz on an ESX 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 Integration for VMware vCenter. Details on manually installing the agents are at http:// en.
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.
– 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, About Inventory Jobs.
The Dell Online Services provide access to renew a host system's warranty. • Click Renew Warranty to launch a portal used to renew a host system's warranty. Review the Warranty Days Left status under Server Information to check if the warranty requires renewal; a warning or critical icon is displayed if the warranty is getting close to the expiration date. See, Renewing Host Warranty.
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.
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.
5. 6. 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.
• Uploading OpenManage Integration for VMware vCenter License To The Administration Console Standard Licensing Scenarios Scenario 1 If you purchase 10 host licenses which is purchased on March, 10th, 2012, then after a period of 3 years that is on March 10th, 2015, the host licenses will get expired and you can only partially use certain features in the product. The firmware update and deployment task will not be available for you. After license is expired you cannot add or edit the connection profile.
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 And Status You must complete an inventory job prior to displaying the entire datacenter hardware configuration and status.
• Viewing And Editing An Existing Connection Profile • Deleting A Connection Profile • Testing A Connection Profile • Refreshing A Connection Profile Editing a Connection Profile After you have configured a connection profile, you can edit the profile name, description, associated hosts, and credentials. NOTE: The vCenters that display during this procedure have authenticated using the same Single Sign On (SSO).
4. In the Name and Credentials tab, do the following: a. Under Profile, type the Profile Name and optional Description. b. Under vCenter, view the associated hosts for this connection profile. See the note above about why you see the hosts displayed here. c. Under iDRAC Credentials, do the following: • The user name is root and this entry cannot be modified if you do not select the Active Directory. If the Active directory is set, you can choose any Active directory user not just root. • Domain\Username
8. The Associated Host tab lets you test the iDRAC and Host Credentials on the selected servers. Do one of the following: • To begin the test, select the hosts to check and then click the Test Connection icon. The other options are inactive. When the test is done click Finish. • To stop the tests click Abort All Tests. In the Abort Tests dialog box, click OK, and then click Finish. Deleting A Connection Profile 1.
Security 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. 2. To update the log with the most recent data, click Refresh. 3.
6. To limit (filter) the number of event log entries, choose one of the following: • 7. 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. 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. 8. • To cancel, click Cancel.
• Updating Older Firmware Versions • Running the Update Firmware Wizard for Clusters and Datacenters Running The Firmware Update Wizard This functionality is only available for 11th and 12th generation Dell servers that have either an iDRAC Express or Enterprise card. When your firmware was installed on or after October 14th, 2010, you can automatically update your firmware versions using the Firmware Update Wizard.
Updating Older Firmware Versions Firmware must be at a minimum level for the Firmware Update Wizard to run. When it is not, you are offered options to help update your firmware, prior to running the Firmware Update Wizard. Typically, firmware installed earlier than July 29, 2009 requires you to download and run an ISO file, see Firmware Updates. For firmware installed between July 29, 2009 and prior to Oct.
3. Click Update Firmware. If this link is not enabled or if you get an popup message when you click this option, then there is a firmware update job in progress or scheduled, close the dialog box, wait and try this again later. View the status of all jobs on the Firmware Update Jobs tab in Job Queues. 4. In the Welcome page, review the information about the update before proceeding with the wizard. 5. Click Next. 6.
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. 4. To see more details about a particular job, in the datagrid for a particular job, click Details.
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.
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.
Hardware Management 5 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 OpenManage Integration 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.
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. Create a Hypervisor Profile Contains the hypervisor installation information needed for ESX/ESXi deployment. See Creating A New Hypervisor Profile. Create a Deployment Template Optionally contains a hardware profile, a hypervisor profile, or both. You can save and reuse these profiles as needed for all available datacenter servers.
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.
NOTE: There are two RAID configuration options configured in the Hardware Profile: 1. 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. 2.
12. To display the boot order options, expand Boot Order, and then click Edit to make updates: 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.
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.
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. 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.
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 An Updated Hardware Profile To refresh an updated hardware profile: 1.
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.
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.
Renaming Hypervisor Profile 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.
• Building Deployment Templates • Duplicating Deployment Templates • Renaming Deployment Templates • Deleting A Deployment Template 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.
• 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.
list is disabled until the Internal Dual SD Module option button is selected. Toggling the option buttons should enable/ disable the drop-down list. 1. In the Global Settings page, to install the hypervisor, select one of the following deployment targets: • Hard Disk If you are deploying to a hard disk, click this option.
10. Click Next. To continue with the task to Step 5, click Deployment Wizard Step 5. 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.
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.
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.
Console Administration 6 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).
4. Under Admin User Account, do the following: a. In the Admin User Name text box, enter the administrator's user name. b. In the Password text box, enter the password. c. In the Verify Password text box, enter the password again. 5. Click Register. Modifying The vCenter Administrator Login 1. Launch a web Browser then enter https:// 2. In the left pane, click VCENTER REGISTRATION. The registered vCenters are displayed in the right pane.
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.
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://. 2.
Generating a Certificate Signing Request 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, 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 Generate Certificate Signing Request for HTTPS Certificates.
Setting up Global Alerts Alert management lets you enter global settings for how alerts are stored for all vCenter instances. 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 ALERT MANAGEMENT. To enter new vCenter alert settings, click Edit. 4. Enter numeric values for the following items: 5.
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. Launch a web Browser then enter https://. 2. In the left pane, click BACKUP AND RESTORE. 3. To edit the backup and restore settings, click Edit Automatic Scheduled Backup (this makes fields active). 4. To enable the backups, click Enabled. 5.
Understanding the vSphere Client Console The Console is found within the vSphere Web Client on a virtual machine. The Console works hand and hand with the Administration Console. The Console provides the ability to: • Configure network settings • Change the virtual appliance password • Set the local timezone • Reboot the virtual appliance • Reset the virtual appliance to factory settings • Refresh Console Use the arrow keys to navigate up or down.
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 . 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.
Migration Path to migrate from 1.6/1.7 to 2.1 OpenManage Integration for VMware vCenter version 2.1 is an OVF release only. There is no RPM update path from the older versions to this version. You can migrate from older version (1.6 or 1.7) to the version 2.1 release using the Backup and Restore path. Also, the migration path is only supported from version 1.6 and 1.7. If you are at a lower version than 1.
NOTE: Unregistering the plug-in has removed all the customizing that was done on the registered alarms by the plug-in. The following steps will not be able to restore the customizing, however, it will re-register the alarms in the default state. 1. Perform the steps 3-5 in the section Migration Path to migrate from 1.6/1.7 to 2.1 in this chapter. 2. Register the plug-in to the same vCenters that you had registered earlier in the older plug-in. 3.
Troubleshooting 7 Use this section to find answers to troubleshooting questions. This section includes: • Frequently asked questions (FAQ) • Bare metal deployment issues • Contacting Dell • Related product information Frequently Asked Questions (FAQ) This section contains some common questions and solutions. Using OpenManage Integration for VMware vCenter to update an Intel Network card with the firmware version of 13.5.2 is not supported.
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.
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 are the Required Port Settings for the OpenManage Integration for VMware vCenter? NOTE: When deploying the OMSA agent using the Fix non-complient vSphere hosts link available from the Compliance window in the Dell Management Center, the OpenManage Integration for VMware vCenter starts the httpClient service and enables port 8080 on 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.
Port Number Protocols Port Type Max.
Table 5. Expected translations.
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.
1. In vSphere Client, select Hosts and Clusters, then in the left pane, select the host and then click the Configuration tab. 2. In the left pane, under Software click Security Profile. 3. Scroll down to Lockdown Mode, and then click Edit. 4. In the Lockdown Mode dialog box, to disable Lockdown Mode, clear the Enable check box, and then click OK. 5. Log in to the host console and select Restart Management Agents, press , and to confirm, press . 6.
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. Why Do I See Auto-discovered Systems Without Model Information in the Deployment Wizard This usually indicates that the firmware version installed on the system does not meet recommended minimum requirements.
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.
• 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.
Virtualization—Related Events for Dell Poweredge 11th and 12th Generation Servers 8 The following table contains the virtualization-related critical and warning events, including event name, description and severity level. Table 7. Dell PowerEdge 11th and 12th Generation Server Events Event Name Description Severity Recommended Action Dell-Current sensor detected a warning value A current sensor in the specified system exceeded its warning threshold.
Dell - Power supply detected a failure A power supply has been disconnected or has failed. Dell - Power supply sensor A power supply sensor in detected a non-recoverable the specified system value detected an error from which it cannot recover. Error Put the system into maintenance mode Error No action Dell - Memory Device Status warning A memory device correction Warning rate exceeded an acceptable value.
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. Error No action Dell - Processor sensor A processor sensor in the Error detected a non-recoverable specified system has failed. value No action Dell - Device configuration error A configuration error was detected for a pluggable device in the specified system.
carrier in the specified system exceeded its warning threshold. Dell - Temperature sensor detected a failure value Error Put the system into maintenance mode Dell - Temperature sensor A temperature sensor on detected a non-recoverable the backplane board, value system board, or drive carrier in the specified system detected an error from which it cannot recover.
independent error condition. Dell - Storage: Controller warning Controller warning. Refer to Warning the Tasks & Events tab on the vSphere client for details. No action Dell - Storage: Controller failure Controller failure. Refer to the Tasks & Events tab on the vSphere client for details. Error Put the system into maintenance mode Dell - Storage: Channel Failure Channel failure.
Dell - Storage: Array disk warning Array disk warning. Warning No action Dell - Storage: Array disk information Array disk information. Info No action Dell - Storage: Power supply warning Power supply warning.
Dell - Watchdog Power cycle Watchdog Power cycle error No Action Dell - System Power Exceeds PSU Wattage System Power Exceeds PSU error Wattage No Action Dell - System Power Exceeds Error Cleared System Power Exceeds Error Cleared info No Action Dell - Power Supply Inserted Power Supply Inserted info No Action Dell - Internal Dual SD Module is present Internal Dual SD Module is present info No Action Dell - Internal Dual SD Module is online Internal Dual SD Module is online info No Act
Dell - Integrated Dual SD Module information Integrated Dual SD Module information info No Action Dell - Integrated Dual SD Module redundancy information Integrated Dual SD Module redundancy information info No Action Dell - Network failure or critical event Network failure or critical event error No Action Dell - Network warning Network warning warning No Action Dell - Network information Network information info No Action Dell - Physical disk failure Physical disk failure error No A
Understanding Auto-Discovery A Auto-Discovery is the process of adding a Dell PowerEdge 11th or 12th Generation bare-metal server into a pool of available servers for use by the OpenManage Integration for VMware vCenter. Once a server is discovered, use it for hypervisor and hardware deployment. This appendix provides sufficient information about Auto-Discovery to help you with system configuration.
For Auto-Discovery to occur, the following conditions must be met: • Power: Connect the server to the power outlet. The server does not need to be powered on. • Network connectivity: The server’s iDRAC must have network connectivity and must communicate with the provisioning server over port 4433. You can obtain the IP address using a DHCP server or manually specify it in the iDRAC Configuration Utility.
NOTE: If for some reason the Auto-Discovery did not complete successfully, there is no way to connect to the iDRAC remotely. Remote connection would require that you have enabled a non-admin account on the iDRAC. If there is no enabled account present on the iDRAC, then the only way to access the iDRAC is to login to the box locally and enabling the account on the iDRAC. 1. Enter the iDRAC IP address into a browser. 2. Log in to the iDRAC Enterprise GUI. 3.
19. Use the arrow keys to select LAN User Configuration. 20. Use the arrow Keys to select Provisioning Server. 21. Press Enter. 22. Enter the IP address of the host. 23. Press ESC. 24. Use arrow keys to select Account Access. 25. Use the space bar to toggle the option to Disable. 26. Use the arrow keys to select Auto-Discovery. 27. Use the space bar to toggle the option to Enabled. 28. From your keyboard, press ESC. 29. Press ESC again.
