I've been doing it for years with no ill effects. The only thing I do
is change the backup/master designations in chassis redundancy to
clear the alarm about running on the backup RE:
mx960> show configuration chassis redundancy |display set
set chassis redundancy routing-engine 0 backup
set chassis redundancy routing-engine 1 master
set chassis redundancy failover on-loss-of-keepalives
set chassis redundancy failover on-disk-failure
set chassis redundancy graceful-switchover
On Thu, Jun 28, 2018 at 09:28:25AM -0500, Aaron Gould wrote:
> In my testing I haven't seen an issue with leaving it like this, however,
> that is my lab testing.... I only turned up my dual re, (5) node 100 gig
> ring of mx960's about 2 months ago with live traffic, and haven't had to do
> any issu upgrades or anything ... so I can only speak from my lab test thus
> far... but, with re1 running as master and re0 running as backup, it's been
> fine in lab.
>
> ...lab 240...
> root@lab-mx-240> show chassis routing-engine | grep "slot|state|elec"
> Slot 0:
> Current state Backup
> Election priority Master (default)
> Slot 1:
> Current state Master
> Election priority Backup (default)
>
> ...lab 960...
> {master}
> agould@lab-960> show chassis routing-engine | grep "slot|state|elec"
> Slot 0:
> Current state Backup
> Election priority Master (default)
> Slot 1:
> Current state Master
> Election priority Backup (default)
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
