Routing

Can we have console access to a new shipped RE without putting it in chassis .Idea is to downgrade or upgrade newly shipped RE before putting it in SRX5800 chassis . It will save some of our time during maintenance window. 

1. You do it in a lab similar chassis.
2.  You apply to local Juniper distributer for leasing chassis.
3. You do it right in your dual RE chassis with no downtime. 

A. Do RE as a backup, which you wanna replace (this may cause a pretty small downtime).

B. Deactivate chasiss redundacy and GRES. 

Deactivate: 

system {
    commit synchronize;
}
chassis {
    redundancy {
        failover {
            on-loss-of-keepalives;
            on-disk-failure;
        }
        graceful-switchover;
    }
}
routing-options {
    nonstop-routing;
}

C. Switch off RE, which you are going to replace and then take it out from chassis. 

D. Insert new RE, turn it on. 

E. Connect to new RE by console, make a root password, allow root to use ssh or make another super-user, assign IP address on OoB fpx0 interface. 

F. Connect to new RE by normal cable, copy a Junos to /var/tmp, check MD5 checksum, make an upgrade/downgrade.

G. At this point both RE have the same version of Junos OS. 

H. Now you should restore scripts and config on newly added RE, 

> request system scripts synchronize all 

before "commit synchronize" from Master RE, better to have minimum configuration on "added" RE like only root password. 

# commit synchronize 

K. Acticate chassis redundancy and GRES. 

WBW, 
Dmitry 

Can we have console access to a new shipped RE without putting it in chassis .Idea is to downgrade or upgrade newly shipped RE before putting it in SRX5800 chassis . It will save some of our time during maintenance window.