cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 9

intermittent trouble following VMs after vMotion

We're running Orion NPM v10.1.2, APM v4.0, IVIM v1.1 and our VMWare environment is ~90% ESX v4.1 with the remaining 10% awaiting upgrade from v4.0.

I've noticed that we periodically lose connectivity to virtual machines after they get moved to another ESX host.  The network adapters go into an "unknown" state and can't recover.  The original usually needs to be manually deleted and then we have to poll the VM resources again to get the "new", working vmxnet adapter.  Since our ESX environment can perform these moves just for load-balancing and without administrator intervention, it's a cause for some concern.  Has anyone else seen this?

Tags (2)
4 Replies
Level 19

Have you tried a scheduled discovery? That should detect the changes and correct the monitoring.

0 Kudos

Yes we do have scheduled discoveries running but this doesn't correct it without intervention.  If I discover and import the new vmxnet adapter, the VM will still show as warning with one NIC in an unknown state until I manually delete that old vmxnet adapter. 

0 Kudos

OK, it looks like you are doing everything correctly. I'll mark this for a PM to review.

0 Kudos

Much appreciated

0 Kudos