OpenManage Integration for VMware vCenter Version 4.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. 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. © 2011 - 2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction................................................................................................................................. 9 Whats new in this release.....................................................................................................................................................9 OpenManage Integration for VMware vCenter features................................................................................................. 9 2 About Administration Console.
Appliance settings..........................................................................................................................................................35 vCenter settings............................................................................................................................................................ 37 7 Using Baseline tab...................................................................................................................... 39 Repository profile.
Viewing storage details for data center and clusters................................................................................................66 Viewing additional hardware details for data center and clusters........................................................................... 67 Setting up physical server blink indicator light.................................................................................................................69 Configuring System Lockdown Mode......................
Creating hypervisor profile................................................................................................................................................107 Managing hypervisor profiles......................................................................................................................................108 Creating deployment templates.......................................................................................................................................
Task cannot be scheduled for the time in the past- error in inventory schedule and warranty schedule page of Initial Configuration Wizard appear.......................................................................................................... 131 Installation date appears as 12-31-1969 for some of the firmware on the firmware page..................................132 Successive global refresh cause exception to be thrown in the recent task window. ......................................
The 267027 exception is thrown while adding a 12G bare-metal server with an Express license ... 141 During OS deployment on 14G, hardware profile apply fails due to iDRAC error................................................. 141 OMIVV RPM upgrade fails when proxy is configured with domain user authentication.....................................141 Unable to apply System Profile that has PCIe card in the FX chassis...................................................................
1 Introduction IT administrators use VMware vCenter as the primary console to manage and monitor VMware vSphere ESX/ESXi hosts. OpenManage Integration for VMware vCenter (OMIVV) enables you to manage the Dell hosts better from the VMware web client by providing enhanced capabilities for deployment, manage, monitor and upgrade.
Features Description • The current Cluster aware update feature is enhanced to support the vSAN clusters when the DRS option is enabled. The enhanced feature also supports updating the driver and firmware of vSAN clusters. Deployment and provisioning Create hardware profiles (11th to 13th generation PowerEdge servers), System profiles (14th generation servers), hypervisor profiles, and remotely deploy OS on the bare-metal PowerEdge servers by using VMware vCenter without using PXE.
2 About Administration Console You can achieve the administration of OpenManage Integration for VMware vCenter and its virtual environment by using the following two administration portals: • • Web-based Administration Console Console view for an individual server—the virtual machine console of the OMIVV appliance Topics: • Using Administration Portal Using Administration Portal You can use the administration portal to perform the following tasks: • • • • • • • • • • Register a vCenter server.
Required privileges for nonadministrator users To register OMIVV with vCenter, a nonadministrator user requires the following privileges: NOTE: While registering a vCenter server with OMIVV by a nonadministrator user, an error message is displayed if the following privileges are not assigned: • Alarms • • Create alarm • Modify alarm • Remove alarm Extension • • Register extension • Unregister extension • Update extension Global • • • Cancel task Log event Settings • NOTE: Assign the following health
• Permissions • • Modify permission • Modify role Sessions • • Validate session Task • • Create task Update task NOTE: If a non-administrator user is trying to register vCenter server, then it is mandatory to add Dell privileges to the existing role. For more information about assigning Dell privileges, see Assigning Dell privileges to existing role.
NOTE: Dell recommends that register OMIVV with the VMware vCenter by using Fully Qualified Domain Name (FQDN). For all registrations, the hostname of vCenter should be properly resolvable by the DNS server. The following are the recommended practices for using the DNS server: • Assign a static IP address and hostname when you deploy an OMIVV appliance with a valid DNS registration. A static IP address ensures that during the system restart, the IP address of the OMIVV appliance remains same.
NOTE: Ensure that you do not unregister OMIVV from the vCenter server when an inventory, a warranty, or a deployment job is running. 1. To open Administration Portal, in the Help and Support tab of OpenManage Integration for VMware vCenter, click the link under Administration Console or start a web browser and provide the https:\\ url. 2. In the VCENTER REGISTRATION page, from the vCenter Server IP or Hostname table, click Unregister.
Type the domain name in the format: . 3. Click Update Hostname. The appliance hostname is updated, and you return to the main menu. 4. To reboot the appliance, click Reboot Appliance. NOTE: If you had registered any vCenter servers with the appliance, unregister and re-register all the vCenter instances. NOTE: Ensure that you manually update all references to the virtual appliance across its environment such as provisioning server in iDRAC, DRM.
NOTE: During the upgrade process, the appliance restarts once or twice. NOTE: Once the appliance is RPM upgraded, ensure that you do the following: • Clear the browser cache before log in to the Dell admin portal. • Reinstall the VMware tools. To reinstall the VMware tools: 1. Right-click the OMIVV appliance. 2. Hover over Guest, and then click Install/Upgrade VMware Tools. 3. On the Install/Upgrade VMware Tools dialog box, click Automatic Tools Upgrade, and then click OK.
3. Click Close. Setting up HTTP proxy 1. In the APPLIANCE MANAGEMENT page, scroll down to HTTP PROXY SETTINGS, and then click Edit. 2. Perform the following steps in edit mode: a) b) c) d) e) f) g) Select Enabled to enable the use of HTTP proxy settings. Enter the proxy server address in Proxy Server Address. Enter the proxy server port in Proxy Server Port. Select Yes to use proxy credentials. If using proxy credentials, enter the user name in Username. Type password in Password. Click Apply.
Downgrading deployment mode 1. Log in to the Administration Console. 2. Change the deployment mode to the desired level. 3. Shut down the OMIVV appliance and change the system resources to the desired level. 4. Turn-on the OMIVV appliance. Generating Certificate Signing Request Ensure that you upload the certificate before registering OMIVV with the vCenter.
Managing backup and restore Managing backup and restore is accomplished from the Administrative Console. The tasks on this page include: • • • • Configuring backup and restore Scheduling automatic backups Performing an immediate backup Restoring the database from backup In OpenManage Integration for VMware vCenter, perform the following steps to access the BACKUP AND RESTORE SETTINGS page through the Administration Console: 1.
Restoring OMIVV database from backup The restore operation causes the virtual appliance to reboot after restoration is complete. 1. Open the BACKUP AND RESTORE SETTINGS page. See the Managing backup, and restore. 2. In the BACKUP AND RESTORE SETTINGS page, click Restore Now. 3. In the RESTORE NOW dialog box, enter the path for File Location along with the backup .gz file in CIFS/NFS format. 4. Enter the Username, Password, and Encryption Password for the backup file.
Configuring NTP and setting local time zone 1. Open the virtual machine console. See Opening vSphere client console. 2. To configure the OMIVV time zone information, click Date/Time Properties. 3. In the Date and Time tab, select Synchronize date and time over the network. The NTP Servers window is displayed. 4. To add the NTP server IP or host name, click the Add button, and then press TAB. 5. Click Time Zone, select the applicable time zone, and then click OK. Rebooting virtual appliance 1.
3 Managing multiple appliances You can manage and monitor multiple OMIVV appliances that you register with vCenter servers that belong to the same Platform Service Controller (PSC) or to a different PSC. Dell EMC recommends to use the similar vCenter versions. Dell EMC recommends that you perform a global refresh if page is cached. 1. In VMware vCenter home page, click the OpenManage Integration icon. 2. In Navigator, under the Dell EMC group, click OMIVV Appliances. 3.
4 Accessing OpenManage Integration from web client When you log in to VMware vCenter after installing OMIVV, under the Home tab, the OpenManage Integration icon is located in the main content area under the Administration group. You can use the OpenManage Integration icon to navigate to the OpenManage Integration for VMware vCenter page. The Dell EMC group is displayed in the Navigator pane. VMware vCenter layout has the following three main panes: Table 3.
Icons in web client The product user interface uses many icon-based action buttons for the actions you take. Table 4.
• • • • Host Name—displays a link using the IP address for each Dell EMC host. To view Dell EMC host information, click a specific host link. vCenter—displays the vCenter IP address for this Dell EMC host. Cluster—displays the cluster name, if the Dell EMC host is in a cluster. Connection Profile—displays the name of the connection profile.
Name Description • • • • • iDRAC with Lifecycle Controller Manuals Dell VMware Documentation OpenManage Integration for VMware vCenter Product Page Dell Help and Support Home Dell TechCenter Support Call Tips Offers tips on how to contact Dell Support and route your calls correctly. Troubleshooting Bundle Provides a link to create and download the troubleshooting bundle. You can provide or view this bundle when you contact technical support.
3. In the iDRAC Reset dialog box, under iDRAC Reset, type the host IP address/name. 4. To confirm that you understand the iDRAC reset process, select I understand iDRAC reset. Continue iDRAC reset. 5. Click Reset iDRAC. Opening online help You can open the online help from the Help and Support tab. You can search the document for help on understanding a topic or a procedure. 1.
• Custom Range • If you select Custom Range, you can specify the start and end date based on what you want to filter, and then click Apply. The grid table displays the following information: • • • Category — displays the type of log category Date and Time — displays the date and time of user action Description — displays a description of the user action You can sort the data grid columns in ascending or descending order by clicking the column header.
5 OpenManage Integration for VMware vCenter licensing The OpenManage Integration for VMware vCenter has two types of licenses: • • Evaluation license—when the OMIVV version 4.x appliance is powered on for the first time, an evaluation license is automatically installed. The trial version contains an evaluation license for five hosts (servers) managed by the OpenManage Integration for VMware vCenter.
6 Appliance configuration for VMware vCenter After you complete the basic installation of OMIVV and registration of the vCenters, the Initial Configuration Wizard is displayed when you click the OMIVV icon. You can proceed to configure the appliance by using one of the following methods: • • Configuring the appliance through the Initial Configuration Wizard. Configuring the appliance through the Settings tab in OMIVV.
3. To proceed with the Connection Profile Description dialog box, click Next. NOTE: If you have multiple vCenter servers that are part of the same single sign-on (SSO) registered with the same OMIVV appliance, and if you choose to configure a single vCenter server, repeat steps 1 through 3 until you configure each vCenter. Creating connection profile Before using the Active Directory credentials with a connection profile, ensure that: • • The Active Directory user’s account exist in Active Directory.
• No nonprintable characters • No Invalid characters, such as " / \ [ ] : ; | = , + * ? < > @ Host domain requirements: • Between 1 and 64 characters long • First character must be alphabetical. • Cannot contain a space. • No Invalid characters, such as " / \ [ ] : ; | = , + * ? < > @ b. In Active Directory Password, type the password. The password is limited to 127 characters. c. In Verify Password, type the password again. d.
NOTE: The chassis gets discovered automatically after the inventory for all hosts is run. If the chassis is added to a chassis profile, the chassis inventory automatically runs. In an SSO environment with multiple vCenter servers, the chassis inventory runs automatically with every vCenter when the inventory for any vCenter is run at a scheduled time. NOTE: The settings in this page are reset to default each time the configuration wizard is invoked.
NOTE: The Dell EMC hosts that have alarms enabled respond to some specific critical events by entering in to maintenance mode and you can modify the alarm, when required. The Enabling Dell EMC Alarm Warning dialog box is displayed. 3. To accept the change, click Continue, or to cancel the change, click Cancel. NOTE: Ensure that you complete this step only if you select Enable Alarms for all Dell EMC Hosts. 4.
1. In OpenManage Integration for VMware vCenter, on the Manage > Settings tab, under Appliance Settings at the right side of Firmware Update Repository, click the icon. 2. In the Firmware Update Repository dialog box, select one of the following: • Dell Online—you can access the location that uses the firmware update repository of Dell (Ftp.dell.com). The OpenManage Integration for VMware vCenter downloads selected firmware updates from the Dell repository and updates the managed hosts.
• The user name should be 16 characters or less (only ASCII printable characters). In the Password text box, enter the password. • The password should be 20 characters or less (only ASCII printable characters). In the Verify Password text box, enter the password again. Ensure that the passwords match. 3. To save the specified credentials, click Apply. vCenter settings In this section, configure the following vCenter settings: • • • Enable the OMSA link. See Enabling the OMSA link.
This step can take up to a minute before the change takes effect and is available only if Enable Alarms For Dell EMC Hosts is selected. 5. In Event Posting Level, select either “Do not post any events”, “Post All Events”, “Post only Critical and Warning Events”, or “Post only Virtualization-Related Critical and Warning Events”. For more information, see Events, alarms, and health monitoring. 6. If you want to apply these settings to all vCenters, select Apply these settings to all vCenters.
7 Using Baseline tab You can use the Baseline tab to create repository profile and cluster profile. Topics: • • • • • • • • Repository profile Creating repository profile Editing repository profile Deleting repository profile Cluster profile Creating cluster profile Editing cluster profile Deleting cluster profile Repository profile Repository profile allows you to create or maintain multiple driver or firmware repository profiles.
e. To export the repository profile information to a .CSV file, select a repository profile, and click data grid. in the right-hand corner of the Creating repository profile 1. On the OpenManage Integration for VMware vCenter page, click Manage > Baseline, expand Baseline Info, and then click Repository Profile. 2. Click . 3. On the Welcome page, read the instructions, and click Next to add further details: a. In the Profile Name box, type the repository profile name. b.
NOTE: By default, Synchronize with the Repository Location option is selected. Ensure that this option is selected if you want to recreate the catalog from the latest driver or firmware catalog (share location). 5. Click Next. The Summary page is displayed that provides the information about the repository profile. 6. Click Finish. Deleting repository profile Before deleting the repository profile, ensure that you unlink the repository profile from the associated cluster profiles. 1.
1. On the OpenManage Integration for VMware vCenter page, click Manage > Baseline, expand Baseline Info, and then click Cluster Profile. 2. Click . 3. On the Welcome page, read the instructions, and click Next to add further details: a) In the Profile Name field, type the cluster profile name. b) In the Profile Description field, type description of the cluster profile. The profile description is optional. c) Click Next. 4.
8 Profiles About connection profile The Connection Profiles tab lets you manage and configure connection profiles that contain credentials that are in use by the virtual appliance to communicate with the Dell EMC servers. Associate each Dell EMC server with only one connection profile for management by the OpenManage Integration for VMware vCenter. You can assign multiple servers to a single connection profile.
NOTE: The vCenter hosts that are listed during this procedure are authenticated by using the same Single Sign On (SSO). If you do not see a vCenter host, it might be on a different SSO or you might be using a VMware vCenter version that is less than version 5.5. 1. In OpenManage Integration for VMware vCenter, from the Manage → Profiles → Credential Profiles → Connection Profiles tab, click . 2. On the Welcome page, read the instructions, and click Next. 3.
• • In the Verify Password text box, type the password again. For certificate check, select one of the following: • • To download and store the host certificate and validate it during all future connections, select Enable Certificate Check. To not perform any check and not store the host certificate, do not select Enable Certificate Check. NOTE: The OMSA credentials are the same credentials used for the ESXi hosts. 4. Click Next. 5.
• • • • In the Active Directory User Name text box, type the user name. Type the user name in one of these formats; domain \username or domain/username, or username@domain. The user name is limited to 256 characters. See the 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.
test connection fails, it is recommended that you complete the connection profile wizard actions, run the inventory on the hosts, and then test the connection profile again. • When the test is complete, click Finish. To stop the tests, click Abort All Tests. In the Abort Tests dialog box, click OK, and then click Finish. NOTE: The Date Modified and Last Modified By fields include changes that you perform through the web client interface for a connection profile.
4. To display all the associated chassis, click the icon, if multiple chassis are associated with the chassis profile. 5. In the Chassis Profiles page, view the chassis information. Table 8.
Editing chassis profile After you have created a chassis profile, you can edit the profile name, description, associated chassis, and credentials. 1. In OpenManage Integration for VMware vCenter, click Manage. 2. Click Profiles, and then click Credential Profiles. 3. Expand Credential Profiles, click the Chassis Profiles tab, and select a chassis profile. 4. Click the icon on the main menu. The Edit Chassis Profile window is displayed. 5.
9 Inventory and warranty management After you configure OMIVV, you can monitor the inventory, warranty jobs, manage deployment jobs, and manage firmware update jobs under the Monitor tab. The inventory and warranty are set up in the Initial Configuration Wizard or from the Settings tab. The job queue page manages the following jobs: • • • • Displaying the submitted server deployment or firmware update jobs. Refreshing the firmware update or deployment jobs, or inventory/warranty history queues.
• The number of host licenses exceeds, and you must have additional licenses available for the inventory task to complete. • The host does not have the correct iDRAC license required for 12th and later generation of PowerEdge servers and hence, purchase the correct iDRAC license. • The credentials might be wrong. • The host might not be reachable. To view the host inventory details: 1. In OpenManage Integration for VMware vCenter, click the Monitor tab. 2.
Chassis inventory Duration (MM: SS) Displays the duration of the job in minutes and seconds Start Date and Time Displays the date and time when the inventory schedule started End Date and Time Displays the time the inventory schedule ended NOTE: The chassis inventory is not supported on the following PowerEdge servers: C6320P, C6320, C4130, and C6420.
• • • • • • Blink Indicator Light Run Firmware Update Wizard Launch Remote Access Launch OMSA Launch CMC Configure System Lockdown Mode Running chassis inventory job now You can view and run a chassis inventory job in the Chassis Inventory tab. 1. In the OpenManage Integration for VMware vCenter, click the Monitor tab. 2. Click Job Queue, Inventory History, and then click Chassis Inventory. The list of chassis and its status for the last inventory job is displayed.
vCenter history • • • • Successful Failed In Progress Scheduled Duration (MM:SS) Displays the duration of the warranty job in MM:SS Start Date and Time Displays the date and time when the warranty job started End Date and Time Displays the time the warranty job ended Viewing chassis warranty A warranty job is a scheduled task to get warranty information from Support.dell.com on all systems. You can sort the columns of the inventory view in ascending and/or descending order. 1.
Running host warranty job now Run a warranty job at least once a week. 1. In the OpenManage Integration for VMware vCenter, click the Monitor tab. 2. Click Job Queue, and then click Warranty History. 3. Expand Warranty History to display Hosts Warranty and Chassis Warranty. 4. To view your corresponding warranty job history information, select either Hosts Warranty or Chassis Warranty. 5. Select the warranty job you want to run, and then click . 6. In the Success dialog box, click Close.
Information Description • • Work In Progress Alarms The Dell alarm information is displayed in the notification area portlet. 5. Scroll down to view the Dell EMC Server Management portlet. Table 14. Dell EMC server Management portlet Information Description Service Tag Displays the service tag for your PowerEdge server. Use this ID when you call for support. Model Name Displays the server’s model name. Fault Resilient Memory Displays the status of a BIOS attribute.
Information Description • • • Management Consoles The management consoles are used to launch external system management consoles, such as: • • Host Actions Hypervisor—Displays the Hypervisor version BIOS Version—Displays the BIOS version Remote Access Card Version—Displays the remote access card version Launching the Remote Access Console (iDRAC)—launches the Integrated Dell Remote Access Controller (iDRAC) web user interface.
Table 16.
Hardware: Component Information • URL—displays the live URL for the iDRAC associated with this host Viewing storage details for a single host You can view storage details for a single host on the Dell EMC Hosts Information tab. For information to appear on this page, run an inventory job. The hardware reports data directly from OMSA and iDRAC. See Running inventory jobs. The page displays different options depending on what is selected from the View drop-down list.
Information Description • Physical Disks — When you select this option, the Filter drop-down list is displayed. You can filter physical disks based on the following options: • • • • • Read-Ahead • No-Read-Ahead • Adaptive Read-Ahead • Read Cache Enabled • Read Cache Disabled Default Write Policy—displays the default write policy supported by the controller.
Information Description • • Enclosures • • • Firmware Version—displays the firmware version Minimum Required Firmware—displays the minimum required firmware.
• To cancel, click Cancel. 6. To export the event log to a .CSV file, click . 7. To browse to the location and save the system event log, click Save. Viewing additional hardware details for a single host You can view the firmware, power monitoring, warranty status details for a single host on the Dell EMC Hosts Information tab. For information to appear on this page, run an inventory job. The hardware views directly report the data from OMSA and iDRAC. See Running chassis inventory job now. 1.
Monitoring hosts on clusters and data centers The OpenManage Integration for VMware vCenter enables you to view detailed information for all hosts included in a data center or cluster. You can sort the data by clicking the data grid row header. The data center and cluster pages enable you to export information to a CSV file and offers filter or search functionality on the data grid.
Information Description System Lockdown Mode Only for 14th generation PowerEdge servers: Displays the iDRAC Lockdown Mode of the host, which is turned on, turned off, or unknown. For all PowerEdge servers earlier than 14th generation, the System Lockdown Mode displayed is, not applicable.
Hardware: Component Information • • • • • Service Tag—displays the service tag of the host Type—displays the type of power supply. The power supply types include: • UNKNOWN • LINEAR • SWITCHING • BATTERY • UPS • CONVERTER • REGULATOR • AC • DC • VRM Location—displays the location of the power supply, such as slot 1 Output (Watts)—displays the power in watts Status—displays the status of the power supply.
Hardware: Component Information • • RAC Type—displays the type of the remote access card URL—displays the live URL for the iDRAC associated with this host Viewing storage details for data center and clusters You can view the physical storage details for a data center or cluster on the Datacenter/Cluster Information tab. For information to appear on this page, run an inventory job.
Storage: disks Virtual Disk Description • • • Part Number—displays the storage part number Serial Number—displays the storage serial number Vendor Name—displays the storage vendor name • • • • • • Host—displays the name of the host Service Tag—displays the service tag of the host Name—displays the name of the virtual disk Physical Disk—displays on which physical disk the virtual disk is located Capacity—displays the capacity of the virtual disk Layout—displays the layout type of the virtual storage.
4. In the Monitor tab, select the Dell EMC Datacenter/Cluster Information tab. On the subtab, view the following information for each of the components: Table 23.
Component Information • warranty job is not run, an error has occurred getting the data, or the system does not have a warranty Days Left—displays the number of days left for the warranty Setting up physical server blink indicator light To help in locating a physical server in a large data center environment, you can set the front indicator light to blink for a set time period. 1. In OpenManage Integration for VMware vCenter, in the Navigator area, under Inventory Lists, click Hosts. 2.
10 Events, alarms, and health monitoring The goal of 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 OMIVV plug-in or vCenter. The data center and host system monitoring enables an administrator monitor infrastructure health by displaying hardware (server and storage) and virtualization-related events on the Tasks and Events tab in vCenter.
Event Description Post only virtualization-related critical, and warning events Post virtualization-related events received from hosts into related vCenters. The virtualization-related events are events that Dell selects to be most critical to hosts that run virtual machines. When you configure the events and alarms, you can enable them.
The chassis events are displayed in the following format: Dell-Message:, Chassis name:, Chassis Service Tag:, Chassis Location: Table 25.
Event name Description Severity Recommended action Dell-Fan enclosure removed from system for an extended amount of time A fan enclosure has been removed from the specified system for a user-definable length of time Error No action Dell-Fan enclosure sensor detected a non-recoverable value A fan enclosure sensor in the specified system detected an error from which it cannot recover Error No action Dell-AC power has been restored Sensor Returned to Normal Value Info No action Dell-AC power ha
Event name Description Severity Recommended action 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 Info No action Dell-Temperature sensor detected a warning value A temperature sensor on the backplane board, system board, CPU, or drive carrier in the specified system exceeded its warning threshold Warning No action Dell-Temperature sensor detected a failure value A t
Event name Description Severity Recommended action Dell-Storage: Channel Failure Channel failure Error Put the system into maintenance mode Dell-Storage: Enclosure hardware information Enclosure hardware information Info No action Dell-Storage: Enclosure hardware warning Enclosure hardware warning Warning No action Dell-Storage: Enclosure hardware failure Enclosure hardware error Error Put the system into maintenance mode Dell-Storage: Array disk failure Array disk failure Error Put t
Event name Description Severity Recommended action Dell-System: Software configuration warning System: Software configuration warning Warning No action Dell-System: Software configuration failure System: Software configuration failure Error Put the system into maintenance mode Dell-Storage Security warning Storage security warning Warning No action Dell-Storage Security failure or critical event Storage security failure or critical event Error Put the system into maintenance mode Dell-So
Event name Description Severity Recommended action The fans are not redundant.
Event name Description Severity of a power supply exception, a power supply inventory change, or a system power inventory change. The system was previously operating in a power redundant mode Recommended action configuration and power consumption The power supplies are redundant None Info No action The power supplies are not redundant The current power supply Info configuration does not meet the platform requirements to enable redundancy. If a power supply fails the system may shut down.
Table 27.
To view the event posting levels, see About events and alarms. Viewing events Ensure that you configure events before you can view them in the Events tab. See Configuring events and alarms. View the events for a host, cluster, or data center in the events tab. 1. In the OpenManage Integration for VMware vCenter Navigator, click Hosts, Datacenter or Clusters. 2. In the Objects tab, select a specific host, data center, or cluster for which you want to view events. 3. In the Monitor tab, click Events. 4.
1. Create a connection profile and associate hosts with connection profile. See Creating a connection profile. 2. Verify that hosts inventory is completed successfully. See Viewing hosts inventory. 3. Verify that the SNMP Trap destination in iDRAC is set as the OMIVV appliance IP address. NOTE: Ensure that from the OpenManage Integration > Monitor > Log tab, the user action log confirms the availability of a host for a Proactive HA cluster. 4. Enable Proactive HA on a cluster.
13. To apply the changes, in the Edit Blocked Failure Conditions, click OK, or to cancel, click Cancel. 14. To save the changes, in the Edit Cluster Settings wizard, click OK, or to cancel, click Cancel. After Proactive HA is enabled on a cluster, OMIVV scans through all hosts within the cluster and initializes the Proactive HA health status of all supported host server components. OMIVV can now send the health update notification of supported components to the vCenter server.
Launching OMSA console Before you can start the OMSA console, ensure that you set up the OMSA URL and install and configure the OMSA web server. You can set up the OMSA URL from the Settings tab. NOTE: Install OMSA to monitor and manage PowerEdge 11th generation servers by using OpenManage Integration for VMware vCenter. 1. In OpenManage Integration for VMware vCenter, in the Navigator area, under Inventory Lists, click Hosts. 2. In the Object tab, double-click the host you want. 3.
11 About firmware updates The OMIVV appliance allows you to perform BIOS and firmware update jobs on the managed hosts. You can perform concurrent firmware update jobs across multiple clusters or nonclustered hosts. Running concurrent firmware update on two hosts of the same cluster is not allowed. The following table lists the number of firmware update jobs that you can run simultaneously in various deployment modes, although you can schedule any number of firmware update jobs: Table 28.
• • • • Right-click a host, select All OpenManage Integration Actions > Firmware Update. On the Hosts page, click a host, and then select All OpenManage Integration Actions > Firmware Update. In the Navigator pane, select a host, and then click Summary > Dell EMC Host Information > Run Firmware Wizard. In the Navigator pane, select a host, and then click Monitor > Dell EMC Host Information > Firmware > Run Firmware Wizard.
NOTE: The minimum Maintenance Mode timeout value is 60 minutes. NOTE: The maximum Maintenance Mode timeout value is one day. c) Select either of the following options: • Select Update Now to start the firmware update job immediately. By default, Exit maintenance mode after firmware update completes option is selected. • • • By default, the Move powered off and suspended virtual machines to other hosts in the cluster option is selected.
3. On the Select Update Source page, do the following: a) Select the driver repository profile, or firmware repository profile, or its combinations from the drop-down list. If Baseline repository is associated in Cluster profile, the associated Firmware and Driver repositories are automatically selected. b) Select an appropriate bundle from the Select an Update Bundle drop-down menu. If the driver repository is selected, the Driver Selection page is displayed.
runs automatically on the selected hosts and hosts exit automatically from maintenance mode based on an option selected in the Schedule Firmware Update page. Running firmware update wizard for non-vSAN clusters OMIVV allows you to perform BIOS and firmware updates on all hosts of a cluster. The 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).
8. On the FW Update Information page, view all the firmware update details. 9. Click Next. The Schedule Firmware Update page is displayed. a) Enter the firmware update job name in the Firmware Update Job Name field. The firmware update job name is mandatory and does not use a name that is already in use. If you purge the firmware update job name, you can reuse it again. b) Enter the firmware update description in the Firmware Update Description field, which is optional.
• Right-click a cluster, select Actions > All OpenManage Integration Actions > Firmware Update. OMIVV checks compliance of the host and whether any other firmware update job is in progress in any host within the same cluster. After the verification, the Firmware Update page is displayed. 2. On the Welcome page, read the instructions, and click Next. The Select Servers page is displayed. 3. On the Select Servers page, in the Name tree view, use the check boxes to select the hosts. 4. Click Next.
NOTE: By default, Move powered off and suspended virtual machines to other hosts in the cluster option is selected. Disabling this option disconnects the VM until the host device is online. 10. Click Next. The Summary page is displayed. 11. On the Summary page, click Finish and the The firmware update job has been created successfully message is displayed.
12 Chassis management OMIVV allows you to view additional information for chassis associated with the Modular servers. In the chassis information tab, you can view the chassis overview details for an individual chassis, information about hardware inventory, firmware and management controller, health of the individual chassis components, and chassis warranty information.
Viewing hardware inventory information for chassis You can view information about the hardware inventory within the selected chassis. To view the information in this page, ensure that you run an inventory job and export a CSV file with the component information. 1. In the Home page, click vCenter. 2. In the left pane, under OpenManage Integration, click Dell EMC Chassis. 3. In the left pane, select the corresponding chassis IP. 4. Click the Monitor tab.
Hardware inventory: Component Navigation through OMIVV Information • • Service Tag Power Status To view additional information, select the corresponding I/O module and the following information is displayed: • • • • • • • • PCIe Role Firmware version Hardware version IP address Subnet mask Gateway MAC address DHCP enabled Use either of the following methods: Information about PCIe: • • • PCIe slot • • Slot • Name • Power status • Fabric Server slot In the Overview tab, click PCIe.
Viewing additional hardware configuration for chassis You can view information about the warranty, storage, firmware, management controller details within the selected chassis. To view the information in this page, ensure that you run an inventory job and export a .CSV file with the component information. To view warranty, storage, firmware, management controller details for chassis, perform the following steps: 1. In the Home page, click vCenter. 2.
Hardware configuration Navigation through OMIVV Information • • • • • Virtual Disks Controllers Enclosures Physical Disks Hot Spares NOTE: When you click a highlighted link under storage, the View table displays the details for each highlighted item. In the view table, if you click each line item, additional information is displayed for each highlighted item.
13 Deploying hypervisor OMIVV allows you to configure the following components in the supported bare-metal servers along with deploying the hypervisor and adding it to the specified data center and cluster in a vCenter: • • • • Boot order setting RAID configuration BIOS configuration iDRAC configuration You can create hardware profiles, System profiles, and hypervisor profiles on the bare-metal PowerEdge servers by using VMware vCenter without using PXE.
• • • • • • • Managing System profiles Configuring hardware profile Creating hypervisor profile Creating deployment templates About deployment wizard Deployment job timing Downloading custom Dell EMC ISO images Device discovery Discovery is the process of adding supported PowerEdge bare-metal server. After a server is discovered, you can use it for hypervisor and hardware deployment.
• • • • Additional network settings—ensure that you enable Get DNS server address from DHCP setting, if using DHCP, so that DNS name resolution can occur. Provisioning service location—ensure that iDRAC knows the IP address or host name of the provisioning service server. See Provisioning service location.
enabled account present on the iDRAC, the only way to access the iDRAC is to log in to the box locally and enable the account on the iDRAC. 1. Enter the iDRAC IP address into a browser. 2. Log in to the iDRAC Enterprise GUI. 3. In the Integrated Dell Remote Access Controller 6 — Enterprise > System Summary tab, in the Virtual Console Preview, click Launch. 4. In the Warning — Security dialog box, click Yes. 5. In the iDRAC Utility Console, press F12 once or twice.
27. Use the space bar to toggle the option to Enabled. 28. From your keyboard, press ESC. 29. Press ESC again. Manually configuring PowerEdge 12th and later generation servers for auto discovery Ensure that you have an iDRAC address. When you order servers from Dell EMC, you can ask for the auto discovery feature to be enabled on the servers after you provide the provisioning server IP address. The provisioning server IP address should be the IP address of OMIVV.
After 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 Deployment Wizard. Lastly, view the job status through job queue and change the pending deployment jobs.
• • • Collect System Inventory On Restart (CSIOR) is enabled on a reference server, and the reference server is rebooted, so that the data returned from iDRAC is up-to-date. OpenManage Integration had performed a successful inventory on each of the vCenter managed hosts. Bare-metal servers have the minimum BIOS and firmware versions already installed.
• Enabled attributes display the total number of selected attributes. 8. Click Next. The Summary page is displayed that provides information about the profile details and the attribute statistics of the system configurations. The total number of attributes, total number of enabled attributes, total number of platform-specific attributes, and total number of destructive attributes are displayed under attribute statistics. 9. In the Summary page, click Finish.
• Cloning a hardware profile Enabling CSIOR on reference server Before creating a hardware profile by 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: Table 36. Methods for enabling CSIOR Method Description Locally Uses an individual host by using the Dell Lifecycle Controller United Server Configurator (USC) user interface.
• Clone RAID configuration from the reference server as shown below—use this option, if you want to clone the reference server setting. 8.
Creating or cloning hardware profile 1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates > Hardware Profiles. 2. Click . 3. In the Hardware Profile Wizard, click Next on the Welcome page and perform the following actions: • • In the Profile Name text box, enter the profile name. In the Description text box, enter Description. The description is optional. 4. Click Next. 5.
3. In the Hypervisor Profile dialog box, do the following subtasks: • • In the Profile Name text box, enter the profile name. In the Description text box, enter description, which is an optional entry. 4. Under Choose the Reference ISO Path and Version, in the Installation Source (ISO) text box, type the path to the hypervisor share location. A copy of the hypervisor image is modified to permit a scripted installation.
NOTE: It is recommended to use system profile for 14th generation servers and hardware profile for 13th generation and earlier servers. 6. Select a Hypervisor Profile from the drop-down menu. 7. To apply profile selections and save changes, click Save. To cancel, click Cancel.
VLAN support OMIVV supports hypervisor deployment to a routable VLAN and you can 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. Ensure that the VLAN provided during deployment communicates with both the virtual appliance and the vCenter server.
a) Under Deployment Template, to assign a deployment template to the selected servers, select an existing deployment template from Select Deployment Template. NOTE: System profile based template is displayed only if you select the 14th generation servers on the Select the servers for deployment page.
For the VLAN ID, use the numbers 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames. f) Repeat steps a through h for all servers to be deployed, or select the Apply settings to all selected servers check box. If you select the Apply settings to all selected servers, enter FQDN name and IP address for the other servers. NOTE: While specifying FQDN name for servers, ensure to provide unique host names for each server. 9. Click Next. 10.
For few attributes displayed under Attribute Name of Apply System Profile-Failure Details window is not same as Attribute Name of the system profile when you click More Details. To export the details to a .CSV file, in the right corner of the data grid, click 4. To abort the deployment job, click the . icon. 5. When the message is displayed, click Abort Job to abort, or to cancel, click Do Not Abort Job. 6.
3. To display the Drift Detection job details, which contain detailed information about the servers included in the Drift Detection job, select a Drift Detection job in the upper grid. The following details are displayed in the lower grid: • • • • • • • • Service Tag iDRAC IP Host Name Cluster vCenter Status Start Date and Time End Date and Time 4. To run the Drift Detection job on-demand, click .
batches of up to five concurrent servers to improve time for the overall deployment job. The exact number of concurrent jobs depends on available resources. Table 37.
14 About host, bare-metal, and iDRAC compliance To manage hosts and bare-metal servers with OMIVV, each must meet certain minimum criteria. If not compliant, they are not managed properly by OMIVV. OMIVV displays details about the noncompliance on a bare-metal or a host, and allows you to fix the noncompliance, where applicable.
a) In the vSphere Hosts page, view the list of noncompliant hosts. A table is displayed that lists the noncompliant hosts along with the host IP or host name, model, connection profile, the CSIOR status, OMSA status, WBEM status, SNMP trap status, hypervisor, and the iDRAC license status. b) To view further details of a noncompliant host, select a noncompliant host. c) To swap the columns within the table, drag and drop columns within the data grid. 2.
5. After you install an iDRAC license, run an inventory job for the vSphere host and return to this page after the inventory job is successfully complete for the host to be compliant. Viewing baseline compliance The Baseline Compliance page displays the baseline compliance status based on the drift detection for all OMIVV-managed vSAN hosts associated with the Cluster profile.
• • Recommendation(for driver)—Indicates the importance level of updating the version of an identified component. Reboot required—Indicates whether the appliance reboot is required or not. NOTE: If more than one version of firmware is available, the latest firmware version is always used for compliance comparison. 4. Click Finish. Using OMSA with 11th generation servers To manage the PowerEdge 11th generation servers, OMIVV requires OMSA to be running on them.
7. Enter the OMIVV appliance IP address in the Destination IP Address field. 8. Click Apply Changes. 9. Repeat step 1 to step 8 to configure extra events. NOTE: SNMP community string can be configured from Manage > Settings > Appliance Settings > OMSA SNMP Trap Community String. For more information about SNMP trap community string, see the Configuring SNMP trap community string.
Fixing iDRAC license compliance for bare-metal servers The bare-metal servers listed in the Bare Metal Servers page are noncompliant because they do not have a compatible iDRAC license. A table displays the status of the iDRAC license. You can click a noncomplaint bare-metal server to view more details such as, how many days are remaining for the iDRAC license, and then you can update it, as required.
15 Security roles and permissions The OpenManage Integration for VMware vCenter stores user credentials in an encrypted format. It does not provide any passwords to client applications to avoid any improper requests. The backup database is fully encrypted by using custom security phrases, and hence data cannot be misused. By default, users in the Administrators group have all the privileges.
Dell Operational role The role contains the privileges/groups to accomplish appliance and vCenter server tasks including firmware updates, hardware inventory, restarting a host, placing a host in maintenance mode, or creating a vCenter server task. This role contains the following privilege groups: Table 39. Privilege groups Group name Description Privilege group — Dell.
• • • • Dell.Monitoring.Monitor • • • • 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.Configure Inventory • • • • • • 124 Configure HW Configuration Profile Configure Hypervisor Deployment Profile Configure Connection Profile Assign identity Deploy Dell.Configuration.
16 Frequently Asked Questions-FAQ Use this section to find answers to troubleshooting questions. This section includes: • • Frequently asked questions (FAQ) Bare-metal deployment issues Topics: • • Frequently Asked Questions-FAQ Bare-metal deployment issues Frequently Asked Questions-FAQ This section contains some common questions and solutions. Export All button fails to export to .
1. For VMware vCenter, go to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity and for Windows vCenter, go to C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphereclient-serenity folder in the vCenter appliance and see that old data exists, such as: • com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient-3.0.0.197 2. Manually delete the folder corresponding to the earlier OMIVV version. 3. Restart the vSphere web client service on the vCenter server.
On running fix noncompliant vSphere hosts wizard, the status of a specific host is displayed as Unknown When you run the fix noncompliant vSphere hosts wizard to fix noncompliant hosts, the status of a specific host is displayed as "Unknown". The unknown status is displayed when iDRAC is not reachable. Resolution: Verify the iDRAC connectivity of the host and ensure that inventory is run successfully. Version affected: 4.
The output obtained from the mentioned procedures should display Updated 24 service (s) and Updated 26 service (s) respectively. If the output displayed is Updated 0 service (s), the old certificate thumbprint is incorrect. You can perform the following steps to retrieve the old certificate thumbprint. Also, use the following procedure to retrieve the old certificate thumbprint, if vCenter Certificate Manager is not used to replace the certificates: NOTE: Run the ls_update_certs.
The thumbprint is a sequence of numbers and alphabets which appears as follows:13:1E:60:93:E4:E6:59:31:55:EB:74:51:67:2A:99:F8:3F:04:83:88 7. Retrieve the new certificate by using the following command:/usr/lib/vmware-vmafd/bin/vecs-cli entry getcert -store MACHINE_SSL_CERT --alias __MACHINE_CERT --output /certificates/new_machine.crt 8. Run the following command to change the directory: cd /usr/lib/vmidentity/tools/scripts/ 9. Perform the following steps: a) Run ls_update_certs.
Table 42. Platform Services Controller example Name Type Value url anyURI https://psc.vmware.local/sts/STSService/ vsphere.local 8. Copy the content of the sslTrust field into a text document and save the document as old_machine.txt. 9. Open the old_machine.txt in a text editor. 10. Append the following at the starting and end of the old_machine.txt file respectively: -----BEGIN CERTIFICATE---------END CERTIFICATE----11. Save old_machine.txt now as old_machine.crt.
NOTE: The thumbprint appears as a sequence of numbers and letters after the equal sign, which is as follows: SHA1 Fingerprint=09:0A:B7:53:7C:D9:D2:35:1B:4D:6D:B8:37:77:E8:2E:48:CD:12:1B Run the ls_update_certs.py with the old thumbprint. Log out and log in to the vCenter Web client after the services are updated successfully. The Dell plug-in launches successfully.
• • • if you select ‘All registered vCenters’ in the Initial Configuration wizard, and there are some vCenters with no hosts. when vCenters where some have inventory or warranty tasks already scheduled. when some vCenters with no inventory or warranty schedule set yet. Resolution: Run the setting of inventory and warranty schedule separately again from the Settings page for the vCenters. Versions Affected: 2.
Resolution: Ensure that the host is compliant by using the host compliance wizard of the OpenManage Integration web client. If it is not compliant, use the Fix Host Compliance to get it compliant. Version Affected: 2.2 and later Why is DNS configuration settings restored to original settings after appliance reboot if appliance IP and DNS settings are overwritten with DHCP values There is a known defect where statically assigned DNS settings are replaced by values from DHCP.
Why does Administration Portal display unreachable update repository location If you provide an unreachable Update Repository path, the “Failed: Error while connecting to the URL…. ” error message is displayed on the top of the Appliance Update view. However, the Update Repository Path is not cleared to the value before update. Resolution: Move out of this page to another page and ensure that the page is refreshed.
Port Protocols Number Port Type Maximum Encryption Level Direction Destination Usage Description 69 TFTP UDP None Out OMIVV appliance to TFTP server TFTP Client Used for firmware update on 11G servers with old firmware. 80 HTTP TCP None Out OMIVV appliance to internet Dell Online Data Access Connectivity to the online (internet) warranty, firmware and latest RPM information.
Port Number Protocol s Port Type Maximum Direction Encryption Level 443 HTTPS TCP 128-bit 8080 HTTP TCP 128-bit Destination Usage Description In OMIVV appliance to ESXi HTTPS server Used to provide information to the management station. This port has to open from ESXi. Out ESXi to OMIVV appliance HTTP server; downloads the OMSA VIB and fixes noncompliant vSphere hosts Helps ESXi to download the OMSA/ driver VIB. Table 45.
Unable to view new iDRAC version details listed on vCenter hosts and clusters page Resolution: After successful completion of a firmware update task in the vSphere web client, refresh the Firmware Update page and verify the firmware versions. If the page displays the old versions, go to the Host Compliance page in OpenManage Integration for VMware vCenter, and check the CSIOR status of that host. If CSIOR is not enabled, enable CSIOR and reboot host.
When I tried to use lockdown mode, it fails When I added a host to the connection profile in lockdown mode, the inventory started, but failed stating that “No Remote Access Controller was found or Inventory is not supported on this host.” If you put the host in lockdown mode or remove a host from lockdown mode, ensure that you wait for 30–minutes before performing the next operation in OMIVV.
2. Enter the VMware vCenter admin credentials. 3. Click Content. 4. Click ExtensionManager. 5. Click UnregisterExtension. 6. Enter the extension key to unregister com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient, and then click Invoke method. 7. In the vSphere web client, turn off OMIVV and delete it. The key to unregister must be for the web client.
6. In the User Configuration page for the selected user, select the check box next to Enable user, and then click Apply. Does OMIVV support VMware vCenter server appliance Yes, OMIVV supports the VMware vCenter Server appliance since v2.1. Firmware level not updated when I have performed firmware update with Apply on Next reboot option and system was rebooted To update firmware, run the inventory on the host after the reboot is completed.
Available virtual appliance version displays wrong information when the available version is lesser than the current version In the OMIVV Admin console, under Appliance Management, Available Virtual Appliance Version displays the modes RPM and OVF as available. NOTE: It is recommended that update repository path is set to the latest version and downgrading the virtual appliance version is not supported.
Auto discovery and handshake prerequisites • • Prior to running auto discovery and handshake, ensure that iDRAC and Lifecycle Controller firmware and BIOS versions meet the minimum recommendations. CSIOR must have run at least once on the system or iDRAC. Hardware configuration failure • • • Before initiating a deployment task, ensure that the system has completed CSIOR and is not in the process of rebooting.
17 Related Documentation In addition to this guide, you can access the other guides available at Dell.com/support. Click Choose from all products, then click Software and Security > Virtualization Solutions. Click OpenManage Integration for VMware vCenter 4.2 to access the following documents: • • • OpenManage Integration for VMware vCenter Version 4.2 Web Client User's Guide OpenManage Integration for VMware vCenter Version 4.2 Release Notes OpenManage Integration for VMware vCenter Version 4.
A System specific attributes iDRAC Table 46.
Attribute Name Display Attribute Name Group Display Name IscsiDev1Con2Gateway Initiator Gateway Connection 1 Settings IscsiDev1Con2Ip Initiator IP Address Connection 1 Settings IscsiDev1Con2Mask Initiator Subnet Mask Connection 1 Settings IscsiDev1Con2TargetIp Target IP Address Connection 1 Settings IscsiDev1Con2TargetName Target Name Connection 1 Settings IscsiInitiatorName ISCSI Initiator Name Network Settings Ndc1PcieLink1 Integrated Network Card 1 PCIe Link1 Integrated Devices Nd
Attribute Name Display Attribute Name Group Display Name IscsiInitiatorIpv4SecDns IPv4 Secondary DNS iSCSI Initiator Parameters IscsiInitiatorIpv6Addr IPv6 Address iSCSI Initiator Parameters IscsiInitiatorIpv6Gateway IPv6 Default Gateway iSCSI Initiator Parameters IscsiInitiatorIpv6PrimDns IPv6 Primary DNS iSCSI Initiator Parameters IscsiInitiatorIpv6SecDns IPv6 Secondary DNS iSCSI Initiator Parameters IscsiInitiatorName iSCSI Name iSCSI Initiator Parameters IscsiInitiatorPrimDns Prima
B Customization attributes Table 51. Customization attributes FQDD Attributes OMIVV Customization BIOS Virtualization Technology Always Enabled iDRAC Collect System Inventory on Restart Always Enabled RAID IncludedPhysicalDiskID If IncludedPhysicalDiskID value is Auto Select then we are removing that value RAID RAIDPDState Removed iDRAC User Admin Password Only iDRAC enabled users will have " Password " link to enter the password.
C Additional information The following Dell technical white papers available at delltechcenter.
D Component vs. baseline version comparison matrix Table 52. Component vs. baseline version comparison matrix Drift Type Hardware Firmware Driver Associated Baseline Target Component Scenario Compliance Status Available Available Hardware component matches with the associated baseline. Compliant Available Available Hardware component not matches with the associated baseline. Non-compliant Not available Available The comparison status is not calculated and ignored.
