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 © 2015 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...........................................................................................................................................9 How Does the OpenManage Integration for VMware vCenter Help With vCenter Administration...........
About Host, Bare Metal, and iDRAC Compliance Issues................................................................... 32 Running The Fix Non-Compliant vSphere Hosts Wizard............................................................ 33 Running The Fix Non-Compliant Bare Metal Server Wizard....................................................... 34 iDRAC License Compliance..........................................................................................................
Understanding How To Configure A Hardware Profile..................................................................... 61 Creating A New Hardware Profile.................................................................................................62 Cloning A Hardware Profile.......................................................................................................... 64 About Managing Hardware Profiles...........................................................................................
Setting Up the NTP Servers.......................................................................................................... 80 Generating a Certificate Signing Request.................................................................................... 80 Setting up Global Alerts.......................................................................................................................81 Managing Backup And Restore...........................................................................
How does the OpenManage Integration for VMware vCenter support more than three vCenters in Linked Mode?............................................................................................................. 91 Does OpenManage Integration for VMware vCenter support vCenter in linked mode?........... 91 What are the Required Port Settings for the OpenManage Integration for VMware vCenter?.....................................................................................................................
Does the OpenManage Integration for VMware vCenter support the vSphere Web Client?....98 In the Administration Console, why the Update Repository Path is not set to default path after I reset the appliance to factory settings?.............................................................................98 After backup and restore of OpenManage Integration for VMware vCenter, why alarm settings are not restored? ..................................................................................................
Overview 1 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.
• Organizes deployment of multiple bare-metal servers without requiring Preboot Execution Environment (PXE). • Provides additional intelligence (inventory, events, alarms) to diagnose server problems. • 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.
Figure 1. Error Message Access Control Authentication, Authorization, And Roles The OpenManage Integration for VMware vCenter uses the vSphere Client's current user session and the stored administration credentials for the virtual appliance to perform vCenter operations. The OpenManage Integration for VMware vCenter uses the 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.
Group Name Description ConnectionProfile, Configure ClearLed, Firmware Update Privilege Group - Dell.Inventory Configure Inventory, Configure Warranty Retrieval, Configure ReadOnly Privilege Group - Dell.Monitoring Configure Monitoring, Monitor Privilege Group - Dell.Reporting (Not used) Create a Report, Run a Report Dell Infrastructure Deployment Role This role contains the privileges specifically related to the hypervisor deployment features.
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.
– Create, display, delete, and edit deployment templates • Dell.Configuration.Perform Host-Related Tasks – Blink LED, Clear LED, Configure OMSA URL from the Dell Server Management tab – Launch OMSA Console – Launch iDRAC Console – Display and clear SEL log • Dell.Inventory.
Steps 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 The user interface in both methods is similar except in the wizard you click Save and Continue, whereas in the Settings option
OpenManage Integration for VMware vCenter Home Page When you log into the OpenManage Integration for VMware vCenter home page, the navigation buttons are in the left pane, and the right pane provides useful links and information. This design provides key links into the tasks you do most often. While all these tasks are found under the left-pane navigation, you can also find them on the Overview page for ease of use.
active directory credential can be same for both iDRAC and host or it can be set as separate active directory credential. The user credential must have administrative privilege. NOTE: With installations on hosts that are using 12th or later generation of the Dell PowerEdge servers, the OMSA agent installation is not required. For installations on 11th generation servers, OMSA agent is automatically installed during the deployment process.
NOTE: OMIVV supports SNMP v1 and v2 alerts for 12th generation hosts and later. For hosts prior to 12th generation, OMIVV supports SNMP v1 alerts. To configure events and alarms: 1. 2. In the Configuration Wizard, under Event Posting Levels, select one of the following: • Do not post any events - Blocks hardware events. • Post All Events - Posts all hardware events. • Post only Critical and Warning Events - Posts only critical or warning level hardware events.
NOTE: To make sure that the OMIVV continues to display updated information, it is recommended that you schedule a periodic inventory job. The inventory job consumes minimal resources and will not degrade host performance. To schedule an inventory job: 1. In the Configuration Wizard, in the Inventory Schedule window, do one of the following: • 2. To run inventory schedules, click On Selected Days. • To not run inventory schedules, select Do not run inventory on Dell hosts.
To configure the deployment credentials: 1. In the Deployment Credential window you can view or change the credentials. 2. To change these credentials, under Credentials for Bare Metal Server Deployment, do the following: a. In the User name text box, edit the user name. b. In the Password text box, edit the password. c. In the Verify Password, text box, confirm the password. 3. To save the specified credentials and continue with the Configuration Wizard, click Save and Continue.
NOTE: OMSA is only required on Dell servers prior to 12th Generation. You can use OMSA to: • Manage vCenter elements (detailed sensor/component-level health information). • Clear command logs and system event logs (SELs). • Obtain NIC statistics. • Make sure that the 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.
• Enable or Disable Warranty Expiration Notification. • General: Set the OMSA URL that displays on the Dell Hosts tab in vCenter. You can also enable or disable Warranty Expiration Notification. • Events And Alarms: Enables or disables all hardware alarms (current alert status is displayed on the Alarms tab). Also configures incoming event and alert filtering. • HTTP Proxy: Enable or disable HTTP proxy usage during communication with Internet sites.
NOTE: For information about setting up an OMSA trap destination, see Setting Up An OMSA Trap Destination. Enable or Disable Server Warranty Expiration Notification When you control the warranty settings, the server warranty information is retrieved from Dell online. Use this page to enable or disable server warranty expiration notifications for hosts and clusters. Set or edit this feature in the Dell Management Center on the Settings, General Page.
is limited to 256 characters. Refer to Microsoft Active Directory documentation for user name restrictions. – In the Active Directory Password text box, type the password. The password is limited to 127 characters. – In the Verify Password text box, type the password again. – In the Certificate Check drop-down list, select one of the following: • * To download and store the iDRAC certificate and validate it during all future connections, select Enabled .
– In the Verify Password text box, type the password again. – In the Certificate Check drop-down list, select one of the following: 9. * To download and store the Host certificate and validate it during all future connections, select Enabled . * To perform no check and not store the Host certificate, select Disabled. Click Next. 10. The Test Selected link is used to validate the provided iDRAC and Host Credentials for the selected servers.
About Proxy Configuration The proxy settings define the HTTP proxy and any required credentials used to retrieve information from the Web (including from Dell online), such as: • Enable or disable the proxy server • Enter the proxy server and port number needed • Define any required credentials - user name and password Related Tasks: • Setting Up A Proxy Server • Using The HTTP Proxy For Retrieving Web Based Data • Setting Up The HTTP Proxy Using The Administration Console Setting Up A Proxy Ser
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.
Viewing or Editing Deployment Credentials In Dell Management Center, you can edit the deployment credentials. Deployment credentials are used to securely communicate with an auto-discovered Dell bare-metal server, until the OS deployment is completed. Once deployment completes, after a successful OS deployment, the iDRAC credentials that are provided in the associated connection profile will be set..
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. This contains multiple records on different lines where each record has one or more service tags separated by commas.
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.
3. 4. If your license is out of date, click Purchase/Renew iDRAC License. Log into the Dell License Management page and update or purchase a new iDRAC license. Use the information on this page to identify and update your iDRAC. 5. After you install an iDRAC license, run an inventory job for vSphere hosts and return to this page after the inventory job completes. For bare metal servers, recheck licensed bare metal server compliance.
system and upload the new license file using the Administration Console. Licensing presents the following information: • 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. • In Use - the number of vCenter connection or host connection licenses in use.
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.
Understanding OMSA For 11th Generation Dell PowerEdge Hosts On PowerEdge servers earlier than 12th generation, it is mandatory to install OMSA to work with the OpenManage Integration for VMware vCenter. OMSA is installed automatically on 11th generation Dell PowerEdge hosts during deployment, or if you want to install it manually, you may still do so.
9. Repeat step 1 to step 8 to configure additional events. Viewing Events To view events, do one of the following: • Navigate to the virtual machine and right-click to display the vCenter → Tasks & Events tab and click Events so that the selected level of events is displayed. • Click on the parent node (cluster or datacenter) of the host or the root folder of the vCenter. Events appear only on those nodes in the vSphere tree.
– Memory - Number of slots available and in use, maximum capacity and amount of memory in use, and details on individual DIMMs. – Network Interface Cards (NICs) - Number of installed cards and details on individual NICs. – PCI Slots - Total available and number in use and details on individual slots. – Power Supplies - Number present and details on individual PSUs. – Processors - Number present and details on individual CPUs. – Remote Access Card - IP address information and RAC type and Web interface URL.
The management consoles are used to launch external system management consoles, such as: • Click Remote Access Console to launch the Integrated Dell Remote Access Controller (iDRAC) Web user interface. • Click OMSA Console to launch the OpenManage Server Administrator (OMSA) user interface if it has been configured. See, Enabling The OMSA Link • Click Blade Chassis Console to launch the Chassis Management Controller (CMC) Web user interface.
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.
– Unknown (question mark) - status is unknown for the component A global health status is displayed in the upper-right header bar.
• 7. 8. Individual update details - Version, installation time, if an update is in progress or the update status, and the update version. The update status and version only have data when an update is scheduled, and the update version is the firmware version to which the system will be updated. Under Host Information, click Power Monitoring to display general power information, energy statistics, and reserve power information, including: • Current power budget, profile, warning and failure thresholds.
• List of how many of each storage component is present in the system • Component data table that contains detailed information on that component To view storage data: 1. In vSphere Client, select a host and then select the OpenManage Integration Tab. 2. In the left pane, under Host Information, click Storage. 3. In the Storage page, view the graphical summary or use the table and View and Filter drop-down lists to sort your inventory information.
3. An overview of all hosts in the datacenter is displayed. Use the View drop-down list to view an inventory category. 4. Use the Filter text box to enter a filter for the inventory data. 5. To refresh the displayed inventory, click Refresh.
is limited to 256 characters. Refer to Microsoft Active Directory documentation for user name restrictions. – In the Active Directory Password text box, type the password. The password is limited to 127 characters. – In the Verify Password text box, type the password again. – In the Certificate Check drop-down list, select one of the following: • * To download and store the iDRAC certificate and validate it during all future connections, select Enable .
– In the Password text box type the password. The password is limited to 127 characters. NOTE: For servers that do not have either an iDRAC Express or Enterprise card, the iDRAC test connection result states Not Applicable for this system. NOTE: The OMSA credentials are the same credentials used for ESXi hosts. – In the Verify Password text box, type the password again. – In the Certificate Check drop-down list, select one of the following: 9.
System Event Logs provide information based on the following criteria: Status There are several status icons: Informational (blue exclamation point), Warning (yellow triangle with exclamation point), Error (red X). Time (Server Time) Indicates the time and date the event occurred. Search this page Displays the specific message, server names, configuration settings, and so on. The severity levels are defined as: Info The OpenManage Integration for VMware vCenter operation completed successfully.
There are several status icons: Informational (blue exclamation point), Warning (yellow triangle with exclamation point), Error (red X). • Time (Server Time) Displays the time and date the event occurred. • Search this page Displays the specific message, server names, configuration settings, and so on. To display the system event log for an individual host: 1. From the vSphere Client, under the Inventory heading select Hosts and Clusters. 2. In the tree view, select the host system. 3.
NOTE: For 9th and 10th generation servers, BIOS/BMC/DRAC firmware versions are viewable only at the Cluster View level in vCenter or on the Overview page of the individual host view. Firmware version information is not active in the individual host view under Firmware, and remote firmware updates are not available. Firmware Versions After October 14, 2010 For Firmware updated on or after October 14th, 2010, the Firmware Update Wizard runs.
Components to be Downgraded check box, select the options that are listed as Downgrade. Selecting this option is only recommended to advanced users who understand the implications of downgrading firmware. 5. Select the desired restart option. • Enter maintenance mode, apply updates, and restart. Host goes into maintenance mode. If the host cannot enter maintenance mode, then the host is not restarted and the update is applied during the next reboot.
After this procedure, run the Firmware Update Wizard again to make sure your firmware is completely updated. Running the Update Firmware Wizard for Clusters and Datacenters This functionality is only available for 11th and later generations of Dell servers that have either an iDRAC Express or iDRAC Enterprise. If your firmware was installed on or after October 14th, 2010, you can automatically update your firmware versions using the Firmware Update Wizard.
a. In the Firmware Update Job Name text box, type the firmware update job name. This is a mandatory field. If this is not filled in, this upgrade is not scheduled. Do not use a name that is already in use. If your purge this name, you may reuse it again. b. In the Firmware Update Description, type the description. 15. Under Job Schedule, do one of the following: NOTE: Selecting an option is mandatory. If one is not selected, the upgrade is blocked.
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.
• Secure transmission using a proxy server and credentials NOTE: Dell does not store transmitted service tag information. Related Tasks: • Running A Warranty Retrieval Job • Viewing Server Warranty Information For A Single Host • Viewing Warranty Information For An Entire Data Center Viewing Server Warranty Information For An Entire Data Center Once the warranty job completes, you can view server warranty information in vSphere Client, on the Datacenter View page.
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.
location you can access during the deployment process. For the most up-to date list of supported ESXi versions for this release, see the Release Notes. • OpenManage Integration for VMware vCenter only supports BIOS mode to auto-deploy hypervisor on the target server. Make sure that you have BIOS mode selected in the reference hardware profile prior to applying the Hypervisor profile.
Hardware only Up to 2 hours depending on the complexity and the RAID, BIOS, and boot options to configure Hypervisor and Hardware profiles 1 to 4 hours Server States Within The Deployment Sequence When an inventory job is run, auto-discovered bare-metal systems are classified in different states to help determine if the server is new to the datacenter or has a pending deployment job scheduled. Administrators can use these states to determine if a server should be included in a deployment job.
Understanding How To Configure A Hardware Profile To configure server hardware settings, you must create a hardware profile. A hardware profile is a configuration template you can apply to newly-discovered infrastructure components and it requires the following information: Boot Order The boot order is the boot device sequence and hard drive sequence, which you can edit only if the boot mode is set to BIOS.
Creating A New Hardware Profile To create a new hardware profile: 1. In the Dell Management Center, select Deployment → Deployment Templates → Hardware Profiles. 2. Click Create New. 3. In the New Hardware Profile page, do the following: • In the Profile Name text box, enter the profile name. 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.
• Serial Communication • Embedded Server Management • Power Management • System Security • Miscellaneous Settings Once all updates are made for a category, click Apply to save the changes or click Cancel to cancel the changes. NOTE: For detailed BIOS information, including setting options and explanations, refer to the Hardware Owner’s Manual for the selected server. 15. In the left pane, select iDRAC Settings and then select Network. 16.
Enabling CSIOR On A Reference Server Before creating a hardware profile using a reference server, enable the Collect System Inventory On Reboot (CSIOR) setting and reboot the server to provide accurate inventory and configuration information. There are two methods for enabling CSIOR: Locally This uses an individual host using the Dell Lifecycle Controller United Server Configurator (USC) user interface. Remotely This uses a WS-Man script.
Viewing Or Editing Hardware Profiles To view or edit a hardware profile: 1. In the Dell Management Center, select Deployment → Deployment Templates → Hardware Profiles. 2. Select a profile and click View/Edit. 3. In the Hardware Profile window, to make any changes, click Edit. 4. Click Save to apply changes, or click Cancel to cancel changes. Duplicating Hardware Profiles To duplicate a hardware profile: 1. In the Dell Management Center, select Deployment → Deployment Templates → Hardware Profiles.
• vCenter instance that manages the deployed hosts, plus an optional host profile • The destination cluster or datacenter where the plug-in deploys servers in vCenter NOTE: Use one of the following naming conventions for the Reference ISO file name: NFS format: host:/share/hypervisor_image.iso CIFS format:\\host\share\hypervisor.iso To create a new hypervisor profile: 1. In the Dell Management Center, select Deployment → Deployment Templates → Hypervisor Profile. 2.
• 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. When a VLAN ID is provided, it is applied to the hypervisor's management interface during deployment and tags all traffic with the VLAN ID.
all systems to communicate to each other correctly. If routing is not enabled between these VLANs, then the deployment fails. Viewing Or Editing Hypervisor Profiles To view or edit hypervisor profiles: 1. In the Dell Management Center, select Deployment → Deployment Template → Hypervisor Profiles window. 2. Select a profile and click View/Edit. 3. In the Hypervisor Profiles: Profile Name window, select the profile section to display or change, and make any necessary changes. 4.
The updated hypervisor profile information displays. Building A New Deployment Template A deployment template contains either a hardware profile, a hypervisor profile, or both. The Deployment Wizard uses this template to provision server hardware and deploy hosts within vCenter. To build a new deployment template: 1. In the Dell Management Center, select Deployment → Deployment Templates. 2. Under Available Profiles, click Create New. 3.
4. To display all deployment templates, from the Dell Management Center select Deployment → Deployment Templates and click Refresh. Running The Deployment Wizard The Deployment Wizard steps you through the bare metal server deployment process of: • Selecting undeployed servers. When you deploy hypervisor, you can deploy to an Internal Dual SD Module with a minimum of 1 GB of storage.
Deployment Wizard Step 2: Deployment Templates Deployments to a hardware profile differ from hypervisor deployments. If you are deploying to a hardware profile, click Deployment Wizard Step 6. To select a deployment template: 1. 2. Deployment Template selects/creates a deployment template in one of several ways: • Select an existing deployment template under Available Templates. Information for the selected template populates the right pane.
• Use the Dynamic Host Configuration Protocol (DHCP) to configure IP addresses, subnet mask, gateway IP, hostname and preferred/alternate DNS servers. The DHCP assigned IP address will be used when adding the host to vCenter. When using DHCP, it is highly recommended that an IP reservation for selected NIC MAC addresses be used. NOTE: Use a Fully Qualified Domain Name (FQDN) for hostname instead of localhost. Starting with ESXi 5.
3. To create a new profile, click New and to view or edit the selected profile click View/Edit. 4. To display the selected connection profile settings, click View. 5. Select the Select a Connection Profile for each Server option button, and then select an individual connection profile for each server from the drop-down list. 6. Once a connection profile is selected, click Next. To continue with the task to Step 6, click Deployment Wizard Step 6.
• Modifying An Inventory Job Schedule • Viewing Firmware Update Status for Clusters and Datacenters Managing Deployment Jobs Using The Deployment Job Queue To manage deployment jobs using the deployment job queue: 1. From the Dell Management Center, select Job Queue → Deployment Jobs. 2. To update Deployment Jobs Details, click Refresh. 3. To display a Deployment Job Details dialog, which contains detailed information on the servers included in the deployment job, click Details.
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).
3. In the Register a New vCenter dialog box, under vCenter Name do the following: a. In the vCenter Server IP or Hostname text box, enter the vCenter IP address or a FQDN of the host. b. In the Description text box, enter an optional description. 4. Under Admin User Account, do the following: a. In the Admin User Name text box, enter the administrator's user name. b. In the Password text box, enter the password. c. In the Verify Password text box, enter the password again. 5. Click Register.
The OpenManage Integration for VMware vCenter will work with any of these vCenter Server versions: 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 v6.0 Y Y 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.
3. In the Unregister vCenter dialog box that asks if you really want to unregister this server, click Unregister. Uploading a OpenManage Integration for VMware vCenter License to the Administration Console 1. In OpenManage Integration for VMware vCenter, on the Summary tab, use the link to open the Administration Console. 2. In the Login dialog box, type your password. 3. In the left pane, click VCENTER REGISTRATION. The registered vCenters are displayed in a table.
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.
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. If you are using credentials, in the User Name text box, enter the user name. In the Password text box, type the password. Click Apply.
NOTE: You can use Microsoft Internet Explorer , Firefox, Crome to upload certificates. 1. In OpenManage Integration for VMware vCenter, on the Summary tab, use the link to open the Administration Console. 2. In the Login dialog box, type your password. 3. In the left pane, click APPLIANCE MANAGEMENT. 4. Click Upload Certificate for HTTPS Certificates. 5. In the Upload Certificates dialog box, click OK. 6. To select the certificate to upload, click Browse, and then click Upload. 7.
• Performing An Immediate Backup • Restoring The Database From Backup Configuring Backup And Restore The backup and restore function backs up the OpenManage Integration for VMware vCenter database to a remote location from which it can be restored at a later date. Profiles, templates, and host information are included in the backup. It is recommended that you schedule automatic backups to guard against data loss. After this procedure, you must configure a backup schedule.
Performing An Immediate Backup 1. In OpenManage Integration for VMware vCenter, under Administration Console, use the link to open the Administration Console. 2. In the Login dialog box, type your password. 3. In the left pane, click BACKUP AND RESTORE. 4. Click Backup Now. 5. To use location and encryption password from the Backup settings, in the Backup Now dialog box, select that check box. 6. Enter a Backup Location, User Name, Password, and Encryption Password.
Use the arrow keys to navigate up or down. Once you have selected the option you want, press . After you access the Console screen, VMware vSphere Client takes control of your cursor. To escape from that control, press + . Configuring Network Settings Changes to the network settings are done in the vSphere Client Console. 1. In vSphere Web Client, in the Navigator, select vCenter. 2. In the Navigator, select the Virtual Machine that you want to manage. 3.
Rebooting Virtual Appliance To reboot the virtual appliance: 1. In vSphere Client, select the OpenManage Integration for VMware vCenter virtual machine, and then click the Console tab. 2. Select Reboot this Virtual Appliance and press . 3. The following message is displayed: If there are any processes running on this appliance they will be terminated by this action. Are you sure you wish to do this? 4. Enter y to reboot or n to cancel. The appliance is rebooted.
4. Power on the OpenManage Integration version 3.0 appliance. 5. Setup the network, time zone and so on to the appliance. It is mandatory that the new OpenManage Integration version 3.0 appliance has the same IP address as the old appliance. NOTE: The plug in might not work properly if the IP address for the 3.0 appliance is different from the IP address of the older appliance. In such a scenario, you need to un-register and re-register all the vCenter instances. NOTE: While upgrading OMIVV from 2.
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.
Version Affected: 3.0 How do I resolve error code 2046/2048? When you click the Dell Management Center icon in the vSphere Client, the Flash error code 2046/2048 is displayed in some situations. Perform one of the following solutions to fix the error code 2046/2048: • Upgrade Flash Player to version 18. • Clear both Internet Explorer and Flash Player caches. • Uninstall and reinstall Web browser. • Uninstall and reinstall Flash Player.
Using OpenManage Integration for VMware vCenter to update an Intel Network card from 14.5 or 15.0 to 16.x fails due to staging requirement from DUP This is a known issue with NIC 14.5 and 15.0. You must use the custom catalog to update the firmware to 15.5.0 first before updating the firmware to 16.x. Version Affected: All 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’.
Even if my repository has bundles for selected 11G system, why is firmware update showing that I have no bundles for Firmware Update? When I added a host to the connection profile in lockdown mode, the inventory kicked off but failed stating that “No Remote Access Controller was found or Inventory is not supported on this host.
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 OpenManage Integration for VMware vCenter, the OpenManage Integration for VMware vCenter starts the http Client service and enables port 8080 on releases after ESXI 5.0 to download OMSA VIB and install it.
Table 5. Managed Nodes Port Number Protocols Port Type Max.
What are the Minimum requirements for successful installation and operation of the virtual appliance? The following settings outline the minimum appliance requirements: • Google Chrome, version 28 and later . • Microsoft Internet Explorer, version 9 and 10 • Mozilla Firefox, version 22 and later • Reserved Memory: 2 GB NOTE: For optimal performance Dell recommends 3 GB. • Disk: 43.5 GB. • CPU: 2 virtual CPUs.
was already enabled, then login to the iDRAC console, reset iDRAC, wait for few minutes, and then refresh the Firmware Update page in vSphere Desktop client. How Do I Test Event Settings by Using OMSA to Simulate a Temperature Hardware Fault? To make sure that events are functioning correctly: 1. In the OMSA user interface, navigate to Alert Management → Platform Events. 2. Select the Enable Platform Event Filter Alerts check box. 3. Scroll down to the bottom, and click Apply Changes. 4.
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.
Why Are My Hypervisor Deployments Failing On R210 II Machines? A timeout issue on R210 II systems produces a hypervisor deployments failure error due to the failure of the BIOS to boot from attached ISO. To resolve this issue, manually install hypervisor on the machine. Why Do I See Auto-discovered Systems Without Model Information in the Deployment Wizard This usually indicates that the firmware version installed on the system does not meet recommended minimum requirements.
My vCenter Registration Failed. What Can I Do? vCenter registration can fail due to communication issues, therefore if you are experiencing these issues one solution is to use a static IP address. To use a static IP address, in the Console tab of the OpenManage Integration for VMware vCenter and select Configure Network → Edit Devices and enter the correct gateway and FQDN (Fully Qualified Domain Name). Enter the DNS server name under Edit DNS Config.
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.
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. 7. Enable Get DNS domain name from DHCP. 8.
Virtualization-related Events For Dell PowerEdge Servers 8 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 6.
Dell - Power supply detected a warning A power supply sensor reading in the specified system exceeded a user definable warning threshold. Warning No action Dell - Power supply detected a failure A power supply has been disconnected or has failed. Error Put the system into maintenance mode Dell - Power supply sensor detected a nonrecoverable value A power supply sensor Error in the specified system detected an error from which it cannot recover.
Dell - An AC power cord An AC power cord has Error has lost its power lost its power, and lack of redundancy requires this to be classified as an error. No action Dell - Processor sensor returned to a normal value Sensor Returned to Normal Value No action Dell - Processor sensor detected a warning value A processor sensor in Warning the specified system is in a throttled state.
temperature sensor reading exceeds the error threshold for which the system is configured, the operating system shuts down and the system powers off. This event may also be initiated on certain systems when a fan enclosure is removed from the system for an extended period of time. Dell - Temperature sensor returned to a normal value Sensor Returned to Normal Value.
detected the failure of one or more fans. Dell - Fan sensor detected a nonrecoverable value A fan sensor detected an Error error from which it cannot recover.
Dell - Storage: Enclosure hardware failure Error Put the system into maintenance mode Dell - Storage: Array disk Array disk failure. 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.
Dell - CPU Presence (Processor Presence detected) CPU Presence (Processor Presence detected) Info No Action Dell - System Event Log (SEL) Full (Logging Disabled) System Event Log (SEL) Full (Logging Disabled) Error No Action Dell - System Event Log (SEL) Cleared System Event Log (SEL) Cleared Info No Action Dell - SD Card redundancy Has Returned to Normal SD Card redundancy Info Has Returned to Normal No Action Dell - SD Card Redundancy has been Lost SD Card Redundancy has been Lost Error
Dell - Internal Dual SD Module is online Internal Dual SD Module Info is online No Action Dell - Internal Dual SD Module is operating normally Internal Dual SD Module Info is operating normally No Action Dell - Internal Dual SD Module is write protected Internal Dual SD Module Warning is write protected No Action Dell - Internal Dual SD Module is writable Internal Dual SD Module Info is writable No Action Dell - Integrated Dual SD Module is absent Integrated Dual SD Module is absent Error No
Dell - Network information Network information Info No Action Dell - Physical disk failure Physical disk failure Error No Action Dell - Physical disk warning Physical disk warning Warning No Action Dell - Physical disk information Physical disk information Info No Action Dell - An error was detected for a PCI device An error was detected for a PCI device Error No Action Dell - A warning event was detected for a PCI device A warning event was detected for a PCI device Warning No Action
Dell - Power usage audit Power usage audit failure or critical event. failure or critical event. Error No Action Dell - Configuration: Software configuration failure. Configuration: Software configuration failure. Error No Action Dell - Chassis Management Controller detected a warning. Chassis Management Controller detected a warning. Warning No Action Dell - Link status warning. Link status warning. Warning No Action Dell - Security warning. Security warning.
A Understanding Auto-Discovery 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.
Auto-Discovery Prerequisites Before attempting to discover 11th, 12th, or later generation Dell PowerEdge bare-metal servers, install the OpenManage Integration for VMware vCenter. Only 11th generation Dell PowerEdge or later servers with iDRAC Express or iDRAC Enterprise can be discovered into the OpenManage Integration for VMware vCenter’s pool of bare-metal servers. Network connectivity from the Dell bare-metal server’s iDRAC to the OpenManage Integration for VMware vCenter virtual machine is required.
7. In the User Configuration page, under General, clear the Enable User check box. 8. Click Apply. 9. After you have successfully set up Auto-Discovery, to re-enable each account, repeat steps 1 to 8, but this time select the Enable User check box and click Apply. Manually Configuring a Server For Auto-Discovery (11th Generation of PowerEdge Servers) You must have the iDRAC and host IP addresses.
Figure 6. Press CTRL + E to activate this screen. 11. In the iDRAC6 Configuration Utility, use the arrow keys to select LAN Parameters. 12. Press Enter. 13. If this host is a blade, to configure NIC, use the space bar to toggle the options to Enabled. 14. If you are using DHCP, use the arrow keys to select Domain Name from DHCP. 15. Use the space bar to toggle the option to On. 16. If you are using DHCP, use the arrow keys to navigate to the IPv4 settings and select DNS Servers from DHCP. 17.
If you have not ordered your bare metal appliance to use Auto-Discovery from the factory, you can set it up manually. iDRAC has two user interfaces, both are reached using the IP address of the iDRAC you want to set up. On successful Auto-Discovery of bare-metal servers, the new administrator account is created or an existing account is enabled with the credentials returned by the handshake service. All the other administrative accounts that were disabled prior to Auto-Discovery are not enabled.
