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. Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview.......................................................................................................................................9 OpenManage Integration for VMware vCenter .......................................................................................................9 Key Features.............................................................................................................................................................
Running The Fix Non-Compliant vSphere Hosts Wizard..................................................................................30 Running The Fix Non-Compliant Bare Metal Server Wizard............................................................................31 iDRAC License Compliance..............................................................................................................................32 Upgrading OpenManage Integration for VMware vCenter........................................
Creating A New Hardware Profile................................................................................................................... 57 Cloning A Hardware Profile..............................................................................................................................59 About Managing Hardware Profiles.......................................................................................................................60 Viewing Or Editing A Hardware Profile................
Setting up Global Alerts.......................................................................................................................................... 76 Managing Backup And Restore..............................................................................................................................77 Configuring Backup And Restore.....................................................................................................................77 Scheduling Automatic Backups............
Why is the DNS configuration settings restored to original settings after appliance reboot if using DHCP for appliance IP and DNS settings overwritten..................................................................................... 87 How come I do not see my new iDRAC version details listed on the vCenter Hosts & Clusters page?.......... 87 How Do I Test Event Settings by Using OMSA to Simulate a Temperature Hardware Fault?.........................
Enabling or Disabling Administrative Accounts on iDRAC Servers......................................................................102 Manually Configuring a Server For Auto-Discovery (11th Generation of PowerEdge Servers)...........................102 Manually Configuring a Server for Auto–Discovery (12th Generation of PowerEdge Servers)...........................
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 that his 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 the following methods described later in this section: • Configuration Tasks Using the Configuration Wizard • Configuration Tasks Using the Settings Options Although using the Configuration Wizard is the most common method used, you can also accomplish this through the a
OpenManage Integration for VMware vCenter Home Page When you log in to the OpenManage Integration for VMware vCenter home page, the navigation buttons are in the left pane, and the right pane provides useful links and information. This design provides key links into the tasks you do most often. While all these tasks are found under the left-pane navigation, you can also find them on the home page for ease of use.
To create a new connection profile using the wizard: 1. From the Connection Profiles tab, click Create New. 2. In the Profile Name and Description panel, enter the Profile Name and an optional Description that are used to help manage custom connection profiles, and then click Next. 3. In the Associated Hosts panel, select the host(s) associated with the Connection Profile, and click Next. 4. View the information about credentials and connection protocols and click Next. 5.
• 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 enable all hardware alarms and events, select the Enable Alarms for Dell Hosts check box. NOTE: Dell hosts that have alarms enabled respond to critical events by entering maintenance mode. 3. In the dialog box that displays, click Continue to accept this change, or click Cancel.
2. • 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.
Setting The Default Firmware Update Repository [Wizard] Firmware repository settings contain the firmware catalog location used to update deployed servers. You can set up firmware repository initially here in the wizard or later from the Dell Management Center → Settings option. In addition, you can run the firmware update later from the OpenManage Integration tab. To set the default firmware update repository: 1.
Configuring NFS Shares To use NFS shares with the OpenManage Integration for VMware vCenter for backup and restore operations, firmware updates, and as a staging folder, there are certain configuration items that you must complete. CIFS shares do not require additional configuration. To configure NFS shares: 1. On the Linux or Unix OS machine hosting the NFS shares, edit /etc/exports to add: /share/path (rw) *(ro).
NOTE: OMSA software is only required on Dell servers prior to 12th generation of Dell PowerEdge servers. Warranty Expiration Notification can be used to: • Monitor the warranty expiration date. • Set a minimum number of warranty days left threshold beyond which either a warning or critical alert is generated. The alert appears as an icon on the host's OpenManage Integration tab.
NOTE: With installations on hosts that are 12th and later generation of Dell PowerEdge servers, the OMSA agent installation is not required. For installations on 11th generation of Dell PowerEdge servers, the OMSA agent is now automatically installed during the deployment process. NOTE: Refer the About OpenManage Integration for VMware vCenter Licensing for more information about licensing. NOTE: You are not allowed to create a connection profile if the number of hosts added exceeds the license limit.
• • 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.
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.
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. In the Dell Management Center, select Settings → HTTP Proxy, and then click Edit. 2. Select the Use Proxy check box. 3. Click Apply. 4. To validate settings, click Test Connection. Running Inventory Jobs To run the inventory job: 1.
4. If you selected On Selected Days, then do the following: a. Select the check box next to each day of the week that you want to run the warranty jobs. b. In the text box, enter the time in HH:MM format. The time you enter is your local time. Calculate the time difference you need to run the warranty jobs at the proper time. 5. To run the warranty jobs now, navigate to Job Queue → Warranty History and then click Run Now.
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.
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. Do one of the following: • To delete an individual server, click the Service Tag check box, and then click Delete Selected. 5.
required if OpenManage Server Administrator (OMSA) must be installed or updated. In addition, a reboot is required on any host that has never run CSIOR. If you select to automatically reboot an ESXi host, the following actions take place: • For a CSIOR status fix: If CSIOR is not enabled on the host, then CSIOR is set to ON on the host, and then the host is set into maintenance mode and rebooted. • For an OMSA status fix: a. OMSA is installed on the host. b.
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 OpenManage Integration for VMware vCenter The following is the upgrade scenario for the OpenManage Integration for VMware vCenter: • Upgrading From Trial Version To Full Product Version NOTE: Perform an appliance backup before you begin the upgrade. See Performing An Immediate Backup. Upgrading From a Trial Version To a Full Product Version To upgrade from trial version to a full product versions: 1. Go to the Dell Web site and purchase the full product version.
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 only Virtualization-Related Critical and Warning Events Post Virtualization related events received from hosts into related vCenters. Virtualization related events are those that Dell has selected to be most critical to hosts running virtual machines. When you configure your events and alarms, you can enable them.
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-administratoromsa.aspx. To deploy the OMSA agent tar.
Viewing Events To view events, do one of the following: • Navigate to the virtual machine and right-click to display the vCenter → Tasks & Events tab and click Events so that the selected level of events is displayed. • Click on the parent node (cluster or datacenter) of the host or the root folder of the vCenter. Events appear only on those nodes in the vSphere tree.
– Remote Access Card - IP address information and RAC type and Web interface URL. See, About Inventory Jobs.
Resetting iDRAC Sometimes iDRAC may become nonresponsive to requests and this results in unexpected behavior within the OpenManage Integration for VMware vCenter. The only way to recover from this state is to reset iDRAC. An iDRAC reset performs a normal reboot of the iDRAC. This reboot does not reboot the host. After you perform a reset, it takes 1 or 2 minutes for iDRAC to return to a usable state.
• Weekly at a specific time and on selected days. • At a set time interval a completed inventory is required to gather the data needed by the majority of the OpenManage Integration for VMware vCenter features. NOTE: To make sure that the inventory contains up-to-date information, the inventory job should run a minimum of once a week. The inventory job consumes minimal resources and does not degrade host performance. To modify the inventory job schedule: 1.
* Disabled: This value indicates that it supports valid systems with any operating system version and here memory operational mode in BIOS is not set to FRM. * Blank: If memory operational mode in BIOS is not supported the FRM attribute is not displayed. • 4. 5. 6. Recent System Log Entries provide the 10 most recent system event log entries. To launch the System Event Log window that displays additional log details, click Details.
• The server does not have the correct iDRAC license required for 12th and later generation servers and you must purchase the correct iDRAC license. The Buy Now link is for purchasing the product for the first time and not for upgrades. The Buy Now link only appears if you are using a evaluation license.
Displaying The Entire Datacenter Hardware Configuration And Status You must complete an inventory job prior to displaying the entire datacenter hardware configuration and status.
• Refreshing A Connection Profile Viewing Or Editing An Existing Connection Profile After you have configured a connection profile, you can edit the profile name, description, associated hosts, and iDRAC and OMSA Agent credentials. To view or edit an existing connection profile: 1. From the OpenManage Integration for VMware vCenter, select Connection Profiles. 2. Under Available Profiles, select the profile to view or edit and then click Edit/View. 3.
• • 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.
Refreshing A Connection Profile To refresh a connection profile: Click Refresh. NOTE: If a host is removed from vCenter, then it is removed from the connection profile. Understanding System Event Logs In vSphere Client Host View The System Event Log provides status information for hardware discovered by the OpenManage Integration for VMware vCenter.
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.
NOTE: Once the repository is created, save it to a location that the registered hosts can access. Repository passwords cannot exceed 31 characters. Do not use any of the following characters in a password: @, &, %, ', ", , (comma), < > The Firmware Update Wizard always checks for the minimum firmware levels for iDRAC, BIOS, and Lifecycle Controller, and attempts to update them to required minimum versions.
3. Select the bundle for your host and click Next. 4. Select the desired firmware updates and click Next. Components that are either a downgrade, already up-to-date, or currently scheduled for update are not selectable. If you select the Allow Components to be Downgraded check box, select the options that are listed as Downgrade. Selecting this option is only recommended to advanced users who understand the implications of downgrading firmware. 5. Select the desired restart option.
firmware versions using the Firmware Update Wizard. This wizard only updates hosts that are part of a connection profile and compliant in terms of firmware, CSIOR status, hypervisor, and OMSA status (11th generation servers only). If your host is not listed, run the Compliance Wizard for vSphere Hosts from the OpenManage Integration for VMware vCenter or select the host that is not listed from the Hosts and Clusters view and use the Firmware Update Wizard.
2. In the Time text box, type the time in HH:MM, and then click Finish. NOTE: The time is the local timezone where your client is physically located. Invalid time values result in a blocked update. Viewing Firmware Update Status for Clusters and Datacenters For information to display on this page, run a firmware update for a cluster or a datacenter. This page only displays information about firmware updates for clusters and datacenters.
Setting Up Physical Server Front Indicator Light To assist in locating a physical server in a large datacenter environment, you can set the front indicator light to blink for a set time period. To set up a physical server's front indicator light: 1. In vSphere Client, under the Inventory heading, select Hosts and Clusters. 2. From Hosts and Clusters, select the host system in the tree view and select the OpenManage Integration tab. 3. Under Host Actions, select Blink Indicator Light. 4.
To view the server warranty information for an entire datacenter: 1. From the vSphere Client, under the Inventory heading select Hosts and Clusters. 2. From Hosts and Clusters, select the datacenter in the tree view and select the OpenManage Integration tab. 3. An overview of all hosts in the datacenter is displayed. In the View drop-down list select Warranty. 4. In the Filter text box, enter a filter for the warranty data. 5. To refresh the displayed inventory, click Refresh. 6.
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.
NOTE: Operating system deployment from OpenManage Integration for VMware and vCenter ( OMIVV ) fails if the BOOT mode in the target machine is set to UEFI 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.
Unconfigured The server has contacted the OpenManage Integration for VMware vCenter and is waiting to be configured. See Understanding Deployment Job Times. 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.
NOTE: For systems that have iDRAC Express, the iDRAC configuration cannot be extracted; therefore, the server should not be used as a reference server. If it is used as a target system, then no iDRAC configuration from the reference server is applied. RAID Configuration The RAID configuration displays the current RAID topology on the reference server at the time the hardware profile was extracted. NOTE: There are two RAID configuration options configured in the Hardware Profile: 1.
12. To display the boot order options, expand Boot Order, and then click Edit to make updates: NOTE: For Dell 13th generation PowerEdge Servers, only the current boot mode details are displayed for the hardware profiles. NOTE: Operating system deployment from OpenManage Integration for VMware and vCenter fails if the BOOT mode in the target machine is set to UEFI a. In the Boot Mode drop-down list to select either BIOS or UEFI. b.
a. Add User: Manually enter an iDRAC user and the required information. When finished, click Save to save your changes or Cancel to cancel. b. Delete User: Delete the selected user. Select the check box for the user and click Delete, or click Cancel to cancel. c. Edit User: Manually edit an iDRAC user’s information. When finished, click Save to save your changes or Cancel to cancel.
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. 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.
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.
6. To add the settings to the profile, click Save. 7. In the left pane, click vCenter Settings, and then edit where required: • vCenter Instance: Displays the server instance that manages a host after deployment. • vCenter Version: Displays the current version. • vCenter Destination Container: Datacenter or cluster that hosts the new physical servers; click Browse to search for vCenter destinations. • 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 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.
• 2. Internal Dual SD Module — Deploys the hypervisor on the Internal Dual SD Module. If any of the selected servers do not support an Internal Dual SD Module, or an Internal Dual SD Module is not present during deployment, perform one of the following actions: • Select the Deploy the hypervisor to the first hard disk for servers that do not have an available Internal Dual SD Module check box if you want to deploy the hypervisor on the first hard disk of the servers.
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.
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 Dell Management Center, under Deployment click Deployment Wizard. 2. On the Select Servers tab, click Remove Servers. 3. In the Remove Servers dialog box, select the check box of the server to remove. 4.
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).
b. In the Description text box, enter an optional description. 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. OpenManage Integration for VMware vCenter Requirements Supported vSphere versions for release 2.
v5.5 U2 Y Y With any given vCenter version, the ESX / ESXi hosts it administrates must be equal or lower in version. To administrate a vSphere v4.1 or v5.0 environment with OMIVV, you must have at least a v5.0 U3 vCenter administrating it. 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. In the left pane, click VCENTER REGISTRATION.
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 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.
5. • Maximum number of alerts • Number of days to retain alerts • Timeout for duplicate alerts (seconds) To save your settings, click Apply, or click Cancel to cancel. Managing Backup And Restore Managing backup and restore is accomplished from the Administrative Console.
7. Click Apply. Performing An Immediate Backup To perform an immediate backup: 1. Launch a web Browser then enter https://. 2. In the left pane, click BACKUP AND RESTORE. 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.
Configuring Network Settings Changes to the network settings are done in the vSphere Client on the Console tab. 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.
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.2 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.
Why is the processor version “Not Applicable” in Processor view in the System overview page? In case of PowerEdge 12th Generation Dell Servers and higher generations, the processor version is in the Brand column. In case of lower generation servers processor version is shown in the Version column.
I Have the OMSA Agent Installed on a Dell Host System, But I Still Get an Error Message That OMSA is Not Installed. What Should I Do? To resolve this issue on an 11th generation server: 1. Install OMSA with the Remote Enablement component on the host system. 2. If you are using the command line to install OMSA, make sure to specify the -c option. If OMSA is already installed, reinstall it with the -c option and restart the service: srvadmin-install.sh -c srvadmin-services.
Resolution: The task has to be cancelled manually. Version Affected: All What Setting Should I Use For UserVars.CIMoeMProviderEnable With ESXi 4.1 U1? Set UserVars.CIMoemProviderEnabled to 1. I Am Using A Reference Server to Create a Hardware Profile But it Failed. What Should I Do? Check to make sure that minimum recommended versions of iDRAC firmware, Lifecycle Controller firmware, and BIOS are installed.
3. Click Content. 4. Click ExtensionManager. 5. Click UnregisterExtension. 6. Enter the extension key com.dell.plugin.openManage_integration_for_VMware_vCenter, and then click Invoke method. 7. 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.
Does the OpenManage Integration for VMware vCenter support the VMware vCenter Server appliance? Yes, the OpenManage Integration for VMware vCenter supports the VMware vCenter Server appliance. Does the OpenManage Integration for VMware vCenter support the vSphere Web Client? Yes, the OpenManage Integration for VMware vCenter supports the VMware vSphere Web client.
how to set up a network to support auto-discovery, see the Dell Auto-Discovery Network Setup Specification at http:// attachments.wetpaintserv.us/xBUlrs4t%2B2TzbrwqYkblvQ%3D%3D2 62254 If auto-discovery was not requested at the time of purchase, it can be enabled as follows: 1. During the boot process, press . 2. In the iDRAC setup window, enable the NIC (blade servers only). 3. Enable Auto-Discovery. 4. Enable DHCP. 5. Disable admin accounts. 6. Enable Get DNS server address from DHCP.
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 5.
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 11th, 12th, or 13th generation of Dell PowerEdge 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.
