[j-nsp] Regular maintenance advice

[Skeeve Stevens]

Tom,

Phil just did that.... nice too.

*Skeeve Stevens, CEO*
eintellego Pty Ltd
skeeve at eintellego.net ; www.eintellego.net <http://www.eintellego.net.au>

Phone: 1300 753 383 ; Fax: (+612) 8572 9954

Cell +61 (0)414 753 383 ; skype://skeeve

facebook.com/eintellego

twitter.com/networkceoau ; www.linkedin.com/in/skeeve

PO Box 7726, Baulkham Hills, NSW 1755 Australia

The Experts Who The Experts Call
Juniper - Cisco – Brocade - IBM



On Wed, Apr 4, 2012 at 04:18, Tom Storey <tom at snnap.net> wrote:

> On 3 April 2012 15:41, Julien Goodwin <jgoodwin at studio442.com.au> wrote:
> > If you can be strict about it you can say anything but up/up and
> > down/down are problems.
>
> What about SONET/SDH interfaces that display down/up?
>
> The interface can be admin down, but if its still receiving a
> SONET/SDH signal from the other side then line proto will be up -
> nothing necessarily wrong with that. :-)
>
> In reply to Skeeves original email, is there any reason you couldn't
> script something like this? At least give a device a once over and
> produce a summary report of "problems for this device" after which the
> tech can then target only devices that have issues that need
> attention. Otherwise you find yourself wasting time looking at a bunch
> of boxes that dont need to be looked at when you could be doing
> something more productive.
>
> Or better yet, syslog and SNMP traps collectors and some scripts that
> produce a dashboard highlighting any issues detected. :-)
>
> Scripts, scripts, scripts everywhere. :-)
>