[Nagiosplug-help] Cisco Switch monitoring

[Stewart St. Dennis]

What about network sniffing tools like WireShark?

There is a philosophical / practical boundary to what Nagios should be responsible for.  At some point, specialized tools should be brought in to discover the "why" behind the "what" that Nagios uncovered. 

Just my thoughts,
Stewart

Stewart St. Dennis
CTO, ZAXIA 
-----Original Message-----
From: Leandro Roggerone <leandro_roggerone at dmcwireless.com>
Date: Wed, 04 May 2011 15:51:43 
To: <nagiosplug-help at lists.sourceforge.net>
Reply-To: Nagios Plugin Help List <nagiosplug-help at lists.sourceforge.net>
Subject: [Nagiosplug-help] Cisco Switch monitoring

  Hello everyone, I need to do a very deep monitoring on a Cisco switch, 
I have a router and a server connected through it, and somethimes it  
seems to be some comunication loss between them, I can not find anything 
related neither the router or the server, so I think it could be a 
switch issue.

Switch model is 3560.
Actually Im monitoring:
Cpu usage.
Memory usage.
Enviroment parameters
Interface status (only up and down ports) with check_ifstatus.

So, is there any other pluging to add to my schedule? Something I can 
use to figure out what the problem is ?
Is there any other plugin to check ethernet link quality? like packets, 
arp table problems ....
Any suggestion will be nice,
Thank you in advance, bye
Leo.


------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null