SRX

last person joined: 21 hours ago 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
  • 1.  srx3400 chassis cluster reth lag issue

    Posted 07-30-2013 15:48

    Hi All,

     

    does anyone have an idea about the following:

     

    Admin@KIR-SRX3400-2# run show lacp interfaces

    error: the lacp subsystem is not responding to management requests

    {secondary:node1}[edit] Admin@KIR-SRX3400-2#

     

    thank you for your support



  • 2.  RE: srx3400 chassis cluster reth lag issue

     
    Posted 07-30-2013 22:53

    What is the Junos version that you are using?

    You might have to open up a case with JTAC for troubleshooting.

     

    Regards,

    Raveen



  • 3.  RE: srx3400 chassis cluster reth lag issue

    Posted 08-01-2013 10:34

    Try running the command from the primary node.



  • 4.  RE: srx3400 chassis cluster reth lag issue

    Posted 08-02-2013 06:21

    from the primary node, it is working properly. but from the secondary node it gives me the following result:

     

    {secondary:node1}[edit]

    Admin@KIR-SRX3400-2# run show lacp interfaces

    error: the lacp subsystem is not responding to management requests

    {secondary:node1}[edit]

    Admin@KIR-SRX3400-2#

     

    the junos version is the one recommended by JTAC:

    {secondary:node1}[edit]
    Admin@KIR-SRX3400-2# run show version
    node0:
    --------------------------------------------------------------------------
    Hostname: KIR-SRX3400-1
    Model: srx3400
    JUNOS Software Release [11.4R7.5]

     

    thank you for your support



  • 5.  RE: srx3400 chassis cluster reth lag issue
    Best Answer

    Posted 08-04-2013 03:12

    Hi,

     

    My understanding is that some subsystem will only be available on the node that is currently primary for RG0.

     

    Best practice would be to deterimine who is primary for RG0 and then run your "show lacp interface" commands, "show route", etc...

     

    Example:

     

    node0 is primary for RG0 (control-plane)

    node1 is primary for RG1 (data-plane)

     

    You would initiate your ping from node0 because it is primary for RG0, but your ping via the data-plane (RG1) would go out via node1.

     

    Sometime "this" works because say node1 is primary for both RG0 and RG1 or node0 is primary for RG0 and RG1.  Just do your troubleshooting from whichever node is primary for RG0 and things will make more sense...

     

    Hope this helps clear up some things...

     

    I was actually experienceing this live this morning  (20130804) during a cut-over from Checkpoint Crossbeams to Juniper SRX's... and a co-worker cleared things up for me...  =_)



  • 6.  RE: srx3400 chassis cluster reth lag issue

    Posted 08-01-2013 13:39
    I've seen this before on other Srxs its when too much is happening. Or the device is not ready