We are happy to announce some recent updates and bug fixes on monitoring traffic for individual VNics per virtual machine.
What we heard
We have had our ears tuned to a bunch of technical watering holes and have heard a few things. For example, you wanted to be able to monitor inbound and outbound traffic on specific virtual network adapters (vNics) on individual virtual machines in your data center.
What we did
We released a new capability for monitoring inbound and outbound traffic for individual VNics per virtual machine in UR6.
Read about it here
Now it’s your turn
If you want to take advantage of the inbound and outbound monitoring per VNic, follow the instructions in the
KB article. If you are using VMM 2012 R2 and Operations Manager together and have implemented this, make sure you have also re-associated VMM and OpsMgr. For details about how to do this
o The new Management Pack has been updated to fix bugs that caused Operations Manager to provide inaccurate information about free disk space.
VMM – OpsMgr integration and Windows Azure Pack
o Some users use large V-IPAddress sets instead of IP ranges to make it easier to add or remove individual IPs. The VMM Management Pack schema currently limits this field to 256 chars (default). However, some users have values ~500 characters long, causing discovery to break the VMM-OpsMgr integration with an unexpected exception from SCOM. This was fixed in System Center 2012 R2 UR6.