[j-nsp] Regular maintenance advice

[Gordon Smith]

 Most of this you can automate on your monitoring boxes.
 e.g. use rancid to generate an email on config changes, interfaces 
 flapping & chassis alarms will generate SNMP alerts.

 You only need to snapshot when upgrading code. Definitely make that 
 part of the upgrade procedure, and let rancid keep track of the config.

 Another thing to look at would be BGP peers - number of routes, 
 uptimes, etc. Low uptimes on a peer can indicate a problem at the far 
 end that the cust isn't aware of.

 Cheers,
 Gordon


 On Wed, 4 Apr 2012 00:28:09 +1000, Skeeve Stevens wrote:
> Hey all,
>
> I am designing a document for low level technicians to regularly
> (depending on sensitivity of the device) login to the Juniper
> router/or switch to look around and make sure that things are 'ok'.
>
> I am seeking comments of anything else that would be useful for an
> technician to look at that would catch their eye that something is
> potentially wrong.
>
> So far I have:
>
> ---
>
> RJ01 – Router
>
> Description: Standard Juniper Router or Switch
>
> 1. Show log messages
>
>      a.     Look at last few days for anything suspicious
>
>           i.     Interfaces flapping
>
> 2. Show interfaces terse
>
>      a.     Anything down that shouldn’t be?
>
>
> 3. Show chassis alarm
>
>      a.     Look for any alarm information
>
> 4. Show system snapshot
>
>      a.     If older than 1 week then – ‘Request system snapshot’
>
> 5. Show system uptime
>
>      a.     As expected?
>
> 6. Show system storage
>
>      a.     Confirm / (root) disk space is not getting full.
>
>