OpenManage Integration for VMware vCenter Version 5.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2010 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction................................................................................................................................. 5 OpenManage Integration for VMware vCenter (OMIVV) licensing............................................................................... 5 Buy software license....................................................................................................................................................... 5 Manage Licenses...........................
Reset backup and restore settings..............................................................................................................................33 Update OMIVV appliance and repository location.......................................................................................................... 34 Upgrade OMIVV appliance using RPM.............................................................................................................................
1 Introduction This guide provides instructions to install and configure OpenManage Integration for VMware vCenter (OMIVV). OMIVV is used to discover, monitor, and manage PowerEdge servers running VMware vCenter. After successfully completing the installation of OMIVV, to perform inventory management, monitoring and alerts, firmware updates, and warranty management, see OpenManage Integration for VMware vCenter User's Guide available at https://www.dell.com/support.
2. Download and save the license file to a known location. The license file might be packaged inside a .zip file. Ensure that you unzip the .zip file and upload only the license .xml file. The license file is likely to be named based on your order number, such as 123456789.xml. Manage Licenses License file for new purchases When you order a new license, an email is sent from Dell EMC after the order confirmation. You can download the new license file from the Dell EMC Digital Locker at https://www.dell.
• • For the OMIVV appliance mode, ensure that you deploy OMIVV in the appropriate mode based on your virtualization environment. For more information, see Configure deployment mode. Configure your network to match the port requirements. For more information, see Port information. Hardware requirements OMIVV supports full support for Dell EMC PowerEdge servers with full feature support for iDRAC Express and Enterprise.
Server Minimum BIOS Version R430 1.0.4 or later R530 1.0.2 or later R830 1.0.2 or later R930 1.0.2 or later R230 1.0.2 or later R330 1.0.2 or later T630 1.0.2 or later T130 1.0.2 or later T330 1.0.2 or later T430 1.0.2 or later M630 1.0.0 or later M830 1.0.0 or later FC430 1.0.0 or later FC630 1.0.0 or later FC830 1.0.0 or later Table 3. Supported BIOS version for iDRAC9-based PowerEdge servers 8 Introduction Server Minimum BIOS Version R240 1.0.0 or later R340 1.0.
Server Minimum BIOS Version MX740C 1.0.0 or later MX840C 1.0.0 or later R6515 1.0.3 or later R7515 1.0.3 or later R6525 1.0.0 or later R7525 1.2.4 or later Table 4. Supported BIOS version for vSAN Ready Nodes vSAN Ready Node Minimum BIOS Version R740xd 1.0.0 or later R640 1.0.0 or later R440 1.0.0 or later R6415 1.0.0 or later C6420 1.0.0 or later R840 1.0.0 or later Supported iDRAC with Lifecycle Controller versions Table 5.
Features Platform BIOS/Firmware Updates# Y Y Proactive HA Y Y Warranty Information Y Y Management Compliance Y Y Configuration Compliance Y Y Auto/Manual discovery of bare-metal server Y Y Bare-Metal compliance Y Y Hardware Configuration Y Y OS Deployment Y Y Blink Server LED Y Y View/Clear SEL logs Y Y Link and Launch iDRAC Y Y iDRAC reset Y Y System Lockdown Mode N Y System Profile Y Y Cluster Profile Y Y Host management using unified chassis IP N Y@ Su
Storage space required for provisioned storage The OMIVV virtual appliance requires at least 95 GB of disk space for provisioned storage. Default virtual appliance configuration The OMIVV virtual appliance is provisioned with 8 GB of RAM and two virtual CPU (Small Deployment Mode). Software requirements Ensure that the vSphere environment fulfills virtual appliance system requirements, port access, clock synchronization, and listening port requirements.
NOTE: The PowerEdge MX host is supported only when used with ESXi 6.5 U2 and later. Port information This section lists all the port requirements to configure your virtual appliance and managed nodes. Table 11. Virtual appliance Port Number Protocols Port Type Maximum Encryptio n Level Directi on Destination Usage Description 53 DNS TCP None Out OMIVV appliance to DNS server DNS client Connectivity to the DNS server or resolving the host names.
Table 12. Managed nodes (ESXi) Port Number Protocols Port Type Maximum Encryptio n Level Directio n Destination Usage Description 162 SNMP UDP None Out ESXi to OMIVV appliance Hardware Events Asynchronous SNMP traps that are sent from ESXi. This port have to open from ESXi. 443 WSMAN TCP 128-bit In OMIVV appliance to ESXi iDRAC communic ation Used to provide information to the management station. This port has to open from ESXi.
2 Install and configure OMIVV Ensure that all requirements are met and you are running the required VMware vCenter. For more information, see Hardware requirements and Software requirements. The following high-level steps outline the overall installation and configuration procedure for OMIVV: 1. Download the DellEMC_OpenManage_Integration_..zip file from the Dell support website at https://www.dell.com/support.
• • There is a route between the vCenter, OMIVV, and the iDRAC networks, if vCenter, OMIVV, and iDRAC are connected to different networks. This is applicable only If the OMIVV appliance is not configured with two NICs. The VMware vSphere environment meets virtual appliance system requirements, port access, clock synchronization, and listening port requirements. NOTE: The virtual appliance functions as a regular virtual machine.
a) In the Virtual machine name field, enter the name of the template. The name can include up to 80 characters. b) From the Select a location for the Virtual Machine list, select a location for deploying the template. c) Click Next. The Select a compute resource window is displayed. 8. From the Select a compute resource list, select the destination compute resource, and click Next. It is mandatory to select destination compute resource to proceed further.
You can use the HTTPS certificates for secure communication between OMIVV appliance and host systems. To set up this type of secure communication, send the CSR certificate to a signing authority, and then upload the resulting CSR using the admin console. There is also a default certificate that is self-signed and can be used for secure communication—this certificate is unique to every installation. 1. On the APPLIANCE MANAGEMENT page, click Upload Certificate in the HTTPS CERTIFICATES area. 2.
Downgrade deployment mode 1. Log in to the Administration Console. 2. Change the deployment mode to the required level. 3. Shut down the OMIVV appliance and change the system resources to the required level. 4. Turn on the OMIVV appliance. Register new vCenter server 1. Open Administration Console from a supported browser. To open Administration Console, start a web browser and enter https://.
Figure 2. vCenter Registration 3. In the vCenter Registration window, click Register a New vCenter Server. 4. In the Register a New vCenter Server window, perform the following substeps: a) Under vCenter Name, in the vCenter Server IP or Hostname text box, enter the server IP or FQDN, NOTE: It is recommended that you register OMIVV with the VMware vCenter by using Fully Qualified Domain Name (FQDN).
• If you are using the full product version, the license file can be downloaded from the Dell Digital Locker at https:// www.dell.com/support, and you can import this license to your virtual appliance. To import the license file, click Upload License. For more information about uploading a license, see Upload license to OMIVV Administration Console. Figure 3.
1. Create a role or modify existing role with a required privileges for the role. For more information about the list of privileges required for the role, see Required privileges for non-administrator users. For the steps required to create or modify a role and select privileges in the vSphere Client (HTML-5), see the VMware vSphere documentation 2. Assign a user to the newly created role after you define a role and select privileges for the role.
• Host profile • • Edit • View Permissions • • Modify permission • Modify role Sessions • • Validate session Task • • Create Update NOTE: If a vCenter server is registered using non-administrator user to access any OMIVV features, non-administrator user must have Dell privileges. For more information about assigning Dell privileges, see Assign Dell privileges to existing role.
Unregister vSphere Lifecycle Manager in Dell EMC administration console The vCenter must be 7.0 and later version. 1. Go to https://. 2. On the VCENTER REGISTRATION page, under vSphere Lifecycle Manager, click Unregister. The UNREGISTER VSPHERE LIFECYCLE MANAGER dialog box is displayed. 3. Click Unregister. The vSphere Lifecycle Manager is registered. The confirmation message is displayed that indicates successful unregistration of vSphere Lifecycle Manager.
NOTE: When the OMIVV appliance is not able to retrieve an IP address from the network (DHCP), 0.0.0.0 is displayed as the IP address. To resolve this, you must manually configure the static IP. a) On the Date and Time tab, select the Synchronize date and time over the network check box. The Synchronize date and time over the network check box is enabled only after NTP is configured successfully using the Admin portal.
a) Click the IPv4 Settings tab, select Manual from the Method drop-down list, and click Add. NOTE: If you select Automatic (DHCP), do not enter any IP address because the OMIVV appliance will automatically receive IP from the DHCP server during the next restart. b) Enter a valid IP, netmask (in the Classless Inter-Domain Routing (CIDR) format), and gateway information. If you enter an IP address in the Netmask box, it is automatically converted to its respective CIDR format.
NOTE: Sometimes, after you configure the OMIVV appliance with a static IP, the OMIVV terminal utility page does not immediately refresh and display the updated IP. To resolve this issue, exit the OMIVV terminal utility, and then log in again. 8. To change the hostname of the OMIVV appliance, click Change Hostname. a) Enter a valid hostname, and click Update hostname. NOTE: If any vCenter servers are already registered with the OMIVV appliance, unregister and re-register all the vCenter instances.
1. Turn off the OMIVV appliance. 2. Edit the VM settings using the vSphere Client (HTML-5) and add the additional Network adapter. To edit the VM settings, right-click VM, and then click Edit Settings. 3. Click ADD NEW DEVICE, select Network Adapter. a) Select the appropriate network for the NIC, and then select the Connect At Power On check box. b) Select the VMXNET3 adapter type from the drop-down menu. NOTE: OMIVV supports VMXNET3 type of NIC. 4. Turn on the OMIVV appliance.
WARNING: Do not use "+" to add any new network interface. It is mandatory to use the vSphere Edit Settings to add a NIC. 6. Select the NIC that you want to configure and click . 7. To identify the correct NIC, use the MAC ID displayed on the Ethernet tab, and then compare it against the MAC ID displayed in the vSphere Client (HTML-5). Ensure that you do not change the default MAC address that is listed in the Ethernet tab. 8.
a) Select Manual or Automatic (DHCP) from the Method drop-down list. b) If you select the Manual method, click Add, and then enter the valid IP address, Netmask (in the CIDR format), and gateway details. It is recommended that you use the static IP in case if you want to control over the priority of the DNS servers (primary and secondary DNS entries). Typically, vSphere elements of data center such as vCenter and ESXi hosts are managed using hostname or FQDN.
Typically, the network that you have configured as the default gateway does not require any manual route configuration because the gateway is capable of providing the reachability. However, for networks where default gateway is not configured (the Use this connection only for resources on its network check box is selected), a manual route configuration may be required. Because the default gateway is not configured for this network to reach external networks, manual routing configurations are required.
6. Click Change Admin Password. Configure Network Time Protocol (NTP) and set local time zone 1. Open the OMIVV web console. 2. In the OpenManage Integration for VMware vCenter Virtual Appliance Setup utility, click Date/Time Properties. Ensure to enter the NTP details in Admin console. For more information, see Set up Network Time Protocol (NTP) servers. 3. On the Date and Time tab, select Synchronize date and time over the network. The NTP Servers window is displayed. 4.
3. To reset the appliance, click Yes. If you click Yes, the OMIVV appliance is reset to the factory default settings and all other settings and existing data is deleted. After the factory reset is complete, register vCenters to OMIVV appliance again. NOTE: When the OMIVV appliance is reset to factory default settings, any updates that you had done on the network configuration are preserved. These settings are not reset.
Schedule automatic backups For more information about configuring the backup location and credentials, see Configuring backup and restore. 1. On the BACKUP AND RESTORE SETTINGS page, click Edit Automatic Scheduled Backup. The relevant fields are enabled. 2. To enable the backups, click Enabled. 3. Select the Days for Backup check boxes for the days of the week on which you want to run the backup jobs. 4. In Time for Backup (24 Hour, HH: mm), enter the time in the HH: mm format.
Update OMIVV appliance and repository location • • • • • To ensure that all data is protected, perform a backup of the OMIVV database before updating the OMIVV appliance. See Manage backup and restore. The OMIVV appliance requires Internet connection to display the available upgrade mechanisms and perform the RPM upgrade. Ensure that the OMIVV appliance has Internet connection. If you require a proxy network, based on the environment network settings, enable the proxy settings, and enter the proxy data.
Upgrade OMIVV appliance using backup and restore It is recommended that you do not 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.
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 click Edit. To disable Proactive HA, in the Proactive HA Failures and Responses screen, clear the check box against Dell Inc provider.
3 Configure OMIVV appliance using initial configuration wizard After you complete the basic installation of OMIVV and registration of the vCenters, the Initial Configuration Wizard is displayed automatically for the first time, when you launch OMIVV in vCenter.
If you want to modify the inventory job schedule, go to Settings > vCenter Settings > Data Retrieval Schedule > Inventory Retrieval or Jobs > Inventory > Hosts Inventory. If you want to modify the warranty retrieval job schedule, go to Settings > vCenter Settings > Data Retrieval Schedule > Warranty Retrieval or Jobs > Warranty. c) Configure events and alarms. For information about configuring events and alarms, see Configure events and alarms.
• • To download and store the host certificate and validate it during all future connections, select the Enable Certificate Check check box. To enter the credentials for hosts that are already configured and enabled for AD, select the Use Active Directory check box. • • • Enter the username in the Active Directory User Name box. Enter the username in one of the formats such as domain \username or username@domain. The username is limited to 256 characters.
2. To use the warranty features of OMIVV, you must have an Internet connection. If your environment requires proxy to reach Internet, ensure that you configure the proxy settings in the Admin portal. Hardware warranty information is retrieved from Dell Online and displayed by OMIVV. Only the Service Tag is sent and not stored by Dell Online. In PSC environment with multiple vCenter servers, the chassis warranty runs automatically with every vCenter when the warranty for any vCenter is run.
• • • • Configure latest appliance version notification Configure deployment credentials Override severity of health update notification Initial Configuration Configure warranty expiration notification Enable the warranty expiration notification to get notified if warranties for any of the hosts are nearing expiration. 1. On the OMIVV home page, click Settings > Notifications > Warranty Expiration Notification. 2. Select Enable Warranty Expiration Notification for hosts. 3.
The data grid displays all the supported Proactive HA events. The data grid columns include columns such as events id, event description, component type, default severity, and override severity column for customizing the severity of the host and its components. 2. To change severity of a host or its component, in the Override Severity column, select the required status from the drop-down list. This policy applies to all the Proactive HA hosts across all vCenter servers that are registered with OMIVV. 3.
A Accessing documents from the Dell EMC support site You can access the required documents using the following links: • • • • • • • • For Dell EMC Enterprise Systems Management documents — www.dell.com/SoftwareSecurityManuals For Dell EMC OpenManage documents — www.dell.com/OpenManageManuals For Dell EMC Remote Enterprise Systems Management documents — www.dell.com/esmmanuals For iDRAC documents — www.dell.com/idracmanuals For Dell EMC OpenManage Connections Enterprise Systems Management documents — www.
B Related Documentation In addition to this guide, you can access the other guides available at https://www.dell.com/support. Click Browse all products, then click Software > Virtualization Solutions. Click OpenManage Integration for VMware vCenter 5.1 to access the following documents: • • • OpenManage Integration for VMware vCenter Version 5.1 User's Guide OpenManage Integration for VMware vCenter Version 5.1 Release Notes OpenManage Integration for VMware vCenter Version 5.
C Contacting Dell NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: 1. Go to Dell.com/support. 2. Select your support category. 3.
