Layer 2 connectivity awareness?

[RijilV]

2009/3/11 Victor Lee <durendel at gmail.com>

> In the course of my learning (just starting out) how to work with Nagios I
> have found that it isn't aware of layer 2 connections. In other words, if I
> have 2 switches with a trunk between them Nagios doesn't seem to provide me
> a way to either note that manually on the map nor does it seem to be aware
> of that type of connectivity. The same applies to servers, there doesn't
> seem to be a way to identify which switch a server is connected to. Now I
> admit this might be due to my limited knowledge of the product so I ask the
> members here. Am I correct in this assessment?
>
>

This isn't really what nagios does..  You might want to looks at something
like opsview if you want a picture of your network like that.  Also, fwiw, I
think what you're really asking for is a layer 1 map if you want to know
what host is plugged into what port - layer2 would be like what host is on a
particular broadcast domain.


I think most people give up on the nagios map pretty quickly, or at the most
setup a few partent/child hosts and leave it at that.

.r'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090311/a7a66bd1/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
-------------- next part --------------
_______________________________________________
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