Ad Widget

Collapse

NIC Teaming traffic stats

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • davewall
    Junior Member
    • Oct 2013
    • 4

    #1

    NIC Teaming traffic stats

    Hi,
    Can someone please help me determine the best way to monitor two teamed network cards on a Windows 2008R2 Server.

    I can monitor the indivual cards themselves but not the team.

    I am currently using perfmon to obtain the information.
  • steveboyson
    Senior Member
    • Jul 2013
    • 582

    #2
    It depends on how your NICs are teamed. Usually you install a teaming driver which sits on top of your NICs, practically "disabling" them. The you monitor just the teamed device (HP is doing it that way).

    What does "ipconfig /all" show? Do you see any "additional" network adapters?
    If that is the case it should appear also for the zabbix agent or in SNMP discovery.

    Comment

    • tchjts1
      Senior Member
      • May 2008
      • 1605

      #3
      We have a fair amount of servers with teamed nics where I am. I use (default) low level discovery rules which seem to pick up the team just fine.

      What version of Zabbix are you using?

      Comment

      • davewall
        Junior Member
        • Oct 2013
        • 4

        #4
        Thanks for your advice guys,

        Steve: they are HP servers using the HP driver. If I do an IPCONFIG I can see the two teams however in perfmon all it shows is indivual NIC's.

        I am using version 2.0.5 of Zabbbix, quite a newbee and not really sure how to setup discovery rules...

        Any hints

        Comment

        • steveboyson
          Senior Member
          • Jul 2013
          • 582

          #5
          could you post the output of
          "zabbix_agentd.exe -c <your-config-file> -t net.if.discovery"

          Comment

          • davewall
            Junior Member
            • Oct 2013
            • 4

            #6
            c:\Program Files\zabbix-x64>zabbix_agentd.exe -c "C:\Program Files\zabbix-x64\za
            bbix_agentd.conf" -t net.if.discovery
            net.if.discovery [s|{
            "data":[
            {
            "{#IFNAME}":"WAN Miniport (IPv6)"},
            {
            "{#IFNAME}":"WAN Miniport (Network Monitor)"},
            {
            "{#IFNAME}":"Prod Cluster HeartBeat-QoS Packet Scheduler
            -0000"},
            {
            "{#IFNAME}":"Prod Cluster HeartBeat-WFP LightWeight Filt
            er-0000"},
            {
            "{#IFNAME}":"Prod Data"},
            {
            "{#IFNAME}":"HP NC553i Dual Port FlexFabric 10Gb Converg
            ed Network Adapter"},
            {
            "{#IFNAME}":"WAN Miniport (IP)"},
            {
            "{#IFNAME}":"Prod Data-QoS Packet Scheduler-0000"},
            {
            "{#IFNAME}":"Prod Data-WFP LightWeight Filter-0000"},
            {
            "{#IFNAME}":"HP NC553i Dual Port FlexFabric 10Gb Converg
            ed Network Adapter #2"},
            {
            "{#IFNAME}":"WAN Miniport (Network Monitor)-QoS Packet S
            cheduler-0000"},
            {
            "{#IFNAME}":"WAN Miniport (IP)-QoS Packet Scheduler-0000
            "},
            {
            "{#IFNAME}":"HP NC553i Dual Port FlexFabric 10Gb Converg
            ed Network Adapter #3"},
            {
            "{#IFNAME}":"WAN Miniport (IPv6)-QoS Packet Scheduler-00
            00"},
            {
            "{#IFNAME}":"Microsoft Failover Cluster Virtual Adapter"
            },
            {
            "{#IFNAME}":"HP NC553i Dual Port FlexFabric 10Gb Converg
            ed Network Adapter #4"},
            {
            "{#IFNAME}":"Microsoft Failover Cluster Virtual Adapter-
            QoS Packet Scheduler-0000"},
            {
            "{#IFNAME}":"Microsoft Failover Cluster Virtual Adapter-
            WFP LightWeight Filter-0000"},
            {
            "{#IFNAME}":"HP NC553i Dual Port FlexFabric 10Gb Converg
            ed Network Adapter #5"},
            {
            "{#IFNAME}":"HP NC553i Dual Port FlexFabric 10Gb Converg
            ed Network Adapter #6"},
            {
            "{#IFNAME}":"Prod Cluster HeartBeat"},
            {
            "{#IFNAME}":"WAN Miniport (PPPOE)"},
            {
            "{#IFNAME}":"RAS Async Adapter"},
            {
            "{#IFNAME}":"Software Loopback Interface 1"},
            {
            "{#IFNAME}":"WAN Miniport (SSTP)"},
            {
            "{#IFNAME}":"WAN Miniport (IKEv2)"},
            {
            "{#IFNAME}":"WAN Miniport (L2TP)"},
            {
            "{#IFNAME}":"WAN Miniport (PPTP)"},
            {
            "{#IFNAME}":"Microsoft ISATAP Adapter"},
            {
            "{#IFNAME}":"Microsoft ISATAP Adapter #2"},
            {
            "{#IFNAME}":"Microsoft ISATAP Adapter #5"}]}]

            Comment

            • steveboyson
              Senior Member
              • Jul 2013
              • 582

              #7
              What about "{#IFNAME}":"Prod Data"}?
              Could it be that that is one of your teamed NIC?

              It seems you are having 3x "HP NC553i Dual Port FlexFabric 10Gb Converged Network Adapter" installed giving 6 NIC ports in total.

              I assume, "Prod Data", "Prod Cluster HeartBeat" and "Microsoft Failover Cluster Virtual Adapter" are the three teams built on top of the physical NICs.

              I would suggest you exclude all "*WAN*", "*ISATAP*", "*QoS*Scheduler", "*RAS*Async*" and "*Loopback*" adapters via a regular expression exclusion list.
              For achieving that, open the discovery rule, check that macro {#IFNAME} is linked with a correct discovery regular expression.
              Then go to Administration->General->Regular expressions (on the upper right of the screen) and insert new regExps in the previously chosen exlusion list.
              Attached Files

              Comment

              • davewall
                Junior Member
                • Oct 2013
                • 4

                #8
                Thanks Steve, very helpful, I have done what you suggested and created a new discovery with a regular expression to exlude the devices I didn't want.

                Thanks Again!

                Comment

                Working...