HI All, we have figured out how to get xymon monitoring snmp devices such as our cisco cores... the problem is any port not plugged in is alarming.. is there a way to tell xymon not to monitor ports that are not being used?
-Gavin
Gavin Leonard
[cid:image001.gif at 01CA92C4.2B2F83E0]
Director, Systems-Network Engineering
T
801-828-1735
F
801-828-1704
E
gleonard at progrexion.com<mailto:gleonard at progrexion.com>
Research | Marketing | Sales Generation
www.progrexion.com<http://www.progrexion.com/>
This email and its contents are confidential. If you are not the intended recipient, delete this email and do not use or disclose the information within this email or its attachments. Thank you.
Hi Gavin;
Can't help you, but if you tell me how you got as far as you did, I'd be happy to emulate and perhaps help.
Thanks,
.vp
HI All, we have figured out how to get xymon monitoring snmp devices such as our cisco cores… the problem is any port not plugged in is alarming.. is there a way to tell xymon not to monitor ports that are not being used?
-Gavin
On Monday, 11 January 2010 21:44:16 Gavin Leonard wrote:
HI All, we have figured out how to get xymon monitoring snmp devices such as our cisco cores...
Is it xymon (4.3 beta) that is monitoring them, or is it devmon that is polling, and reporting the results to Xymon?
the problem is any port not plugged in is alarming..
By default, devmon alarms on ports that are not shut but down. Depending on your policy on the management of network ports, either:
-disable the if_stat test, if you don't care that unshut ports are down -shut unused ports -alarm only on specific port types/names that are down and not shut, by using an appropriate except option in the DEVMON tag in bb-hosts
is there a way to tell xymon not to monitor ports that are not being used?
I haven't investigated the native SNMP support in Xymon 4.3, the above is only for devmon.
Regards, Buchan
participants (3)
-
bgmilne＠staff.telkomsa.net
-
gleonard＠progrexion.com
-
wiskbroom＠hotmail.com