SRX

last person joined: yesterday 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
  • 1.  HA cluster execute commands on peer

    Posted 04-02-2014 12:45

    Hi

     

    In an active/passive SRX cluster, if you are unabl eto log into the primary node, can you make changes on secondary node and have them sync to the primary node?

     

    Also is there command similar to Cisco ASA's 

    failover exec mate using which you can send commands to the peer?

     

    Thanks!



  • 2.  RE: HA cluster execute commands on peer

    Posted 04-02-2014 13:06

    commit synchronize

    It should be the default anyways. Check to see if you can add this comman:

    #set system commit synchronize

    Dont know about the other command



  • 3.  RE: HA cluster execute commands on peer

    Posted 04-02-2014 14:14
    Making the change in standby fw and then syncing it to the active fw wouldn't cause any issues like breaking the cluster, would it?


  • 4.  RE: HA cluster execute commands on peer
    Best Answer

    Posted 04-02-2014 14:22

    No cluster would still be fine and both nodes synched. Only thing you would need be aware is if you are making changes to policies that would affect existing sessions then for sure those sessions would be affected. BTW, is it a bug or just IP change that is preventing you from accessing main node? And what happens to console connection?



  • 5.  RE: HA cluster execute commands on peer

    Posted 04-03-2014 09:04



  • 6.  RE: HA cluster execute commands on peer

    Posted 04-03-2014 11:47

    Okay. no problem 🙂



  • 7.  RE: HA cluster execute commands on peer

    Posted 04-07-2014 00:02

    Hi there,

     

    If you can only connect to the secondary node, try either of the two commands below for access to the master:

     

    user@node> request routing-engine login node 1
    ?
    --- JUNOS 12.1X44-D20.3 built 2013-07-19 03:52:31 UTC
    No alarms currently active

    {secondary:node1}
    user@node> exit

    rlogin: connection closed

    {primary:node0}
    user@node> start shell
    % rlogin -T node1
    ?
    --- JUNOS 12.1X44-D20.3 built 2013-07-19 03:52:31 UTC
    No alarms currently active

    {secondary:node1}
    user@node>

     

    The above method is the reverse of your issue, however I just happened to be logged into the primary of my cluster.

     

    I hope that this is of help,