0 Replies Latest reply on Feb 21, 2017 7:59 AM by swf5002@psu.edu

    vsphere vmkernel adapter on separate tcp/ip stack not being discovered




      I'm running vsphere 6 and I have a distributed switch.  We're monitoring vmware with NPM (no VMAN as of writing).  In vsphere 6 you can easily create new tcp/ip stacks for various functions.  We separate our vmotion traffic onto a separate stack.  I noticed however that since doing this, the vmkernel adapter associated with that new tcp/ip stack is not showing up in solarwinds.  Has anyone run into this?