[j-nsp] Regular maintenance advice

[Misha Gzirishvili]

Hi Skeeve,
I think, forwarding messages to syslog server, will avoid rutine of logging
on device.
rsyslog or syslog-ng with web interface and mysql backend will allow your
support to search for desired messages using web UI.
For uptime and disk usage -  I think, that snmp is the best way.
On Apr 3, 2012 6:44 PM, "Julien Goodwin" <jgoodwin at studio442.com.au> wrote:

> On 04/04/12 00:28, Skeeve Stevens wrote:
> > 1. Show log messages
> >
> >      a.     Look at last few days for anything suspicious
> >
> >           i.     Interfaces flapping
>
> "show int | match flap" is your friend. Also chassisd
>
> > 2. Show interfaces terse
> >
> >      a.     Anything down that shouldn’t be?
>
> Also anything *up* that shouldn't be.
>
> If you can be strict about it you can say anything but up/up and
> down/down are problems.
>
> > 3. Show chassis alarm
> >
> >      a.     Look for any alarm information
>
> If you have any EX (at least, can't remember for SRX/J, not for M/...)
> also add:
>
> show system alarms
>
> (It's sad how few people know about this)
>
> > 4. Show system snapshot
> >
> >      a.     If older than 1 week then – ‘Request system snapshot’
>
> er, why?
> Do a snapshot on OS upgrade, shouldn't be needed after that.
>
> Verifing "commit sync" is default is also good.
>
> > 5. Show system uptime
> >
> >      a.     As expected?
> >
> > 6. Show system storage
> >
> >      a.     Confirm / (root) disk space is not getting full.
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>