View Full Version : Item for Receive and Sent packets
imonteirov
14-12-2006, 02:00
What's the item to monitor traffic of In and Out on my NIC?
ipInRequest?
My station is Windows XP. :confused: :confused: :confused:
Calimero
14-12-2006, 09:20
Using zabbix agent or SNMP ?
imonteirov
14-12-2006, 18:33
Yes, agent 1.1.1 . but i don't know ( and don't finding.. ) set item for monitoring Packets in/out :confused: :confused:
Calimero
15-12-2006, 09:25
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
imonteirov
15-12-2006, 11:10
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? :confused: :confused: :confused:
Calimero
15-12-2006, 13:32
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? :confused: :confused: :confused:
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.
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
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.
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.