OpenManage Integration for VMware vCenter Version 5.2 User's Guide October 2020 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. © 2010 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Introduction................................................................................................................10 Whats new in this release................................................................................................................................................ 10 OpenManage Integration for VMware vCenter features.........................................................................................
Chapter 7: Capture baseline configuration using cluster profile...................................................49 Cluster profile.....................................................................................................................................................................49 Create cluster profile........................................................................................................................................................49 Edit cluster profile...............
Chapter 12: Manage OMIVV jobs.................................................................................................. 73 Deployment jobs................................................................................................................................................................ 73 Discovery jobs....................................................................................................................................................................
Schedule warranty retrieval jobs............................................................................................................................103 Chapter 16: Chassis Management.............................................................................................. 105 View Dell EMC chassis information.............................................................................................................................105 View chassis inventory information...........................
Dell Infrastructure Deployment role............................................................................................................................ 145 About privileges................................................................................................................................................................145 Chapter 19: Frequently Asked Questions-FAQ............................................................................ 147 Frequently Asked Questions-FAQ...............
After backup and restore of OMIVV, alarm settings are not restored ........................................................ 155 OS deployment fails when NPAR is enabled on a target node and disabled in System Profile..............156 Available OMIVV appliance version displays wrong information when the available version is lesser than the current version..........................................................................................................................
OMIVV instance is not removed from vCenter after resetting OMIVV appliance to factory settings. 162 OMIVV shows only BIOS and iDRAC attributes on the Profile Settings page of System Profile.......... 163 OS deployment is completed with unknown error.............................................................................................163 Chassis Management Controller (CMC) firmware update fails in FX2 chassis..........................................163 ISO profile deployment fails in OMIVV...........
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.
Table 1. OMIVV features (continued) Features Description Detect key hardware faults and perform virtualization-aware actions. For example, migrate workloads or place host in a maintenance mode. Provide intelligence such as inventory, events, alarms to diagnose server and chassis problems. Support for VMware Proactive HA feature. Firmware updates The cluster-aware server firmware update includes the following: Update supported servers to the most recent version of BIOS and firmware.
NOTE: From OMIVV 5.0 onwards, only VMware vSphere Client (HTML-5) is supported and the vSphere Web Client (FLEX) is not supported.
2 Log in to Dell EMC OMIVV 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 1. Go to https://. The account lockout duration is one minute. You cannot start a new session when the account is locked.
4. Under vCenter User Account, perform the following steps: a. In the vCenter User Name box, enter the username of administrator or a non-administrator username with the required privileges. b. In the Password box, enter the password. c. In the Verify Password box, enter the password again. d. Select the Register vSphere Lifecycle Manager check box. Selecting the Register vSphere Lifecycle Manager check box allows you to use vSphere Lifecycle Manager feature from vCenter 7.0 and later. 5. Click Register.
○ Register extension ○ Unregister extension ○ Update extension ● Global ○ Cancel task ○ Log event ○ Settings ● Health Update Provider ○ Register ○ Unregister ○ Update ● Host ○ CIM ￭ CIM Interaction ● Host.
2. In vSphere Client (HTML-5), expand Menu, click Administration → Roles. 3. From the Roles provider drop-down list, select a vCenter server. 4. From the Roles list, select Dell-Operational, and then click PRIVILEGES. 5. To assign the Dell privileges, click the edit icon [ The Edit Role page is displayed. ]. 6. In the left pane, click Dell, and then select the following Dell privileges for the selected role, and then click NEXT: ● ● ● ● ● Dell.Configuration Dell.Deploy-Provisioning Dell.Inventory Dell.
To remove OpenManage Integration for VMware vCenter, unregister OMIVV from the vCenter server by using the Administration Console. 1. Go to https://. 2. On the VCENTER REGISTRATION page, in the vCenter Server IP or Hostname table, click Unregister. NOTE: Ensure to select the correct vCenter because OMIVV can be associated with more than one vCenter. 3. To confirm the unregistration of the selected vCenter server, in the UNREGISTER VCENTER dialog box, click Unregister.
Restart OMIVV appliance 1. On the APPLIANCE MANAGEMENT page, click Restart the Virtual Appliance. 2. To restart the OMIVV appliance, in the Restart Virtual Appliance dialog box, click Apply. Upgrade OMIVV appliance and repository location ● To ensure that all data is protected, perform a backup of the OMIVV database before updating the OMIVV appliance. See Manage backup and restore on page 20.
For the available OMIVV appliance version, the applicable RPM and OVF OMIVV appliance upgrade mechanisms are displayed with a tick mark [ ]. 2. To upgrade the OMIVV plug-in from an existing version to the available version, perform one of the following steps: ● To upgrade using RPM that is available in Update Repository Path, ensure that Update Repository Path is set to the path: https://linux.dell.
2. Turn off the older OMIVV appliance from vCenter. 3. Deploy the new OpenManage Integration appliance OVF. 4. Power on the OpenManage Integration new appliance. 5. Set up the network and time zone for the new appliance. NOTE: It is recommended that you retain the identity (IP or FQDN) of the earlier OMIVV appliance for the new OMIVV appliance. 6. The OMIVV appliance comes with default certificate. If you want to have a custom certificate for your appliance, update the same.
1. Go to https:\\. 2. In the Login dialog box, type the password. 3. In the left pane, click BACKUP AND RESTORE. Configure backup and restore The backup and restore function backs up the OMIVV database to a remote location (NFS and CIFS) from which it can be restored later. The profiles, configuration, and host information are in the backup. It is recommended that you schedule automatic backups to guard against data loss. NOTE: The NTP settings are not saved and restored. 1.
● Repository Profiles will use only 64-bit bundles. NOTE: If you perform backup and restore from 4.x to 5.x, a warning symbol is displayed against the cluster profile name because OMIVV does not support 32-bit firmware bundle in 5.x. To use the latest changes for the cluster profile, edit the cluster profile. ● Firmware Update jobs that are scheduled on 11G servers are canceled. Ensure that the correct deployment mode is configured before performing the restore operation.
NOTE: If the OMIVV admin portal is taking a long time to load information, ensure that NTP settings are correct and the NTP server is reachable by the OMIVV virtual machine. Configure deployment mode For any of the mentioned deployment modes, ensure that you reserve sufficient memory resources to the OMIVV appliance using reservations. See vSphere documentation for steps about reserving memory resources.
4. Change the deployment mode to the required level. Extended monitoring Ensure to enable Extended Monitoring to support OpenManage Management Pack for vRealize Operations Manager. It is recommended to perform extended monitoring through the 'Medium' deployment mode. Ensure to enable SNMP Trap Monitoring to support SNMP alerts for OpenManage Management Pack for vRealize Operations Manager. This allows the user to monitor the health status of the server or chassis in real time. 1.
1. Go to https://. 2. In the Login dialog box, enter the password. 3. In the left pane, click ALERT MANAGEMENT. To enter new vCenter alert settings, click Edit. 4. Enter numeric values in the following fields: By default, the counts of the current number of alerts are displayed. ● Maximum number of alerts ● Number of days to retain alerts ● Timeout for duplicate alerts (seconds) 5. To save your settings, click Apply.
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. c.
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.
6. Click Change Admin Password. 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 on page 22. 3. On the Date and Time tab, select Synchronize date and time over the network. The NTP Servers window is displayed. 4.
Read-only user role There is a unprivileged user called "readonly" with shell access for diagnostic purposes. The read-only user has limited privileges to run few commands.
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.
3. To view the health status of host at data center-level, select a data center, and then click Monitor > OMIVV Datacenter Information > Warranty. Licenses The Licenses section displays the following information: ● Count of all hosts and vCenter license ● Count of available host and vCenter licenses ● Count of host and vCenter licenses that are in use. To purchase license, on the Dashboard page, under the Licenses section, click BUY LICENCE.
For more information, see Management Compliance on page 68 ● Chassis Credential Profile For more information, see Chassis credential profile on page 42 ● Cluster Profile For more information, see Cluster profile on page 49 ● Deployment For more information, see Deployment checklist on page 62 Monitor hosts and chassis using dashboard 37
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.
The AD credential can be either same or separate for both the iDRAC and hosts. d. In the Host Root area, enter the local host credentials or AD credentials. The default username is root. ● To enter the local host credentials, perform the following: ○ Enter password. Host password is required only for hosts running ESXi 6.5 U3 and earlier versions. To skip this step for ESXi 6.7 and later versions, ensure that the Use Host Credentials check box is cleared. If password is entered for host running ESXi 6.
○ Change password. ○ To download and store the iDRAC certificate and validate it during all future connections, select the Enable Certificate Check check box. ● To change the credentials for an iDRAC that is already configured and enabled for AD, select the Use Active Directory check box. NOTE: The iDRAC account requires administrative privileges for updating firmware and deploying an Operating System (OS). ○ Change the username in the Active Directory User Name box.
NOTE: The Date Modified and Last Modified By fields include changes that you perform using the vSphere Client interface for a host credential profile. Any changes that the OMIVV appliance performs on the respective host credential profiles do not affect these two fields. View host credential profile 1. On the OMIVV home page, click Compliance & Deployment > Host Credential Profile.
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.
● When you change the credentials ● If the chassis is newly selected 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.
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. A table displays all the chassis credential profile along with the following information: ● Profile Name—The name of the chassis credential profile ● Description—Profile description ● Chassis IP/Host Name—The chassis IP or hostname link.
To delete the chassis credential profile, click OK for the delete confirmation message.
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.
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. After creating the catalog, it downloads, parses, and the status is displayed on the home page of the repository profile. Successfully parsed repository profiles are available during the cluster profile creation and during the firmware update. Edit repository profile 1.
6. On the Summary page, review the profile information, and then click FINISH. Edit Validated MX Stack Catalog 1. On the Repository Profile page, select Validated MX Stack Catalog, and then click EDIT. 2. You can only edit the following: a. The catalog description. b. The Synchronize with repository location check box. To update only the profile name or review information, clear the Synchronize with repository location check box so that the catalog remains unchanged in OMIVV.
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.
d. Click OK. The selected cluster is displayed on the Associate Cluster(s) page. 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.
1. On the OMIVV home page, click Complinace & Deployment > Profiles > Cluster Profile. 2. Select a cluster profile that has warning symbol against the profile name. 3. Click UPDATE PROFILES. 4. To update the associated profiles to the latest, click OK. After you update the profiles, the baseline cannot be reverted. Warning symbol disappears when the cluster profile is synced with the updated repository profiles or system profile. Delete cluster profile 1.
8 Manage bare-metal servers View bare-metal servers On the Bare-metal Servers page, you can: ● View the bare-metal servers discovered using auto discovery and manual discovery. The information such as Service Tag, Model name, iDRAC IP, Server Status, System Lockdown Mode, Compliance Status, and iDRAC License Status are displayed. The following are the different states of the bare-metal servers: ○ Unconfigured—The server is added to OMIVV and waiting to be configured.
Auto discovery Auto discovery is the process of adding bare-metal server. Once a server is discovered, use it for operating system and hardware deployment. Auto discovery is an iDRAC feature that removes the need to manually discover a bare-metal server using OMIVV. Auto discovery prerequisites Before attempting to discover the PowerEdge bare-metal servers, ensure that OMIVV is installed. The PowerEdge servers with iDRAC Express or iDRAC Enterprise can be discovered into a pool of bare-metal servers.
● For iDRAC9: Go to iDRAC Settings > Users > Local Users. 4. In the Local Users tab, locate any administrative accounts other than root. 5. To disable the account, under User ID, select the ID. 6. Click Next. 7. In the User Configuration page, under General, clear the Enable User check box. 8. Click Apply. 9. To re-enable each administrative account, repeat steps 1–8 after you have successfully set up auto discovery, but select the Enable User check box now, and click Apply.
e. Enter END IP. The End IP must be the last octet of the IP and greater than Start IP. f. Enter Exclusion List. Exclusion list is the list of IPs that you want to exclude from the list. The value you enter in the Exclusion List must be within Start IP and End IP ranges. The values must be comma separated, each value can be a last octet value or a range of last octet values separated by -. For example: To discover all the IPs from 100.100.100.1 to 100.100.100.50 excluding IPs from 100.100.100.25 to 100.100.
1. To renew iDRAC license, on the OMIVV home page, click Compliance & Deployment > Deployment. 2. Select a bare-metal server for which iDRAC license is noncompliant, and click PURCHASE/RENEW IDRAC LICENSE. 3. Log in to the Dell Digital Locker and update or purchase a new iDRAC license. 4. After you install an iDRAC license, click REFRESH.
9 Manage deployment profiles System profile The system profile captures the component-level settings and configuration of iDRAC, BIOS, RAID, Event Filters, FC, and NICs. These configurations can be applied to other identical servers during an operating system deployment on bare-metal servers. The system profile can be used in cluster profile to maintain baseline for configuration. Prerequisites Before you create or edit the system profile, ensure that: ● The CSIOR feature is enabled on the reference server.
1. On the OMIVV home page, click Compliance & Deployment > Profiles > System Profile > CREATE NEW PROFILE. 2. On the Create System Profile page of the wizard, read the instructions, and then click GET STARTED. 3. On the Name and Description page, do the following: a. Enter profile name and description. The description field is an optional field. b. Select any of the following system profile types: ● Basic—Displays the minimal set of attributes for iDRAC, BIOS, RAID, NIC, and FC.
Edit system profile It is recommended that you use Google Chrome to create or edit System Profile. 1. On the Create System Profile page, select a System Profile, and then click EDIT. 2. On the Name and Description page, change the profile name and description. The description is optional. NOTE: After creating the Basic or Advanced system profile, you cannot modify the profiles. 3. On the Reference Server page, to change the reference server that is either a host or a bare-metal, click SELECT.
● ● ● ● 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. To export the system profile information, click . . Delete system profile Deleting a system profile that is part of a running deployment task might cause the deletion job to fail. 1.
7. Click FINISH. View an ISO profile 1. On the OMIVV home page, click Compliance & Deployment > ISO Profile. A table displays all the ISO profiles along with the following information: ● ● ● ● Profile Name—The name of the profile Description—The profile description Installation Source—The ISO file location (NFS or CIFS) ESXi Base Version—The ESXi base version 2. If you want to remove or add the column names from the wizard, click 3. To export an ISO profile information, click . .
10 System profile and ISO profile deployment To deploy system profile and ISO profile, ensure that all the servers are met following requirements in your environment: ● All the servers are displayed in the System Profile and ISO Profile Deployment wizard. ● Specific hardware support information mentioned in the OpenManage Integration for VMware vCenter Compatibility Matrix. ● Minimum supported versions of the iDRAC firmware and BIOS are available.
To discover a bare-metal server, click DISCOVER. For more information about discovering bare-metal servers, see Manual discovery of bare-metal servers on page 54. ● System Profile To create a system profile, click CREATE. For more information about creating system profile, see Create system profile on page 57. ● ISO Profile To create an ISO profile, click CREATE. For more information about creating ISO profile, see Create an ISO profile on page 60.
Deploy ISO profile (ESXi installation) You can perform the deployment only on the compliant bare-metal servers. For more information, see View bare-metal servers on page 52. 1. To launch the deployment wizard, go to Compliance & Deployment > Deployment > DEPLOY. 2. On the System Profile and ISO Profile Deployment Checklist page of the deployment wizard, verify the deployment checklist, and then click GET STARTED. 3. On the Select Server (s) page, select one or more servers.
NOTE: In host credential profile, it is recommended that you associate the user that is used to discover the bare-metal, else the discovered user gets disabled in iDRAC after operating system deployment. 10. On the Configure Network Settings page, perform the following tasks: a. Enter a Fully Qualified Host Name (FQDN) for the server. A fully qualified domain name for the hostname is mandatory. The use of localhost for the FQDN is not supported. The FQDN is used when adding the host to vCenter.
8. From the ISO Profile drop-down menu, select an appropriate ISO profile, and then click NEXT. 9. To create a preview job on iDRAC, on the Configuration Preview page, select an iDRAC IP, and then click PREVIEW. Configuration Preview is an optional task. The system profile preview operation may take few minutes to complete. The comparison status is displayed in the Result column. The following are the comparison results: ● Completed—The preview job is successfully run.
Table 4. Server states in the deployment sequence Server state Description Unconfigured The server is added to OMIVV and is waiting to be configured. Configured The server is configured with all hardware information that is required for a successful operating system deployment.
11 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.
If hosts with WBEM non-compliance exist, ensure to manually fix the conditions for those hosts that caused the WBEM service enablement to fail. You can fix the error conditions by viewing them in the user logs. Enable OMIVV to enable the WBEM service for those hosts during inventory. 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.
To stop all the test connections, click ABORT TEST. 6. Click OK. The selected hosts are added to the selected host credential profile and inventory is triggered. Configuration Compliance The Configuration Compliance page displays the compliance status that is based on the drift detection for all the clusters that are associated with the cluster profile.
● ● ● ● ● ● ● ● Service Tag—Indicates the Service Tag of the host. Drift Status—Indicates the drift status (non-compliant or failed). Instance—Indicates the hardware component name. Group—Indicates the group name of the attributes. Attribute Name—Indicates the attribute name. 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.
12 Manage OMIVV jobs The Jobs page displays the following jobs: ● ● ● ● ● ● ● Deployment Discovery Firmware Updates System Lockdown Mode Drift Detection Inventory Warranty OMIVV clears older jobs when the total number of jobs reaches 500 that includes user-created (for example, deployment jobs) and OMIVV-created (for example, health metric collection job) jobs. If the number of jobs exceeds 500, the older 500 jobs are deleted.
The selected jobs are then cleared from the Deployment Jobs page. Discovery jobs After the discovery task is created, you can track the job status on the Discovery Jobs page. 1. On the OMIVV home page, click Jobs > Discovery Jobs. A table displays all the discovery jobs along with the following information: ● ● ● ● Name—The discovery job name Description—The job description Scheduled Time—The date and time when the job is scheduled. Status—The status of the discovery job.
WARNING: If you stop a firmware update job that is already submitted to MX chassis, the firmware might still get updated on the host. OMIVV reports the job as canceled. 5. If you want to purge earlier firmware update jobs or scheduled firmware updates, click CLEAR COMPLETED. The Purge Firmware Update Jobs dialog box is displayed. You can only purge jobs that are canceled, successful, or failed and cannot purge scheduled or active jobs. 6.
● ● ● ● ● ● ● Name—The System Lockdown Mode job name Description—The job description Schedule Time—The date and time when the System Lockdown Mode job is scheduled. vCenter—The vCenter name Status—The status of the System Lockdown Mode job Collection Size—The number of servers in the System Lockdown Mode job Progress Summary—The job progress details of the System Lockdown Mode job 2. To view the more information about the servers in the System Lockdown Mode job, select a System Lockdown Mode job.
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. On the OMIVV home page, click Jobs > Inventory > Host Inventory. 2. Select a vCenter to view all the associated hosts inventory job information.
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. You can also modify the inventory schedule from the Settings > Data Retrieval Schedule > Inventory Retrieval page. 1. On the Jobs page, select a vCenter instance, and click EDIT SCHEDULE. The Inventory Data Retrieval dialog box is displayed. 2.
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.
○ Scheduled ● Duration (MM:SS)—The duration of the warranty job in MM:SS ● Start Date and Time—The date and time when the warranty job started. ● End Date and Time—The time the warranty job ended. 2. To run the chassis warranty job on-demand, click RUN NOW.
13 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 To To To 2. Click export the logs data, click . sort the data in the grid, click a column header. navigate between pages, click previous and next icons. refresh the logs, click the refresh icon on the upper-left corner.
14 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 on page 82. ● Configure the latest appliance version notification. For more information, see Configure latest appliance version notification on page 82. ● Override severity for Proactive HA alerts. For more information, see Override severity of health update notification on page 86.
To receive periodic notification about the availability of latest version (RPM, OVF, RPM/OVF) of OMIVV, perform the following steps to configure the latest version notification: 1. On the OMIVV home page, click Settings > Appliance Settings > Notifications > Latest Version Notification. 2. Select the Enable Latest Version Notification (Recommended) check box. 3. To receive the latest appliance version notification, select the day and time. 4. Click APPLY.
Proactive HA events Based on the components supported by VMware for Proactive HA, the following events are registered by the Dell Inc provider during its registration with vCenter: Table 5.
Table 6.
● A cluster with DRS enabled is created and configured in the vCenter console. To enable DRS on a cluster, see the VMware Documentation. ● All hosts that are part of the cluster should be part of a host credential profile and successfully inventoried. ● For a modular server, the corresponding chassis must be added to the chassis credential profile and successfully inventoried. 1. In vSphere Client, expand Menu, and then select Hosts and Clusters. All the hosts and clusters are displayed in the left pane. 2.
● Dashboard > Quick References > START INITIAL CONFIGURATION WIZARD 1. On the Welcome page, read the instructions, and then click GET STARTED. 2. On the Select vCenter page, from the vCenters drop-down menu, select a specific vCenter or All Registered vCenters, and then click NEXT. NOTE: If you have multiple vCenter servers that are part of the same PSC registered with the same OMIVV appliance, and if you choose to configure a single vCenter server, repeat step 2 until you configure each vCenter. 3.
● Firmware update using OMIVV This setting can be overridden while updating the firmware using OMIVV. However, overriding the setting will not have any impact on the settings that is done on the Firmware Update Settings page. ● Firmware remediation using vSphere Lifecycle Manager This setting cannot be overridden while performing firmware remediation. 1. Select the Clear iDRAC Jobs and reset iDRAC check box. 2. Click APPLY.
● Maximum Host Connection Licenses—the number of host connections that were purchased (with a maximum of 2000 hosts supported for a single OMIVV instance). ● In Use—the number of vCenter connection or host connection licenses in use. For host connection, this number represents the number of hosts (or servers) that have been inventoried. ● Available—the number of vCenter connections or host connection licenses available for future use.
The Troubleshooting Bundle dialog box is displayed. 2. In the Troubleshooting Bundle dialog box, click CREATE. Depending on the size of the logs, creating the bundle may take some time. 3. To save the file, click DOWNLOAD. Reset iDRAC Resetting iDRAC performs a normal iDRAC reboot. After resetting iDRAC, the iDRAC is normally restarted but not the host. After resetting, iDRAC can be used only after few minutes. Reset only if an iDRAC is not responding on an OMIVV appliance.
15 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.
View alarms and events setting After you configure alarms and events, you can view if the vCenter alarms for hosts are enabled and which event posting level is selected on the Settings tab. 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 on page 92.
Table 9. Virtualization events (continued) Event name Description Severity Recommended action DellSoftware defined alertStorageSoftwareDefinedSubSystemWa storage subsystem rning warning Warning No action Dell-alertTemperatureProbeReadWarning Unable to read Temperature Sensors Warning No action Dell-alertTemperatureProbeChangeFailure Temperature increase Error Critical Check the chassis event log for fan issues and fix any issues present.
Table 9.
Table 9.
Table 9.
Table 9.
Table 9.
Table 9.
Table 9. Virtualization events (continued) Event name Description Severity Recommended action Power supply redundancy is lost The current power Critical operational mode is non-redundant because of a power supply exception, a power supply inventory change, or a system power inventory change. The system was previously operating in a power redundant mode Check the event log for power supply failures.
Table 9. Virtualization events (continued) Event name Description Severity Recommended action because of a power supply exception, a power supply inventory change, or a system power inventory change. The system was previously operating in a power redundant mode Power supply redundancy is degraded The current power Warning operational mode is non-redundant because of a power supply exception, a power supply inventory change, or a system power inventory change.
Table 9. Virtualization events (continued) Event name Description Severity Recommended action Critical Remove and reinstall failed fans or install additional fans configuration change occurred, which requires additional fans The fans are not redundant.
1. On the OMIVV home page, click Settings > vCenter Settings > Data Retrieval Schedule > Warranty Retrieval. 2. Select the Enable Warranty Data Retrieval (Recommended) check box. In PSC environment with multiple vCenter servers, if the schedule for individual vCenter is different and you select the All Registered vCenters option to update the warranty schedule, the warranty schedule settings page displays the default schedule. 3. Select the warranty data retrieval day and time, and click APPLY.
16 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. ● Health—Displays the health status of chassis.
Viewing hardware inventory information for chassis You can view information about the hardware inventory 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 Hardware. Table 10.
Table 10. Hardware inventory information (continued) Hardware inventory: Component Navigation through OMIVV Information information about the temperature sensors is displayed for chassis and associated modular servers. 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 I/O Modules. OR ● On the Overview page, click I/O Modules.
Table 10. Hardware inventory information (continued) Hardware inventory: Component Navigation through OMIVV Information NOTE: PCIe information is not applicable for M1000e chassis. iKVM—Only for PowerEdge M1000e ● 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 iKVM. OR ● On the Overview page, click iKVM.
○ Redundancy Mode ○ Hardware Version ● IPv4 Information ○ IPv4 Enabled ○ DHCP Enabled ○ IP Address ○ Subnet Mask ○ Gateway ○ Preferred DNS Server ○ Alternate DNS Server ● IPv6 Information ○ IPv6 Enabled ○ DHCP Enabled ○ IP Address ○ Link Local Address ○ 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 conf
● ● ● ● ● ● ● ● Health State Slot Slot Assignment Disk Name Capacity Bus protocol Media If a disk in the PowerEdge MX chassis is unassigned, its slot assignment is shown as NA. For M1000e chassis, if you have a storage module, the following storage details are displayed in a grid view without any additional information: ● ● ● ● ● ● ● Name Model Service Tag IP Address (Link to storage) Fabric Group Name Group IP Address (link to storage group).
● ● ● ● ● ● ● Hostname Service Tag Model iDRAC IP Location Slot Location Last Inventory 4. To view more information about host, select a host. View related chassis information The Chassis Relation section shows the relationship between chassis in an MX chassis that is deployed in the MCM mode. NOTE: Related chassis information is applicable only for a PowerEdge MX chassis that is configured in an MCM group. 1. On the OMIVV home page, click Hosts & Chassis > Chassis > Chassis List.
Chassis and host management using the Unified Chassis Management IP If an iDRAC IPv4 is disabled for a host that is managed using host credential 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 credential profile to manage the chassis and its associated hosts.
MX chassis firmware update Before scheduling the firmware update, ensure that the following conditions are met in the environment: ● Ensure that the MX chassis is part of chassis credential profile and successfully inventoried. ● If any of its hosts are undergoing firmware updates, chassis firmware cannot be updated. NOTE: By using the MX chassis firmware update feature, you can update only management module firmware. 1.
17 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. ● Health—displays the health status of hosts. To filter by health status of each Dell EMC host, click the filter icon present against the search. ● vCenter—displays vCenter IP address of the host.
Table 12. OMIVV Host Information (continued) Information Description value. This is applicable for PowerEdge servers that support Fault Resilient Memory (FRM) option, running ESXi 5.5 or later version. The four different values of BIOS attribute are: ● 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 FRM.
Table 13. OMIVV host health Information Description OMIVV Host Health Component health is a graphical representation of the status of all major host server components: Server Global status, Server, Power supply, Temperature, Voltages, Processors, Batteries, Intrusion, Hardware log, Power management, Power, and Memory. The chassis health parameters are applicable for models VRTX version 1.0 and later, M1000e version 4.4 and later. For versions less than 4.
Table 14. Hardware information for a single host (continued) Hardware: Component Information ○ SWITCHING ○ BATTERY ○ UPS ○ CONVERTER ○ REGULATOR ○ AC ○ DC ○ VRM ● Location—displays the location of the power supply, such as slot 1. ● Output (Watts)—displays the power in watts. Memory ● Memory Slots—displays the Used, Total, and Available memory count. ● Memory Capacity—displays the Installed Memory, Total Memory Capacity, and Available Memory. ● Slot—displays the DIMM slot.
NOTE: When the hosts are managed by using chassis profile, if you click Storage, and then select the following from the View drop-down menu: ● Enclosures—The Controller ID of the storage enclosure is displayed as 0 instead of the correct Controller ID. ● Physical Disks—The media type for HDD is displayed as Magnetic Drive instead of Hard Disk Drive. Table 15. Storage details for a single host Information Description Virtual Disks ● ● ● ● ● Name—displays the name of the virtual drive.
Table 15. Storage details for a single host (continued) Information Description ○ REMOVED ○ CLEARED ○ SMART ALERT DETECTED ○ 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: ● ● ● ● ● ● ● ● ● ● ● ● Controllers ○ 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.
● ● ● ● Name—displays the name of all the firmware on this host. Type—displays the type of firmware. Version—displays the version of all the firmware on this host. Installation Date—displays the installation date. NOTE: When the hosts are managed using the chassis credential profile, the firmware inventory data show few extra components such as Life Cycle Controller and Software RAID. You can launch firmware update and configure system lockdown mode wizards from this page.
View system event log information of a single host System event log (SEL) provides status information for hardware that is discovered by OMIVV and displays the following information: ● Status—There are several status icons such as Informational (blue exclamation point), Warning (yellow triangle with exclamation point), Error (red X), and Unknown (a box with a ?). The severity levels are defined as: ○ Info ○ Warning ○ Error ● Time (Server Time)—Indicates the time and date when the event occurred.
Table 16. Overview of data centers and clusters (continued) Information Description Warranty Summary Displays the warranty status for the selected host.
Table 17. Hardware information for data centers and clusters (continued) Hardware: Component Information ● ● ● ● Part Name—displays the FRU part name. Part Number—displays the FRU part number. Manufacturer—displays the name of the manufacturer . Serial Number—displays the serial number of the manufacturer. ● Manufacture Date—displays the manufacture date. Hardware: Processor ● ● ● ● ● ● ● Hardware: Power Supply ● Host—displays the hostname. ● Service Tag—displays the service tag of the host.
Table 17. Hardware information for data centers and clusters (continued) Hardware: Component Information ● Manufacturer—displays only the manufacturer name. ● MAC Address—displays the NIC MAC address. Hardware: PCI Slots Host—displays the hostname. Service Tag—displays the service tag of the host. Slot—displays the slot. Manufacturer—displays the manufacturer name of the PCI slot. ● Description—displays the description of the PCI device. ● Type—displays the PCI slot type.
Table 18. Storage details for a data center and cluster (continued) Storage: disks Description ● ● ● ● ● Connector ID—displays the connector ID. Enclosure ID—displays the enclosure ID. Device ID—displays the device ID. Bus Protocol—displays the bus protocol. Remaining Rated Write Endurance—displays the SSD remaining write endurance. ● Hot Spare Type(Not applicable for PCIe)—shows the hot spare type. The options include: ○ No—there is no hot spare.
Table 18. Storage details for a data center and cluster (continued) Storage: disks Description ● Disk Cache Policy—displays the default cache policy that is supported by the controller. The options include: ○ Enabled—cache I/O ○ Disabled—direct I/O View firmware information of a data center and cluster The following information about each firmware component is displayed: ● ● ● ● Host—displays the name of the host. Service Tag—displays the service tag of the host.
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. Running concurrent firmware update on two hosts of the same cluster is not allowed. NOTE: In a multi-appliance environment, to perform firmware update on cluster or host, ensure that the appliance registered with target vCenter is loaded.
● 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.
8. On the Select Firmware Components page, select the firmware components that require an update, and then click NEXT. 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.
5. To export the catalog, select a catalog and click Export. 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.
c. Create a repository profile in OMIVV using the downloaded catalog. For more information about creating a repository profile, see Create repository profile on page 46. 4. Based on the firmware repository profile you have selected, select an appropriate bundle, and then click NEXT. Only 64-bit bundles are supported. NOTE: Only one bundle can be selected for OEM (debranded) servers even if they are of different models.
● The DRS is enabled. NOTE: For a stand-alone host, the DRS check is not applicable. To skip the prerequisites check, clear the Check Prerequisites check box on the Schedule Updates page. NOTE: Driver update is not supported on vSphere cluster and host. 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 host credential profile of the host for which the firmware update job is in progress.
a. Enter the Maintenance Mode timeout value between 60–1440 minutes. If the wait time goes beyond the specified time, the update jobs fail and enter maintenance task will be canceled or timed out. However, the components may get updated automatically when the host is restarted. By default, the following options are selected: ● Exit maintenance mode after firmware update completes—If you disable this option, host remains in maintenance mode.
If you change the firmware repository profile, a message is displayed indicating that the selected repository profile is not associated to baseline and using a different repository may affect the baseline comparison. 4. Based on the firmware repository profile you have selected, select an appropriate bundle, and then click NEXT. Only 64-bit bundles are supported. NOTE: Only one bundle can be selected for OEM (debranded) servers even if they are of different models.
Table 19. Example for multiple components with same type present in server (continued) Component Current version Available version HDD3 V1 V3 In this case, the Select Firmware Components page displays the following: Table 20.
vSphere Lifecycle Manager overview The vSphere Lifecycle Manager is a service that runs in vCenter server (applicable for vCenter 7.0 and later versions). vSphere Lifecycle Manager allows you to create baseline image that consists of ESXi image, firmware, and driver. It will make sure that every host in the cluster is aligned to the baseline image by performing compliance check. If any non-compliance, provides an option to remediate cluster.
Before managing the clusters using vSphere Lifecycle Manager, ensure that: ● The vSphere Lifecycle Manager is enabled in the Dell EMC administration console. For more information, see Register vSphere Lifecycle Manager in Dell EMC administration console on page 136. ● Hosts in the clusters are management compliant. For more information, see Management Compliance on page 68. ● The cluster profile is created for the selected cluster and the cluster profile is associated with firmware repository in OMIVV.
NOTE: After you upgrade OMIVV appliance, vSphere Lifecycle Manager check compliance task fails for image created with older version of OMIVV. To resolve this, save the image with latest version of Hardware Support Package (HSP). ● Incompatible: Displays when: ○ The cluster that is selected in vCenter is not associated with the selected Firmware and Drivers Addon (cluster profile in OMIVV) .
● Connectivity to the firmware repository and the required firmware components. To verify the prerequisites for firmware remediation, click RUN PRE-CHECK. The pre-check task status and results are displayed in the Image Compliance section. If pre-check fails for any host, fix the issue and rerun pre-check or continue with remediation task. Remediate cluster in vSphere Lifecycle Manager In the Image Compliance section, you can remediate an individual host or all hosts in the cluster at a time. a.
Example response: The following example contains only firmware non-compliance. "result": [ { "value": [ { "value": { "hardware_modules": [ { "value": { "current": { "version": "25.5.6.0009" }, "details": { "component_class": "PCI_DEVICE", "description": "PERC H730 Mini" } "notifications": { "info": [ { "id": "Different versions.", "time": "2020-02-04T10:47:54.422Z", "message": { "args": [], "default_message": "Different versions.", "id": "Different versions.
} ], Run remediation pre-check Command: POST https://{VC IP/FQDN}/api/esx/settings/clusters/{cluster ID}/software?vmw-task=true&action=check Description: Runs checks on the cluster before applying the desired state across all hosts in the cluster. Checks if all hosts in the cluster are in a good state to be updated with the desired state. HTTP response codes: 200. For the list of all the response codes, see Response codes on page 173.
"host": "host-16", "type": "HOST", "check_statuses": [ { { { "check": "name": { "args": [], "default_message": "Host Hardware support check.", "id": "com.vmware.vcIntegrity.lifecycle.ClusterHealthCheckTask.HwSupportCheck.Name" }, "description": "args": [], "default_message": "Checks if the hardware update can be performed.", "id": "com.vmware.vcIntegrity.lifecycle.ClusterHealthCheckTask.HwSupportCheck.Description" }, "check": "com.vmware.vcIntegrity.lifecycle.ClusterHealthCheckTask.
Set up 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. To launch the Blink Server LED Indicator wizard, perform either of the following actions: a. On the OMIVV home page, expand Menu, select Hosts and Clusters, right-click a host or cluster, and then go to Summary > OMIVV Host Information > Host Actions > Blink Server LED Indicator. b.
18 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.
○ Register, unregister, and configure events/alerts — Receive SNMP traps and post events ● Dell.Configuration.Firmware Update ○ ○ ○ ○ ○ ○ Perform firmware update Load firmware repository and DUP file information on the firmware update wizard page Query firmware inventory Configure firmware repository settings Configure staging folder and perform update by using the staging feature Test the network and repository connections ● Dell.Deploy-Provisioning.
19 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 163 Frequently Asked Questions-FAQ This section contains some common questions and solutions.
2. Press F2 and go to Troubleshooting Options. 3. In Troubleshooting Options, go to Restart Management Agents. 4. To restart the management agents, press F11. A valid iDRAC IP is now available. NOTE: Host inventory can also fail when OMIVV fails to enable WBEM services on hosts running ESXi 6.5. See Create host credential profile on page 38 for more information about WBEM service.
Extracting thumbprint from the old certificate For more information, see https://kb.vmware.com/s/article/2121701. 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.
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.
Table 26. Virtual appliance (continued) Port Number Protocol s Port Type Maximum Directi Encryptio on n Level Destination Usage Description scripts to communicate with the OMIVV appliance. 443 HTTPS TCP 128-bit In iDRAC to OMIVV appliance Auto Discovery 443 WSMAN TCP 128-bit In/Out OMIVV appliance to or from iDRAC iDRAC iDRAC, or CMC, or OME-Modular communication communication, used to manage and monitor the managed nodes.
Password is not changed for user used for bare-metal discovery after successfully applying system profile that has same user with new changed credentials in iDRAC user list The password of the user who is used from discovery is not changed to the new credential if only System Profile (Configuration of the hardware) is selected for deployment. This is done intentionally so that the plug-in can communicate with the iDRAC for future use in deployment needs.
1. Ensure that the iDRAC can ping the appliance. 2. Ensure that your network is not running too slow. 3. Ensure that the ports: 2049, 4001–4004 are open and the firewall is set accordingly. How do I force remove OMIVV appliance from vCenter 1. Go to vSphere Client and clear the check box against the Dell Provider for all the Proactive HA enabled cluster. 2. Go to https:///mob 3. Enter the VMware vCenter admin credentials. 4. Click Home > Content > HealthUpdateManager. 5.
2. To automatically open the iDRAC console, click Launch iDRAC GUI. 3. Navigate to the user list in the iDRAC console, and click one of the following: ● iDRAC7: Select iDRAC settings > Users tab. ● iDRAC8: Select iDRAC settings > Users tab. ● iDRAC9: Select iDRAC settings > Users tab. For iDRAC 7 and 8: a. To edit the settings, in the User ID column, click the link for the admin (root) user. b. Click Configure User, and then click Next. c.
OS deployment fails when NPAR is enabled on a target node and disabled in System Profile OS deployment fails when a System Profile with a disabled NIC Partitioning (NPAR) is applied on a target machine. Here, NPAR is enabled on the target node and only one of the partitioned NIC, except partition 1 is selected as the NIC for the Management Tasks during the deployment process through the deployment wizard.
Resolution: System profile that is taken from an FC640 server in slot 1 of a FX2s chassis can only be applied on another FC640 server residing in the slot 1 of another FX2s chassis. 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.
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.
Resolution: 11G servers are not supported with OMIVV 5.0. Manually remove the unsupported 11G hosts from the host credential profile. Version Affected: 5.0 Unable to launch vCenter from flex client after upgrading the OMIVV appliance Resolution: See VMware KB article for resolution: https://kb.vmware.com/s/article/54751. Version affected: 5.
Resolution: Rediscover the server. If the missing server is supported, then it is listed in the bare-metal inventory. Version Affected: 5.0 After OS deployment, OMIVV failed to add ESXi host to vCenter or failed to add Host Profile or Enter Maintenance Mode is failed for host After OS deployment, OMIVV queries vCenter to perform the host actions (Add host, Add Host Profile, or Enter Maintenance Mode).
Proactive HA initialization is not happening after performing backup and restore When you restore OMIVV from the previous version that is registered with the vSphere Client, for Proactive HA enabled clusters the Dell Provider is disconnected. Resolution: Disable and enable the Proactive HA for clusters. Version Affected: 5.
Sometimes, OMIVV takes long time to complete vCenter unregistration When you unregister vCenter having large number hosts (above 300), OMIVV remains in the loading state for long time. Resolution: Refresh the browser. If the vCenter un-registration is not successful, unregister the vCenter again. Version Affected: 5.1 After updating OMIVV certificate, "Failed to connect OMIVV appliance. The SSL certificate is not valid" error message is displayed Resolution: Restart the vCenter Client service.
OMIVV shows only BIOS and iDRAC attributes on the Profile Settings page of System Profile Resolution: Upgrade Google Chrome to latest version. Version Affected: 5.2 OS deployment is completed with unknown error This issue occur when you perform OS deployment with different user other than the user used to discover the server. The error message on the OMIVV Logs page shows class not found error. Resolution: NA , this issue does not affect the functionality of the OMIVV features. Version affected: 5.
accounts are disabled. It is not necessary to configure a static IP address for the iDRAC. It gets one from a DHCP server on the network. To use the auto discovery feature, a DHCP server or a DNS server (or both) must be configured to support the discovery process. CSIOR should already be run during the factory process. If auto discovery was not requested at the time of purchase, it can be enabled as follows: 1. During the boot routine, press Ctrl+E. 2.
A System specific attributes iDRAC Table 28.
Table 29.
Table 31.
FC Table 32.
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.
Table 34. Component vs. baseline version comparison matrix (continued) Drift Type 172 Not available Available The comparison status is not calculated and ignored. Compliant 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.
