OpenManage Integration for VMware vCenter Version 4.0.1 Web Client User's Guide June 2017 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. Copyright © 2017 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 What's new in this release.................................................................................................................................................... 9 OpenManage Integration for VMware vCenter features.................................................................................................
Appliance settings..........................................................................................................................................................35 vCenter settings............................................................................................................................................................ 37 Chapter 7: Profiles........................................................................................................................
About events and alarms for hosts................................................................................................................................... 70 About events and alarms for chassis................................................................................................................................. 71 Viewing chassis events..................................................................................................................................................
Deploying OMSA agent on ESXi system...................................................................................................................106 Setting up OMSA trap destination.............................................................................................................................106 Reporting and fixing compliance for bare-metal servers..............................................................................................
Even if repository has bundles for selected 11G system, why is firmware update displaying that there are no bundles for firmware update?...........................................................................................................................120 Why is DNS configuration settings restored to original settings after appliance reboot if appliance IP and DNS settings are overwritten with DHCP values................................................................................................
Enabling auto discovery on newly purchased system............................................................................................. 129 Chapter 16: Related Documentation.............................................................................................. 130 Accessing documents from the Dell EMC support site................................................................................................
1 Introduction IT administrators use VMware vCenter as the primary console to manage and monitor VMware vSphere ESX/ESXi hosts. OpenManage Integration for VMware vCenter (OMIVV) enables you to manage the Dell hosts better from the VMware web client by providing enhanced capabilities for deployment, manage, monitor and upgrade.
Table 1. OMIVV features (continued) Features Description Service Information Retrieve warranty information for the Dell servers and its associated chassis from Dell’s warranty database and allow for easy online warranty upgrading. Security role and permissions Integrate with standard vCenter authentication, rules, and permissions. NOTE: From OMIVV 4.0 onwards, only VMware vSphere Web client is supported and the vSphere Desktop client is not supported. NOTE: For vCenter 6.
2 About Administration Console You can achieve the administration of OpenManage Integration for VMware vCenter and its virtual environment by using the following two administration portals: • • Web-based Administration Console Console view for an individual server (the virtual machine console of the OMIVV appliance) Topics: • Using Administration Portal Using Administration Portal You can use the administration portal to perform the following tasks: • • • • • • • • • Register a vCenter server.
Required privileges for non-administrator users To register OMIVV with vCenter, a non-administrator user requires the following privileges: NOTE: While registering a vCenter server with OMIVV by a non-administrator user, an error message is displayed if the following privileges are not assigned.
• Task ○ Create task ○ Update task Registering vCenter server by non-administrator user with required privileges You can register a vCenter server for the OMIVV appliance by using a non-administrator user with the required privileges. See Registering a vCenter server on page 13 for information on registering a vCenter server through a non-administrator user or as an administrator. Assigning Dell privileges to existing role You can edit an existing role to assign the Dell privileges.
• Ensure that OMIVV host name entries are present in both forward and reverse lookup zones in your DNS server. b. In the Description text box, enter a description (optional). 4. Under vCenter User Account, perform the following steps: a. In the vCenter User Name text box, enter the administrator’s user name or a non-administrator user name with the required privileges. b. In the Password text box, enter the password. c. In the Verify Password text box, enter the password again. 5. Click Register.
NOTE: Since there can be more than one vCenter, ensure that you select the correct vCenter. 3. To confirm the unregistration of the selected vCenter server, in the UNREGISTER VCENTER dialog box, click Unregister. NOTE: If you have enabled Proactive HA on clusters, ensure that Proactive HA is disabled on the clusters. For disabling Proactive HA, access the Proactive HA Failures and Responses screen of a cluster by selecting Configure > Services > vSphere Availability, and then clicking Edit.
NOTE: If you had registered any vCenter servers with the appliance, unregister and re-register all the vCenter instances. NOTE: Ensure that you manually update all references to the virtual appliance across its environment such as provisioning server in iDRAC, DRM. Updating virtual appliance repository location and virtual appliance To ensure that all data is protected, perform a backup of the OMIVV database prior to an update of the virtual appliance. See Managing backup and restore on page 19. 1.
Updating appliance through backup and restore To update the OMIVV appliance from the OMIVV version x to version y, perform the following steps: 1. Take a backup of the database for the older release. 2. Power off the older OMIVV appliance from vCenter. NOTE: Do not unregister the OMIVV plug-in from vCenter. Unregistering the plug-in from vCenter removes all the alarms registered on vCenter by the OMIVV plug-in and all the customization that is performed on the alarms, such as actions, and so on. 3.
Setting up Network Time Protocol (NTP) servers You can use Network Time Protocol (NTP) to synchronize the virtual appliance clocks to that of an NTP server. 1. In the APPLIANCE MANAGEMENT page, click Edit in the NTP Settings area. 2. Select Enabled. Enter the host name or IP address for a preferred and secondary NTP server and click Apply. NOTE: It might take around 10 minutes for the virtual appliance clocks to synchronize with the NTP server.
A message is displayed stating that if a new request is generated, certificates created using the previous CSR can no longer be uploaded to the appliance. To continue with the request, click Continue, or to cancel, click Cancel. 2. If you continue with the request, in the GENERATE CERTIFICATE SIGNING REQUEST dialog box, enter the Common Name, Organizational Name, Organizational Unit, Locality, State Name, Country, and Email for the request. Click Continue. 3.
Configuring backup and restore The backup and restore function backs up the OMIVV database to a remote location from which it can be restored later. The profiles, templates, and host information are included in the backup. Dell recommends that you schedule automatic backups to guard against data loss. NOTE: NTP Settings are not saved and restored. 1. In the BACKUP AND RESTORE SETTINGS page, click Edit. 2. In the highlighted SETTINGS AND DETAILS area, perform the following steps: a. b. c. d.
About vSphere client console The vSphere client console is found within the vSphere client on a virtual machine. The console works in close association with the Administration Console.
Resetting virtual appliance to factory settings 1. Open the virtual machine console. See Opening vSphere client console. 2. Click Reset Settings. The following message is displayed: All the settings in the appliance will be Reset to Factory Defaults and the appliance will be rebooted. Do you still wish to continue? 3. To reset the appliance, click Yes, or to cancel, click No. If you click yes, the OMIVV appliance is reset to the original factory settings and all other settings and existing data is lost.
3 Managing multiple appliances You can manage and monitor multiple OMIVV appliances that you register with vCenter servers belonging to the same Platform Service Controller (PSC) and the same vCenter version. Dell recommends you to perform a global refresh if page is cached. 1. In VMware vCenter home page, click the OpenManage Integration icon. 2. In Navigator, under the Dell group, click OMIVV Appliances. 3.
4 Accessing OpenManage Integration from web client When you log in to VMware vCenter after installing OMIVV, under the Home tab, the OpenManage Integration icon is located in the main content area under the Administration group. You can use the OpenManage Integration icon to navigate to the OpenManage Integration for VMware vCenter page. The Dell group is displayed in the Navigator pane. VMware vCenter layout has the following three main panes: Table 3.
Icons in web client The product user interface uses many icon-based action buttons for the actions you take. Table 4. Icon buttons defined Icon buttons Definition Add or create something new Add a server to a connection profile, data center, and cluster Abort a job Collapse a list Expand a list Delete an object Change a schedule Edit Purge a job Export a file Enable WBEM service Locating software version The software version is found on the OpenManage Integration for VMware vCenter Getting Started tab.
• Connection Profile—displays the name of the connection profile. Viewing OpenManage Integration for VMware vCenter licensing tab When you install OpenManage Integration for VMware vCenter license, the number of supported hosts and vCenter servers are displayed in this tab. You can also view the version of the OpenManage Integration for VMware vCenter at the top of the page. The page under licensing displays the Buy License link.
Table 5. Information in the help and support tab (continued) Name Description • • • OpenManage Integration for VMware vCenter Product Page Dell Help and Support Home Dell TechCenter Support Call Tips Offers tips on how to contact Dell Support and route your calls correctly. Troubleshooting Bundle Provides a link to create and download the troubleshooting bundle. You can provide or view this bundle when you contact technical support. For more information, see Downloading the troubleshooting bundle.
Opening online help You can open the online help from the Help and Support tab. You can search the document for help on understanding a topic or a procedure. 1. In OpenManage Integration for VMware vCenter, in the Help and Support, under Product Help, click OpenManage Integration for VMware vCenter Help. The online help content is displayed in the browser window. 2. Use the left-pane table of contents or search to find the topic of your choice. 3.
• • • Category — displays the type of log category Date and Time — displays the date and time of user action Description — displays a description of the user action You can sort the data grid columns in ascending or descending order by clicking the column header. Use the Filter text box to search within your content. At the bottom of the page grid, the following information is displayed: Table 6.
5 OpenManage Integration for VMware vCenter licensing The OpenManage Integration for VMware vCenter has two types of licenses: • • Evaluation license—when the OMIVV version 4.x appliance is powered on for the first time, an evaluation license is automatically installed. The trial version contains an evaluation license for five hosts (servers) managed by the OpenManage Integration for VMware vCenter.
6 Appliance configuration for VMware vCenter After you complete the basic installation of OMIVV and registration of the vCenters, the Initial Configuration Wizard is displayed when you click the OMIVV icon. You can proceed to configure the appliance by using one of the following methods: • • Configuring the appliance through the Initial Configuration Wizard. Configuring the appliance through the Settings tab in OMIVV.
3. To proceed with the Connection Profile Description dialog box, click Next. NOTE: If you have multiple vCenter servers that are part of the same single sign-on (SSO), and if you choose to configure a single vCenter server, repeat steps 1 through 3 until you configure each vCenter. Creating connection profile Before using the Active Directory credentials with a connection profile, ensure that: • • The Active Directory user’s account exist in Active Directory.
Host user name requirements: ○ Between 1 and 64 characters long ○ No nonprintable characters ○ No Invalid characters, such as " / \ [ ] : ; | = , + * ? < > @ Host domain requirements: ○ Between 1 and 64 characters long ○ First character must be alphabetical ○ Cannot contain a space ○ No Invalid characters, such as " / \ [ ] : ; | = , + * ? < > @ b. In Active Directory Password, type the password. The password is limited to 127 characters. c. In Verify Password, type the password again. d.
NOTE: The settings in this page are reset to default each time the configuration wizard is invoked. If you have previously configured a schedule for inventory, ensure that you replicate the previous schedule in this page before completing the wizard functions so that the previous schedule is not overridden by the default settings. 1. In the Initial Configuration Wizard, from the Inventory Schedule dialog box, select Enable Inventory Data Retrieval, if it is not enabled.
3. To accept the change, click Continue, or to cancel the change, click Cancel. NOTE: Ensure that you complete this step only if you select Enable Alarms For Dell Hosts. 4. To restore the default vCenter alarm settings for all managed Dell servers, click Restore Default Alarms. It might take up to a minute before the change takes effect. NOTE: After restoring the appliance, the events and alarms settings are not enabled even if the GUI shows as enabled.
• Dell Online—you can access the location that uses the firmware update repository of Dell (Ftp.dell.com). The OpenManage Integration for VMware vCenter downloads selected firmware updates from the Dell repository and updates the managed hosts. NOTE: Based on the network settings, enable proxy settings if network needs proxy. • Shared Network Folder—you can have a local repository of the firmware in a CIFS-based or NFS-based network share.
3. To save the specified credentials, click Apply. vCenter settings In this section, configure the following vCenter settings: • • • Enable the OMSA link. See Enabling the OMSA link. Configure events and alarms. See the Configuring events and alarms. Configure the data retrieval schedules for inventory and warranty. See the Viewing data retrieval schedules for inventory and warranty. Enabling OMSA link Install and configure an OMSA web server before enabling the OMSA link.
NOTE: The option is not available, if you have already selected All Registered vCenters from the drop-down list on the Settings tab. 7. To save, click Apply. Viewing data retrieval schedules for inventory and warranty 1. In the OpenManage Integration for VMware vCenter, on the Manage > Settings tab, under vCenter Settings, click Data Retrieval Schedule. On clicking, data retrieval schedule expands to expose the edit options for inventory and warranty. 2.
7 Profiles Credential Profiles allows you to manage and configure the connection profiles, and the chassis profiles while Deployment Template allows you to manage and configure hardware and hypervisor profiles. Topics: • • About connection profile About chassis profile About connection profile The Connection Profiles tab lets you manage and configure connection profiles that contain credentials that are in use by the virtual appliance to communicate with the Dell servers.
Table 7. Connection profile information (continued) Connection profile fields Description Last Modified By Displays the details of the user who modified the connection profile Creating connection profile You can associate multiple hosts to a single connection profile. To create a connection profile, perform the following steps: NOTE: The vCenter hosts that are listed during this procedure are authenticated by using the same Single Sign On (SSO).
○ In the Active Directory User Name text box, type the user name. Type the user name in either 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. ○ In the Active Directory Password text box, type the password. The password is limited to 127 characters. ○ In the Verify Password text box, type the password again.
4. Select a profile, and click the icon. 5. In the Welcome tab of the Connection Profile window, read the information and click Next. 6. In the Name and Credentials tab, perform the following steps: a. Under Profile, type the Profile Name and Description, which is optional. b. Under vCenter, view the associated hosts for this connection profile. See the note preceding about why you see the hosts displayed here. c.
8. In the Select Hosts dialog box, select hosts for this connection profile. 9. Click OK. The Associated Host dialog box lets you test the iDRAC and host credentials on the selected servers. NOTE: If you select hosts that are running ESXi 6.5 or later, ensure that you click the service on all those hosts. icon for enabling the WBEM 10. Perform one of the following steps: • • To create a connection profile without testing the credentials, click Finish.
Viewing chassis profiles Ensure that you create a chassis profile or a chassis profile exists before viewing. After one or more chassis profiles are created, you can view them in the chassis profiles page. 1. In OpenManage Integration for VMware vCenter, click Manage. 2. Click Profiles, and then click Credential Profiles. 3. Expand Credential Profiles and click the Chassis Profiles tab. The chassis profiles are displayed. 4.
If the selected chassis is already a part of another profile, then a warning message is displayed, stating that the selected chassis is associated with a profile. 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. 8. Click OK. The Associated Chassis page is displayed. 9.
5. To abort all selected tests and cancel the testing, click Abort All Tests. In the Abort Tests dialog box, click OK. 6. To exit, click Cancel.
8 Inventory and warranty management After you configure OMIVV, you can monitor the inventory, warranty jobs, manage deployment jobs, and manage firmware update jobs under the Monitor tab. The inventory and warranty are set up in the Initial Configuration Wizard or from the Settings tab. The job queue page manages the following jobs: • • • • Displaying the submitted server deployment or firmware update jobs. Refreshing the firmware update or deployment jobs, or inventory/warranty history queues.
• The host does not have the correct iDRAC license required for 12th and later generation of Dell PowerEdge servers and hence, purchase the correct iDRAC license. • The credentials might be wrong. • The host might not be reachable. To view the host inventory details: 1. In OpenManage Integration for VMware vCenter, click the Monitor tab. 2. Click Job Queue, expand Inventory History, and then click Host Inventory. The vCenter information is displayed in the upper grid. 3.
Table 10. Chassis information (continued) Start Date and Time Displays the date and time when the inventory schedule started End Date and Time Displays the time the inventory schedule ended Modifying inventory job schedules To ensure that there is up-to-date host information, schedule the inventory job to run at a minimum frequency of once a week. The inventory job consumes minimal resources and does not degrade host performance.
• Launch CMC Running chassis inventory job now You can view and run a chassis inventory job in the Chassis Inventory tab. 1. In the OpenManage Integration for VMware vCenter, click the Monitor tab. 2. Click Job Queue, Inventory History, and then click Chassis Inventory. The list of chassis and its status for the last inventory job is displayed. NOTE: The scheduled chassis inventory is run the same time as the scheduled host inventory. 3. Click .
Table 11. vCenter, hosts history information (continued) vCenter history Duration (MM:SS) Displays the duration of the warranty job in MM:SS Start Date and Time Displays the date and time when the warranty job started End Date and Time Displays the time the warranty job ended Viewing chassis warranty A warranty job is a scheduled task to get warranty information from Support.dell.com on all systems. You can sort the columns of the inventory view in ascending and/or descending order. 1.
2. Click Job Queue, and then click Warranty History. 3. Expand Warranty History to display Hosts Warranty and Chassis Warranty. 4. To view your corresponding warranty job history information, select either Hosts Warranty or Chassis Warranty. 5. Select the warranty job you want to run, and then click the icon. 6. In the Success dialog box, click Close. A warranty job is now in queue. NOTE: Chassis warranty is run automatically for all the chassis once the host warranty is run.
Table 14. Dell server Management portlet Information Description Service Tag Displays the service tag for your Dell PowerEdge server. Use this ID when you call for support. Model Name Displays the server’s model name. Fault Resilient Memory Displays the status of a BIOS attribute. The BIOS attribute is enabled in the BIOS during initial setup of the server and displays the memory operational mode of the server. Restart your system when you change the memory operational mode value.
6. View the Dell Host Health portlet: Table 15. Dell host health Information Description Dell 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 16.
Table 17. Storage details for a single host Component Information Storage Displays the count of virtual disks, controllers, enclosures, and associated physical disks with the global hot spare and dedicated hot spare counts. When you select from the View drop-down list, the selected option is highlighted.
Table 18. Storage details for a single host (continued) Information Description Physical Disks — When you select this option, the Filter drop-down list is displayed. • • • • Name—displays the name of the physical disk Device FQDD—displays the device FQDD Capacity—displays the physical disk capacity Disk Status—displays physical disk status.
About system event logs in web client System event log (SEL) provides status information for hardware discovered by OMIVV and displays information based on the following criteria: Status There are several status icons: Informational (blue exclamation point), Warning (yellow triangle with exclamation point), Error (red X), and Unknown (a box with a ?). Time (Server Time) Indicates the time and date when the event occurred.
Table 19. Single host information Component Information Firmware • • • The host page lets you use the search, filter, and export a CSV file of firmware information • Power Monitoring NOTE: The host time, as used here, means the local time where the host is located.
NOTE: To display the full list of details, select a specific host from the data grid. Table 20. Overview of data centers and clusters Information Description Datacenter/Cluster Information Displays the following: • • • Hardware Resources Displays the following: • • • Warranty Summary Datacenter/cluster name Number of Dell’s managed hosts Total energy consumption Total Processors Total Memory Virtual Disk Capacity Displays the warranty status for the selected host.
2. Click Datacenters or Clusters. 3. In the Objects tab, select the specific data center or cluster for which you want to view the component-specific details. 4. In the Monitor tab, select the Dell Datacenter/Cluster Information tab. On the Hardware: subtab, view the following information for each of the components. Table 21.
Table 21.
Table 22. Storage details for a data center and cluster (continued) Storage: disks Description ○ ○ ○ ○ ○ ○ ○ ○ REBUILDING INCOMPATIBLE REMOVED CLEARED SMART ALERT DETECTION UNKNOWN FOREIGN UNSUPPORTED NOTE: For more information about the meaning of these alerts, see the OpenManage Server Administrator Storage Management User's Guide at dell.
Table 22. Storage details for a data center and cluster (continued) Storage: disks Description • • ○ Read Cache Enabled ○ Read Cache Disabled Default Write Policy—displays the default write policy supported by the controller. The options include: ○ Write-Back ○ Force Write Back ○ Write Back Enabled ○ Write-Through ○ Write Cache Enabled Protected ○ Write Cache Disabled Disk Cache Policy—displays the default cache policy supported by the controller.
Table 23. Single host information (continued) Component Information • • • • • • • • • Warranty Summary NOTE: To view a warranty status, ensure to run a warranty job. See Running a warranty retrieval job. The Warranty Summary page lets you monitor the warranty expiration date. The warranty settings control when server warranty information is retrieved from Dell online by enabling or disabling the warranty schedule, and then setting the Minimum Days Threshold alert.
9 About firmware updates The OMIVV appliance allows you to perform BIOS and firmware update jobs on the managed hosts. You can perform concurrent firmware update jobs across multiple clusters or non-clustered hosts. Running concurrent firmware update on two hosts of the same cluster is not allowed. The following table lists the number of firmware update jobs that you can run simultaneously in various deployment modes, although you can schedule any number of firmware update jobs: Table 24.
• • In the Navigator pane, select a host, and then click Summary > Dell Host Information > Run Firmware Wizard. In the Navigator pane, select a host, and then click Monitor > Dell Host Information > Firmware > Run Firmware Wizard. OMIVV checks compliance of the host and whether any other firmware update job is in progress in any host within the same cluster. After the verification, the Firmware Update wizard is displayed and you can view the Welcome page.
9. Click Finish. The firmware update job takes several minutes to complete and the time varies based on the number of components included for the firmware update job. You can view the status of the firmware update jobs in the Job Queue page. To access the job queue page, in OpenManage Integration, select Monitor > Job Queue > Firmware Updates..
a. Enter the firmware update job name in the Firmware Update Job Name field. The firmware update job name is mandatory and does not use a name that is already in use. If you purge the firmware update job name, you can reuse it again. b. Enter the firmware update description in the Firmware Update Description field. The description is optional. c. Under Schedule Firmware Updates, select an option from the following: • • To run the update job now, click Update Now.
10 Events, alarms, and health monitoring The goal of hardware management is to provide the system health status and up-to-date infrastructure information that an administrator needs to respond to critical hardware events without leaving the OMIVV plug-in or vCenter. The data center and host system monitoring enables an administrator monitor infrastructure health by displaying hardware (server and storage) and virtualization-related events on the Tasks and Events tab in vCenter.
Table 25. Event posting level (continued) Event Description Post only virtualization-related critical and warning events Post virtualization-related events received from hosts into related vCenters. The virtualization-related events are events that Dell selects to be most critical to hosts that run virtual machines. When you configure the events and alarms, you can enable them.
Table 26.
Table 26.
Table 26.
Table 26.
Table 26.
Table 26. Virtualization events (continued) Event name Description Severity Recommended action configuration change occurred, which requires additional fans The fans are not redundant.
Table 26. Virtualization events (continued) Event name Description Severity Recommended action previously operating in a power redundant mode Power supply redundancy is degraded The current power operational Warning 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 27. Proactive HA events (continued) DellChassisFan Fan Chassis simulated Fan redundancy event DellChassisPower Power Chassis simulated Power redundancy event Viewing alarms and events setting Once 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. In OpenManage Integration for VMware vCenter, in the Manage > Settings tab, under vCenter Settings, expand Events and Alarms.
4. Enable Proactive HA on a cluster. See Enabling Proactive HA on a cluster. Configuring Proactive HA for Modular servers To configure for Modular servers, perform the following steps: 1. Create a connection profile and associate hosts with connection profile. See Creating a connection profile. 2. Verify that hosts inventory is completed successfully. See Viewing hosts inventory. 3. Create a chassis profile for associated chassis. See Creating a chassis profile. 4.
Table 28.
Launching Remote Access console (iDRAC) You can start the iDRAC user interface from the Dell Server Management portlet. 1. In OpenManage Integration for VMware vCenter, in the Navigator area, under Inventory Lists, click Hosts. 2. On the Object tab, double-click the host you want. 3. On the Summary tab, scroll down to the Dell Server Management portlet. 4. Click Management Consoles > Remote Access Console (iDRAC).
11 Chassis management OMIVV allows you to view additional information for chassis associated with the Modular servers. In the chassis information tab, you can view the chassis overview details for an individual chassis, information about hardware inventory, firmware and management controller, health of the individual chassis components, and chassis warranty information.
NOTE: For M1000e version 4.3 and earlier, the active errors are not displayed. Viewing hardware inventory information for chassis You can view information about the hardware inventory within the selected chassis. To view the information in this page, ensure that you run an inventory job and export a CSV file with the component information. 1. In the Home page, click vCenter. 2. In the left pane, under OpenManage Integration, click Dell Chassis. 3. In the left pane, select the corresponding chassis IP. 4.
Table 29. Hardware inventory information (continued) Hardware inventory: Component Navigation through OMIVV Information • • • • • • • In Overview tab, click I/O Modules. In Monitor tab, expand the left pane, click Hardware Inventory, and then click I/O Modules.
Viewing additional hardware configuration for chassis You can view information about the warranty, storage, firmware, management controller details within the selected chassis. To view the information in this page, ensure that you run an inventory job and export a .CSV file with the component information. To view warranty, storage, firmware, management controller details for chassis, perform the following steps: 1. In the Home page, click vCenter. 2.
Table 32. Storage information Hardware configuration Navigation through OMIVV Information • • • • • Virtual Disks Controllers Enclosures Physical Disks Hot Spares NOTE: When you click a highlighted link under storage, the View table displays the details for each highlighted item. In the view table, if you click each line item, additional information is displayed for each highlighted item.
• 88 Last Inventory Chassis management
12 Deploying hypervisor OMIVV allows you to configure the following components in the supported bare-metal servers along with deploying the hypervisor and adding it to the specified data center and cluster in a vCenter. • • • • Boot order setting RAID configuration BIOS configuration iDRAC configuration You can create hardware profiles, hypervisor profiles on the bare-metal Dell PowerEdge servers by using VMware vCenter without using PXE.
• • • • Creating deployment templates About Deployment Wizard Deployment job timing Downloading custom Dell ISO images Device discovery Discovery is the process of adding supported Dell PowerEdge bare-metal server. After a server is discovered, you can use it for hypervisor and hardware deployment. See OpenManage Integration for VMware vCenter Compatibility Matrix for the list of the PowerEdge servers required for deployment.
• Auto discovery enabled—ensure that the server’s iDRAC has auto discovery enabled so that the auto discovery process can begin. 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 by using a DHCP scope option.
4. In the Warning — Security dialog box, click Yes. 5. In the iDRAC Utility Console, press F12 once or twice. The Authentication Required dialog box is displayed. 6. In the Authentication Required dialog box, view the name that is displayed, and press Enter. 7. Enter Password. 8. Press Enter. 9. When the Shutdown/Restart dialog box is displayed, press F11. 10.
Manually configuring PowerEdge 12th and later generation servers for auto discovery Ensure that you have an iDRAC address. When you order servers from Dell, you can ask for the auto discovery feature to be enabled on the servers after you provide the provisioning server IP address. The provisioning server IP address should be the IP address of OMIVV.
Table 35. Requirements for creating hardware profile Requirements Description Boot order The boot order is the boot device sequence and hard drive sequence that you can edit only if the boot mode is set to BIOS. BIOS settings The BIOS settings include memory, processor, SATA, integrated devices, serial communications, embedded server management, power management, system security, and miscellaneous settings.
3. In the Hardware Profile Wizard, click Next on the Welcome page and do the following: • • In the Profile Name text box, enter the profile name. In the Description text box, type a description. The description is optional. 4. Click Next. The Reference Server dialog box is displayed. You can either select reference servers from the dialog box directly or through the browse button in the reference server window. 5.
iii. Select Enable Boot Sequence Retry so that the server automatically retries the boot sequence. iv. To apply the changes, click OK, or to cancel the changes, click Cancel. b. To display the hard drive sequence options, Expand Hard Drive Sequence, and click Edit. Update the following: i. To change the displayed hard drive sequence, select the device and click either Move Up or Move Down. ii. To apply the changes, click OK, or to cancel the changes, click Cancel.
Managing hardware profiles The hardware profiles define hardware configuration of a server by using a reference server. From OpenManage Integration for VMware vCenter, there are several management actions that you can perform on existing hardware profiles, including: • • Viewing or editing hardware profile Deleting hardware profile Viewing or editing hardware profile 1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates > Hardware Profiles.
Managing hypervisor profiles There are several management actions that you can perform on existing hypervisor profiles, including: • • Viewing or editing hypervisor profiles Deleting hypervisor profiles Viewing or editing hypervisor profiles 1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates > Hypervisor Profiles. The hypervisor profiles are displayed. 2. Select a profile, and click the icon. 3.
3. To confirm the template deletion, click Delete on the message box, or to cancel, click Cancel. About Deployment Wizard The Deployment Wizard describes the deployment process, which is as follows: • • • Selecting compliant bare-metal servers. Selecting a deployment template, which consists of hardware and hypervisor profiles. Selecting the installation target (hard disk or iDSDM). • • • • When you deploy hypervisor, you can deploy to an Internal Dual SD Module.
Figure 2. VLAN network. In this example network, the OMIVV appliance is on VLAN 5, while the vCenter and the VMkernal of the ESXi hosts being deployed are on VLAN 10. Since OMIVV does not support multi-VLAN homing, VLAN 5 must route to VLAN 10 for all systems to communicate to each other correctly. If routing is not enabled between these VLANs, the deployment fails.
If any of the selected servers do not support an IDSDM, or an IDSDM is not present during deployment, perform one of the following actions: ○ Select Deploy the hypervisor to the first hard disk for servers that do not have an available Internal Dual SD Module check box, if you want to deploy a hypervisor on the first hard disk of the servers. CAUTION: If you select this option and deploy the hypervisor on the first hard disk drive of the servers, all the data on the disk drives are erased.
ii. To start the job immediately, select Run Deployment Job Now. To go to the job queue after the deployment job starts, select Go to the Job Queue after the job is submitted. 11. Click Finish. After the deployment wizard tasks are complete, you can manage deployment jobs by using Job Queue. . Managing deployment jobs using Job Queue 1. In the OpenManage Integration for VMware vCenter, on the Monitor > Job Queue tab, click Deployment Jobs.
Table 38. Server states in the deployment sequence Server state Description Unconfigured The server has contacted OMIVV and is waiting to be configured. Configured The server is configured with all hardware information that is required for a successful hypervisor deployment. Downloading custom Dell ISO images The custom ESXi images that contain all Dell drivers are required for deployment. 1. Navigate to support.dell.com. 2. Under Browse for a product, click View products. 3.
13 About host, bare-metal, and iDRAC compliance To manage hosts and bare-metal servers with OMIVV, each must meet certain minimum criteria. If not compliant, they are not managed properly by OMIVV. OMIVV displays details about the noncompliance on a bare-metal or a host, and allows you to fix the noncompliance, where applicable.
2. To fix noncomplaint hosts, click Fix non-compliant vSphere Hosts. The Fix Non-compliant vSphere Hosts wizard is launched. This is a dynamic wizard and only those pages are displayed that are related to the selected noncompliant hosts. If all the selected noncompliant hosts are CSIOR-compliant, you can view the Turn On CSIOR page in the wizard. 3. In the Fix Non-compliant vSphere Hosts wizard, click Next in the Welcome page. 4.
NOTE: When deploying the OMSA agent using OMIVV, OMIVV starts the HttpClient service and enables port 8080 and releases after ESXi 5.0 to download OMSA VIB and install it. Once the OMSA installation is completed, the service automatically stops and the port is closed. NOTE: Apart from the preceding options, you can use the web client host compliance, which installs and configures the OMSA agent.
A table is displayed that lists the noncompliant servers along with the Service Tag, model, iDRAC IP, server status, compliance status, and the iDRAC license status. b. To view further details of a server, select a noncompliant server. c. To export the noncomplaint information of a server to a .CSV file, in the right-hand corner of the table, click the d. To filter the content of the data grid, click the Filter field. e. To swap the columns within the table, drag and drop columns within the data grid.
14 Security roles and permissions The OpenManage Integration for VMware vCenter stores user credentials in an encrypted format. It does not provide any passwords to client applications to avoid any improper requests. The backup database is fully encrypted by using custom security phrases, and hence data cannot be misused. By default, users in the Administrators group have all the privileges.
Dell Operational role The role contains the privileges/groups to accomplish appliance and vCenter server tasks including firmware updates, hardware inventory, restarting a host, placing a host in maintenance mode, or creating a vCenter server task. This role contains the following privilege groups: Table 39. Privilege groups Group name Description Privilege group — Dell.
○ ○ ○ ○ • Get the vCenter's Address/IP Get host IP/Address Get the current vCenter session user based on the vSphere client session ID Get the vCenter inventory tree to display the vCenter inventory in a tree structure. Dell.Monitoring.Monitor ○ Get host name for posting the event ○ Perform the event log operations, for example get the event count, or change the event log settings ○ Register, unregister, and configure events/alerts — Receive SNMP traps and post events • Dell.Configuration.
15 Troubleshooting Use this section to find answers to troubleshooting questions. This section includes: • • Frequently asked questions (FAQ) Bare-metal deployment issues on page 129 Topics: • • Frequently Asked Questions (FAQ) Bare-metal deployment issues Frequently Asked Questions (FAQ) This section contains some common questions and solutions.
iDRAC license type and description are displayed incorrectly for non-compliant vSphere hosts If a host is noncomplaint when CSIOR is disabled or has not been run, iDRAC license information is displayed incorrectly although valid iDRAC license is available. Hence, you can view the host in vSphere hosts list, but when you click the host for details, the information in iDRAC License Type is displayed as empty and iDRAC License Description is displayed as ”Your license needs to be upgraded".
The Dell provider is now listed in the Proactive HA provider list. Version affected: 4.0 Why is inventory failing when performing firmware update task on ESXi 5.x host? After registering a vCenter server, if you perform firmware update task on an ESXi 5.x host and select iDRAC as the component from the Select Component screen, the ESXi in the host might not be synchronized with the new iDRAC IP, thereby resulting in an invalid iDRAC IP provided to OMIVV.
Dell Management Center does not display all the relevant logs when trying to filter a severity category. How can I view all the logs? When you select a severity category to filter the log data by choosing All Categories from the drop-down, all the logs belonging to specific category are displayed accurately. However, if you filter by choosing Info from the drop-down, the Firmware update logs are not displayed and only the task initiation logs are displayed.
NOTE: The retrieved certificate thumbprint is in the following format: SHA1 Fingerprint=13:1E:60:93:E4:E6:59:31:55:EB:74:51:67:2A:99:F8:3F:04:83:88 The thumbprint is a sequence of numbers and alphabets which appears as follows:13:1E:60:93:E4:E6:59:31:55:EB:74:51:67:2A:99:F8:3F:04:83:88 6. Retrieve the new certificate by using the following command: "%VMWARE_CIS_HOME%"\vmafdd\vecs-cli entry getcert --store MACHINE_SSL_CERT --alias __MACHINE_CERT --output c:\certificates\new_machine.crt 7.
Retrieving the old certificate from Managed Object Browser (MOB) You can retrieve the old certificate for the vCenter server system by connecting to Platform Service Controller (PSC) by using the Managed Object Browser (MOB). To retrieve the old certificate, you should find the sslTrust field of the ArrayOfLookupServiceRegistrationInfo managed object by performing the following steps: NOTE: In this guide, the C:\certificates\ folder location is used to store all certificates. 1. Create the C:\certificates\
• • Extract the thumbprint by using a Certificate Viewer Tool. See Extracting the certificate thumbprint by using a Certificate Viewer tool on page 117. Extract the thumbprint by using a command line on the appliance. See Extracting Thumbprint by using the command line on page 117. Extracting the certificate thumbprint by using a Certificate Viewer tool Perform the following steps to extract the certificate thumbprint: 1. In Windows, double-click the old_machine.
Version Affected: 3.0 and later In Administration Console, why Update Repository Path is not set to default path after I reset appliance to factory settings? After you reset the appliance, go to the Administration Console, and then click APPLIANCE MANAGEMENT in the left pane. In the Appliance Settings page, the Update Repository Path is not changed to the default path. Resolution: In Administration Console, manually copy the path in the Default Update Repository field to the Update Repository Path field.
Why “Task cannot be scheduled for the time in the past” error in inventory schedule/warranty schedule page of Initial Configuration Wizard appear? In web client, the error “Task cannot be scheduled for the time in the past” appears: • • • if you select ‘All registered vCenters’ in the Initial Configuration wizard, and there are some vCenters with no hosts. when vCenters where some have inventory or warranty tasks already scheduled. when some vCenters with no inventory or warranty schedule set yet.
Even if repository has bundles for selected 11G system, why is firmware update displaying that there are no bundles for firmware update? When I add a host to the connection profile in lockdown mode, the inventory kicks off but failed stating that “No Remote Access Controller was found or Inventory is not supported on this host.” Inventory is supposed to work for a host in lockdown mode.
times-out for hours, although job status in LC prompts as ‘FAILED’? When the invalid DUP is picked for firmware update, the status of the task in the vCenter console window remains ‘In Progress’ but the message is changed to the reason of failure. This is a known VMware defect and will be fixed in the future releases of VMware vCenter. Resolution: The task must be canceled manually.
Why connection profiles to which host belongs to when I create\edit connection profile in web GUI cannot be seen? This happens when the vCenter server is registered to the appliance through IP instead of FQDN. Re-registering the vCenter server to the same appliance does not solve this issue. A new setup registered with FQDN is required. Why is select host window in web UI is blank on editing connection profile? This happens when the vCenter server is registered to the appliance through IP instead of FQDN.
What generation of Dell servers does OMIVV configure and support for SNMP traps? OMIVV supports OMSA SNMP traps on pre-12th generation servers and the iDRAC traps on 12th generation servers. What vCenter servers are managed by OMIVV? OMIVV manages only registered vCenter servers in either linked mode or not in a linked mode. Does OMIVV support vCenter in linked mode? Yes, OMIVV supports up to 10 vCenter servers either in a linked mode or not in a linked mode.
Table 44. Managed nodes Port number Protocols Port type Max.
has same user with new changed credentials in iDRAC user list? The password of the user used from discovery is not changed to the new credential if only hardware profile template is selected for deployment. This is done intentionally so that the plug-in is able to communicate with the iDRAC for future use in deployment needs.
For an ESXi host, ensure that you install OMSA VIB by using the VMware Remote CLI tool, and reboot the system. Can OMIVV support ESXi with lockdown mode enabled? Yes, lockdown mode is supported in this Release on hosts ESXi 5.0 and later. When I tried to use lockdown mode, it fails When I added a host to the connection profile in lockdown mode, the inventory started, but failed stating that “No Remote Access Controller was found or Inventory is not supported on this host.
NFS share is set up with ESXi ISO, but deployment fails with errors mounting share location To find the solution: 1. Ensure that the iDRAC is able to 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 removal of virtual appliance? 1. Go to Https:///mob 2. Enter the VMware vCenter admin credentials. 3. Click Content. 4. Click ExtensionManager. 5.
Performance during connection profile test credentials is slow or unresponsive The iDRAC on a server has only one user (for example, only root) and the user is in a disabled state, or all users are in a disabled state. Communicating to a server in a disabled state causes delays. To fix this issue, you can either fix the disable state of the server, or reset iDRAC on the server to re-enable the root user to default setting. To fix a server in a disabled state: 1.
After backup and restore of OMIVV, why alarm settings are not restored? Restoring the OMIVV appliance backup does not restore all the Alarm settings. However, in the OpenManage Integration for VMware GUI, the Alarms and Events field displays the restored settings. Resolution: In the OpenManage Integration for VMware GUI, in the Manage > Settings tab, manually change theEvents and Alarms settings. Bare-metal deployment issues This section deals with issues found during the deployment process.
16 Related Documentation In addition to this guide, you can access the other guides available at Dell.com/support/manuals. Click Choose from all products. In the All product dialog box, click Software and Security > Virtualization Solutions. Click OpenManage Integration for VMware vCenter 4.0.1 to access the following documents: • • • OpenManage Integration for VMware vCenter Version 4.0.1 Web Client Installation Guide OpenManage Integration for VMware vCenter Version 4.0.
