So, after using branch series SRX’s for a long while, I am very familiar with the process of logging into the other (non-local) RE using the familiar command:

request routing-engine login node x

where x is the number of the other routing engine. But when you are on a high-end/data center SRX (like a 3000/5000 series) doing a request routing-engine ? gives you this:

{primary:node0}
user@dc-srx01> request chassis routing-engine ?
Possible completions:
  master               Set Routing Engine mastership
{primary:node0}
user@dc-srx01>

Well, that’s no good…and it’s not even a hidden command that you can force on the box, so what gives?

It appears that the correct way to do it on the high-end SRX series is this:

{primary:node0}
user@dc-srx01>start shell
%rlogin -Jk -T node1
--- JUNOS 11.4R9.4 built 2013-05-02 12:00:00 UTC
{secondary:node1}
user@dc-srx01>

assuming that you want to go to node1, obviously you can replace that with node0 if you need to get to node0 from node1. I hope this helps others out there and maybe after 2 or 3 tries at the CLI, you just googled and found this. 🙂

Happy node switching!

One thought on “High-end (aka Data Center) SRX – how the heck do you login to the other routing engine (RE)?

Leave a Reply