Enumerating Interfaces

[Greg Pangrazio]

That is the solution we are working towards now as well.  we didn't
have a good way at the start and just needed to track the states of
the ports.  Most of ours are redundant wan links anyway so if the host
is down we don't need to be alerted on the ports anyway.

Greg Pangrazio





On Wed, Sep 8, 2010 at 11:48 AM, Max <perldork at webwizarddesign.com> wrote:
> What I have done in the past and currently do is that each port that
> is connected to another networking device is modelled as a Nagios host
> - the host check is then the SNMP port status and the IF stats are
> collected as services on the host.  The parent of the port is the
> network device itself and that way any child devices can be associated
> with the port and will be marked as unreachable should the port be
> administratively or operationally turned down.
>
> - Max
>
> On Wed, Sep 8, 2010 at 12:22 PM, Jason Frisvold <frisvolj at lafayette.edu> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 09/07/2010 05:45 PM, Greg Pangrazio wrote:
>>> Well we use similar switches here.  what we do is create the host then
>>> services for the interfaces and if we have port channels I use the
>>> multiple check_service_cluster for all the interfaces in the port
>>> channel.  I just use check snmp for the interfaces.  If you want more
>>> specifics i can give you config definitions and command defs etc.
>>
>> Yeah, that's kind of what I settled with so far..  Testing it out on the
>> SAN switches and maybe I'll move that config to other switches too..
>> I'm using PNP4Nagios, so I wrote a custom script to check the
>> ifOperStatus and get the traffic information on the port as well.  So a
>> single check is telling me status, throughput, errors, and discards...
>>
>> I am running into one problem, though, and I'm not sure how to handle
>> it..  How are you handling parent/child for these ports, or are you?  In
>> other words, I'd like to pair the device connected to the port with the
>> port itself.  However, I'm enumerating each switch for the ports, so I
>> don't have individual services for each device/port combo...  My config
>> looks something like this :
>>
>> define service {
>>   use                     service-standard
>>   hosts                   fcswitch1.example.com,fcswitch2.example.com
>>   servicegroups           fc-switch-standard
>>   service_description     Switch Port fc1/1
>>   check_command           check_snmp_traffic!fc1/1!-C $USER2$
>> }
>>
>> I think I'm going to have to enumerate each host/port combo, or live
>> without parent/child...  *sigh*
>>
>>> Greg Pangrazio
>>
>>
>> - --
>> - ---------------------------
>> Jason Frisvold
>> Network Engineer
>> frisvolj at lafayette.edu
>> - ---------------------------
>> "What I cannot create, I do not understand"
>>   - Richard Feynman
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.14 (GNU/Linux)
>> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAkyHuFwACgkQO80o6DJ8UvmAsACaAugytCgxrgsePwlNbrw27Cpi
>> rkgAn0e4leboXWricN/+5CtiC07TkUm0
>> =rEMU
>> -----END PGP SIGNATURE-----
>>
>> ------------------------------------------------------------------------------
>> This SF.net Dev2Dev email is sponsored by:
>>
>> Show off your parallel programming skills.
>> Enter the Intel(R) Threading Challenge 2010.
>> http://p.sf.net/sfu/intel-thread-sfd
>> _______________________________________________
>> Nagios-users mailing list
>> Nagios-users at 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
>>
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
>

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Nagios-users mailing list
Nagios-users at 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