OpenManage Integration for VMware vCenter for Desktop Client User's Guide Version 3.
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. Copyright © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview......................................................................................................................... 8 OpenManage Integration for VMware vCenter ..................................................................................................................8 Key Features.......................................................................................................................................................................
Upgrading From a Trial Version To a Full Product Version........................................................................................... 29 OpenManage Integration for VMware vCenter licensing.................................................................................................. 29 4 End-To-End Hardware Management..............................................................................30 Monitoring the Datacenter And Host System.....................................................
Creating A New Hypervisor Profile................................................................................................................................... 54 Managing Hypervisor Profiles...........................................................................................................................................54 VLAN Support............................................................................................................................................................
Resetting The Virtual Appliance To Factory Settings.................................................................................................. 73 Refreshing the Console View......................................................................................................................................73 Logging out from the console..................................................................................................................................... 73 Read-only User Role...........
Why is the DNS configuration settings restored to original settings after appliance reboot if using DHCP for appliance IP and DNS settings overwritten.................................................................................................................82 How come I do not see my new iDRAC version details listed on the vCenter Hosts & Clusters page?....................... 82 How Do I Test Event Settings by Using OMSA to Simulate a Temperature Hardware Fault?......................................
1 Overview 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.
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
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. 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 that his role provides are Create Template, Configure HW Configuration Profile, Configure Hypervisor Deployment Profile, Configure Connection Profile, Assign Identity, and Deploy. Dell.
– 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 – 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 firmwa
– Launch OMSA Console – Launch iDRAC Console – Display and clear SEL log • Dell.Inventory.
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
• 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.
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.
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. 2. • To use a proxy server, under Settings enter a Proxy Server Address. 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.
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.
• 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.
• Firmware Repository: 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.
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.
• 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.
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.
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.
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.
• 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 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.
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.
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.
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.
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.
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.community.dell.com/ techcenter/systems-management/w/wiki/1760.openmanage-server-administrator-omsa.aspx. 1.
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. • 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.
– Information through a tested, secure connection See Warranty Retrieval. 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.
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.
– 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.
8. • Current power budget, profile, warning and failure thresholds. • Energy consumption, system peak power, and amperage statistics. • Reserve power and peak reserve capacity. 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.
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.
4. Use the Filter text box to enter a filter for the inventory data. 5. To refresh the displayed inventory, click Refresh.
* 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.
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.
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.
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.
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.
8. In the Select Updated Bundles page, select the update bundles using the check boxes. NOTE: • 9. 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. 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.
• 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.
• Warranty information updated at scheduled intervals • Secure transmission using a proxy server and credentials NOTE: Dell does not store transmitted service tag information.
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.
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 Running The Deployment Wizard . 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.
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.
• In the Profile Name text box, enter the profile name. 4. • In the Description text box, type an optional description. 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.
• Virtual Media 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.
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.
Refreshing Hardware Profiles 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 ESXi to a server, a hypervisor profile must be created.
• Understanding VLAN Support • Viewing Or Editing Hypervisor Profiles • Duplicating Hypervisor Profiles • Renaming Hypervisor Profiles • Deleting Hypervisor Profiles • Refreshing Hypervisor Profiles 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.
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. Duplicating Hypervisor Profiles To duplicate a hypervisor profile: 1.
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. 6. • To create a new hardware/hypervisor profile, click Create New. 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.
• 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.
2. • Hard Disk — Deploys the hypervisor on the hard disk drive. • Internal Dual SD Module — Deploys the hypervisor on the Internal Dual SD Module.
• 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 dropdown list to assign all servers to the same existing profile. 3.
• Managing Deployment Jobs Using Deployment Job Queue • Running Inventory Jobs • 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.
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).
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. 4. Assign the Dell privileges to the role created or modified in step 1. See Assigning Dell privileges to the role. Now, a non-administrator user with the required privileges can use the OMIVV features with Dell hosts.
– 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. 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 Registering a vCenter Server for more information on registering a vCenter server.
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. 5. Click Register. NOTE: For all vCenter operations, OMIVV uses the privileges of the registered user and not the privileges of the loggedin user.
ESXi version support Server generation 11G v6.0 U3 12G Y 13G Y Y Table 5. Supported vCenter Server versions for release 3.2 vCenter version Desktop client support Web client support v5.1 U2 Y N v5.1 U3 Y N v5.5 U1 Y Y v5.5 U2 Y Y v5.5 U3 Y Y v6.0 Y Y v6.0 U1 Y Y v6.0 U2 Y Y v6.0 U3 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.
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:// 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.
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, Managing Backup and Restore. 1.
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.
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.
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.
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.
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.
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.
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.
7 Troubleshooting 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.
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.
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.
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.
Table 6. Virtual appliance ports Port number Protocols Port type Max.
Port number Protocols Port type Max. Encryption Direction Level Usage Configurable 69 TFTP UDP 128–bit In/Out Trivial File Transfer No 111 NFS UDP/TCP 128–bit In SUN Remote Procedure Call (Portmap) No 68 BOOTP UDP None Out Bootstrap Protocol Client 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 .
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.
On trying a firmware update with an invalid DUP, the hardware update job status on the vCenter console neither fails nor times-out for hours, though the job status in LC says ‘FAILED’. Why is this happening? 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.
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. 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.
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.
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.
Event Name Description Severity Recommended action Dell - Power supply sensor detected a non-recoverable value A power supply sensor in the specified system detected an error from which it cannot recover. Error No action Dell - Memory Device Status warning A memory device correction rate exceeded an acceptable value. Warning No action Dell - Memory Device error A memory device correction rate exceeded an acceptable value, a memory spare bank was activated, or a multibit ECC error occurred.
Event Name Description Severity Recommended action Dell - Processor sensor detected a non-recoverable value A processor sensor in the specified system has failed. Error No action Dell - Device configuration error A configuration error was detected for a pluggable device in the specified system.
Event Name Description Severity Recommended action specified system detected an error from which it cannot recover. Dell - Fan sensor returned to a normal value Sensor Returned to Normal Value Info No action Dell - Fan sensor detected a warning value Fan Sensor reading in the host exceeded a warning threshold value. Warning No Action Dell - Fan sensor detected a failure value A fan sensor in the specified system detected the failure of one or more fans.
Event Name Description Severity Recommended action Dell - Storage: Array disk failure Array disk failure. Error Put the system into maintenance mode Dell - Storage: EMM failure EMM failure. Error Put the system into maintenance mode Dell - Storage: power supply failure Power supply failure.
Event Name Description Dell - SD Card Redundancy has been Lost SD Card Redundancy has been Error Lost No Action Dell - SD Card Redundancy Degraded SD Card Redundancy Degraded Warning No Action Dell - Module SD Card Present (SD Card Presence Detected) Module SD Card Present (SD Card Presence Detected) Info No Action Dell - Module SD Card Failed (Error) Module SD Card Failed (Error) Error No Action Dell - Module SD Card Write Protect(Warning) Module SD Card Write Protect (Warning) Warning
Event Name Description Severity Recommended action Dell - Integrated Dual SD Module failure Integrated Dual SD Module failure Error No Action Dell - Internal Dual SD Module is offline Internal Dual SD Module is offline Warning No Action Dell - Integrated Dual SD Module redundancy is degraded Integrated Dual SD Module redundancy is degraded Warning No Action Dell - SD card device has detected a warning SD card device has detected a warning Warning No Action Dell - SD card device has detec
Event Name Description Severity Recommended action Dell - Link status failure or critical event. Link status failure or critical event. Error No Action Dell - System: Software configuration failure. System: Software configuration failure. Error No Action Dell - Storage Security failure or critical event. Storage Security failure or critical event. Error No Action Dell - Chassis Management Controller audit failure or critical event.
A Disabling Administrative Accounts on iDRAC Servers NOTE: Refer to the iDRAC documentation for information about disabling administrative accounts in iDRAC Servers.
