Ad Widget

Collapse

Item for Receive and Sent packets

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • imonteirov
    Junior Member
    • Nov 2006
    • 15

    #1

    Item for Receive and Sent packets

    What's the item to monitor traffic of In and Out on my NIC?
    ipInRequest?
    My station is Windows XP.
  • Calimero
    Senior Member
    • Nov 2006
    • 481

    #2
    Using zabbix agent or SNMP ?

    Comment

    • imonteirov
      Junior Member
      • Nov 2006
      • 15

      #3
      Yes, agent 1.1.1 . but i don't know ( and don't finding.. ) set item for monitoring Packets in/out
      Last edited by imonteirov; 14-12-2006, 19:36.

      Comment

      • Calimero
        Senior Member
        • Nov 2006
        • 481

        #4
        Don't know if it was already implemented in agent 1.1.1 but:

        net.if.in[eth0,packets]
        net.if.out[eth0,packets]

        works fine on agent 1.1.4

        Comment

        • imonteirov
          Junior Member
          • Nov 2006
          • 15

          #5
          Ok! My agent W32 is 1.1.1. ethx interface don't available . My lab use Windows...
          What's the item to monitor traffic of In and Out on my NIC with zabbix 1.1.4 and Agent W32 1.1.1?

          Comment

          • Calimero
            Senior Member
            • Nov 2006
            • 481

            #6
            Originally posted by imonteirov
            Ok! My agent W32 is 1.1.1. ethx interface don't available . My lab use Windows...
            What's the item to monitor traffic of In and Out on my NIC with zabbix 1.1.4 and Agent W32 1.1.1?
            OK, you're on Windows. I think you need to use Performance Counters, using: something like perf_counter[\Network Interface(Realtek RTL8169_8110 Family Gigabit Ethernet NIC)\Bytes Total/sec].

            I'm not familiar with these (I've only tested zabbix agent on Linux, and SNMP on both W32 ans Linux) so you should search the forum for the right syntax.

            Alternatively you could use SNMP.

            Comment

            • 753713
              Senior Member
              • Apr 2006
              • 137

              #7
              Windows Traffic Incoming/Outging dont´t working

              Hi,
              i have installed Zabbix Server 1.1.6 and Windows Agent 1.1.6.

              Item Configuration:

              Type: Zabbix Agent
              Key: net.if.out[eth0,packets]
              Type of information: Numeric (float)

              The traffic monitoring don´t working.

              server log:
              Parameter [net.if.out[eth0,packets]] is not supported by agent on host [server] Old status [0]

              Ideas? or Howto

              Christian
              Last edited by 753713; 12-02-2007, 17:15.
              ______________________________
              Version : 2.0.x
              Server OS: Ubuntu 12.04
              Zabbix Servers: 12
              Monitored Windows Server: ~ 1000
              ______________________________

              Comment

              • SierraX
                Junior Member
                • Dec 2006
                • 21

                #8
                Originally posted by 753713
                Key: net.if.out[eth0,packets]
                Afaik is a eth0 name for a Microsoft NIC not possible. Use 'ipconfig -all' in a cmd and copy the name of the Interface to the agentd.conf. Don't forget to restart the service.

                I got a similar Problem please help. The NIC got a #2 in the Name. Is there a way to use a UNIX like (\#2) way to handle this special char. Name chage of the NIC is not possible. Using of the first NIC will checked this Time but seems also not possible.
                Last edited by SierraX; 27-02-2007, 11:20.

                Comment

                • SierraX
                  Junior Member
                  • Dec 2006
                  • 21

                  #9
                  Originally posted by SierraX
                  I got a similar Problem please help. The NIC got a #2 in the Name. Is there a way to use a UNIX like (\#2) way to handle this special char. Name chage of the NIC is not possible. Using of the first NIC will checked this Time but seems also not possible.
                  Solved: I test it on a now (1.1.6) Agent. You did not need the NIC Name. The Connection Name (in German 'LAN-Verbindung') is working too. There are no special char.

                  Comment

                  Working...