Troubleshooting connectivity

[Mick]

On Saturday 01 March 2008, Hugo van der Kooij wrote:
> Mick wrote:

> | I want to monitor a network device (e.g. an IP camera) and when it
>
> fails to be
>
> | able to see which network link went down - the ISP network? the modem?
> | router? or the camera itself?
> |
> | I would try to do this by e.g. running traceroute, or tcptraceroute,


> You need to rethink the solution. You need to add more hosts in there
> that will represent your path to the camera and then use the parents
> definition to make the path clear.

Thanks Hugo, that's how I do it currently (I think).  The cable modem is 
acting as bridge so it is not ping-able, but the router is ping-able and then 
each device, e.g. the camera, is httping reachable on a particular port.  I 
thought however, that a complete tcptraceroute log would draw a comprehensive 
picture whenever a customer asks a question about failed devices.
-- 
Regards,
Mick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080301/6ee01e18/attachment.sig>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- 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