none
Monitoring Virtual Network on Hyper-V

    Question

  • Guys,

    Do you have some tips to monitor this scenario:

     

    1.       I have a Hyper-V cluster

    2.       I have some VMs in this Hyper-V

    3.       Each VM has your virtual network (from virtual network adapter in Hyper-V)

     

    So, what’s the best way to monitor the network traffic in these virtual networks? I need to know what’s the traffic in each VM, but without install any agent in VMs, only using the physical machine to monitor this.

     

    Any suggestion?
    Friday, August 28, 2009 12:09 AM
    Moderator

Answers

  • Actually, what you need to monitor when you do not have an agent on the Guest is outlined in this article 


    The “Hyper-V Virtual Network Adapter” and the “Hyper-V Legacy Network Adapter” counter sets allow you to see how much ingress and egress a VM is doing

    This counter sets are named with the friendly name of the VM plus the name of the network adapter followed by two GUIDs. The GUIDs are the internal id of the VM and adapter which is important when querying via WMI.

    There are two counter sets because there are two types of virtual network card you can assign to a VM. If you assign a Legacy Network Adapter then the counter set you should use is the “Hyper-V Legacy Network Adapter”. In general you should not use the network adapter type because it is not enlightened, creates a lot of CPU load in the root, and is generally slower than the Network Adapter. The challenge is you need the Legacy Network Adapter to get a VM working before installing Integration Services. Once your VM is working with Integration Services you should use the Network Adapter and the “Hyper-V Virtual Network Adapter” counter set. Keep in mind Windows Server 2008 and Windows Server 2008 R2 both have integration Services pre-installed.

    The “Hyper-V Legacy Network Adapter” counters to monitor are;

    • Bytes Dropped
    • Bytes Sent / Sec
    • Bytes Received / Sec

    In the “Hyper-V Virtual Network Adapter” you should monitor;

    • Bytes / Sec
    • Packets / Sec

    Pete Zerger, MVP-OpsMgr and SCE | http://www.systemcentercentral.com
    Friday, August 28, 2009 5:45 PM
    Moderator

All replies

  • Hi,
     
    See if you have a performance counter of those network cards on the host machines, that could be a way to monitor it.

    --

    Anders Bengtsson
    Microsoft MVP - Operations Manager
    www.contoso.se
    Friday, August 28, 2009 2:44 PM
    Moderator
  • Actually, what you need to monitor when you do not have an agent on the Guest is outlined in this article 


    The “Hyper-V Virtual Network Adapter” and the “Hyper-V Legacy Network Adapter” counter sets allow you to see how much ingress and egress a VM is doing

    This counter sets are named with the friendly name of the VM plus the name of the network adapter followed by two GUIDs. The GUIDs are the internal id of the VM and adapter which is important when querying via WMI.

    There are two counter sets because there are two types of virtual network card you can assign to a VM. If you assign a Legacy Network Adapter then the counter set you should use is the “Hyper-V Legacy Network Adapter”. In general you should not use the network adapter type because it is not enlightened, creates a lot of CPU load in the root, and is generally slower than the Network Adapter. The challenge is you need the Legacy Network Adapter to get a VM working before installing Integration Services. Once your VM is working with Integration Services you should use the Network Adapter and the “Hyper-V Virtual Network Adapter” counter set. Keep in mind Windows Server 2008 and Windows Server 2008 R2 both have integration Services pre-installed.

    The “Hyper-V Legacy Network Adapter” counters to monitor are;

    • Bytes Dropped
    • Bytes Sent / Sec
    • Bytes Received / Sec

    In the “Hyper-V Virtual Network Adapter” you should monitor;

    • Bytes / Sec
    • Packets / Sec

    Pete Zerger, MVP-OpsMgr and SCE | http://www.systemcentercentral.com
    Friday, August 28, 2009 5:45 PM
    Moderator