OpenManage Integration for VMware vCenter Version 5.0 User's Guide September 2019 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 - 2019 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................................................................................................................. 9 Whats new in this release..................................................................................................................................................9 Important notes....................................................................................................................................................................
Delete repository profile.................................................................................................................................................. 47 Chapter 7: Capture baseline configuration using cluster profile...................................................49 Cluster profile.....................................................................................................................................................................49 Create cluster profile...............
Chapter 10: Manage jobs.............................................................................................................. 71 Deployment jobs................................................................................................................................................................. 71 Chassis firmware update jobs......................................................................................................................................... 71 Host firmware update jobs.
Chapter 14: Chassis Management...............................................................................................100 View Dell EMC chassis information.............................................................................................................................100 View chassis inventory information.............................................................................................................................100 Viewing hardware inventory information for chassis........
What should I do when a web communication error in the vCenter HTML-5 Client opens after changing the DNS settings in OMIVV...............................................................................................................137 Installation date be displays as 12-31-1969 for some of the firmware on the firmware page................. 137 I am not seeing OpenManage Integration icon in HTML-5 Client even if registration of plug-in to vCenter was successful.............................................
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. ........................................... 146 Configuring the System Lockdown mode at a cluster level sometimes displays a message "No hosts under the cluster has successful inventory"........................................................................................
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.
Table 1.
Table 1. OMIVV features (continued) Features Description ● ● ● ● MX chassis firmware update Firmware update Deployment Service Information Security role and permissions Provides an option to update management module firmware for MX chassis. NOTE: From OMIVV 5.0 onwards, only VMware vSphere Client (HTML-5) is supported and the vSphere Web Client (FLEX) is not supported.
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 by non-administrator user To perform the following tasks, ensure that you have vCenter Administrator privileges. 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.
￭ ￭ ￭ Network configuration Query patch Security profile and firewall NOTE: If you are using vCenter 6.5 or upgrading to vCenter 6.5 or later, ensure that you assign the modify cluster privilege. ￭ Host.Config - Advanced settings - Connection - Maintenance - Network configuration - Query patch - Security profile and firewall ○ Inventory ￭ ￭ ￭ Add host to cluster Add standalone host Modify cluster NOTE: If you are using vCenter 6.5 or upgrading to vCenter 6.
For more information about the available OMIVV roles within vCenter, see Security roles and permissions. 7. Edit the role name and enter description for the selected role, if required. 8. Click FINISH. Log out and log in from the vCenter. The user with necessary privileges can now perform the OMIVV operations.
Upload license to Administration Portal You can use this option to upload OMIVV host license. 1. Go to https://. 2. In the Login dialog box, type the password. 3. In the left pane, click VCENTER REGISTRATION. The registered vCenter servers are displayed in the working pane. 4. Click Upload License. 5. In the UPLOAD LICENSE dialog box, click Browse to go to the license file, and then click Upload.
● Before logging into to any of the registered vCenter servers, ensure that you update all appliances simultaneously under the same Platform Service Controller (PSC) before logging in to any of the registered vCenter servers. Else, you may see inconsistent information across OMIVV instances. 1. In the APPLIANCE UPDATE section of the APPLIANCE MANAGEMENT page, verify the current and available OMIVV version.
Upgrade OMIVV appliance using backup and restore Dell EMC recommends not to change or remove cluster or host that is managed by OMIVV after taking backup and before restoring the backup file. If the cluster or host that is managed by OMIVV is changed or removed, reconfigure profiles (for example, Host credential profile, cluster profile) associated with those clusters and hosts after restore. Do not unregister the OMIVV plug-in from vCenter.
● ● ● ● Schedule automatic backups Perform an immediate backup Restore the database from backup Reset backup and restore settings on page 20 In OpenManage Integration for VMware vCenter, perform the following steps to access the BACKUP AND RESTORE SETTINGS page through the Administration Console: 1. Go to https:\\. 2. In the Login dialog box, type the password. 3. In the left pane, click BACKUP AND RESTORE.
● 11G bare-metal servers are not supported. Only the 12G and later generations servers are retained after restore. ● Hardware Profiles and Deployment Templates are not supported. Dell EMC recommends using System Profile for deployment. ● Deployment tasks that are scheduled on 11G servers and/or using Hardware Profile based Deployment Templates are canceled. ● All 11G servers are removed from Credential Profiles and consumed licenses are relinquished. ● Repository Profiles will use only 64-bit bundles.
3. After configuring NTP, start the terminal console and select the Sychronize date and time over the network check box. NOTE: It might take around 10 minutes for the OMIVV clocks to synchronize with the NTP server. 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.
Set up global alerts Alert management enables you to configure global settings for how alerts are stored at OMIVV for all vCenter instances. 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: ● ● ● ● Current number of alerts Maximum number of alerts Number of days to retain alerts Timeout for duplicate alerts (seconds) 5.
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. Shut down 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 network adapter, and then select the Connect At Power On check box. b. Select the E1000 adapter type from the drop-down menu. OMIVV supports only E1000 type of network adapter. 4. Power on the VM.
WARNING: Do not use "+" to add any new network interface. It is mandatory to use the vSphere Edit Settings to add a network adapter. 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 to 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.
The admin password should be at least eight characters and should include one special character, one number, one uppercase, and one lowercase letter. 4. Enter a new password in Enter new Admin Password, and click Change Password. 5. Retype the new password in Please Confirm Admin Password, and press Enter. Configure NTP and setting local time zone 1. Open the OMIVV VM console. See Open OMIVV VM console on page 23. 2. To configure the OMIVV time zone information, click Date/Time Properties.
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: ● ● ● ● ● ● ● The health status of hosts and chassis Warranty status of hosts and chassis Hosts and vCenter license information Configuration compliance status Jobs states Total number of compliant bare-metal servers that are available for deployment Quick references Health The Health section displays the health status of all the OMIVV-managed hosts and chassis.
● The total number of available host and vCenter licenses ● The total number of host and vCenter licenses that are in use. To purchase license, click BUY LICENCE. Ready for Deployment The number of bare-metal servers lists only the compliant bare-metal servers that are discovered using OMIVV. To deploy the bare-metal servers, click DEPLOY. Configuration Compliance The Configuration Compliance section displays the hosts that are part of cluster which is associated with the cluster profile.
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. Each server must be associated to a host credential profile to be managed by OMIVV. 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 enter 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 OS. ○ Enter the user name in the Active Directory User Name box. Enter the user name in one of the formats such as domain\username or username@domain. The user name is limited to 256 characters. See the Microsoft Active Directory Documentation for user name restrictions.
Related tasks Edit host credential profile on page 37 Delete host credential profile on page 39 Related information Host credential profile on page 35 Edit host credential profile on page 37 Delete host credential profile on page 39 Test host credential profile on page 39 Edit host credential profile You can edit the credentials of multiple host credential profiles at a time. 1. On the Name and Credentials page, do the following: a. Edit the profile name and description. b.
The Associated Hosts page is displayed. 3. To add or remove the hosts from the associated hosts list, on the Associated Hosts page, click ADD HOST. NOTE: Do not add a PowerEdge MX server with a disabled iDRAC IPv4 to a host credential profile. These servers are managed using a chassis credential profile. The selected hosts are displayed on the Associated Hosts page. 4. To test the connection, select one or more hosts, and then click BEGIN TEST.
3. To export the host credential profile information, click . Related information Host credential profile on page 35 Test host credential profile Using the test credential profile feature, you can test the host and iDRAC credentials. Dell EMC recommends selecting all the 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. Select all the associated hosts and click BEGIN TEST. a.
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.
For example, you have a profile Test associated with Chassis A. If you create another profile Test 1 and try to associate Chassis A to Test 1, a warning message is displayed. Test connection runs automatically for the selected chassis. Test connection runs automatically: ● For the first time after the chassis is selected ● 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.
Test connection runs automatically: ● For the first time after the chassis is selected ● 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, Dell EMC recommends managing all the lead and member chassis using the lead chassis.
● Chassis IP/Host name ● Chassis Service Tag 3. To export the chassis credential profile information, click . Related information Chassis credential profile on page 40 Test chassis credential profile Using chassis test credential profile feature, you can test the credentials of a chassis that is associated with the chassis credential profile. Dell EMC recommends selecting all the chassis. 1. On the OMIVV home page, click Compliance & Deployment > Chassis Credential Profile. 2.
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.
● For driver repository, download the offline driver bundles ( .zip files) and save to the shared location by providing the full path of the shared location. OMIVV automatically creates the catalog inside the OMIVV appliance. Driver bundles are available at https://my.vmware.com/web/vmware/downloads ● OMIVV requires write access to the CIFS or NFS. ● Files within the subfolders are ignored. ● Files exceeding 10-MB sizes are ignored. ● Driver repository is applicable only for vSAN clusters. 6.
NOTE: OMIVV supports only Server Message Block(SMB) version 1.0 and SMB version 2.0 based CIFS shares. 5. To validate the catalog path and credentials, click BEGIN TEST. This validation is mandatory to continue further. Test connection results are displayed. 6. Click NEXT. The Synchronize with repository location page is displayed. 7. On the Synchronize with repository location page, select the Synchronize with repository location check box, and then click NEXT.
Edit Validated MX Stack Catalog 1. On the Repository Profile page, select Validated MX Stack Catalog, and then click EDIT. 2. You can edit only the following: a. The catalog description. b. The Synchronize with repository location check box. To only update the profile name or review information, clear the Synchronize with repository location check box so that the catalog remains unchanged in OMIVV.
Related information Repository profile on page 44 Create repository profile on page 44 Edit repository profile on page 45 48 Manage firmware and driver repositories using repository profile
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.
5. Click NEXT. The Associate Cluster (s) page is displayed. 6. On the Associate Cluster (s) page, perform the following tasks: a. Select an instance of a registered vCenter server. b. To associate the clusters, click BROWSE. To select the cluster, ensure that you have at least one host that is associated to the cluster, which is successfully managed by OMIVV. c. Click OK. The selected clusters are displayed on the Associate Cluster(s) page. d. Click NEXT. 7.
View cluster profile 1. On the OMIVV page, click Compliance & Deployment > Profiles > Cluster Profile.
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.
● To view more information about the compliance issue, click DETAILS in the lower horizontal pane. You can also perform the following tasks on the Bare-metal Servers page: ● ● ● ● ● 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.
Provisioning service location Use the following options to obtain the provisioning service location by iDRAC during auto discovery: ● Manually specified in the iDRAC—manually specify the location in the iDRAC configuration utility under LAN User Configuration, Provisioning Server. ● DHCP scope option—specify the location using a DHCP scope option. ● DNS service record—specify the location using a DNS service record.
3. Click Back, and click Remote Enablement. 4. Set Enable Auto-Discovery as Enabled and Provisioning Server as the IP address of the OMIVV. 5. Save the settings. The server is auto that is discovered upon next server boot. After successful auto discovery, the root user gets enabled, and the Enable Auto-Discovery flag is disabled automatically. Manual discovery of bare-metal servers You can manually add a bare-metal server that is not added using the auto discovery process.
Refresh bare-metal servers The refresh operation rediscovers the bare-metal servers by connecting to iDRAC and collecting the basic inventory. NOTE: If you perform the refresh operation on the "Configured" bare-metal servers, the server status changes to the "Non-configured" state because the refresh operation rediscovers the server. 1. On the OMIVV home page, click Compliance & Deployment > Deployment > REFRESH. 2. On the Refresh Bare-metal Servers page, select a server, and click OK.
For more information, see Deploy system profile and ISO profile on page 59. To launch the deployment wizard, go to Compliance & Deployment > Deployment > DEPLOY. Deploy system profile (configuration of the hardware) 1. On the System Profile and ISO Profile Deployment Checklist page of the deployment wizard, verify the deployment checklist, and then click GET STARTED. You can perform the deployment only on the compliant bare-metal servers. For more information, see View bare-metal servers on page 52. 2.
○ If any one of the selected servers does not support an IDSDM or BOSS module, or if IDSDM or BOSS is not installed in the servers during deployment then the deployment operation on those servers is skipped. To deploy the OS on the first boot disk of the servers, select the Deploy the hypervisor to the first boot disk for servers that do not have an available Internal Dual SD Module check box.
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 on page 52. 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 job timing The system profile and ISO profile deployment can take between 30 minutes to several hours to complete, depending on multiple factors. When starting a deployment job, Dell EMC recommends that you plan your deployment time according to the guidelines provided. The amount of time it takes to complete the system profile and ISO profile deployment varies with deployment type, complexity, and number of deployment jobs running simultaneously.
Before creating the system profile, Dell EMC recommends configuring the reference server attribute and value as required, and then apply it to all the required target servers. The system profiles search for an exact instance (FQDD) while applying the profile, which works successfully on rack servers (identical), but may have few restrictions in modular servers.
NOTE: Pseudo attributes are not displayed in system profile. For more information, see the Server Configuration XML File document. Before selecting the attributes other than the attributes that are selected by default, check the nature of attribute, dependency, and other details.
The Profile Settings page is displayed. 6. On the Profile Settings page, you can view or modify the profile settings for the components such as iDRAC, BIOS, RAID, NIC, CNA, FCoE, and EvenFilters based on the configuration of the reference server. By default, platform-specific and readonly attributes are not listed. For more information about platform-specific attributes, see System specific attributes on page 153.
Related information System profile on page 60 ISO profile An ISO profile contains the folder path for the Dell EMC customized ESXi ISO image file that is saved on the NFS or CIFS folders. An ISO profile is used in the deployment wizard. Related tasks Create an ISO profile on page 64 Edit an ISO profile on page 64 View an ISO profile on page 65 Create an ISO profile An ISO profile requires Dell EMC customized ISO file location on an NFS or CIFS. 1.
Related information ISO profile on page 64 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 .
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.
● WBEM Status—The WBEM status (Compliant or Non-compliant). The CSIOR status shows Not applicable for hosts that are managed using chassis. ● iDRAC Firmware Version—The iDRAC firmware version ● iDRAC License Status—The iDRAC License status (Compliant or Non-compliant). 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.
The wizard configures the SNMP trap destination status to Configured after you fix the iDRAC or host credentials by providing valid information in host credential profile, or make any one of the first four slots available in the iDRAC trap destination, or disable System Lockdown Mode in iDRAC. NOTE: System Lockdown Mode is applicable only for 14th generation and later servers.
NOTE: Only the hosts that are not managed by OMIVV are displayed in the Select Hosts window. OMIVV tests the connection automatically, and test connection results are displayed in the Add OEM Hosts window. The iDRAC Test and Host Test columns displays the test connection result for iDRAC Credentials and Host Credentials. 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.
View drift report The Configuration Compliance Report page displays the drift details of the hardware, firmware, and driver components. The drift detection job status is displayed in the Summary section. For Hardware: ● ● ● ● ● ● ● ● ● 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 (non-compliant or failed). Instance—Indicates the hardware component name. Group—Indicates the group name of the attributes.
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.
● ● ● ● ● ● Status—The status of the firmware update job Scheduled time—The firmware update job scheduled time Name—The name of the job 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 standalone chassis. The member chassis will not take part in it. ● Progress—The progress details of the firmware update job 3.
5. If you want to purge earlier firmware update jobs or scheduled firmware updates, click . 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. In the Purge Firmware Update Jobs dialog box, select Older than date and job Status, click OK. The selected jobs are then cleared from the Host Firmware Update jobs list.
● Progress Summary—The progress details of the drift detection job 2. To view the updated Drift Detection Job Details, click Refresh. 3. To view the more information about the servers in the drift detection job, select a drift detection job. The following information is displayed: ● ● ● ● ● ● ● ● Service Tag iDRAC IP Host Name Cluster vCenter Status Start Date and Time End Date and Time 4. To run the Drift Detection job on-demand, click .
The following information is displayed: ● ● ● ● ● ● ● Overview Hardware Inventory Storage Firmware Power Monitoring Warranty System Event Log When the hosts are managed using the chassis credential profile, the firmware inventory data show few extra components such as Lifecycle Controller and Software RAID. NOTE: Inventory job for hosts exceeding the license limit is skipped and marked as Failed. 7.
● Duration (MM:SS)—The duration of the job in minutes and seconds ● Start Date and Time—The date and time when the inventory job started. ● End Date and Time—The date and time when the inventory job completed In an MCM group, inventory runs only on lead chassis. Inventory information provides data about both lead and member chassis. NOTE: The chassis inventory job is not supported on the following PowerEdge servers: C6320P, C6320, C4130, and C6420.
3. To run the host warranty on-demand, click Run now [ ]. Modify host warranty job The warranty jobs are originally configured in the Initial Configuration Wizard. You can also modify warranty job schedules on the Settings > Warranty Data Retrieval page. 1. On the Jobs page, expand Warranty, and then select Host Warranty. 2. Select a vCenter and click . 3. Under the Warranty Data section, do the following: a. Select the Enable Warranty Data Retrieval (Recommended) check box. b.
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 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.
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 on page 79. ● Configure the latest appliance version notification. For more information, see Configure latest appliance version notification on page 79. ● Override severity for Proactive HA alerts. For more information, see Override severity of health update notification on page 83.
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.
Related references Proactive HA events on page 81 Related information Override severity of health update notification on page 83 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.
NOTE: It is recommended that all the modular hosts in a Proactive HA cluster should not be in the same chassis, because the chassis components (PSU and fan) failure affects all its associated servers. 1. Create a host credential profile and associate hosts with host credential profile. See Create host credential profile on page 35. 2. Verify that hosts inventory is completed successfully. See View host inventory job on page 74.
NOTE: You cannot customize the severity of the Proactive HA components with the Info severity level. 1. In OpenManage Integration for VMware vCenter, click Settings > Proactive HA Configuration. The data grid displays all the supported Proactive HA events and includes columns; events id, event description, component type, default severity, and override severity column for customizing the severity of the host and its components. 2.
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. Dell EMC recommends associating your OMIVV hosts with a configuration baseline because it enables you to closely monitor the configuration changes happening in hosts and associated clusters.
Related concepts OpenManage Integration for VMware vCenter licensing on page 86 Related tasks Buy software license on page 86 OpenManage Integration for VMware vCenter licensing The OpenManage Integration for VMware vCenter has two types of licenses: ● Evaluation license—when the OMIVV appliance is powered on for the first time, an evaluation license is automatically installed.
Access support information Table 7. Information on the support page Name Description Documentation Support Provides the following documentation links: ● PowerEdge Servers ● OMIVV Manuals ● 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.
3. To confirm that you understand the iDRAC reset process, select the I understand the effects of resetting iDRAC. Continue to reset iDRAC on the selected host check box. 4. Click RESET iDRAC.
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.
View chassis alarms 1. In vSphere Client, expand Menu, and then select Hosts and Clusters. 2. In the left pane, select an instance of vCenter. 3. In the right pane, click Monitor > Issues and Alarms > Triggered Alarms. 4. In Triggered Alarms, click alarm name to view the alarm definition.
Table 9.
Table 9.
Table 9.
Table 9.
Table 9.
Table 9. Virtualization events (continued) Event name Description Severity Recommended action occurred, which requires additional fans. The fans are not redundant One of more fans have failed or have been removed or a configuration change occurred, which requires additional fans Info Remove and reinstall failed fans or install additional fans The fans are not redundant.
Table 9. Virtualization events (continued) Event name Description Internal Dual SD Module is not None redundant Severity Recommended action Info Install additional SD card and configure for redundancy if redundancy is desired Chassis events Power supply redundancy is lost The current power Critical operational mode is nonredundant 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 The fans are not redundant.
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.
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 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.
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.
Table 12. OMIVV Host Information (continued) Information Description ● 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. ● 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.
Table 13. OMIVV host health Information Description 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.3 only two health indicators are displayed, namely Healthy and Warning or Critical (Inverted triangle with an exclamatory mark in orange color). The overall health indicates the health that is based on the chassis with the least health parameter.
Table 14. Hardware information for a single host (continued) Hardware: Component Information ○ 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. ● Size—displays the memory size.
Table 15. Storage details for a single host Information Description Virtual Disks ● ● ● ● ● Name—displays the name of the virtual drive. Device FQDD—displays the FQDD. Physical Disk—displays on which physical disk the virtual drive is located. Capacity—displays the capacity of the virtual drive. Layout—displays the layout type of the virtual storage, which means the type of RAID that was configured for this virtual drive. ● Media Type—displays either SSD or HDD.
Table 15. Storage details for a single host (continued) Information Description ○ 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.
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 power monitoring information of a single host You can view the information such as general information, thresholds, reserve power capacity, and energy statistics. ● General Information—displays the Power Budget and Current Profile name.
Monitor hosts on clusters and data centers The OMIVV enables you to view detailed information about all hosts in a data center or cluster. View OMIVV data center and cluster information View overview of data center and cluster You can view the information such as data center or cluster information, system lockdown mode, hardware resources, and warranty information. To view the information about this page, ensure that inventory is completed successfully.
Table 16. Overview of data centers and clusters (continued) Information Description System Lockdown Mode Only for 14th generation PowerEdge servers: Displays the iDRAC Lockdown Mode of the host, which is turned on, turned off, or unknown. For all PowerEdge servers earlier than 14th generation, the System Lockdown Mode displayed as Not Applicable.
Table 17. Hardware information for data centers and clusters (continued) Hardware: Component Information ○ UPS ○ CONVERTER ○ REGULATOR ○ AC ○ DC ○ VRM ● Location—displays the location of the power supply, such as slot 1. ● Output (Watts)—displays the power in watts. ● Status—displays the status of the power supply. The status options include: ○ ○ ○ ○ ○ ○ ○ ○ ○ OTHER UNKNOWN OK CRITICAL NOT CRITICAL RECOVERABLE NOT RECOVERABLE HIGH LOW Hardware: Memory ● ● ● ● ● Host—displays the hostname.
View storage information of a data center and cluster Table 18. Storage details for a data center and cluster Storage: disks Description Physical Disk ● ● ● ● Host—displays the hostname. Service Tag—displays the service tag of the host. Capacity—displays the physical disk capacity. Disk Status—displays physical disk status.
Table 18. Storage details for a data center and cluster (continued) Storage: disks Description ● ● ● ● Controller ID—displays the controller ID. Device ID—displays the device ID. Media Type—displays either SSD or HDD. Bus Protocol—displays the technology that the physical disks in the virtual drive are using. The possible values are: ○ SCSI ○ SAS ○ SATA ○ PCIe ● Stripe Size—displays the stripe size, which provides the amount of space that each stripe consumes on a single disk.
● ● ● ● ● ● System System System System System System Peak Peak Peak Peak Peak Peak Power—displays the host peak power. Power Start Date—displays the date and time when the host peak power started Power End Date—displays the date and time when the host peak power ended Amps—displays the hosts peak amps. Amps Start Date—displays the starting date and time of the host peak amps. Amps End Date—displays the end date and time of the host peak amps.
The Firmware Update Wizard always checks for the minimum firmware levels for iDRAC and BIOS and attempts to update them to the required minimum versions. See OpenManage Integration for VMware vCenter Compatibility Matrix for more information about the minimum firmware levels for iDRAC and BIOS. Once iDRAC and BIOS firmware versions meet the minimum requirements, the firmware update process enables updates for all firmware versions including iDRAC, RAID Controller, NIC, BIOS, and so on.
a. A single DUP can reside on a CIFS or NFS share that is accessible by the OMIVV appliance: Enter the file location in one of the following formats, and then go to step 9. ● NFS—:/\.exe NOTE: Ensure that the file name for the single component DUP does not have any blank space. For CIFS share, OMIVV prompts you to enter the username and password that can access the share drive. 5.
● Schedule Update ● Apply Updates on Next Reboot 12. On the Review Summary page, review the firmware update information, and then click FINISH. The firmware update jobs can take up to several hours depending on the components and number of servers selected. You can view the status of the jobs on the Jobs page.
If you do not want to update firmware or driver, or firmware or driver is up-to-date, from the drop-down menu, select No Repository selected. 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.
Update firmware on vSphere host Before scheduling the firmware update on vSphere hosts (ESXi only), 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. ● The DRS is enabled. NOTE: For a stand host, the DRS check is not applicable. To skip the prerequisites check, clear the Check Prerequisites check box on the Schedule Updates page.
To clear all the firmware components across all the pages, click . 8. On the Schedule Updates page, enter the firmware update job name and description. The description is an optional field. The firmware update job name is mandatory. If you purge the firmware update job name, you can reuse the job name again. 9. Under the Additional Settings section, do the following: a. Enter the Maintenance Mode timeout value between 60–1440 minutes.
1. To launch the firmware update wizard, on the OMIVV home page, expand Menu, select Hosts and Clusters, and then perform either of the following actions: ● Right-click a cluster, select OMIVV Cluster Actions > Firmware Update. ● Select a cluster, in the right pane, select Monitor > OMIVV Cluster Information > Firmware > Run Firmware Wizard. 2. On the Firmware Update Checklist page, ensure that all the prerequisites are verified before scheduling the update, and then click GET STARTED. 3.
Update same firmware component type The following are the key points to remember when updating firmware components of same type: ● If multiple components of the same type with same versions are present in the server, only one version of the component is displayed on the Select Firmware Components page. The update will be applied to all the components and the drift details are displayed for only one version of the component. For example, Table 19.
Table 23. Example for multiple available version present in catalog (continued) Component Current version Available version HDD3 V2 V4 In this case, the Select Firmware Components page displays the following: Table 24.
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 13th and earlier generation of PowerEdge servers, you are prompted with a message that this feature is not supported on this platform. 5. Click OK. A job is successfully created for the configuring System Lockdown Mode. To check the job status, go to Jobs > System Lockdown Mode.
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.
○ Get host name for posting the event ○ Perform the event log operations, for example get the event count, or change the event log settings ○ Register, unregister, and configure events/alerts — Receive SNMP traps and post events ● Dell.Configuration.
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 on page 151 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 35 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 Encryptio n Level Direction Destination Usage Description 4433 HTTPS TCP 128-bit In iDRAC to OMIVV appliance Auto Discovery Provisioning server that is used for auto discovering managed nodes. 2049 NFS UDP/ TCP None In/Out OMIVV appliance to NFS Public Share NFS public share that is exposed by OMIVV appliance to the managed nodes and used in firmware update and operating system deployment flows.
Table 28. Managed nodes (iDRAC or CMC or OME-Modular) (continued) Port Protoco Number ls Port Type Maximum Encryptio n Level Direction Destination Usage Description appliance. That is used for operating system deployment and firmware update. To access the iDRAC configurations from the OMIVV. Used in deployment flow. 4001 to NFS UDP None In/Out 4004 iDRAC to/ from OMIVV Public Share For iDRAC to access NFS public share that is exposed by OMIVV appliance.
Attempting to deploy ESXi on server fails 1. Ensure that the ISO location (NFS path) and staging folder paths are accurate. 2. Ensure that the NIC selected during assignment of server identity is accessible by the virtual appliance. 3. Ensure that you select the management NICs based on the network connectivity to the OMIVV. 4. If using static IP address, ensure that the network information provided (including subnet mask and Default Gateway) is accurate.
What should I do as firmware update failed Check the OMIVV appliance logs to see if the tasks timed out. If so, iDRAC must be reset by performing a cold reboot. After the system is up and running, check to see if the update was successful by either running an inventory or by using the Firmware tab. What should I do as vCenter registration failed vCenter registration can fail due to communication issues, if you are experiencing these issues, a solution is to use a static IP address.
Firmware level not updated when I have performed firmware update with Apply on Next reboot option and system was rebooted To update firmware, run the inventory on the host after the reboot is completed. Sometimes, where the reboot event does not reach the appliance, the inventory is not automatically triggered. In such situation, you must rerun the inventory manually to get the updated firmware versions.
During deployment, system profile apply fails due to iDRAC error During deployment, OMIVV attempts to create configuration update job in iDRAC. However, the job creation may fail sometimes and displays a message indicating that a Configuration job is already created. Resolution: Clear the stale entries and retry the deployment. Log in to iDRAC to clear the jobs.
When creating a host credential profile for the host having ESXi 6.5U1, the Service Tag of the host is not displayed on the Select Hosts page When the OMIVV queries vCenter for the Service Tag of ESXi, vCenter cannot return the Service Tag because the Service Tag value is null. Resolution: Update the ESXi version to ESXi 6.5U2 or ESXi 6.7 U1. Version Affected: 4.
Sometimes post RPM upgrade of OMIVV appliance, multiple entries in the logs are seen in vCenter Recent Tasks Sometimes, after RPM upgrade, multiple entries are displayed in logs when viewed on vCenter Recent Tasks. Resolution: Restart the vCenter services. Version Affected: 4.
g. Reboot the appliance. 2. a. Back up OMIVV from Admin Portal b. Create an OMIVV appliance. c. Shut down the appliance d. Add the required network adapter (s) and complete the network adapters configuration. e. Reboot the appliance. f. Restore the latest backed up data. Version Affected: OMIVV 5.
iDRAC license status is displayed as compliant on the management compliance page when the iDRAC IP is not reachable After performing periodic inventory, if iDRAC not reachable, iDRAC License status is displayed as compliant on the management compliance page. Resolution: Ensure that the iDRAC is reachable and run the inventory again to get the right iDRAC license details. ESXi host is either disconnected or not responding state after successful OS deployment using OMIVV.
OMIVV page displays invalid session, or time out exception, or two million errors in Firefox browser If the OMIVV page is idle for some time (5–10 minutes), the invalid session, or time out exception, or two million errors is displayed. Resolution: Refresh the browser. If the issue persists, log out and log in from vCenter. To see the correct data in OMIVV, ensure that you complete the task listed in resolution. Version Affected: 5.
In vCenter, recent tasks pane does not show the details column for some OMIVV task notifications Resolution: To see the task notifications, in vCenter, go to Task Console of vCenter. Version Affected: 5.0 Unable to see the failure details in OMIVV logs for failed MX chassis firmware update job Resolution: Log in to OME-Modular and check the firmware update job status. If the status shows Success in OME-Modular, OMIVV updates firmware details in the next chassis inventory. Version Affected: 5.
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. In the iDRAC setup window, enable the NIC (blade servers only). 3. Enable Auto-Discovery. 4. Enable DHCP. 5. Disable admin accounts. 6. Enable Get DNS server address from DHCP. 7.
A System specific attributes iDRAC Table 29.
Table 30.
Table 32.
FC Table 33.
B Additional information The following Dell technical white papers available at delltechcenter.
C Customization attributes Table 34. 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 35. 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 35. Component vs. baseline version comparison matrix (continued) Drift Type 160 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.
