First, I don't fully understand the whole Discovery aspect of things, so this could be something totally obvious I'm missing ...
I can setup a Discovery rule that uses icmp + zabbix agent, to pick up all the hosts on a network ... I can also setup an Action that adds those hosts that have Zabbix Agent running, and properly link them to a desired template ... piece of cake, love the system so far.
The problem is trying to get an Action that auto-adds Cisco switches, for example ...
I have my Discovery rule for the network setup so that it checks:
ICMP Ping, SNMPv1 agent, Zabbix agent
When I enable and check on the Monitor -> Discovery page, it finds all of the pingable IPs ... in this case, they are all Cisco switches, no server/hosts on that network ...
The problem is that, from what I can tell, its not finding an SNMP agent there ... if my understanding is correct, on the 'Monitor -> Discovery' page, the right columns only get created if/when a check succeeds ... in my case, I have a column for iCMP, but nothing for SNMP or Zabbix (which I take to mean it wasn't able to access either at those IPs ) ...
I've checked the dchecks table within the database, to make sure my community string is correct, as well as tested it with snmpget, and it works great:
snmpget -c <community string> -v 1 <ip> sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Cisco Internetwork Operating System Software
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(11)EA1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Wed 28-Aug-02 10:25 by antonino
the following is a screen shot of my Discovery Rule ... *seems* very straightforward from what I can tell ...
One thought I had was that OID <-> Name translation wasn't working, so I've tried the same rule above, but instead of sysDescr.0, I have:
.1.3.6.1.2.1.1.1.0
I wiped out the old rule and built a fresh, so that there wasn't anything 'stuck' in the database ... that doesn't appear to make a difference either ...
So, I'm at a loss ... I figure its something obvious in setting this up that I'm overlooking ... or a bug I can't find having been previously reported ...
Help?
Thx
I can setup a Discovery rule that uses icmp + zabbix agent, to pick up all the hosts on a network ... I can also setup an Action that adds those hosts that have Zabbix Agent running, and properly link them to a desired template ... piece of cake, love the system so far.
The problem is trying to get an Action that auto-adds Cisco switches, for example ...
I have my Discovery rule for the network setup so that it checks:
ICMP Ping, SNMPv1 agent, Zabbix agent
When I enable and check on the Monitor -> Discovery page, it finds all of the pingable IPs ... in this case, they are all Cisco switches, no server/hosts on that network ...
The problem is that, from what I can tell, its not finding an SNMP agent there ... if my understanding is correct, on the 'Monitor -> Discovery' page, the right columns only get created if/when a check succeeds ... in my case, I have a column for iCMP, but nothing for SNMP or Zabbix (which I take to mean it wasn't able to access either at those IPs ) ...
I've checked the dchecks table within the database, to make sure my community string is correct, as well as tested it with snmpget, and it works great:
snmpget -c <community string> -v 1 <ip> sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Cisco Internetwork Operating System Software
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(11)EA1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Wed 28-Aug-02 10:25 by antonino
the following is a screen shot of my Discovery Rule ... *seems* very straightforward from what I can tell ...
One thought I had was that OID <-> Name translation wasn't working, so I've tried the same rule above, but instead of sysDescr.0, I have:
.1.3.6.1.2.1.1.1.0
I wiped out the old rule and built a fresh, so that there wasn't anything 'stuck' in the database ... that doesn't appear to make a difference either ...
So, I'm at a loss ... I figure its something obvious in setting this up that I'm overlooking ... or a bug I can't find having been previously reported ...
Help?
Thx
Comment