[j-nsp] Regular maintenance advice

[Chuck Anderson]

On Wed, Apr 04, 2012 at 09:27:29AM +1000, Skeeve Stevens wrote:
> On Wed, Apr 4, 2012 at 04:57, Piotr Szlenk <piotr.szlenk at gmail.com> wrote:
> > Try this one. This should provide info about current code on both
> > partitions on EX series.
> >
> > > show system snapshot media internal
>
> Thanks for that Piotr.
> 
> What are the current thoughts/best practices on the snapshot?
> 
> Like your mis-match below, I have some switches which are the same.

You need to manually synchronize the software versions from primary to
backup slices on all VC members one at a time after doing a software
upgrade (and verifying you are happy with the new software).
Otherwise, if there is a failure/corruption of the primary flash, it
will boot into the backup slice running the old version.

> Should they be running a current snapshot if possible (maybe except while
> upgrading or becoming stable) ?

It is only necessary after a change in software version or after flash
corruption such as if the switch is power cycled without being
shutdown properly (substitute alternate w/1 or 2 as necessary for
repair):

ex-switch> request system snapshot media internal slice alternate member N

Another useful command to see what partitions are currently being used
for what purposes:

ex-switch> show system storage partitions
fpc0:
--------------------------------------------------------------------------
Boot Media: internal (da0)
Active Partition: da0s2a
Backup Partition: da0s1a
Currently booted from: active (da0s2a)

Partitions information:
  Partition  Size   Mountpoint
  s1a        184M   altroot   
  s2a        184M   /         
  s3d        369M   /var/tmp  
  s3e        123M   /var      
  s4d        62M    /config   
  s4e               unused (backup config)