HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

Insight with ESX - VM with multiple network

 
GARRIVIER
Occasional Visitor

Insight with ESX - VM with multiple network

Hye all,

we are using ESX 3.5 U5 on our infrastructure. The monitoring is done using Insight.

Our VM are cluster node, so using 2 networks. The monitoring is done over the public network.

When we do a dyscovery with insight the VM are recognized and associated with the ESX Server, but the IP@ is the private one (maybe because de first vswitch is the vmConsole/private network one?). We have some non-cluster related VM which are correctly discovered (ie. on the right network)

therefore, we cannot monitor our VM without manually redeclaring the VM ...

Does anyone know either how to conigure the discovery process for the VM so that the correc IP is discovered or to change the IP adress under insight after the discovery ?

regards,

DG
1 REPLY
Rob Buxton
Honored Contributor

Re: Insight with ESX - VM with multiple network

You could try adding entries into the Discovery Exclusion list. I've used that on some servers where multiple networks have confused HP SIM.