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. Copyright © 2017 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 What's new in this release.................................................................................................................................................... 9 OpenManage Integration for VMware vCenter features.................................................................................................
Appliance settings..........................................................................................................................................................35 vCenter settings............................................................................................................................................................ 37 7 Profiles......................................................................................................................................
10 Events, alarms, and health monitoring......................................................................................... 71 About events and alarms for hosts.................................................................................................................................... 71 About events and alarms for chassis................................................................................................................................ 72 Viewing chassis events.....................
Fixing iDRAC license compliance for vSphere hosts............................................................................................... 106 Using OMSA with 11th generation servers..................................................................................................................... 107 Deploying OMSA agent on the ESXi system............................................................................................................ 107 Setting up OMSA trap destination..................
Why is DNS configuration settings restored to original settings after appliance reboot if appliance IP and DNS settings are overwritten with DHCP values.................................................................................................121 Using OMIVV to update the Intel network card with firmware version of 13.5.2 is not supported................... 121 Using OMIVV to update Intel network network card from 14.5 or 15.0 to 16.x fails due to staging requirement from DUP..........................
A System specific attributes......................................................................................................... 131 B Customization attributes...........................................................................................................134 C Additional information...............................................................................................................
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 Service Information Retrieve warranty information for the Dell EMC servers and its associated chassis from Dell’s warranty database and allow for easy online warranty upgrading. Security role and permissions Security role and permissions includes the following functionalities: • • Integrate with standard vCenter authentication, rules, and permissions. Support for iDRAC Lockdown Mode in 14th generation servers. NOTE: From OMIVV 4.
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.
• 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 update privileges, if you are using VMware vCenter 6.5 or upgrading to vCenter 6.
• Update task Registering vCenter server by nonadministrator user with required privileges You can register a vCenter server for the OMIVV appliance by using a nonadministrator user with the required privileges. See Registering a vCenter server for information about registering a vCenter server through a nonadministrator user or as an administrator. Assigning Dell privileges to existing role You can edit an existing role to assign the Dell privileges.
4. Under vCenter User Account, perform the following steps: a) In the vCenter User Name text box, enter the administrator’s user name or a non-administrator user name with the required privileges. b) In the Password text box, enter the password. c) In the Verify Password text box, enter the password again. 5. Click Register.
NOTE: If you have enabled Proactive HA on clusters, ensure that Proactive HA is disabled on the clusters. For disabling Proactive HA, access the Proactive HA Failures and Responses screen of a cluster by selecting Configure > Services > vSphere Availability, and then clicking Edit. To disable Proactive HA: In the Proactive HA Failures and Responses screen, clear the check box against Dell Inc provider.
NOTE: Ensure that you manually update all references to the virtual appliance across its environment such as provisioning server in iDRAC, DRM. Updating virtual appliance repository location and virtual appliance To ensure that all data is protected, perform a backup of the OMIVV database prior to an update of the virtual appliance. See Managing backup and restore. 1. In the APPLIANCE UPDATE section of the APPLIANCE MANAGEMENT page, verify the current and available version.
Updating appliance through backup and restore To update the OMIVV appliance from the OMIVV version x to version y, perform the following steps: 1. Take a backup of the database for the older release. 2. Power off the older OMIVV appliance from vCenter. NOTE: Do not unregister the OMIVV plug-in from vCenter. Unregistering the plug-in from vCenter removes all the alarms registered on vCenter by the OMIVV plug-in and all the customization that is performed on the alarms, such as actions, and so on. 3.
NOTE: It might take around 10 minutes for the virtual appliance clocks to synchronize with the NTP server. Configuring deployment mode Ensure that the following system requirements for the desired deployment modes are met: Table 2.
Uploading HTTPS certificate Ensure that the certificate uses PEM format. You can use the HTTPS certificates for secure communication between the virtual appliance and host systems. To set up this type of secure communication, a CSR must be sent to a certificate authority and then the resulting certificate is uploaded using the Administration Console. There is also a default certificate that is self-signed and can be used for secure communication; this certificate is unique to every installation.
Configuring backup and restore The backup and restore function backs up the OMIVV database to a remote location from which it can be restored later. The profiles, templates, and host information are included in the backup. It is recommended that you schedule automatic backups to guard against data loss. NOTE: NTP Settings are not saved and restored. 1. In the BACKUP AND RESTORE SETTINGS page, click Edit. 2.
About vSphere client console The vSphere client console is found within the vSphere client on a virtual machine. The console works in close association with the Administration Console.
Resetting virtual appliance to factory settings 1. Open the virtual machine console. See Opening vSphere client console. 2. Click Reset Settings. The following message is displayed: All the settings in the appliance will be Reset to Factory Defaults and the appliance will be rebooted. Do you still wish to continue? 3. To reset the appliance, click Yes, or to cancel, click No. If you click yes, the OMIVV appliance is reset to the original factory settings and all other settings and existing data is lost.
3 Managing multiple appliances You can manage and monitor multiple OMIVV appliances that you register with vCenter servers belonging to the same Platform Service Controller (PSC) and the same vCenter version. It is recommended 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.
• • • 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. Viewing OpenManage Integration for VMware vCenter licensing tab When you install OpenManage Integration for VMware vCenter license, the number of supported hosts and vCenter servers are displayed in this tab.
Name Description • • • • 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. For more information, see Downloading the troubleshooting bundle.
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. In OpenManage Integration for VMware vCenter, in the Help and Support, under Product Help, click OpenManage Integration for VMware vCenter Help. The online help content is displayed in the browser window. 2.
• 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. Use the Filter text box to search within your content.
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), 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 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 settings in this page are reset to default each time the configuration wizard is invoked. If you have previously configured a schedule for inventory, ensure that you replicate the previous schedule in this page before completing the wizard functions so that the previous schedule is not overridden by the default settings. 1. In the Initial Configuration Wizard, from the Inventory Schedule dialog box, select Enable Inventory Data Retrieval, if it is not enabled.
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. To restore the default vCenter alarm settings for all managed Dell EMC servers, click Restore Default Alarms. It might take up to a minute before the change takes effect. NOTE: After restoring the appliance, the events and alarms settings are not enabled even if the GUI shows as enabled.
NOTE: Based on the network settings, enable proxy settings if network needs proxy. • Shared Network Folder—you can have a local repository of the firmware in a CIFS-based or NFS-based network share. This repository can either be a dump of Server Update Utility (SUU) that Dell releases periodically or a custom repository created using DRM. This network share should be accessible by OMIVV. NOTE: If you are using CIFS share, the repository passwords cannot exceed 31 characters. 3.
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. Configure events and alarms. See the Configuring events and alarms. Configure the data retrieval schedules for inventory and warranty. See the Viewing data retrieval schedules for inventory and warranty. Enabling OMSA link Install and configure an OMSA web server before enabling the OMSA link.
NOTE: Selecting the option overrides the existing settings for all vCenters. NOTE: The option is not available, if you have already selected All Registered vCenters from the drop-down list on the Settings tab. 7. To save, click Apply. Viewing data retrieval schedules for inventory and warranty 1. In the OpenManage Integration for VMware vCenter, on the Manage > Settings tab, under vCenter Settings, click Data Retrieval Schedule.
7 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 the icon. 2. In the Welcome page, 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.
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.
8 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 Modifying inventory job schedules To ensure that there is up-to-date host information, schedule the inventory job to run at a minimum frequency of once a week. The inventory job consumes minimal resources and does not degrade host performance.
• • • 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. NOTE: The scheduled chassis inventory is run the same time as the scheduled host inventory. 3. Click .
vCenter history • • 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.
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 the icon. 6. In the Success dialog box, click Close. A warranty job is now in queue. NOTE: Chassis warranty is run automatically for all the chassis once the host warranty is run.
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. The BIOS attribute is enabled in the BIOS during initial setup of the server and displays the memory operational mode of the server. Restart your system when you change the memory operational mode value.
Information Description • • Host Actions Launching the Remote Access Console (iDRAC)—launches the Integrated Dell Remote Access Controller (iDRAC) web user interface. Launching OMSA console—launches the OMSA console to access the OpenManage Server Administrator user interface. To blink at various time intervals, set up the physical server to blink at various time intervals. See Blink indicator light. 6. View the Dell EMC Host Health portlet: Table 15.
Hardware: Component Hardware: Power Supply Information • • • Brand—displays the processor brand Version—displays the processor version Cores—displays the number of cores in this processor • Type—displays the type of power supply.
1. In OpenManage Integration for VMware vCenter, in the Navigator pane, click Hosts. 2. In the Objects tab, select the specific host for which you want to view Storage: Physical Disk details. 3. In the Monitor tab, select the Dell EMC Host Information tab. On the Storage subtab, view the following: Table 17.
Information Physical Disks — When you select this option, the Filter drop-down list is displayed. You can filter physical disks based on the following options: • • • • Description • • Write Cache Enabled Protected • Write Cache Disabled Cache Policy—displays if cache policy is enabled • • • • Name—displays the name of the physical disk Device FQDD—displays the device FQDD Capacity—displays the physical disk capacity Disk Status—displays physical disk status.
Information Description • Service Tag—displays the service tag About system event logs in web client System event log (SEL) provides status information for hardware discovered by OMIVV and displays 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), and Unknown (a box with a ?). Time (Server Time) Indicates the time and date when the event occurred.
2. In the Objects tab, select the specific host for which you want to view details. 3. In the Monitor tab, select the Dell EMC Host Information tab. On the Hardware: subtab, view the following information for each of the components: Table 19.
2. Click Datacenters or Clusters. 3. In the Objects tab, select the specific data center or cluster for which you want to view host details. 4. In the Monitor tab, select the Dell EMC Datacenter/Cluster Information > Overview tab, and view the details. NOTE: To display the full list of details, select a specific host from the data grid. Table 20.
Information Description Last Inventory Displays the day, date, and time of the last inventory job Connection Profile Displays the name of the connection profile Remote Access Card Version Displays the remote access card version BIOS Firmware Version Displays the BIOS firmware version Viewing hardware details for data centers and clusters You can view hardware details for a single host on the Dell EMC Datacenter/Cluster Information tab. For information to appear on this page, run an inventory job.
Hardware: Component Information • • Output (Watts)—displays the power in watts Status—displays the status of the power supply.
Table 22. Storage details for a data center and cluster Storage: disks Description Physical Disk • • • • Host—displays the host name Service Tag—displays the service tag of the host Capacity—displays the physical disk capacity Disk Status—displays physical disk status.
Storage: disks Description • • • • • SAS • SATA Stripe Size—displays the stripe size, which provides the amount of space that each stripe consumes on a single disk Default Read Policy—displays the default read policy supported by the controller. The options include: • 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.
Component Information • • • • • • • • • • • • • Warranty Summary NOTE: To view a warranty status, ensure to run a warranty job. See Running a warranty retrieval job. The Warranty Summary page lets you monitor the warranty expiration date. The warranty settings control when server warranty information is retrieved from Dell online by enabling or disabling the warranty schedule, and then setting the Minimum Days Threshold alert.
• To turn off the blink, in the Indicator Light dialog box, click Blink Off, and then click OK. Configuring System Lockdown Mode The System Lockdown Mode setting is available in iDRAC for 14th generation of the PowerEdge servers. The setting when turned on locks the system configuration including firmware updates. This setting is intended to protect the system from unintentional changes.
9 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 non-clustered 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 24.
• • 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. 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 wizard is displayed and you can view the Welcome page.
• • To avoid a service interruption, select Apply updates on next reboot. To apply the update and reboot even if the host is not in maintenance mode, select Apply Updates, and Force Reboot without entering maintenance mode. It not recommended to use this method. 8. Click Next. The Summary page is displayed that provides details about all components for firmware update. 9. Click Finish.
You can filter comma-separated values from the content of the various components of the data grid by using the Filter field. You can also drag and drop columns within the component data grid. If you want to export from the wizard, use the Export to CSV button. By selecting the Allow Firmware downgrade check box, you can select a firmware version earlier than the current version. 8. In the FW Update Information page, view all the firmware update details. 9. Click Next.
The selected jobs are then cleared from the queue.
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.
Table 26.
Event name Description Severity Recommended 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 has been lost warning An AC power cord has lost its power, but there is sufficient redundancy to classify this as a warning Warning No action Dell-An AC power cord has lost its power
Event name Description Severity Recommended action 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 temperature sensor on the backplane board, system board, or drive carrier in the specified syste
Event name Description Severity Recommended 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 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 Error Put t
Event name Description Severity Recommended action 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-Software change update warning Software change update warning Warning No action Dell-Chassis Management Controller audit warning Chassis Management Controller Warning audit warning No action Dell-Chassis Management Controller audi
Event name Description Severity Recommended action The power supplies are redundant None Info No action Power supply redundancy is lost The current power operational Critical mode is non-redundant because 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 Check the event log for power supply failures.
Event name Description Severity Recommended action Info No action previously operating in a power redundant mode The power supplies are redundant None 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. If unintended, review system configuration and power consumption and install power supplies accordingly.
Table 28.
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.
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. See Enabling Proactive HA on a cluster.
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. Based on the health update notification from OMIVV, the vCenter server takes a manual or automatic action that you have selected for Remediation.
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. In the Summary tab, scroll down to the Dell EMC Host Information. 4. In the Dell EMC Host Information section, click OMSA Console.
11 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.
12 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.
• • • • • 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. See OpenManage Integration for VMware vCenter Compatibility Matrix for the list of the PowerEdge servers required for deployment.
• • • Provisioning service location—ensure that iDRAC knows the IP address or host name of the provisioning service server. See Provisioning service location. Account access disabled—ensure that you enable the administrative account access to iDRAC and if there are any iDRAC accounts with administrator privileges, first disable them from within the iDRAC web console. Once auto discovery completes successfully, the administrative iDRAC account is re-enabled.
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. The Authentication Required dialog box is displayed. 6. In the Authentication Required dialog box, view the name that is displayed, and press Enter. 7. Enter Password. 8. Press Enter.
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.
Configuring hardware profile To configure server hardware settings, create a hardware profile. A hardware profile is a configuration template that you can apply to newly discovered infrastructure components and it requires the following information: Table 35. Requirements for creating hardware profile Requirements Description Boot order The boot order is the boot device sequence and hard drive sequence that you can edit only if the boot mode is set to BIOS.
Creating or customizing hardware profile 1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates > Hardware Profiles. 2. Click the icon. 3. In the Hardware Profile Wizard, click Next on the Welcome page and do the following: • • In the Profile Name text box, enter the profile name. In the Description text box, type a description. The description is optional. 4. Click Next. The Reference Server dialog box is displayed.
1. In the Boot Mode list, select BIOS or UEFI. 2. In the View list, under Boot Device Sequence, to change the displayed boot device sequence, select the device, and click either Move Up or Move Down. 3. Select Enable Boot Sequence Retry so that the server automatically retries the boot sequence. 4. To apply the changes, click OK, or to cancel the changes, click Cancel. b) To display the hard drive sequence options, Expand Hard Drive Sequence, and click Edit. Update the following: 1.
• • Viewing or editing hardware profile Deleting hardware profile Viewing or editing hardware profile 1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates > Hardware Profiles. The hardware profiles are displayed. 2. To edit a profile, select a profile, and click . 3. In the Hardware Profile wizard, to configure with different values, click Edit. 4. To apply changes, click Save, or to cancel changes, click Cancel.
• • Viewing or editing hypervisor profiles Deleting hypervisor profiles Viewing or editing hypervisor profiles 1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates > Hypervisor Profiles. The hypervisor profiles are displayed. 2. Select a profile, and click the icon. 3. In the Hypervisor Profile dialog box, provide updated values. 4. To apply changes, click Save, or to cancel changes, click Cancel.
2. In the Deployment Template page, select a template, and click the icon. 3. To confirm the template deletion, click Delete on the message box, or to cancel, click Cancel. About deployment wizard The deployment wizard describes the deployment process, which is as follows: • Selecting compliant bare-metal servers.
Figure 2. VLAN network. In this example network, the OMIVV appliance is on VLAN 5, while the vCenter and the VMkernal of the ESXi hosts being deployed are on VLAN 10. Since OMIVV does not support multi-VLAN homing, VLAN 5 must route to VLAN 10 for all systems to communicate to each other correctly. If routing is not enabled between these VLANs, the deployment fails.
• Internal Dual SD Module—deploys a hypervisor on the IDSDM. NOTE: If an IDSDM is available on at least one of the selected servers, the Internal Dual SD Module option is enabled. If not, only the Hard Disk option is available.
• Enter the time. 2. To start the job immediately, select Run Deployment Job Now. To go to the job queue after the deployment job starts, select Go to the Job Queue after the job is submitted. 11. Click Finish. After the deployment wizard tasks are complete, you can manage deployment jobs by using Job Queue. . Managing deployment jobs using Job Queue 1. In the OpenManage Integration for VMware vCenter, on the Monitor > Job Queue tab, click Deployment Jobs.
Table 37.
13 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 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. To fix noncomplaint hosts, click Fix non-compliant vSphere Hosts. The Fix Non-compliant vSphere Hosts wizard is launched.
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. Using OMSA with 11th generation servers To manage the PowerEdge 11th generation servers, OMIVV requires OMSA to be running on them. For an 11th generation host that is deployed though OMIVV, OMSA is installed automatically.
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. Reporting and fixing compliance for bare-metal servers A bare-metal server is noncompliant when: • • • • • It is not a supported server. It does not have a supported iDRAC license (iDRAC Express is the minimum requirement). It does not have supported versions of iDRAC, BIOS, or LC.
1. In OpenManage Integration for VMware vCenter, select the Manage > Deployment tab. In the Bare Metal Servers page, view the list of noncompliant servers that is displayed in a table. 2. Select a bare-metal server where iDRAC License Status is Non-compliant or Unknown. 3. If license is out of date, click the Purchase/Renew iDRAC License link. 4. Log in to the Dell License Management page and update or purchase a new iDRAC license. Use the information in this page to identify and update your iDRAC. 5.
14 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 • • • • • • 112 Configure HW Configuration Profile Configure Hypervisor Deployment Profile Configure Connection Profile Assign identity Deploy Dell.Configuration.
15 Troubleshooting 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. Why 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.
1. Open the iDRAC virtual console. 2. Press F2 and navigate to Troubleshooting Options. 3. In Troubleshooting Options, navigate to Restart Management Agents. 4. To restart the management agents, press F11. A valid iDRAC IP is now available. NOTE: Host inventory can also fail when OMIVV fails to enable WBEM services on hosts running ESXi 6.5. See Creating connection profile for more information about WBEM service.
Updating the ssl Anchors in Windows vSphere 6.0 1. Download the lstoolutil.py.zip file from http://kb.vmware.com/selfservice/search.do? cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2121701. 2. Copy the lstoolutil.py file to the %VMWARE_CIS_HOME%"\VMware Identity Services\lstool\scripts\ folder. NOTE: Do not replace the lstoolutil.py file if you are using vSphere 6.0 Update 1.
2. Run the following command to enable accessing the Bash shell: shell.set --enabled true 3. Type shell and press Enter. 4. Create folders or certificates by using the following command: mkdir /certificates 5. Retrieve the old certificate by using the following command: /usr/lib/vmware-vmafd/bin/vecs-cli entry getcert -store BACKUP_STORE --alias bkp___MACHINE_CERT --output /certificates/old_machine.crt 6.
Table 41. vCenter server example Name Type Value url anyURI https://vcenter.vmware.local:443/sdk • For Platform Services Controller 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.
1. Move or upload the old_machine.crt certificate to PSC in the C:\certificates\old_machine.crt location that is created in step 1 of retrieving the old certificate procedure. You can use Windows Secure Copy (WinSCP) or another SCP client to move or upload the certificate. 2. Connect to External Platform Services Controller through remote desktop connection. 3. Open command prompt in administrative mode. 4. Run the following command to extract the thumbprint: "%VMWARE_OPENSSL_BIN%" x509 -in c:\certificates
Why “Task cannot be scheduled for the time in the past” error in inventory schedule/warranty schedule page of Initial Configuration Wizard appear? In web client, the error “Task cannot be scheduled for the time in the past” appears: • • • 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.
Even if repository has bundles for selected 11G system, why is firmware update displaying that there are no bundles for firmware update? When I add a host to the connection profile in lockdown mode, the inventory kicks 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.
times-out for hours, although job status in LC prompts as ‘FAILED’? When the invalid DUP is picked for firmware update, the status of the task in the vCenter console window remains ‘In Progress’ but the message is changed to the reason of failure. This is a known VMware defect and will be fixed in the future releases of VMware vCenter. Resolution: The task must be canceled manually.
Does OMIVV support vCenter in linked mode? Yes, OMIVV supports up to 10 vCenter servers either in a linked mode or not in a linked mode. For more information about how OMIVV works in linked mode, see the white paper, OpenManage Integration for VMware vCenter: Working in Linked Mode at www.dell.com.
Port number Protocols Port type Max.
7. Select the Broadcast a Message check box, and select Apply Changes. 8. To cause the temperature warning event, from the tree view on the left, select Main System Chassis. 9. Select Temperatures under Main System Chassis. 10. Select the System Board Ambient Temp link, and select the Set to Values option button. 11. Set the Maximum Warning Threshold to a value preceding the current listed reading. For example, if the current reading is 27, set the threshold to 25. 12.
4. Ensure that at least one Virtual Disk is seen by the system. ESXi also installs to an internal SD card. Why hypervisor deployments failing on Dell PowerEdge R210 II machines? A timeout issue on the Dell PowerEdge R210 II systems produces a hypervisor deployment failure error due to the failure of the BIOS to boot from the attached ISO. Resolution: Manually install hypervisor on the machine.
In vSphere web client, clicking Dell server management portlet or Dell icon returns 404 error Check if the OMIVV appliance is running; if not, then restart it from the vSphere web client. Wait for a few minutes for the virtual appliance web service to start, and then refresh the page. If the error continues, try to ping the appliance by using the IP address or fully qualified domain name from a command line. If the ping does not resolve, review your network settings to ensure that they are correct.
Why is host still displayed under chassis even after removing host from vCenter tree? The hosts under the chassis are identified as part of the chassis inventory. After a successful chassis inventory, the host list under the chassis is updated. Therefore, even if the host is removed from the vCenter tree, the host is displayed under the chassis until the next chassis inventory is run.
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.
16 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.1 to access the following documents: • • • OpenManage Integration for VMware vCenter Version 4.1 Web Client User's Guide OpenManage Integration for VMware vCenter Version 4.1 Release Notes OpenManage Integration for VMware vCenter Version 4.
A System specific attributes iDRAC Table 45.
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 50. 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.
