Hello Rab,
I monitor the following services on my Cisco Switches.
Ping
Uplink status + bandwidth utilisation
CPU (Avg 5 mins)
Environment (FAN, PSU)
If my server was connected to the network as below:
Server1 => Switch1 => Switch2 => Localhost (Nagios)
I would configure the parent/child relationship this way.
Server1 Parent = Switch1
Switch1 Parent = Switch2
Switch2 Parent = Localhost
If you do this you will end up with the Nagios network map looking like
your network documentation. Also If switch2 does down Nagios will
assume Switch1 and Server1 are also unavailable and will suppress
notifications.
I have also setup service dependencies so that all my switch as follows
define servicedependency {
dependent_host_name HPK3044
dependent_service_description CPU 5 min
average,Environmental monitoring,Link to HPD-LRE Bandwidth,Link to
HPD-LRE Status,Link to HPKDC1 Bandwidth,Link to HPKDC1 Status,Vlan 1
Bandwidth,Vlan 1 Status
host_name HPK3044
service_description Ping
inherits_parent 1
execution_failure_criteria w,u,c
notification_failure_criteria w,u,c
dependency_period 24x7
This makes all the monitored services on the switch dependant on the
switch being pingable. If the ping service is in the warning, critical
or unknown state all the other services will not produce notifications.
Hope this helps
Chris Macleod
From: Robert Jackson [mailto:r...@walkermartyn.co.uk]
Sent: 13 August 2010 10:20
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] What Switch Metric Are You Monitoring
I'm currently on Nagios Core 3.2.1 and I'm just starting to setup
monitoring of our network switches. Can someone share what switch
metrics they are recording (and find most useful). Just now, I'm only
registering PING and Uptime (through SMNP). Also how are you handling
parent/child relationships for the switches/ports etc? Basically if a
switch is down, then I would only want to receive and alert regarding
this and not anything else related to the port or device connected to
the port.
Regards,
Rab.
=====================================================
Robert Jackson Phone: +44 (0) 141 332
7999
IT Manager Fax: +44 (0) 141
331 2820
Walker Martyn Ltd
1 Park Circus Place Email:
r...@walkermartyn.co.uk <mailto:r...@walkermartyn.co.uk>
Glasgow G3 6AH, Scotland Web:
http://www.walkermartyn.co.uk <http://www.walkermartyn.co.uk>
=====================================================
************************************************************************
The information in this internet E-mail is confidential and is intended
solely for the addressee. Access, copying or re-use of information in it
by anyone else is unauthorised. Any views or opinions presented are
solely those of the author and do not necessarily represent those of
Walker Martyn Ltd or any of its affiliates. If you are not the intended
recipient please contact administra...@walkermartyn.co.uk.
Walker Martyn Ltd, company number SC197533. Company is registered in
Scotland and has its registered office at 1 Park Circus Place, Glasgow
G3 6AH, UK.
****************************************************************
________________________________________________________________________
This e-mail has been scanned for all viruses by MessageLabs. TEG-IN
________________________________________________________________________
This e-mail has been scanned for all viruses by Message Labs.
Please enjoy our brands responsibly. www.drinkaware.co.uk
The Edrington Group is a private limited company registered in Scotland
(Registered Number SC 36374) with its Registered Office at 2500 Great Western
Road, Glasgow, G15 6RW.
________________________________________________________________________
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null