OpenManage Integration for VMware vCenter Version 5.
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. © 2010 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction................................................................................................................................10 Whats new in this release................................................................................................................................................... 10 OpenManage Integration for VMware vCenter features............................................................................................... 10 2 About Administration Console...
7 Capture baseline configuration using cluster profile...................................................................... 44 Cluster profile.......................................................................................................................................................................44 Create cluster profile...........................................................................................................................................................
10 Manage jobs............................................................................................................................. 64 Deployment jobs.................................................................................................................................................................. 64 Chassis firmware update jobs............................................................................................................................................
14 Chassis Management................................................................................................................ 90 View Dell EMC chassis information...................................................................................................................................90 View chassis inventory information..................................................................................................................................
17 Frequently Asked Questions-FAQ.............................................................................................. 131 Frequently Asked Questions-FAQ.................................................................................................................................... 131 iDRAC license type and description are displayed incorrectly for non-compliant vSphere hosts...................... 131 Dell provider is not displayed as health update provider......................................
Available OMIVV appliance version displays wrong information when the available version is lesser than the current version.................................................................................................................................................. 140 The 267027 exception is thrown while adding a 12G and later bare-metal server .............................................140 During deployment, system profile apply fails due to iDRAC error................................................
D Component vs. baseline version comparison matrix..................................................................... 152 E Response codes........................................................................................................................
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 reduce the complexity of managing your data center by streamlining the tasks associated with the management and monitoring of Dell EMC server infrastructure in the vSphere environment. Whats new in this release This release of OpenManage Integration for VMware vCenter 5.
Features Description • Hardware compliance NOTE: Hardware compliance is not supported for hosts that are managed using chassis credential profile. Driver updates Driver updates for vSAN clusters. Deployment Deployment includes the following: • • Create and deploy system profiles. Remotely deploy an operating system on the bare-metal servers using VMware vCenter without using PXE.
2 About Administration Console You can administer the OpenManage Integration for VMware vCenter and its virtual environment using either of the two administrations portals mentioned below: • • Web-based Administration Console Console view for an individual server—the virtual machine console of the OMIVV appliance Register new vCenter server Your account should have the necessary privileges to create a server.
Register vCenter server using a non-administrative account You can register vCenter servers for the OMIVV appliance with vCenter administrator credentials or a non-administrator user with the Dell privileges. To enable a non-administrator user with the required privileges to register a vCenter server, perform the following steps: 1. Create a role or modify existing role with a required privileges for the role.
• Inventory • • Add host to cluster • Add standalone host • Modify cluster Lifecycle Manager: General Privileges • Read NOTE: The vSphere Lifecycle Manager General Privileges are applicable only for vCenter 7.0 and later.
1. Go to https://. 2. In the left pane, click VCENTER REGISTRATION. The registered vCenter servers are displayed in the working pane. 3. To update the certificate for a vCenter server IP or hostname, click Update. Modify vCenter login credentials You can modify the vCenter login credentials with administrative privileges or a non-administrator user with necessary privileges. If a Proactive HA feature is enabled on a cluster, you must not change the user who is associated to it.
Manage the OMIVV appliance The OMIVV appliance management enables you to manage the OpenManage Integration for VMware vCenter network, NTP, and HTTPS information, and enables an administrator to perform the following actions: • • • • • • • • • • • • Restart the OMIVV appliance. See Restart OMIVV appliance. Update the OMIVV appliance, and configure an update repository location. See Update OMIVV appliance and repository location Upgrade OMIVV appliance using RPM. See Upgrade OMIVV appliance using RPM.
2. To update the OMIVV appliance, perform the mentioned tasks for the upgrade mechanisms as applicable from the version of OMIVV. OMIVV upgrade options Backup and restore You can perform backup and restore from OMIVV 4.3 and later to the latest version (with vCenter 6.5 and later). RPM upgrade You can perform RPM upgrade from OMIVV 5.0 and later to the latest version. Upgrade OMIVV appliance using RPM Ensure that you are upgrading to a version of the appliance that is greater than the current one. 1.
NOTE: If the IP address for the new appliance is different from the IP address of the older appliance the Proactive HA feature may not work properly. In such a scenario, disable and enable the Proactive HA for each cluster where Dell EMC host is present. 6. The OMIVV appliance comes with default certificate. If you want to have a custom certificate for your appliance, update the same. See Generate a Certificate Signing Request (CSR) and Upload HTTPS certificate. Else, skip this step. 7.
The encryption password can contain alphanumeric characters and special characters, such as, “!, @, #, $, %, and *”. e) In Verify Password, retype the encrypted password. 3. To save these settings, click Apply. 4. Configure the backup schedule. See Scheduling automatic backups. After this procedure, configure a backup schedule. Schedule automatic backups For more information about configuring the backup location and credentials, see Configuring backup and restore. 1.
Generate and download the troubleshooting bundle To generate the troubleshooting bundle, ensure that you log in to admin portal. The troubleshooting bundle contains logging information of OMIVV that can be used to assist in resolving issues or sent to Technical Support. 1. On the APPLIANCE MANAGEMENT page, click Generate Troubleshooting Bundle. 2. Click Download Troubleshooting Bundle. Set up HTTP proxy 1. On the APPLIANCE MANAGEMENT page, scroll down to HTTP PROXY SETTINGS, and then click Edit. 2.
The allocated CPU and memory are verified against the required CPU and memory for the set deployment mode. • • • If the verification fails, an error message is displayed. If the verification is successful, the OMIVV appliance restarts and the deployment mode is changed after you confirm the change. If the required deployment mode is already set, a message is displayed. 5.
1. On the APPLIANCE MANAGEMENT page, click Upload Certificate in the HTTPS CERTIFICATES area. 2. Click OK in the UPLOAD CERTIFICATE dialog box. 3. To upload the certificate, click Browse, and then click Upload. To check the status, go to Event Console of vSphere Client of registered vCenters. While uploading certificate, OMIVV administration console becomes unresponsive for up to 3 minutes.
NOTE: When the OMIVV appliance is not able to retrieve an IP address from the network (DHCP), 0.0.0.0 is displayed as the IP address. To resolve this, you must manually configure the static IP. a) On the Date and Time tab, select the Synchronize date and time over the network check box. The Synchronize date and time over the network check box is enabled only after NTP is configured successfully using the Admin portal.
a) Click the IPv4 Settings tab, select Manual from the Method drop-down list, and click Add. NOTE: If you select Automatic (DHCP), do not enter any IP address because the OMIVV appliance will automatically receive IP from the DHCP server during the next restart. b) Enter a valid IP, netmask (in the Classless Inter-Domain Routing (CIDR) format), and gateway information. If you enter an IP address in the Netmask box, it is automatically converted to its respective CIDR format.
NOTE: Sometimes, after you configure the OMIVV appliance with a static IP, the OMIVV terminal utility page does not immediately refresh and display the updated IP. To resolve this issue, exit the OMIVV terminal utility, and then log in again. 8. To change the hostname of the OMIVV appliance, click Change Hostname. a) Enter a valid hostname, and click Update hostname. NOTE: If any vCenter servers are already registered with the OMIVV appliance, unregister and re-register all the vCenter instances.
1. Turn off the OMIVV appliance. 2. Edit the VM settings using the vSphere Client (HTML-5) and add the additional Network adapter. To edit the VM settings, right-click VM, and then click Edit Settings. 3. Click ADD NEW DEVICE, select Network Adapter. a) Select the appropriate network for the NIC, and then select the Connect At Power On check box. b) Select the VMXNET3 adapter type from the drop-down menu. NOTE: OMIVV supports VMXNET3 type of NIC. 4. Turn on the OMIVV appliance.
WARNING: Do not use "+" to add any new network interface. It is mandatory to use the vSphere Edit Settings to add a NIC. 6. Select the NIC that you want to configure and click . 7. To identify the correct NIC, use the MAC ID displayed on the Ethernet tab, and then compare it against the MAC ID displayed in the vSphere Client (HTML-5). Ensure that you do not change the default MAC address that is listed in the Ethernet tab. 8.
a) Select Manual or Automatic (DHCP) from the Method drop-down list. b) If you select the Manual method, click Add, and then enter the valid IP address, Netmask (in the CIDR format), and gateway details. It is recommended that you use the static IP in case if you want to control over the priority of the DNS servers (primary and secondary DNS entries). Typically, vSphere elements of data center such as vCenter and ESXi hosts are managed using hostname or FQDN.
Typically, the network that you have configured as the default gateway does not require any manual route configuration because the gateway is capable of providing the reachability. However, for networks where default gateway is not configured (the Use this connection only for resources on its network check box is selected), a manual route configuration may be required. Because the default gateway is not configured for this network to reach external networks, manual routing configurations are required.
Configure Network Time Protocol (NTP) and set local time zone 1. Open the OMIVV web console. 2. In the OpenManage Integration for VMware vCenter Virtual Appliance Setup utility, click Date/Time Properties. Ensure to enter the NTP details in Admin console. For more information, see Set up Network Time Protocol (NTP) servers. 3. On the Date and Time tab, select Synchronize date and time over the network. The NTP Servers window is displayed. 4.
3 Monitor hosts and chassis using dashboard The dashboard displays the following: • • • • • • • Health status of hosts and chassis Warranty status of hosts and chassis License information of Hosts and vCenter Configuration compliance status of hosts States of jobs that are scheduled using OMIVV Bare-metal servers available for deployment Quick references to OMIVV features Health The Health section displays the health of all OMIVV-managed hosts and chassis.
Configuration Compliance The Configuration Compliance section displays the hosts that are part of cluster that is associated with the cluster profile. The hosts that are displayed here are configured using the same Platform Service Controller (PSC). To view the configuration compliance status of hosts, click VIEW COMPLIANCE. Jobs The Jobs section displays the jobs that are scheduled using OMIVV. The job details are displayed only for last 7 days.
4 Manage hosts using host credential profile Host credential profile A host credential profile stores the iDRAC and host credentials that OMIVV uses to communicate with the servers. OMIVV manages the hosts that are associated to a host credential profile. You can associate multiple servers to a single host credential profile. The PowerEdge MX chassis host can be managed using a single unified chassis management IP.
• • To download and store the host certificate and validate it during all future connections, select the Enable Certificate Check check box. To enter the credentials for hosts that are already configured and enabled for AD, select the Use Active Directory check box. • • • Enter the username in the Active Directory User Name box. Enter the username in one of the formats such as domain \username or username@domain. The username is limited to 256 characters.
c) In the Host Root area, enter the host local credentials and AD credentials. • To change the local credentials of ESXi host, do either of the following: • • • • The default username is root. You cannot edit it. Enter a valid password. For ESXi 6.7 and later, entering valid password is not mandatory. To download and store the host certificate and validate it during all the future connections, select the Enable Certificate Check check box.
By default, the Date Modified and Last Modified columns are not selected. To select these columns, click 3. To export the host credential profile information, click . . Test host credential profile Using the test credential profile feature, you can test the host and iDRAC credentials. It is recommended that you select all hosts. 1. On the OMIVV home page, select a host credential profile that has associated hosts, and then click TEST. The Test Host Credential Profile page is displayed. 2.
5 Manage chassis using chassis credential profile Chassis credential profile A chassis credential profile stores the chassis credentials that OMIVV uses to communicate with the chassis. OMIVV manages and monitors the chassis which are associated to a chassis credential profile. You can assign multiple chassis to a single chassis credential profile. The PowerEdge MX chassis host can be managed using a single unified chassis management IP.
The test result is displayed in the Test Results section as Passed or Failed. To test the chassis connectivity manually, select the chassis and click BEGIN TEST. For a PowerEdge MX chassis configured with an MCM group, It is recommended that you manage all the lead and member chassis using the lead chassis. The member chassis test connection operation fails , and test result status is indicated as Fail. The lead chassis IP link is displayed. Click the lead chassis IP link to discover the complete MCM group.
View chassis credential profile After you create one or more chassis credential profiles, you can view the chassis and the associated chassis on the chassis credential profile page. 1. On the OMIVV home page, click Compliance & Deployment > Chassis Credential Profile.
6 Manage firmware and driver repositories using repository profile Repository profile A repository profile enables you to create and manage driver or firmware repositories. You can use the firmware and driver repository profiles to: • • • Update firmware of hosts Update driver for hosts that are part of vSAN clusters. Create cluster profile and baseline the clusters.
NOTE: For SMB 1.0 share used for driver repository, add the file separator at the end of the directory path. 7. To validate the catalog path and credentials, click BEGIN TEST. To continue creating a repository profile, you must complete this validation process. The test connection results are displayed. 8. Click NEXT. The Synchronize with repository location page is displayed. 9. Click NEXT. The Summary page is displayed that provides the information about the repository profile. 10. Click FINISH.
• • Custom Online—OMIVV uses Custom Online (HTTP or HTTPS share) as a source for catalog and update packages. When you create a custom repository using Server Update Utility (SUU), ensure that the signature file for the catalog (catalog.xml.gz.sign) is present in the catalog file folder. Shared Network Folder—OMIVV uses shared network folder (CIFS or NFS) as a source for catalog and update packages. a) If you select Custom Online, enter the catalog online path.
2. In the delete confirmation dialog box, click DELETE.
7 Capture baseline configuration using cluster profile Cluster profile A cluster profile enables you to capture the configuration baseline (hardware configuration, firmware, or driver versions) and maintain the required state for clusters by identifying any drift against the configuration baseline. To create a cluster profile, ensure that you have any one of these profiles: system profile, firmware repository profile, driver repository profile, or its combinations.
e) Click NEXT. 7. On the Schedule Drift Detection page, select the date and time, and then click NEXT. The Summary page is displayed that provides the information about the cluster profile. 8. Click FINISH. The drift detection job runs immediately after the cluster profile is saved and later runs during the scheduled time. View the job completion status on the Jobs page.
4. To update the associated profiles to the latest, click OK. After you update the profiles, the baseline cannot be reverted. The cluster profile is synced with the updated repository profiles or system profile , and then the warning symbol disappears. Delete cluster profile 1. On the OMIVV home page, click Compliance & Deployment > Profiles > Cluster Profile. 2. Select a cluster profile, and then click DELETE. 3. In the Delete Confirmation dialog box, click DELETE.
8 Deployment To deploy system profile and ISO profile, ensure that the servers are displayed in the Deployment Wizard and all the servers are as per the following requirements: • • • • • • • • • Meet specific hardware support information mentioned in the OpenManage Integration for VMware vCenter Compatibility Matrix. Meet minimum supported versions of the iDRAC firmware and BIOS. See the OpenManage Integration for VMware vCenter Compatibility Matrix for specific firmware support information.
• • • • • Manual discovery of bare-metal servers Remove bare-metal servers System Profile and ISO Profile deployment Refresh bare-metal servers Purchase or renew iDRAC license Device discovery Discovery is the process of adding supported bare-metal server. After a server is discovered, you can use it for system profile and iso profile deployment. For more information about the list of supported servers, see OpenManage Integration for VMware vCenter Compatibility Matrix.
For detailed information about how to configure the DHCP scope option and DNS service record, see Dell Auto-Discovery Network Setup Specification at https://www.dell.com/support. Enable or disable administrative accounts in iDRAC Before setting up auto discovery, disable all IDRAC accounts except one which does not have admin access. After auto discovery, you can enable all accounts except the root account.
The Add Server dialog box is displayed. 2. In the Add Server dialog box, do the following: a) In the iDRAC IP Address box, enter an iDRAC IPv4. b) Enter the iDRAC credentials. 3. Click OK. Adding server may take a few minutes. When the discovery operation is in progress, you can close the Add Server page. Discovery process proceeds in the background. The discovered server is displayed on the Bare-metal Servers page. The time out value for the manual discovery is set to 15 minutes.
• System profile deployment • For more information, see Deploy system profile (configuration of the hardware). ISO profile deployment • For more information, see Deploy ISO profile (ESXi installation) . System profile and ISO profile deployment For more information, see Deploy system profile and ISO profile. To launch the deployment wizard, go to Compliance & Deployment > Deployment > DEPLOY. Deploy system profile (configuration of the hardware) 1.
• Internal Dual SD Module (IDSDM)—deploys an operating system on the IDSDM. 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 First boot Disk option is available. • • If any one of the selected servers does not support an IDSDM or BOSS module, or if an IDSDM or BOSS is not installed in the servers during deployment then the deployment operation on those servers is skipped.
Deploy system profile and ISO profile You can perform the deployment only on the compliant bare-metal servers. For more information, see View bare-metal servers. 1. On the System Profile and ISO Profile Deployment Checklist page of the deployment wizard, verify the deployment checklist, and then click GET STARTED. 2. On the Select Server (s) page, select one or more servers. The Select Deployment Options page is displayed. 3.
deployment jobs running simultaneously. The deployment jobs are run in batches of up to five concurrent servers to improve time for the overall deployment job. The exact number of concurrent jobs depends on available resources. The following table displays the average value, and may vary based on factors like configuration of the server, generation of the server, and number of bare metal servers scheduled for deployment: Table 3.
NOTE: • While using the system profile, exporting a system profile with Enterprise license and importing the same system profile on servers with Express license fails. • You cannot import system profile by using the Express license of iDRAC9 firmware 3.00.00.00. You must have an Enterprise license. Create system profile It is recommended that you use Google Chrome to create or edit System Profile. 1. On the OMIVV home page, click Compliance & Deployment > Profiles > System Profile > CREATE NEW PROFILE.
The total number of attributes, total number of enabled attributes, and total number of destructive attributes are displayed under the attribute statistics. 9. Click FINISH. The saved profile is displayed on the System Profile page. Some attributes of System Profile are overridden for the OMIVV to be functional. For more information about customized attributes, see Customization attributes.
View system profile 1. On the OMIVV home page, click Compliance & Deployment > System Profile. A table displays all the system profiles along with the following information: • • • • Profile Name—The name of the system profile Description—The profile description Reference Server—The iDRAC IP from which the system configuration details are extracted. Server Model—The model name of the reference server 2. If you want to remove or add the column names from the wizard, click 3.
Select the correct ESXi version so that the appropriate installation boot script is used. If you select an incorrect ESXi version, the deployment may fail. 6. To verify the ISO file path and authentication, click BEGIN TEST. Test results are displayed. 7. Click FINISH. View an ISO profile 1. On the OMIVV home page, click Compliance & Deployment > ISO Profile.
9 Compliance Management Compliance To view and manage hosts in OMIVV, each host must meet certain criteria. If the hosts do not meet the compliance criteria, OMIVV will not manage and monitor them. OMIVV displays details about the noncompliance host, and enables you to fix the noncompliance, where applicable. The host is non-compliant if: • • The host is not associated to a Host Credential Profile.
NOTE: When a PowerEdge MX host is managed using a chassis credential profile, the iDRAC Firmware version is displayed as Not Applicable on the Management Compliance page. This is because iDRAC firmware compliance is not applicable for iDRAC9-based servers. For the list of iDRAC9-based servers, see the compatibility matrix. Fix a non-compliant host The host is non-compliant if: • • The host is not associated to a Host Credential Profile.
Fix iDRAC license compliance The compatible iDRAC license is one of the compliance criteria for hosts. If hosts do not have compatible iDRAC license, those hosts listed as noncompliant hosts on the Management Compliance page. You can click a noncomplaint host to view the details such as iDRAC expiation date, license type, and license description. The RUN INVENTORY is active if the iDRAC compliance status is non-compliant or Unknown for any one of the hosts that are associated to a host credential profile.
• • • Hardware Configuration Compliance—Displays the drift in attributes between the system profile that is used in the cluster profile and the associated hosts that are part of cluster. Firmware Compliance—Displays the firmware version drift between the firmware repository profile that is used in the cluster profile and the associated hosts that are part of cluster.
For firmware and driver: • • • • • • • • • Host Name or IP—Indicates the host IP or hostname. Service Tag—Indicates the Service Tag of the host. Drift Status—Indicates the drift status. Component Name—Indicates the name of the component. Current Value—Indicates the current value of the attribute in the host. Baseline Value—Indicates the baseline value. Drift Type/Error—Indicates the reason for non-compliance. For more information about the drift type, see Component vs. baseline version comparison matrix.
10 Manage jobs Deployment jobs After the deployment tasks are complete, you can track the deployment job status on the Deployment Jobs page. 1. On the OMIVV home page, click Jobs > Deployment Jobs. A table displays all the deployment jobs along with the following information: • • • • • • Name—The deployment job name Description—The job description Scheduled Time—The date and time when the job is scheduled.
• • • Description—The firmware update job description vCenter—The vCenter name Collection Size—The number of chassis in the firmware update job • The total number of chassis includes only lead and stand-alone chassis. The member chassis will not take part in it. Progress Summary—The progress details of the firmware update job 3. To view more information about a particular job, select a job.
System Lockdown Mode jobs The System Lockdown Mode setting is supported only for iDRAC9-based servers. The setting when turned on locks the system configuration including firmware updates. This setting is intended to protect the system from unintentional changes. You can turn on or turn off the System Lockdown Mode for managed hosts using the OMIVV appliance or from the iDRAC console. From the OMIVV version 4.1 and later, you can configure and monitor the Lockdown Mode of iDRAC in servers.
• • • • • Cluster vCenter Status Start Date and Time End Date and Time 4. To run the Drift Detection job on-demand, click . In a baselined cluster, after adding a host to the host credential profile or chassis credential profile, the drift detection job is automatically run on a newly added host. View host inventory job The Host Inventory page displays information about the latest inventory job run on a host that is associated to a Host Credential Profile. 1.
• Configure System Lockdown Mode • When the hosts are managed using chassis, Configure System Lockdown Mode is not supported. Run Firmware Wizard Modify host inventory job After associating hosts to a Host Credential Profile, you must periodically schedule inventory to ensure that inventory information of hosts is up to date. Inventory Jobs displays the status of inventory jobs that are run on the hosts.
View hosts warranty A warranty job is a scheduled task to get warranty information from www.dell.com/support on all systems. Ensure that the OMIVV appliance has Internet connectivity to extract warranty information. Depending on the network settings, OMIVV might require proxy information for Internet reachability and fetch warranty information. The proxy details can be updated in the Administration Console. 1. On the OMIVV home page, click Jobs > Warranty > Hosts Warranty. 2.
• End Date and Time—The time the warranty job ended. 2. To run the chassis warranty job on-demand, click Run now [ ].
11 Manage logs View log history 1. On the OpenManage Integration for VMware vCenter page, to view all the logs, click Logs. The OMIVV log retrieval process retrieves all the logs from its database. This may take a few seconds based on the log size. • • • • To export the logs data, click . To sort the data in the grid, click a column header. To navigate between pages, click previous and next icons. To refresh the logs, click the refresh icon on the upper-left corner. 2.
12 Manage OMIVV appliance settings On the Settings page, you can perform the following tasks: • • • • • • Configure warranty expiration notification settings. For more information, see Configure warranty expiration notification. Configure the latest appliance version notification. For more information, see Configure latest appliance version notification . Override severity for Proactive HA alerts. For more information, see Override severity of health update notification. Initial Configuration.
4. Click APPLY. Configure deployment credentials OMIVV acts as a provisioning server. The deployment credentials enable you to communicate with iDRAC that uses the OMIVV plugin as a provisioning server in the auto discovery process. The deployment credentials enable you to set up iDRAC credentials to communicate securely with a bare-metal server that is discovered using auto discovery until the operating system deployment is complete.
Table 5. Dell Proactive HA events Dell Inc provider event Component type Description DellFanRedundancy Fan Fan redundancy event DellPowerRedundancy Power supply (PSU) Power redundancy event DellIDSDMRedundancy Storage IDSDM redundancy event NOTE: When the hosts are added to Proactive HA enabled cluster and if IDSDM components are present, ensure that Internal SD Card Redundancy is configured in the iDRAC settings as Mirror.
Event name Description Severity Redundancy Degraded Redundancy is degraded Warning Redundancy Lost Redundancy is lost Critical Configure Proactive HA for Rack and Tower servers Ensure that all hosts are configured for redundancy of all the three supported redundant components (power supply, fans, and IDSDM). 1. Create a host credential profile and associate hosts to a host credential profile. See Create host credential profile. 2. Verify that hosts inventory is completed successfully.
After Proactive HA is enabled on a cluster, OMIVV initializes Proactive HA health and redundancy status and reports them to vCenter. Based on the health update notification from OMIVV, the vCenter server performs the manual or automatic action that you have selected for Remediation. To override the existing severity, see Override severity of health update notification.
c) Configure events and alarms. For information about configuring events and alarms, see Configure events and alarms. d) To apply individual settings, click the Apply button separately, and then click NEXT. It is highly recommended to enable all the additional settings. If any of the additional settings are not applied, a message is displayed indicating that the all the additional settings are mandatory. 5. On the Next Steps page, read the instructions, and then click FINISH.
The License Management section displays the links to the following: • • Product licensing portal (Digital Locker) Admin console OpenManage Integration for VMware vCenter (OMIVV) licensing OMIVV 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 OMIVV.
Name Description • iDRAC with Lifecycle Controller Administration Console Provides a link to the Administration Console. General Help Provides a link to the Dell EMC support site. Reset iDRAC Provides a link to reset iDRAC that can be used when iDRAC is not responsive. This reset performs a normal iDRAC reboot. For more information about resetting iDRAC, see Reset iDRAC. Before calling Tech Support Provides tips on how to contact Dell EMC Support and route your calls correctly.
13 Manage vCenter settings About events and alarms On the Settings page, you can enable the events and alarms for hosts and chassis, select the event posting level, and restore default alarms. You can configure events and alarms for each vCenter or for all registered vCenters. The events and alarms corresponding to a chassis are associated with vCenter. The following are the four event posting levels: Table 8.
Configure events and alarms To receive events from the servers, ensure that the SNMP trap destination is set in iDRAC. OMIVV supports SNMP v1 and v2 alerts. 1. On the OMIVV home page, click Settings > vCenter Settings > Events and Alarms. 2. To enable alarms for all hosts and its chassis, click Enable Alarms for all hosts and its chassis. The Enable the Dell EMC Alarm Warning page displays the clusters and non-clustered host that might be impacted after enabling the Dell EMC alarms.
1. On the OMIVV home page, click Settings > Events and Alarms. The following details are displayed: • • vCenter alarms for Dell EMC hosts—Displays either Enabled or Disabled. Event posting level 2. Configure events and alarms. See Configure events and alarms. To view the event posting levels, see About events and alarms.
Event name Description Severity Recommended action Dell-Memory Device Status warning A memory device correction rate exceeded an acceptable value Warning No action Dell-Memory Device error A memory device correction Error rate exceeded an acceptable value, a memory spare bank was activated, or a multibit ECC error occurred Put the system into maintenance mode Dell-Fan enclosure inserted into system Sensor returned to normal value Info No action Dell-Fan enclosure removed from system A fan enc
Event name Description Dell-Battery sensor detected a failure value A battery sensor in the specified Error system detected that a battery has failed No action Dell-Battery sensor detected a nonrecoverable value A battery sensor in the specified Error system detected that a battery has failed No Action 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.
Event name Description Severity Recommended action Dell-Voltage sensor detected a failure value A voltage sensor in the specified Error system exceeded its failure threshold Put the system into maintenance mode Dell-Voltage sensor detected a nonrecoverable value A voltage sensor in the specified Error system detected an error from which it cannot recover No action Dell-Current sensor returned to a normal value Sensor Returned to Normal Value Info No action Dell-Storage: storage management erro
Event name Description Severity Recommended action Dell-Fluid Cache Disk failure Fluid cache disk failure Error Put the system into maintenance mode Dell-Cable failure or critical event Cable failure or critical event Error Put the system into maintenance mode Dell-Chassis Management Controller detected a warning Chassis Management Controller Warning detected a warning No action Dell-Chassis Management Controller detected an error Chassis Management Controller Error detected an error Put th
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.
Event name Description Severity Recommended action Internal Dual SD Module redundancy is degraded Either one of the SD card or both the SD cards are not functioning properly Warning Replace the failed SD card Internal Dual SD Module is not redundant None Info Install additional SD card and configure for redundancy if redundancy is desired Chassis events Power supply redundancy is lost The current power operational Critical mode is non-redundant because of a power supply exception, a power suppl
Managing data retrieval schedule Schedule inventory job To view the latest inventory data on OMIVV, you must schedule an inventory job to run periodically to ensure that inventory information of hosts or the chassis is up-to-date. It is recommended that you run the inventory job on a weekly- basis. NOTE: The chassis is managed in OMIVV context. There is no context of vCenter in chassis management.
14 Chassis Management View Dell EMC chassis information You can view the chassis information that is discovered and inventoried using OMIVV. Dell EMC chassis lists all the Chassis that is managed by OMIVV. 1. On the OMIVV home page, click Hosts & Chassis > Chassis > Chassis List. The following information is displayed: • • • • • • • • • • Name—Displays an IP address link for each Dell EMC chassis. IP Address/FQDN—Displays the vCenter IP address or FQDN. Service Tag—Displays the Service Tag of the chassis.
2. Select a chassis, click the Service Tag link. The Overview page is displayed. 3. On the Overview page, click Hardware. Table 10. Hardware inventory information Hardware inventory: Component Navigation through OMIVV Information Fans • Information about fans: • • • On the Dell EMC Chassis page, click Chassis > Chassis List, click the Service Tag link. On the Overview page, in the left pane, select Hardware. In the right pane, expand Fans. OR On the Overview page, click Fans.
Hardware inventory: Component Navigation through OMIVV Information • • • • • • • • • • • Fabric (Only for PowerEdge MX chassis) • • • • In the right pane, expand I/O Modules. OR On the Overview page, click I/O Modules. On the Dell EMC Chassis page, click Chassis > Chassis List, click the Service Tag link. On the Overview page, in the left pane, select Hardware. In the right pane, expand Fabric. OR On the Overview page, click Fabric.
Hardware inventory: Component Navigation through OMIVV Information NOTE: The iKVM tab is displayed only if the chassis contains iKVM module. View firmware inventory information You can view the firmware-related information for the selected chassis. 1. On the OMIVV home page, click Hosts & Chassis > Chassis > Chassis List. The Dell EMC Chassis page is displayed. 2. Select a chassis, click the Service Tag link. The Overview page is displayed. 3. On the Overview page, click Firmware.
• • Gateway • Preferred DNS Server • Alternate DNS Server Local Access Configuration • • • • Quick Sync Hardware Present LCD Present LED Present KVM Enabled 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. View storage inventory information You can view the storage-related information for the selected chassis. 1. On the OMIVV home page, click Hosts & Chassis > Chassis > Chassis List.
• Group IP Address (link to storage group). 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. View warranty information You can view the warranty-related information for the selected chassis. 1. On the OMIVV home page, click Hosts & Chassis > Chassis > Chassis List. The Dell EMC Chassis page is displayed. 2.
Manage PowerEdge MX chassis The way that you manage an MX7000X chassis is different from managing other Dell EMC chassis such as M1000e, VRTX, and FX2. You can manage an MX chassis in a standalone mode having public IPs for Management Module and iDRAC IPs. Also, you can configure an MX chassis in the Multi-Chassis Management (MCM) mode having one lead and multiple members. Dell EMC OpenManage Enterprise-Modular supports wired MCM groups.
Add PowerEdge MX Chassis A host with valid IPv4 iDRAC IP can be added to host credential profile and during the host inventory, the associated MX chassis gets discovered automatically and displayed on the Dell EMC Chassis page. If an iDRAC IPv4 is disabled for a host, the host inventory fails and chassis is not discovered. In such cases, an MX chassis must be added manually and should be associated to a chassis credential profile to manage the chassis and its associated hosts.
You cannot select only member chassis for update or downgrade. Selecting the lead chassis automatically selects the member chassis. To select all the firmware components across all the pages, click To clear all the firmware components across all the pages, click . . 6. On the Schedule Job page, do the following: a) Enter the firmware update job name and description. The description is an optional field.
15 Host Management View OMIVV hosts You can view all the OMIVV-managed hosts on the OMIVV Hosts page. 1. On the OMIVV home page, click Hosts & Chassis > Hosts. 2. On the OMIVV Hosts tab, view the following information: • • • • Host Name—displays the IP address of the host. To view the host information, select a host. vCenter—displays vCenter IP address of the host. Cluster—displays the cluster name, if the Dell EMC host is in a cluster.
Information Description • • • • NUMA Enabled and Protected: This value indicates that the system is supported and the operating system version is ESXi 5.5 or later and the memory operational mode in BIOS is set to NUMA. Enabled and Not Protected: This value indicates that it supports the system with operating system version lesser than ESXi 5.5. Disabled: This value indicates that it supports valid systems with any operating system version and the memory operational mode in BIOS is not set to FRM.
Information Description • • • Warning (yellow triangle with exclamation point)— component has a noncritical error. Critical (red X)—component has a critical failure. Unknown (question mark)—status is unknown for the component. For example, if there are five healthy signs and one warning sign, the overall health is shown as warning. NOTE: Power monitoring information is not available for hosts with cabled PSU or for modular servers.
Hardware: Component Information NICs • • • Slot—displays the DIMM slot. Size—displays the memory size. Type—displays the memory type. • Total—displays the total count of available network interface cards. Name—displays the NIC name. Manufacturer—displays only the manufacturer name. MAC Address—displays the NIC MAC address. • • • PCI Slots • • • • • • Remote Access Card • • • • PCI Slots—displays the Used, Total, and Available PCI slots. Slot—displays the slot.
Information Description • • • • Physical Disks When you select this option from the View drop-down menu, the Filter drop-down list is displayed. • SCSI • SAS • SATA Default Read Policy—displays the default read policy that is 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 that is supported by the controller.
Information Description • • • • • • • • Controllers • • • • • • • • Remaining Rated Write Endurance—displays the SSD remaining write endurance. Connector ID—displays the connector ID. Enclosure ID—displays the enclosure ID. Device ID—displays the device ID. Model—displays the model number of the physical storage disk. Part Number—displays the storage part number. Serial Number—displays the storage serial number. Vendor—displays the storage vendor name. Controller ID—displays the controller ID.
• • Reading—displays the average value of readings over a one-minute time period. Peak Time (Host Time)—displays the date and time of the host peak amps. Peak Reading—displays the System Peak Power statistic, which is the peak power that is consumed by the system (in watts). NOTE: Power monitoring information is not available for hosts with cabled PSU or for modular servers. NOTE: For hosts managed using chassis, complete power monitoring information is not displayed.
2. In the left pane, select a data center or cluster, and then click Monitor > OMIVV Cluster or Datacenter Information. 3. To view more information, select a specific host. The information such as iDRAC IP, Chassis URL, CPUs, and Memory are displayed in the lower-most horizontal pane of the page. Table 16.
Information Description Power State Displays, if the host has power. Last Inventory Displays the day, date, and time of the last inventory job Host Credential Profile Displays the name of the host credential profile Remote Access Card Version Displays the remote access card version BIOS Firmware Version Displays the BIOS firmware version View hardware information of a data center and cluster Table 17.
Hardware: Component Information • • • • RECOVERABLE NOT RECOVERABLE HIGH LOW Hardware: Memory • • • • • Host—displays the hostname. Service Tag—displays the service tag of the host. Slot—displays the DIMM slot. Size—displays the memory size. Type—displays the memory type. Hardware: NICs • • • • • Host—displays the hostname. Service Tag—displays the service tag of the host. Name—displays the NIC name. Manufacturer—displays only the manufacturer name. MAC Address—displays the NIC MAC address.
Storage: disks Description • • • • SMART ALERT DETECTION UNKNOWN FOREIGN UNSUPPORTED NOTE: For more information about the meaning of these alerts, see the Dell EMC OpenManage Server Administrator Storage Management User's Guide at dell.com/support • • • • • • • • • • Model Number—displays the model number of the physical storage disk. Last Inventory—displays the day, month, and time of the last inventory that was run. Status—displays the host status. Controller ID—displays the controller ID.
Storage: disks Description • • Default Write Policy—displays the default write policy that is supported by the controller. The options include: • Write-Back • Force Write Back • Write Back Enabled • Write-Through • Write Cache Enabled Protected • Write Cache Disabled Disk Cache Policy—displays the default cache policy that is supported by the controller.
• • Unknown—OpenManage Integration for VMware vCenter does not get warranty status because the warranty job is not run, an error has occurred getting the data, or the system does not have a warranty. Days Left—displays the amount of days left for the warranty. Firmware update The OMIVV 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.
• • Ensure that you specify the required time out value for the "Enter maintenance mode" job. If the wait time goes beyond the specified time, the update job fails. However, the components may get updated automatically when the host is rebooted. Rerun the inventory after enabling vSAN. During the firmware update process, Dell EMC recommends not to delete or move the following: • • • The host from vCenter for which the firmware update job is in progress.
The count of the components that is based on criticality status such as Urgent, Recommended, Optional, and Downgrades are displayed. The components which have lower version than the available version in the catalog, or it is in the same level (Up-to-Date), or scheduled for an update cannot be selected. To select the components which have lower version than the available version, select the Allow Firmware downgrade check box.
Update firmware and driver on vSAN cluster Before scheduling the firmware update, ensure that the following conditions are met in the environment: • • • • • • • • • Ensure that host is compliant (CSIOR enabled and host must have supported ESXi version), associated with a host credential profile, and successfully inventoried. If the host is not listed, run the management compliance wizard for hosts from OMIVV and then use the firmware update wizard.
NOTE: Only one bundle can be selected for OEM (debranded) servers even if they are of different models. Even if the bundle is not applicable for one or more of the OEM servers, the components page of the firmware update wizard lists each OEM server or firmware component pair. If the firmware update fails for a given firmware component pair, retry with the alternate bundle displayed for the OEM server. 5.
• • • The host from vCenter for which the firmware update job is in progress. The host credential profile of the host for which the firmware update job is in progress. The repositories that are located in CIFS or NFS. 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. 1.
For hosts managed using chassis credential profile, delete job queue is not supported. By default, the Check Prerequisites option is selected. 10. Under the Update Schedule section, select any one of the following options: • • • • Update Now Schedule Update Apply Updates on Next Reboot Apply Updates, and Force Reboot without enetring Maintenance mode 11. On the Review Summary page, review the firmware update information, and then click FINISH.
The components which have lower version than the available version in the catalog, or it is in the same level (Up-to-Date), or scheduled for an update cannot be selected. To select the components which have lower version than the available version, select the Allow Firmware downgrade check box. You can use the filter option to filter the data based on the specific column names.
Table 21. Example for multiple components with different version present in server Component Current version Available version HDD1 V1 V3 HDD2 V2 V3 HDD3 V2 V3 In this case, the Select Firmware Components page displays the following: Table 22.
View vSphere Lifecycle Manager status in Dell EMC administration console The following are the possible vSphere Lifecycle Manager statuses that you can view in vSphere Lifecycle Manager column: • • • Register (applicable only for vCenter 7.0 and later) — Displays when the vSphere Lifecycle Manager is not registered. Unregister (applicable only for vCenter 7.0 and later)—Displays when vSphere Lifecycle Manager is already registered. NA—Displays only if the registered vCenter is earlier than version 7.0.
The cluster profile created in OMIVV is selected as Firmware and Drivers AddOn in vSphere Lifecycle Manager. For more information about cluster profile, see Cluster profile. To set up an image for selected cluster and associate OMIVV as a Firmware and Drivers Addon, perform the followings tasks: 1. In the vSphere Client, click Hosts and Clusters, and then select a cluster that you want to manage using an image. 2. On the Updates page, in the left pane, expand Hosts, and then click Images. 3.
4. If the host status is Unknown, ensure that the host is added to a host credential profile in OMIVV and inventory is run successfully. Hardware compatibility check vSphere Lifecycle Manager provides an option to perform the hardware compatibility check for vSAN cluster before performing firmware remediation. Hardware compatibility check compares the firmware and driver present in the image against the listed hardware and supported driver in the vSAN Hardware Compatibility List (HCL).
• Select a cluster profile that is applicable for the selected cluster and save the image. Scan firmware compliance Command: POST https://{VC IP/FQDN}/api/esx/settings/clusters/{cluster ID}/software?vmw-task=true&action=scan { } "spec" : { "message": "test commit" } Description: Scans all the hosts in the cluster against the cluster's desired state. The result of this operation can be queried by calling the cis/tasks/{task-id} where the task-id is the response of this operation.
"target": { "version": "25.5.5.0005" } } "key": "" } ], "notifications": { "info": [ { "id": "[vCenter:][Cluster: ][Host: ] The host is non-compliant", "time": "2020-02-04T10:47:54.
"target": { "id": "domain-c8", "type": "ClusterComputeResource" }, "result": { "start_time": "2020-02-12T17:52:09.264Z", "commit": "", "end_time": "2020-02-12T18:03:59.
{ "host": "host-13", "type": "HOST", "check_statuses": [], "status": "OK" }, Remediate cluster Command: POST https://{{VC IP/FQDN}/}}/api/esx/settings/clusters/{cluster ID}/software?vmw-task=true&action=apply { "accept_eula" : true } Description: Applies the desired state associated with the given cluster to hosts within the cluster. HTTP response codes: 200. For the list of all the response codes, see Response codes.
3. To enable the System Lockdown Mode, click Turn On. This option restricts changes to the System configurations (including firmware and BIOS version) in the system. 4. To disable the System Lockdown Mode, click Turn Off. This option enables changes to the System configurations (including firmware and BIOS version) in the system. If you try to configure the System Lockdown Mode for 13G and earlier PowerEdge servers, you are prompted with a message that this feature is not supported on this platform. 5.
16 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.
Table 25. Privilege groups Group name Description Privilege group—Dell.Configuration Perform Host-related tasks, Perform vCenter-related tasks, Configure SelLog, Configure ConnectionProfile, Configure ClearLed, Firmware Update Privilege group—Dell.Inventory Configure inventory, Configure warranty retrieval, Configure readonly Privilege group—Dell.Monitoring Configure monitoring, monitor Privilege group—Dell.
• • • Dell.Configuration.Firmware Update • • • • • • • Configure HW Configuration Profile Configure Hypervisor Deployment Profile Configure Connection Profile Assign identity Deploy Dell.Configuration.
17 Frequently Asked Questions-FAQ Use this section to find answers to troubleshooting questions. This section includes: • • Frequently asked questions (FAQ) Bare-metal deployment issues Frequently Asked Questions-FAQ This section contains some common questions and solutions.
NOTE: Host inventory can also fail when OMIVV fails to enable WBEM services on hosts running ESXi 6.5. See Create host credential profile for more information about WBEM service. On running fix noncompliant vSphere hosts wizard, the status of a specific host is displayed as Unknown When you run the fix noncompliant vSphere hosts wizard to fix noncompliant hosts, the status of a specific host is displayed as "Unknown." The unknown status is displayed when iDRAC is not reachable.
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.
Version Affected: All Running firmware update may display an error message, The firmware repository file does not exist or is invalid. While running the Firmware Update wizard, at cluster level, an error message may be displayed: The firmware repository file does not exist or is invalid. This may be due to a daily background process that was unable to download and cache the catalog file from the repository. This occurs if the catalog file is not reachable at the time the background process runs.
Chassis global health still healthy when some of power supply status has changed to critical The global health of the chassis about the power supply is based on the redundancy policies and whether the chassis power needs are satisfied by the PSU that are still online and functional. So even if some of the PSU is out of power, the overall power requirement of the chassis are met. So the global health of the chassis is Healthy.
Port Number Protocols Port Type Maximum Encryptio n Level Directi on Destination Usage Description 443 WSMAN TCP 128-bit In/Out OMIVV appliance to or from iDRAC iDRAC communication iDRAC, or CMC, or OME-Modular communication, used to manage and monitor the managed nodes. 445/139 SMB TCP 128-bit Out OMIVV appliance to CIFS CIFS communication To communicate with Windows share.
Unable to view new iDRAC version details listed on vCenter hosts and clusters page Resolution: After successful completion of a firmware update task in the vSphere web client, refresh the Firmware Update page and verify the firmware versions. If the page displays the old versions, go to the Host Compliance page in OpenManage Integration for VMware vCenter, and check the CSIOR status of that host. If CSIOR is not enabled, enable CSIOR and reboot host.
5. Click UnregisterExtension. 6. Enter the extension key to unregister com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient, and then click Invoke method. 7. Go to vSphere Client and clear the check box against the Dell Provider for all the Proactive HA enabled cluster. 8. Click Home > Content > HealthUpdateManager. 9. Click QueryProviderList > Invoke method. 10. Copy the provider ID string value, and close the window. 11.
Does OMIVV support VMware vCenter server appliance Yes, OMIVV supports the VMware vCenter Server appliance since v2.1. A server may show as non-compliant with CSIOR status, "Unknown" Resolution: An unknown CSIOR state indicates a non-responsive iDRAC on the host. A manual iDRAC reset on the host fixes this issue.
Available OMIVV appliance version displays wrong information when the available version is lesser than the current version In the OMIVV Admin console, under Appliance Management, Available Virtual Appliance Version displays the modes RPM and OVF as available. NOTE: It is recommended that update repository path is set to the latest version and downgrading the virtual appliance version is not supported.
Drift Detection shows noncompliant for Modular servers that has PCIe card in the FX chassis The System profiles searches for exact instance(FQDD) while comparing with the baseline, which works successfully on Rack servers (identical), but may have few restrictions in Modular servers. For example, in FC640, the System profile (Baseline) created from one modular server shows drift for other modular servers in the same FX chassis because of FQDD mismatches. Version Affected: 4.1 and later.
When upgrading or downgrading some iDRAC firmware versions using OMIVV, even when the 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.
Non-compliant 11G PowerEdge servers are retained in OMIVV inventory after backup and restore After performing the backup and restore operation in OMIVV, the non-compliant and non-inventoried 11G hosts are still associated to the Host Credential Profile. However, if you try to fix the configuration compliance and run a fresh inventory, the job fails on the unsupported 11G servers. Resolution: 11G servers are not supported with OMIVV 5.0.
A server with Unknown status in the earlier version is not listed on the Bare-metal Servers page after backing up and restoring to a latest OMIVV version After restoring a backup from earlier versions, unsupported servers (11G and earlier) are removed from the bare-metal inventory. Servers whose generation has not been determined by the earlier version before the backup will also be removed. Resolution: Rediscover the server. If the missing server is supported, then it is listed in the bare-metal inventory.
Warranty job is not running for certain hosts In a PSC environment with multiple vCenters, if you add a host using FQDN to one vCenter and IP to another vCenter, warranty job runs only for one host instance. Resolution: Remove the disconnected host instance from the host credential profile and run the inventory and warranty job. Version Affected: 5.
• • • For VMware vCenter Server Appliance, go to /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity and for Windows vCenter, go to C:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui\vc-packages \vsphere-client-serenity folder in the vCenter appliance and see if the old data exists, such as: com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient-X.0.0.XXX. Manually delete the folder corresponding to the earlier OMIVV version.
A System specific attributes iDRAC Table 28.
Attribute Name Display Attribute Name Group Display Name 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 Ndc1PcieLink2 Integrated Network Card 1 PCIe Link2 Integrated Devices Ndc1PcieLink3 Integrated Network Card 1 PCIe Link3 In
Attribute Name Display Attribute Name Group Display Name 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 Primary DNS iSCSI Initiator Parameters IscsiInitiatorSecDns Secondary DNS iSCSI Initiator Parameters IscsiInitiatorSubnet Subnet Mask iSCS
B Additional information The following Dell technical white papers available at delltechcenter.
C Customization attributes Table 33. 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.
D Component vs. baseline version comparison matrix Table 34. Component vs. baseline version comparison matrix Drift Type Hardware Firmware Associated Baseline Target Component Scenario Compliance Status Available Available Hardware component matches with the associated baseline. Compliant Available Available Hardware attributes of the component not matches with the associated baseline. Non-compliant Not available Available The comparison status is not calculated and ignored.
Drift Type Available Not available Driver component version is available in the associated baseline but the component is available in host. Non-compliant Not available Not available The comparison status is not calculated and ignored. Compliant Component vs.
E Response codes Table 35. Response Codes Response codes Description 200 Successful generation/return of task information or task list. 202 Successful start of any task.
