https://community.hpe.com/t5/server-management-systems/insight-with-esx-vm-with-multiple-network/m-p/4583512#M40148 You could try adding entries into the Discovery Exclusion list. I've used that on some servers where multiple networks have confused HP SIM. Tue, 16 Feb 2010 22:55:57 GMT Rob Buxton 2010-02-16T22:55:57Z https://community.hpe.com/t5/server-management-systems/insight-with-esx-vm-with-multiple-network/m-p/4583511#M40147 Hye all,<BR /><BR />we are using ESX 3.5 U5 on our infrastructure. The monitoring is done using Insight.<BR /><BR />Our VM are cluster node, so using 2 networks. The monitoring is done over the public network.<BR /><BR />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)<BR /><BR />therefore, we cannot monitor our VM without manually redeclaring the VM ...<BR /><BR />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 ?<BR /><BR />regards,<BR /><BR />DG Sat, 13 Feb 2010 09:41:48 GMT https://community.hpe.com/t5/server-management-systems/insight-with-esx-vm-with-multiple-network/m-p/4583511#M40147 GARRIVIER 2010-02-13T09:41:48Z https://community.hpe.com/t5/server-management-systems/insight-with-esx-vm-with-multiple-network/m-p/4583512#M40148 You could try adding entries into the Discovery Exclusion list. I've used that on some servers where multiple networks have confused HP SIM. Tue, 16 Feb 2010 22:55:57 GMT https://community.hpe.com/t5/server-management-systems/insight-with-esx-vm-with-multiple-network/m-p/4583512#M40148 Rob Buxton 2010-02-16T22:55:57Z