Operational Defect Database
BugZero found this defect 4969 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Hewlett Packard Enterprise | c02548131
Advisory: VMware ESXi - Insight Control Virtual Machine Management (VMM) API "getVEServerList" Command Fails to Return VMware ESXi Hosts of a Registered vCenter if the VMKernel Port Used for Management Traffic Is Not Named "Management Network"
Last update date:
2/29/2024
Affected products:
HPE ProLiant BL260c G5 Server Blade
HPE ProLiant BL280c G6 Server Blade
HPE ProLiant BL2x220c G6 Server Blade
HPE ProLiant BL460c G5 Server Blade
HPE ProLiant BL460c G6 Server Blade
HPE ProLiant BL460c Server Blade
HPE ProLiant BL465c G5 Server Blade
HPE ProLiant BL465c G6 Server Blade
HPE ProLiant BL465c Server Blade
HPE ProLiant BL480c Server Blade
HPE ProLiant BL490c G6 Server Blade
HPE ProLiant BL495c G5 Server Blade
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
The Virtual Machine Manager (VMM) API "getVEServerList" command returns the VMware ESXi hosts for a given vCenter. The vCenter credentials must have been entered in the VMM UI prior to executing this API. This API is used by: HP Systems Insight Manager (HP SIM) to associate a VMware ESXi host to a vCenter server. The association is "HostToVME." Virtualization Manager (VMan) uses the data to filter the registered ESXi hosts for a given vCenter. In VMware ESXi, the default name of the Virtual Machine (VM) Kernel port used for management traffic is "Management Network." These names can be edited from the vCenter client UI. However, if these names are modifed, the API will not report the ESXi host in the output of "getVEServerList." This will result in the following: The association between the host and vCenter will not appear in HP SIM. In the VMan page when trying to activate a Logical Server, the ESXi hosts show up as "Rejected Target Hosts" with an error that the hosts are not part of vCenter. The VMan page can be viewed by using the following menu sequence: Tools > Virtualization Manager. Change the perspective to "Logical Servers" by selecting from the dropdown box: Tools > Logical Servers > Activate.
Scope
Any ProLiant server configured with VMware ESXi and managed using Insight Control Virtual Machine Manager Versions 6.0, 6.1, 6.1.x and 6.2.
Resolution
Modify the "Network Label" of the VMKernel port used for management traffic to "Management Network" by performing the following: Log into the vCenter using the vCenter client. Select the "Hosts and Clusters" view from the menu View > Inventory. Select the ESXi server from the tree displayed in the left pane. Select the "Configuration" tab from the right pane. From the "Hardware" section, select "Networking." Click "Properties" for the Virtual Switch where the VMKernel port used for management traffic is located. In case there are multiple VMKernel ports located on multiple virtual switches and configured for management traffic, select the switch that has the VMKernel port that has the IP that is registered with Insight Control virtual machine management (VMM) OR that will be used for registration with VMM. In the pop-up that displays the virtual switch properties, select the service console port and click the "Edit" button. Change the Network Label to "Management Network" and click OK. Close the virtual switch properties pop-up window. Note : It can take a maximum of five minutes for the cache to get refreshed and the API to report the ESXi host. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HP Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: http://www.hp.com/go/myadvisory NAVIGATION TIP : For hints on navigating HP.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to the Navigation Tips document . SEARCH TIP : For hints on locating similar documents on HP.com, refer to the Search Tips document .
