OpenManage Integration for VMware vCenter Using the vSphere 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..................................................................................33 Running The Fix Non-Compliant Bare Metal Server Wizard............................................................................34 iDRAC License Compliance..............................................................................................................................34 Upgrading OpenManage Integration for VMware vCenter........................................
Creating A New Hardware Profile................................................................................................................... 60 Cloning A Hardware Profile..............................................................................................................................62 About Managing Hardware Profiles.......................................................................................................................63 Viewing Or Editing A Hardware Profile................
Setting up Global Alerts.......................................................................................................................................... 80 Managing Backup And Restore..............................................................................................................................80 Configuring Backup And Restore.....................................................................................................................80 Scheduling Automatic Backups............
Can the OpenManage Integration for VMware vCenter Support ESX/ESXI with Lockdown Mode Enabled?...........................................................................................................................................................93 Inventory is Failing on Hosts ESXi 4.0 Update2 and ESXi Update 3 in Lockdown Mode After a Reboot..........93 When I tried to use lockdown mode, it failed...................................................................................................
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.
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.
– To configure Host Credentials without Active Directory, do the following: * In the User Name text box, type the user name. The user name is default as root and is a read-only field. If you have selected the Use Active Directory you can enter any other user name. * In the Password text box type the password. The password is limited to 127 characters. NOTE: The OMSA credentials are the same credentials used for ESX and ESXi hosts. * In the Verify Password text box, type the password again.
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 the Configure HTTP Proxy window, 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.
To run a warranty retrieval job: 1. 2. 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. 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.
* 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.
• 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.
NOTE: OMSA is only required on Dell servers prior to Dell PowerEdge 12th generation 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. For information about setting up an OMSA trap destination, see Setting Up An OMSA Trap Destination.
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.
– To configure Host Credentials without Active Directory, do the following: * In the User Name text box, type the user name. The read only default user name is root. If you select Use Active Directory the user name can be different from root. * In the Password text box type the password. The password is limited to 127 characters. NOTE: The OMSA credentials are the same credentials used for ESX and ESXi hosts. * In the Verify Password text box, type the password again.
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.
4. To validate settings, click Test Connection. Running Inventory Jobs To run the inventory job: 1. Once the Configuration Wizard is complete, click Job Queue → Inventory → Run Now to immediately 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.
Viewing or Editing Deployment Credentials In Dell Management Center, you can edit the deployment credentials. Deployment credentials are used to securely communicate with a bare-metal system using the iDRAC from initial discovery, until the end of the deployment process. Once deployment completes, the credentials are changed to those in the connection profile matched to the bare-metal system from the deployment wizard.
4. Click Apply. Server Security Settings For Deployment 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. NOTE: Use a CSV-delimited file to import servers.
* When the We found these service tags in your file dialog displays, click Apply. The service tags are now displayed in the Service Tag list. Deleting Deployable Servers From A White List For information about security settings for deployable servers, see Server Security Settings For Deployment. To delete deployable servers from a 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.
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 About 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.
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.
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.
When you upgrade from a evaluation license to a full standard license, a new license XML file is sent to you by e-mail. Save the file to your local system and upload the new license file using the Administration Console. Licensing presents the following information: 36 • Maximum vCenter Connection Licenses - up to ten registered and in use vCenter connections are allowed. • Maximum Host Connection Licenses - the number of host connections that were purchased.
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.
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.
– 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, About Inventory Jobs.
• Click OMSA Console to launch the OpenManage Server Administrator (OMSA) user interface if it has been configured. See, Enabling The OMSA Link • Click Blade Chassis Console to launch the Chassis Management Controller (CMC) Web user interface. Dell Online Services 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.
• Running Inventory Jobs • 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.
– 4. 5. 6. 7. 8. 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 servers with ESXi 5.5 or later version.
– Start and end dates and how many days are left on the warranty. – Status of the warranty (active, inactive) 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.
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.
• 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 After you run the Configuration Wizard, you manage credential profiles from the OpenManage Integration for VMware vCenter Manage tab → Templates & Profiles using the following: • Creating A Connection Profile • Viewing And Editing An Existing Connection Profile • Deleting A Connection Profile •
* Verified password: Type your password again. * Enable Certificate Check: The default is a cleared check box. To download and store the iDRAC certificate and validate it during all future connections, select Enable Certificate Check, or clear the Enable Certificate Check check box to perform no certificate check and not store the certificate. NOTE: You need to select Enable if you are using Active-Directory.
4. To exit, click Cancel. 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: After removing the host from vCenter, when you navigate to connection profile page, you will be prompted to remove the host from connection profile. Upon confirmation, the host will be removed from Connection Profile.
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.
Local/shared repository Created with Dell Repository Manager™. These local repositories are located 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.
b) If you have NFS, skip to step 7. Otherwise 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 you have a network connection to ftp.dell.com. c) Click Next. 3. Select the bundle for your host and click Next. 4. Select the desired firmware updates and click Next.
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.
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 blocked. 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.
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.
NOTE: Dell does not store transmitted service tag information. Related Tasks: • Renewing Host Warranty • Running A Warranty Retrieval Job • Viewing Server Warranty Information For A Single Host • Viewing Warranty Information For An Entire Data Center Renewing Host Warranty You can view the warranty status for your servers, or renew the warranty on the Warranty page. 1. In vSphere Client → OpenManage Integration tab → Host Information, click Warranty. 2.
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.
Provisioning Overview Once a physical inventory of the datacenter is complete, all auto-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.
Configured 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. Dell cannot produce custom ESX 4.1 images. For deployments to work all drivers must be present natively in the ISO VMware produces. For the most up-to date list of supported ESXi versions for this release, see the Release Notes.
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: 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.
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.
18. In the left pane, select RAID Configuration. To include RAID configuration information in the profile, select the Include RAID Configuration in this Hardware Profilecheck 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.
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 A Hardware Profile • Duplicating Hardware Profiles • Renaming A Hardware Profile • Deleting A Hardware Profile • Refreshing Hardware Profiles Viewing Or Editing A Hardware Profile To view or edit a hardware profile: 1.
Refreshing An Updated Hardware Profile To refresh an updated hardware profile: 1. In the Dell Management Center, select Deployment → Deployment Templates → Hardware Profiles. 2. Click Refresh. The updated hardware profile information displays. Creating A New Hypervisor Profile To deploy and configure ESX/ESXi to a server, a hypervisor profile must be created.
– 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. To add the information to the profile, click Save. 8.
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 1: Selecting Servers • Deployment Wizard Step 2: Deployment Templates • Deployment Wizard Step 3: Global Settings • Deployment Wizard Step 4: Server Identification • Deployment Wizard Step 5: Connection Profile • Deployment Wizard Step 6: 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.
– Hard Disk If you are deploying to a hard disk, click this option. – Internal Dual SD Module If you are deploying to an Internal Dual SD Module, click this option, and then select the Deploy the hypervisor to the first hard disk for servers that do not have an available Internal Dual SD Module check box, this deploys the hypervisor to the first disk on these systems.
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.
• 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.
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 automatically discovered or manually added. 1. In the Dell Management Center Deployment click Deployment Wizard. 2. On the Select Servers tab, click Remove Servers. 3.
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).
5. 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. 6. Click Register. Modifying The vCenter Administrator Login 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.
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. You can add licenses if you need to add more hosts.
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. 1. 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:// 2.
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) b) c) d) e) f) 6. To enable the use of HTTP Proxy Settings, next to Use HTTP Proxy Settings, select Enable. In the Proxy Server Address text box, enter the proxy server address. In the Proxy Server Port text box, enter the proxy server port. To use proxy credentials, next to Use Proxy Credentials, select Yes.
NOTE: You can use either Microsoft Internet Explorer or Firefox 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.
backup. It is recommended that you schedule automatic backups to guard against data loss. After this procedure, you must configure a backup schedule. To configure backup and restore: 1. 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 Dell Management Console → Settings page. The URL uses the following format and is case insensitive: https:// 2.
3. Click Backup Now. 4. To use location and encryption password from the Backup settings, in the Backup Now dialog box, select that check box. 5. 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. 6. Click Backup. Restoring The Database From A Backup NOTE: The restore operation causes the virtual appliance to reboot after it has completed.
To configure network settings: 1. In the vSphere Client, select the OpenManage Integration for VMware vCenter, and then click the Console tab. 2. In the Console window, select Configure Network, then press . 3. 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 is changed in the vSphere Client using the Console tab.
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 . 3. The following notice is displayed: This operation is completely Irreversible if you continue you will completely reset *this* appliance to its original settings.
6. Restore the database to the new appliance. For more information, see the section, Restoring The Database From A Backup in this guide. 7. Upload the new license file. For more information, see the section, Registering OpenManage Integration for VMware vCenter And Importing The License File in OpenManage Integration Version 2.0 Quick Install Guide. 8. Verify the appliance. For more information, see the section Installation Verification in this guide to ensure the database migration is successful. 9.
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.
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. 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.
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.
The NFS Share is Set Up With the ESX/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. How Do I Force Removal of the Virtual Appliance? 1. Go to https:///mob 2. Click Content. 3. Click ExtensionManager. 4. Click UnregisterExtension. 5. Enter the extension key to unregister com.dell.plugin.
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.
admin accounts are disabled. It is not necessary to configure a static IP address for the iDRAC. It gets one from a DHCP server on the network. To make use of the auto-discovery feature, a DHCP server or a DNS server (or both) must be configured to support the discovery process. CSIOR has already been run by factory process. For more information on how to set up a network to support auto-discovery, see the Dell Auto-Discovery Network Setup Specification at http:// attachments.wetpaintserv.
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.
• 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. • Additional network settings: If using DHCP, enable the Get DNS server address from DHCP setting so that DNS name resolution can occur. • Provisioning service location: The iDRAC must know the IP address or host name of the provisioning service server.
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.
18. To Exit, on your keyboard, press ESC. 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.
15. Press ESC. 16. In the Warning Screen, to confirm Exit, click Yes.
