OpenManage Integration for VMware vCenter Version 4.3 Web Client User's Guide October 2018 Rev.
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. © 2018 - 2019 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.
Configuring events and alarms ................................................................................................................................... 35 Configuration tasks through settings tab.........................................................................................................................36 Appliance settings..........................................................................................................................................................
Viewing overview of data centers and clusters.........................................................................................................68 Viewing hardware details for data centers and clusters...........................................................................................70 Viewing storage details for data center and clusters.................................................................................................
Creating system profile................................................................................................................................................ 112 Managing System profiles................................................................................................................................................. 114 Configuring hardware profile..........................................................................................................................................
OMIVV does not display all the relevant logs when trying to filter a severity category..................................... 138 How do I resolve error code 2000000 caused by VMware Certificate Authority-VMCA..................................138 In Administration Console, Update Repository Path is not set to default path after I reset appliance to factory settings...................................................................................................................................................
Firmware level not updated when I have performed firmware update with Apply on Next reboot option and system was rebooted.......................................................................................................................................150 Host still displayed under chassis even after removing host from vCenter tree.................................................150 In Administration Console, Update Repository Path is not set to default path after I reset appliance to factory settings..
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.
Table 1. OMIVV features(continued) Features Description • • • Monitor and send alerts The monitoring and alerting includes the following functionalities: • • • Firmware updates Support for an MX chassis relationship in the Multi-Chassis Management (MCM) configuration. Fabric information for an MX chassis MCM configuration. QuickSync hardware information for an MX chassis. Detect key hardware faults and perform virtualization-aware actions.
2 About Administration Console You can achieve the administration of OpenManage Integration for VMware vCenter and its virtual environment 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.
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. After registering the vCenter server, OMIVV is registered as a vCenter plug-in, and “Dell EMC OpenManage Integration” icon is visible in the vSphere web client from which you can access the OMIVV functionalities.
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.
▪ ▪ ▪ ▪ ▪ ▪ Advanced settings Connection Maintenance Network configuration Query patch Security profile and firewall NOTE: Assign the following privileges, if you are using VMware vCenter 6.5 or upgrading to vCenter 6.5 or later: ▪ Host.
The changes to permissions and roles take effect immediately. The user with necessary privileges can now perform the OpenManage Integration for VMware vCenter operations. NOTE: For all vCenter operations, OMIVV uses the privileges of the registered user and not the privileges of the loggedin user. NOTE: If specific pages of OMIVV are accessed with no Dell privileges assigned to the logged-in user, the 2000000 error is displayed.
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 on page 20. 1. In the APPLIANCE UPDATE section of the APPLIANCE MANAGEMENT page, verify the current and available version.
• 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. You can view the installation status in the Recent Tasks. NOTE: After the RPM upgrade is complete, you can view the login screen in the OMIVV console. Open a browser, provide the https:\\ link, and navigate to the APPLIANCE
the old data exists, such as: com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClientX.0.0.XXX. ○ Manually delete the folder corresponding to the earlier OMIVV version. Downloading the troubleshooting bundle 1. In the APPLIANCE MANAGEMENT page, click Generate Troubleshooting Bundle. 2. Click the Download Troubleshooting Bundle link. 3. Click Close. Setting up HTTP proxy 1. In the APPLIANCE MANAGEMENT page, scroll down to HTTP PROXY SETTINGS, and then click Edit. 2.
• If the verification is successful, the OMIVV appliance restarts and the deployment mode are changed after you confirm the change. • If the required deployment mode is already set, a message is displayed. 5. If the deployment mode is changed, confirm the changes, and then proceed with rebooting the OMIVV appliance to allow the deployment mode to be updated. NOTE: During the OMIVV appliance boot up, the allocated system resource is verified against the set deployment mode.
3. In the left pane, click ALERT MANAGEMENT. To enter new vCenter alert settings, click Edit. 4. Enter numeric values for the following fields: • Maximum number of alerts • Number of days to retain alerts • Timeout for duplicate alerts (seconds) 5. To save your settings, click Apply, or to cancel, click Cancel. Managing backup and restore Managing backup and restore is accomplished from the Administrative Console.
3. Enter values for Backup Location, Username, Password, and Password for Encryption. The encryption password can contain alphanumeric characters and special characters, such as, “!, @, #, $, %, *”. There is no length restriction. 4. Click Backup. Restoring OMIVV database from backup The restore operation causes the virtual appliance to reboot after restoration is complete. 1. 2. 3. 4. Open the BACKUP AND RESTORE SETTINGS page. See the Managing backup, and restore.
5. Retype the new password in Please Confirm Admin Password, and press Enter. 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.
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 of the 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 OEM hosts 1. On the OpenManage Integration for VMware vCenter page, in the left pane, click OEM Hosts. The OEM Hosts page is displayed. 2.
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. You can also view the version of the OpenManage Integration for VMware vCenter at the top of the page. The page under licensing displays the Buy License link.
Table 5. Information in the help and support tab(continued) Name Description 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. Dell EMC Recommends Provides a link to Dell EMC Repository Manager (DRM).
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. Use the left-pane table of contents or search to find the topic of your choice. 3.
• • • 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. At the bottom of the page grid, the following information is displayed: Table 6.
5 OpenManage Integration for VMware vCenter licensing The OpenManage Integration for VMware vCenter has two types of licenses: • • Evaluation license—when the OMIVV 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. This 90-day trial version is the default license that is supplied when shipped.
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.
Select a vCenter that is not configured yet or if you have added a vCenter to your environment. The vCenter selection page allows you to select one or more vCenters to configure settings. 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.
a. In Active Directory User Name, type the username. Type the username in one of these formats: domain\username or username@domain. The username is limited to 256 characters. NOTE: For host username and domain restrictions, see the following: Host username requirements: ○ Between 1 and 64 characters long ○ No nonprintable characters Host domain requirements: ○ Between 1 and 64 characters long ○ First character must be alphabetical. ○ Cannot contain a space. b.
noncomplaint hosts that require SNMP trap destination to be reconfigured and/or WBEM services to be enabled, see Reporting and fixing compliance for vSphere hosts on page 126. Scheduling inventory jobs You can configure inventory schedule by using the configuration wizard or OpenManage Integration under the OpenManage Integration > Manage > Settings tab. NOTE: To ensure that OMIVV continues to display updated information, it is recommended that you schedule a periodic inventory job.
NOTE: OMIVV supports SNMP v1 and v2 alerts for 12th generation hosts and later and supports only SNMP v1 alerts for hosts earlier than 12th generation. 1.
a. If you want to enable this setting, select the Enable warranty expiration notification for hosts. Selecting the check box enables warranty expiration notification. b. Under Minimum Days Threshold Alert, do the following: i. In the Warning drop-down list, select the number of days before you want to be warned of the warranty expiration. ii. In the Critical drop-down list, select the number of days before you want to be warned of the warranty expiration. 5. Click Apply.
Creating catalog in DRM using OMIVV This section describes the process to create a catalog in DRM version 3.0 and later. 1. On the Home page, click Add New Repository. The Add Repository window is displayed. 2. In the Add Repository window, do the following: a. Enter Repository Name and Description. b. From the Base Catalog drop-down menu, select a catalog. c. From the Integration Type drop-down menu, select OpenManage Integration for VMware vCenter. 3.
• • • 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.
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. On clicking, data retrieval schedule expands to expose the edit options for inventory and warranty. icon against Inventory Retrieval or Warranty Retrieval. 2.
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.
Ensure that Synchronize with repository Location option is selected if you want to refresh your Repository Profile of OMIVV from the latest driver or firmware catalog. 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.
NOTE: At the creation of the cluster profile, a current snapshot of the associated Firmware and Driver Repository is created for the baseline. If the repositories change, the cluster profile would need to be updated again to reflect the changes. Otherwise, any updates performed on the repositories will not be updated to original cluster profile snapshot. 1. On the OpenManage Integration for VMware vCenter page, click Manage > Baseline, expand Baseline Info, and then click Cluster Profile. 2. Click . 3.
2. Select a cluster profile that you want to delete, click . 3. To remove the profile, in the confirmation dialog box, click Yes, or to cancel, click No. If the cluster profile is deleted, the corresponding Drift Detection job is also deleted.
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 servers. Associate each OMIVV-managed 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.
Creating connection profile You can associate multiple hosts to a single connection profile. To create a connection profile, perform the following steps: NOTE: The vCenter hosts that are listed during this procedure are authenticated 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. NOTE: An MX chassis hosts can be managed using a single unified chassis management IP.
• To configure host credentials without Active Directory, perform the following actions: ○ In the User Name text box, the user name is root. The root user name is the default user name, and you cannot change it. NOTE: If Active Directory is set, you can choose any Active Directory user name and not root. ○ In the Password text box, type the password. The password is limited to 127 characters. ○ In the Verify Password text box, type the password again.
NOTE: Ensure that you do not update a connection profile when an inventory, a warranty, or a deployment job is running. NOTE: Ensure that you do not move a host that is associated with a connection profile to another connection profile or remove a host from a connection profile when an inventory, a warranty, or a deployment job is running. 1. In OpenManage Integration for VMware vCenter, click Manage. 2. Click Profiles, and then click Credential Profiles. 3.
8. In the Select Hosts dialog box, select hosts for this connection profile. 9. Click OK. The Associated Host dialog box lets you test the iDRAC and host credentials on the selected servers. 10. Perform one of the following steps: • To begin the test, select the hosts and then click . The other options are inactive. NOTE: : Do not add an MX server having iDRAC IPv4 disabled to a connection profile. These servers can be managed using a chassis profile.
Viewing chassis profiles Ensure that you create a chassis profile or a chassis profile exists before viewing. After one or more chassis profiles are created, you can view the chassis and associated hosts on the chassis profiles page. 1. In OpenManage Integration for VMware vCenter, click Manage. 2. Click Profiles, and then click Credential Profiles. 3. Expand Credential Profiles, and click the Chassis Profiles tab. The chassis profiles are displayed. 4.
Under the Credentials section: a. In the User Name text box, type the user name with administrative rights, which is typically used to log in to the Chassis Management Controller. b. In the Password text box, type the password for the corresponding user name. c. In the Verify Password text box, enter the same password you have entered in the Password text box. The passwords must match. NOTE: The credentials can be a local or the Active Directory credentials.
7. Click to associate the chassis with the chassis profile. NOTE: Chassis are discovered and available to be associated with the chassis profile only after the successful inventory run of any modular host present under that chassis. 8. To select either an individual chassis or multiple chassis, select the corresponding check boxes next to the IP/Host Name column.
4. In the Test Chassis Profile dialog box, select the chassis you want to test and then click . 5. To abort all selected tests and cancel the testing, click Abort All Tests. In the Abort Tests dialog box, click OK. 6. To exit, click Cancel.
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.
Table 10. Chassis information(continued) Chassis inventory Status Displays the status of the chassis. 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.
• NOTE: When the hosts are managed using the Chassis Profile, the firmware inventory data will show few extra components such as Lifecycle Controller and Software RAID. Power Monitoring NOTE: Inventory job for hosts exceeding the license limit will be skipped and marked as Failed.
Table 11. vCenter, hosts history information vCenter history vCenters Displays lists of vCenters Hosts Passed Displays the number of vCenter hosts that passed Last Warranty Displays the date and time when the last warranty job was run Next Warranty Displays the date and time when the next warranty job will run Hosts history Host Displays the host address Status Displays the status.
4. To view your corresponding warranty job history information, select either Hosts Warranty or Chassis Warranty. 5. Click . 6. In the Warranty Data Retrieval dialog box, do the following: a. Under Warranty Data, select the Enable Warranty Data Retrieval check box. b. Under Warranty Data Retrieval Schedule, select the days of the week for the warranty job. c. In the Warranty Data Retrieval Time text box, type the local time for this job.
Table 13. Host summary information Information Description Alternating system Displays alerts for OpenManage Integration for VMware vCenter in a yellow box under the status area and preceding the portlets. Notification area Displays the Dell products integration information in the right side-panel area, where you can find information about: • • • Recent Tasks Work In Progress Alarms The Dell alarm information is displayed in the notification area portlet. 5.
Table 14.
2. In the Host tab, select the specific host for which you want to view Hardware: details. 3. In the Monitor tab, select the OMIVV Host Information tab. NOTE: If System Lockdown Mode is turned on for 14th generation host, a yellow band is displayed at the top with a closed lock icon . On the Hardware: tab, view the following information for each of the components. Table 16.
Table 16.
Viewing storage details for the view option The storage options on the Host Storage page depend on what you select from the View drop-down list. Select either of the mentioned options from the View drop-down list and view the following: Table 18. Storage details for a single host Information Description Virtual drives • • • • • • • • • • • • Physical Disks—When you select this option, the Filter drop-down list is displayed.
Table 18. Storage details for a single host(continued) Information Description • • • • • • • • • • • • • • Controllers • • • • • Enclosures ○ UNKNOWN ○ FOREIGN ○ UNSUPPORTED Configured—displays whether the disk is configured Hot Spare Type(Not applicable for PCIe)—shows the hot spare type. The options include: ○ No—there is no hot spare ○ Global—an unused backup disk that is part of the disk group ○ Dedicated—an unused backup disk that is assigned to a single virtual drive.
Clear Log Click this option to clear all SEL. NOTE: Clear SEL feature is not supported on the host managed using chassis. The severity levels are defined as: Info OMIVV operation completed successfully. Warning OMIVV operation that is partially failed, and was partially successful. Error OMIVV operation failed. You can save the log as an external .CSV file. See Displaying system event logs for an individual host.
Table 19. Single host information(continued) Component Information • Installation Date—displays the installation date NOTE: When the hosts are managed using the Chassis Profile, the firmware inventory data will show few extra components such as Life Cycle Controller and Software RAID. Power Monitoring NOTE: The host time, as used here, means the local time where the host is located. NOTE: Power monitoring information will not be available for hosts with cabled PSU or for modular servers.
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. Overview of data centers and clusters Information Description Datacenter/Cluster Information Displays the following: • • • System Lockdown Mode Displays the status of the iDRAC Lockdown Mode.
Table 20. Overview of data centers and clusters(continued) 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.
Table 21. Hardware information for data centers and clusters(continued) Hardware: Component Information • • • 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.
3. In the Objects tab, select the specific data center or cluster. 4. In the Monitor tab, select the Dell EMC Datacenter/Cluster Information tab and navigate to Storage > Physical Disk/Virtual Disk. To display the full list of details, select a specific host from the data grid. Table 22.
Table 22. Storage details for a data center and cluster(continued) Storage: disks Description • • • • • • • • • Last Inventory—displays the day, date and time the inventory was last run Controller ID—displays the controller ID Device ID—displays the device ID Media Type—displays either SSD or HDD Bus Protocol—displays the technology that the physical disks included in the virtual disk are using.
Table 23. Single host information(continued) Component Power Monitoring NOTE: To display the full list of details, select a specific host from the data grid.
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. 2. 3. 4. 5. In OpenManage Integration for VMware vCenter, in the Navigator area, under Inventory Lists, click Hosts. In the Object tab, double-click the host you want. In the Summary tab, scroll down to the Dell EMC Server Management portlet. Under Host Actions, select Blink Indicator Light.
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.
Table 24. Event posting level(continued) Event Description Post only critical and warning events Posts only events with either a Critical or Warning criticality into related vCenters. Post only virtualization-related critical, and warning events Post virtualization-related events received from hosts into related vCenters. 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.
Virtualization-related events The following table contains the virtualization-related critical and warning events, and includes event name, description, severity level, and recommended action. The vitalization-related events are displayed in the following format: Dell-Message ID:, Message:.
Table 25.
Table 25. Virtualization events(continued) Event name Description Dell-Thermal shutdown protection has been initiated This message is generated Error when a system is configured for thermal shutdown due to an error event. If a temperature sensor reading exceeds the error threshold for which the system is configured, the operating system shuts down and the system powers off.
Table 25.
Table 25.
Table 25. Virtualization events(continued) Event name Description Severity Recommended action NOTE: For all Proactive HA enabled hosts that are part of a cluster, the following virtualization events are mapped to the Proactive HA events; except events, "The fans are not redundant" and "The power supplies are not redundant" are not mapped.
Table 25.
Table 25. Virtualization events(continued) Event name Description Severity Recommended action The fans are not redundant.
Table 27.
NOTE: Proactive HA is available only on the platforms that support redundancy on power, fan, and IDSDM. NOTE: Proactive HA feature is not supported for PSUs for which redundancy cannot be configured (for example, cabled PSUs). Proactive HA is a vCenter (vCenter 6.5 and later) feature that works with OMIVV. When you enable Proactive HA, the feature safeguards your workloads by proactively taking measures based on degradation of redundancy health of supported components in a host.
4. 5. 6. 7. 8. Verify that chassis inventory is completed successfully. See Viewing chassis inventory. Launch CMC or Management Module and verify that the Trap destination for chassis is set as the OMIVV appliance IP address. In Chassis Management Controller, go to Setup > General. In the General Chassis Settings page, select Enable Enhanced Chassis Logging and Events. Enable Proactive HA on a cluster. See Enabling Proactive HA on a cluster.
3. To change severity of a host or its component, in the Override Severity column, select the desired status from the drop-down list. This policy applies to all the Proactive HA hosts across all vCenter servers that are registered with OMIVV. 4. Repeat step 3 for all the events that must be customized. 5. Perform any one of the following actions: a. To save the customization, click Apply Changes. b. To revert the overridden severity after selecting a severity level, click Cancel. c.
11 About firmware updates The OMIVV appliance enables 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 are the two methods by which you can perform firmware update: • Single DUP—performs firmware update for iDRAC, BIOS, or LC by pointing directly to the DUP location (either CIFS or NFS share).
• For the non-vSAN cluster, for more information about running firmware update for the non-vSAN cluster, see Running firmware update wizard for non-vSAN clusters on page 94. Running firmware update wizard for non-vSAN host NOTE: During the firmware update process, ensure that you do not delete the following: • The host from vCenter for which the firmware update job is in progress. • The connection profile of the host for which the firmware update job is in progress.
NOTE: If you select components that require a reboot, ensure that the vCenter environment is configured in such a way that the workloads can be migrated. 6. On the Schedule Firmware Update page, do the following: a. Specify job name in the Firmware Update Job Name field and description in the Firmware Update Description field, which is optional. The firmware update job name is mandatory and ensures that you do not use a name that is already in use.
1. To access the firmware update wizard, in OpenManage Integration, click Hosts and perform either of the following actions: • • • • 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 > OMIVV Host Information > Run Firmware Wizard.
NOTE: The minimum Maintenance Mode timeout value is 60 minutes. NOTE: The maximum Maintenance Mode timeout value is 1440 minutes. d. 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, Move powered down and suspended virtual machines to other hosts in the cluster option is selected.
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. The Select Update Source page is displayed where you can select the bundles. The repository location is also displayed. 5. On the Select Update Source page, from the Select an Update Bundle drop-down, select an appropriate update bundle for your systems. Click Next. NOTE: OMIVV supports 32–bit and 64–bit bundles for firmware update.
Running firmware update wizard for vSAN clusters Ensure that the following condition is met before running the firmware update wizard: • • • • • • • • • DRS is enabled. Hosts are not in maintenance mode. vSAN data objects are healthy. If the vSAN objects health is not healthy for the first host, the firmware update job fails. For other hosts, it waits for 60 minutes for the vSAN object heath to become healthy again. Selected drivers and firmware are compliant as per the VMware vSAN guidelines.
You can also drag columns within the component data grid. If you want to export from the wizard, click 8. On the FW Update Information page, view all the firmware update details, and click Next. The Schedule Firmware Update page is displayed. 9. On the Schedule Firmware Update page, do the following: . a. Enter the firmware update job name in the Firmware Update Job Name field. NOTE: The firmware update job name is mandatory and does not use a name that is already in use.
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.
Chassis and host management using the Unified Chassis Management IP If an iDRAC IPv4 is disabled for a host that is managed using connection profile, the host inventory fails and chassis is not discovered. In such cases, the chassis must be added manually and should be associated to a chassis profile to manage the chassis and its associated hosts.
3. In the left pane, select the corresponding chassis IP. 4. Click the Summary tab. The following information about the selected chassis is displayed: • • • • • Name Model Firmware version Service tag IP Address/FQDN NOTE: If you do not run the inventory job for the chassis, you can see only Service Tag and CMC or Management Module IP address. 5. View the health status of the devices associated with the selected chassis. The main pane displays the overall health of a chassis.
Table 28. Hardware inventory information(continued) Hardware inventory: Component Navigation through OMIVV Information NOTE: In an MX chassis, the presence of a fan is indicated as 'Yes' even when a fan is removed from the chassis. However, the fan health is displayed as Critical on the Summary page with active error. Power supplies Use either of the following methods: Information about power supplies: • • • • • • • Temperature sensors In the Overview tab, click Power Supplies.
Table 28. Hardware inventory information(continued) Hardware inventory: Component Navigation through OMIVV • Information In the Monitor tab, expand the • Compute Count left pane, click Hardware • Uplink Count Inventory, and then click Fabric.
1. 2. 3. 4. In the Home page, click vCenter. In the left pane, under OpenManage Integration, click Dell EMC Chassis. In the left pane, select the corresponding chassis IP. Click the Monitor tab. To see the information about warranty, storage, firmware, and management controller, navigate through OMIVV. Table 29. Firmware details Hardware configuration Navigation through OMIVV Information Firmware a.
Table 30. Management controller details Hardware configuration Navigation through OMIVV Information NOTE: Few attributes of network related information of a member chassis which is part of the MCM configuration is not displayed in the Management Controller section. Table 31. Storage information Hardware configuration Navigation through OMIVV Information Storage In the Monitor tab, click Storage.
Table 32. Warranty information Hardware configuration Navigation through OMIVV Information Warranty In the Monitor tab, click Warranty. Information about warranty: • • • • • • • Provider Description Status Start Date End Date Days Left Last Updated NOTE: To view warranty status, ensure that you run a warranty job. See Running a warranty retrieval job. Viewing associated host for chassis You can view information about the associated host for the selected chassis on the Manage tab. 1. 2. 3. 4.
• • • • Last Inventory Available Slots Profile Name Role NOTE: Related Chassis information is not applicable for standalone chassis.
13 Deploying hypervisor OMIVV enables 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 servers using VMware vCenter without using PXE.
• • • • • • 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 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 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.
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. 9.
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.
Profile". By supporting Server Configuration Profile, OMIVV allows you to export the entire configuration of a 14th generation Dell EMC server and import to target servers. While applying a System profile of a modular server installed in an FX2 chassis to another similar server installed on another FX2 chassis, the slot numbers of both the servers must be the same.
• • In the Profile Name text box, enter the profile name. In the Profile Description text box, type a description. The description value is optional. 4. Click Next. The Reference Server dialog box is displayed. You can either select 14th generation reference servers from the dialog box directly or through the browse button in the profile source page. 5.
9. In the Summary page, click Finish. The profile is automatically saved, and is displayed in the System Profiles window. All system-specific attributes are not supported in the current release. For more information about system-specific attributes, see System specific attributes on page 157. Few attributes of System Profile are overridden for the OMIVV to be functional. For more information about customized attributes, see Customization attributes on page 161.
There are two methods for enabling CSIOR: Table 35. Methods for enabling CSIOR Method Description Locally Uses an individual host by using the Dell Lifecycle Controller United Server Configurator (USC) user interface. Remotely Uses a WS-Man script. For more information on scripting this functionality, see Dell TechCenter and DCIM Lifecycle Controller Management Profile. To enable CSIOR locally on a reference server: 1. Power on the system, and during POST, press F2 to start USC. 2.
• • • • • • • • • • • Memory Settings Processor Settings SATA Settings Boot Settings One-Time Boot Integrated Devices Slot Disablement Serial Communication System Profile Settings System Security Miscellaneous Settings After all updates are made for a category, to save the changes, click Next, or to cancel the changes, click Cancel. NOTE: For detailed BIOS information, including setting options and explanations, see the Hardware Owner’s Manual for the selected server. 9.
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. To select a reference server that is compliant, managed by vCenter, and successfully inventoried by the Dell EMC OpenManage plugin, in the Reference Server page, click Browse.
• • 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. The reference ISO location can be in one of the following formats: • • NFS format: host:/share/hypervisor.iso CIFS format: \\host\share\hypervisor.
6. Select a Hypervisor Profile from the drop-down menu. 7. To apply profile selections and save changes, click Save. To cancel, click Cancel. Managing deployment templates From the OpenManage Integration, there are several management actions you can perform on existing deployment templates, including: • • Viewing or editing deployment templates Deleting deployment templates Viewing or editing deployment templates 1.
Ensure that the VLAN provided during deployment communicates with both the virtual appliance and the vCenter server. The deployment of a hypervisor to a VLAN that cannot communicate to one or both of these destinations causes the deployment to fail. If you have selected multiple bare-metal servers in a single deployment job and want to apply the same VLAN ID to all servers, in the server identification portion of the Deployment Wizard, use Apply settings to all selected servers.
• • If you select a hardware profile only or system profile only deployment template that only configures server hardware, go to step 10. If you select hypervisor profile deployment template that deploys a hypervisor, continue from step 6 (b) onwards. NOTE: If you select hardware profile or system profile only deployment, you are automatically prompted to include information for the Schedule Deployment page. b.
a. b. c. d. e. To expand and view individual server information, under Selected Servers, click . Under Host Name and NIC, enter a Fully Qualified Host Name for the server. In the NIC for Management Tasks drop-down list, select the NIC for managing the server. Enter IP addresses, subnet mask, default gateway, and DNS details, or select the Obtain using DHCP check box. If deploying to a network that requires a VLAN ID, select the VLAN check box and then enter the VLAN ID.
For more details about the system profile based jobs failure, click More Details. The More Details page displays the following information: • • • • • FQDD of the component Value of the attribute Old value New value Message and message ID about the failure (not displayed for few types of errors) 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 .
• Name • Last Run • Next Run • Status • Collection Size • Progress Summary 2. To view the updated Drift Detection Job Details, click Refresh. 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.
Deployment job timing The provisioning and deploying of bare-metal servers can take between 30 minutes to several hours to complete, depending on several factors. When starting a deployment job, Dell EMC recommends that you plan your deployment time according to the guidelines provided. The amount of time it takes to complete provisioning and deployment varies with deployment type, complexity, and number of deployment jobs running simultaneously.
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.
• For an OMSA status fix where supported version of OMSA is installed, but musts be configured: ○ OMSA is configured on the host. ○ The inventory is run to refresh data. To view and fix the noncompliant hosts: 1. In OpenManage Integration for VMware vCenter, from the Manage tab, click Compliance > vSphere Hosts. a. In the vSphere Hosts page, view the list of noncompliant hosts.
Fixing iDRAC license compliance for vSphere hosts The vSphere hosts listed in the vSphere host compliance pages are noncompliant because they do not have a compatible iDRAC license. The table displays the status of the iDRAC license. You can click a noncomplaint host to view more details such as, how many days are remaining for the iDRAC license, and then you can update it, as required.
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. • • Configuration Compliance—Displays the drift in attributes between the System profile used in the Cluster profile and the associated vSAN hosts.
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. For an 11th generation host that is deployed though OMIVV, OMSA is installed automatically. For 11th generation hosts that you deploy manually, you can choose either of the following: • • Install and configure OMSA using OMIVV.
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.
days are remaining for the iDRAC license, and then you can update it, as required. If the Refresh Baremetal Servers link is enabled in the Bare Metal Servers page, there are bare-metal servers that are noncompliant due to the iDRAC license. 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.
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 38. Privilege groups Group name Description Privilege group — Dell.
○ ○ ○ ○ • Get the vCenter's Address/IP Get host IP/Address Get the current vCenter session user based on the vSphere client session ID Get the vCenter inventory tree to display the vCenter inventory in a tree structure. Dell.Monitoring.Monitor ○ Get host name for posting the event ○ Perform the event log operations, for example get the event count, or change the event log settings ○ Register, unregister, and configure events/alerts — Receive SNMP traps and post events • 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 on page 154 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 .
• For administrator users: 1. Reboot the registered OMIVV appliance. 2. Log out from web client and then log in again. The Dell provider is now listed in the Proactive HA provider list. Version affected: 4.0 Inventory failing when performing firmware update task on ESXi 5.x host After registering a vCenter server, if you perform firmware update task on an ESXi 5.
OMIVV does not display all the relevant logs when trying to filter a severity category When you select a severity category to filter the log data by choosing All Categories from the drop-down, all the logs belonging to specific category are displayed accurately. However, if you filter by choosing Info from the drop-down, the Firmware update logs are not displayed and only the task initiation logs are displayed. Resolution: To view all the logs in OMIVV, select All Categories from the Filter drop-down.
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 6. Retrieve the new certificate by using the following command: "%VMWARE_CIS_HOME%"\vmafdd\vecs-cli entry getcert --store MACHINE_SSL_CERT --alias __MACHINE_CERT --output c:\certificates\new_machine.crt 7. Perform the following steps: a. Run ls_update_certs.py by using the following command. "%VMWARE _PYTHON_BIN%" ls_update_certs.py -url b. Replace psc.vmware.
1. Create the C:\certificates\ folder on PSC by using the following command: mkdir C:\certificates\. 2. Open the following link in a browser: https:///lookupservice/mob? moid=ServiceRegistration&method=List 3. Log in with the administrator@vsphere.local user name and provide the password when prompted. NOTE: If you are using a custom name for vCenter Single Sign-On (SSO) domain, use that user name and password. 4.
For example, the thumbprint string can appear as either of the following: • • ea87e150bb96fbbe1fa95a3c1d75b48c30db7971 ea:87:e1:50:bb:96:fb:be:1f:a9:5a:3c:1d:75:b4:8c:30:db:79:71 Extracting Thumbprint by using the command line You can see the following sections for extracting thumbprint by using the command line on the appliance and Windows installation. Extracting thumbprint by using the Command Line on the vCenter server appliance Perform the following steps: 1. Move or upload the old_machine.
Versions Affected: 2.2 and later What should I do when a web communication error in the vCenter web client appears after changing the DNS settings in OMIVV If you see any kind of web communication error in the vCenter web client while doing any OMIVV-related tasks after changing the DNS settings, do either of the following: • • Clear the browser cache. Log out and then log in from web client. The settings page fail to load, if I navigate away and again go back to the settings page For vSphere v5.
Why is web client UI distorted for few Dell screens in IE 10 Sometimes when a popup dialog is displayed, the data in the background might become white and is distorted. Resolution: Close the dialog box; the screen returns back to normal. Version Affected: 2.2 and later I am not seeing OpenManage Integration icon in web client even if registration of plug-in to vCenter was successful OpenManage Integration icon is not displayed in the web client unless the vCenter web client services are restarted.
en.community.dell.com/techcenter/b/techcenter/archive/2013/03/20/intel-network-controller-card-with-v13-5-2-firmware-cannot-beupgraded-using-lifecycle-controller-to-v13-5-6.aspx NOTE: Note: When using one-to-many firmware update, avoid selecting Intel network adapters that are at version 13.5.2, as the update fails and stops the update task from updating remaining servers. Using OMIVV to update Intel network card from 14.5 or 15.0 to 16.
Processor version is displayed as “Not Applicable” in processor view in system overview page In PowerEdge 12th Generation Dell servers and higher generations, the processor version is in the Brand column. In lower generation servers, processor version is shown in the Version column. 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.
Table 42. Virtual appliance(continued) Port Protocols Number Port Type Maximum Encryption Level Direction Destination Usage Description 2049 NFS UDP/T CP None In/Out OMIVV appliance to NFS Public Share NFS public share that is exposed by OMIVV appliance to the managed nodes and used in firmware update and OS deployment flows.
Table 44. Managed nodes (iDRAC/CMC)(continued) Port Number Protocol s Port Type Maximum Encryption Level Direction Destination Usage Description To access the iDRAC configurations from the OMIVV. Used in deployment flow. 4001 to NFS UDP None In/Out 4004 iDRAC to/from OMIVV Public Share For iDRAC to access NFS public share that is exposed by OMIVV appliance. This is used for OS deployment and firmware update. To access the iDRAC configurations from the OMIVV. Used in deployment flow.
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. Select Apply Changes, and the temperature warning event is generated. To cause another event, restore the original settings by using the same Set to Values option. Events are generated as warnings, and then to a normal state.
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. Auto discovered systems are displayed without model information in Deployment wizard This usually indicates that the firmware version installed on the system does not meet the recommended minimum requirements.
What should I do as firmware update failed Check the virtual appliance logs to see if the tasks timed out. If so, iDRAC must be reset by performing a cold reboot. After the system is up and running, check to see if the update was successful by either running an inventory or by using the Firmware tab. What should I do as vCenter registration failed vCenter registration can fail due to communication issues, therefore if you are experiencing these issues, a solution is to use a static IP address.
In Administration Console, Update Repository Path is not set to default path after I reset appliance to factory settings After you reset the appliance, go to the Administration Console, and then click APPLIANCE MANAGEMENT in the left pane. In the Appliance Settings page, the Update Repository Path is not changed to the default path. Resolution: In Administration Console, manually copy the path in the Default Update Repository field to the Update Repository Path field.
During OS deployment on 14G, hardware profile apply fails due to iDRAC error During OS deployment on 14G server, a configuration update job is created in iDRAC when the hardware profile is applied. However, the job fails sometimes and displays a message indicating that a Configuration job is already created. Resolution: To clear the stale entries and retry the OS deployment, run the racadm jobqueue delete -i JID_CLEARALL_FORCE command.
When deploying an OS, the Hardware Profile cannot be applied and the boot order cannot be configured without restarting the host When applying the Hardware Profile, if the BIOS boot mode and NVMe settings are changed, the boot order cannot be configured without restarting the host device. Resolution: Manually change the boot mode from system BIOS by launching the virtual console from iDRAC. Version Affected: 4.3 When creating a connection profile for the host having ESXi 6.
When upgrading or downgrading some iDRAC firmware versions using OMIVV, even when the actual firmware update is successful, OMIVV may indicate that the job is failed. During firmware update, when you downgrade or upgrade the iDRAC versions such as 3.20.20.20, 3.21.21.21, and 3.21.21.22, the job status is indicated as failed even when the job was successfully run. Resolution: Refresh the inventory after the job failure and rerun the job for other components. Version Affected: 4.
• • 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. BIOS configuration should be run in clone mode so that the reference server is an identical system.
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.3 to access the following documents: • • • OpenManage Integration for VMware vCenter Version 4.3 Web Client User's Guide OpenManage Integration for VMware vCenter Version 4.3 Release Notes OpenManage Integration for VMware vCenter Version 4.
A System specific attributes iDRAC Table 45.
Table 46.
Table 48.
FC Table 49.
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.
D Component vs. baseline version comparison matrix Table 51. 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.
