Junos OS

Expand all | Collapse all

Logical Systems with Multiple Routing Engines (how to access redundant RE)

Jump to Best Answer
  • 1.  Logical Systems with Multiple Routing Engines (how to access redundant RE)

    Posted 06-05-2015 13:08

    New to JunOS, and am a little bit unsure how logical system and inheritance between RE's work.  My goal is to have out of band management running in a sandbox, but have reachability to both routing engines via IP for monitoring purposes.  I can reach 10.2.0.20, and 10.2.0.21 (both on the active master), but cannot reach 10.2.0.22 (redundant RE).

     

    shifty@happy-scrappy-a> show route logical-system management

     

    inet.0: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden)

    + = Active Route, - = Last Active, * = Both

     

    0.0.0.0/0          *[Static/5] 23:20:09

                        > to 10.2.0.1 via fxp0.0

    10.2.0.0/24        *[Direct/0] 23:20:09

                        > via fxp0.0

                        [Direct/0] 23:20:09

                        > via fxp0.0

    10.2.0.20/32       *[Local/0] 23:20:09

                          Local via fxp0.0

    10.2.0.21/32       *[Local/0] 23:20:09

                          Local via fxp0.0

     

    {master}

     

    Looking good there, but checking backup RE:

     

    I can reach the backup RE via 'request routing-engine login re1' but get the following when I attempt to look at routes:

    shifty@happy-scrappy-b> show route logical-system management

    error: Logical-system 'management', not running

     

    {backup}

     

    shifty@happy-scrappy-a# show | display inheritance | match re0    

        ## 'happy-scrappy-a' was inherited from group 're0'

                            ## '10.2.0.20/24' was inherited from group 're0'

                                ## 'master-only' was inherited from group 're0'

                            ## '10.2.0.21/24' was inherited from group 're0'

            ## 'routing-options' was inherited from group 're0'

                ## 'static' was inherited from group 're0'

                    ## '0.0.0.0/0' was inherited from group 're0'

                    ## '10.2.0.1' was inherited from group 're0'

     

    {master}[edit]

     

     

    groups {

        re0 {

            system {

                host-name happy-scrappy-a;

            }

            logical-systems {

                management {

                    interfaces {

                        fxp0 {

                            unit 0 {

                                family inet {

                                    address 10.2.0.20/24 {

                                        master-only;

                                    }

                                    address 10.2.0.21/24;

                                }

                            }

                        }

                    }

                    routing-options {

                        static {

                            route 0.0.0.0/0 {

                                next-hop 10.2.0.1;

                                retain;

                                no-readvertise;

                            }

                        }

                    }

                }

            }

        }

        re1 {

            system {

                host-name happy-scrappy-b;

            }

            logical-systems {

                management {

                    interfaces {

                        fxp0 {

                            unit 0 {

                                family inet {

                                    address 10.2.0.20/24 {

                                        master-only;

                                    }       

                                    address 10.2.0.22/24;

                                }           

                            }               

                        }                   

                    }                       

                    routing-options {       

                        static {            

                            route 0.0.0.0/0 {

                                next-hop 10.2.0.1;

                                retain;     

                                no-readvertise;

                            }               

                        }                   

                    }                       

                }                           

            }                               

        }                                   

    }   

     

    Any assistance would be greatly appreciated!



  • 2.  RE: Logical Systems with Multiple Routing Engines (how to access redundant RE)

     
    Posted 06-05-2015 13:15

    Hi,

     

    have you applied your groups to your system ?

     

    set apply-groups "${re}"

     

     

    your backup re will only have Logical Instances active when it takes over from the master routing engine as far as I know



  • 3.  RE: Logical Systems with Multiple Routing Engines (how to access redundant RE)

    Posted 06-05-2015 14:33

    Thanks for the response,

     

    I do have the group set via 

    apply-groups [ re0 re1 ];

     

    If the logical-system is the virtual router instance that I use to access the RE's, is there a way to accomplish what I am trying to do?  Monitoring is only half of the battle, and can probably be done via SNMP with enough visability to make me happy, but I would like to have access to manually force failover if something goes wrong with the primary RE and it doesn't atutomagically flip.  Presently, my only method of access to the backup RE is through the primary.



  • 4.  RE: Logical Systems with Multiple Routing Engines (how to access redundant RE)

     
    Posted 06-05-2015 15:14
    No you can configure the fxp interface so you have out of band management...


  • 5.  RE: Logical Systems with Multiple Routing Engines (how to access redundant RE)

    Posted 06-05-2015 16:31

    Do you have a suggested configuration for the out of band management of the RE?  I went with logical-system as the virtual-router does not appear to be applicable to the fxp.  Once again, I can slap an IP, a default route, and a no re-advertise in the primary router instance, how would I make sure that the RIB does not include any of the private IPs?

     

    I'm used to cisco wherein I would just set an interface with ip forwarding vrfnamehere and walk away.



  • 6.  RE: Logical Systems with Multiple Routing Engines (how to access redundant RE)

     
    Posted 06-06-2015 00:02

    Can you try backup-router option as in below URL for the management network.

     

    http://www.juniper.net/documentation/en_US/junos14.1/topics/task/configuration/backup-router-configuring.html



  • 7.  RE: Logical Systems with Multiple Routing Engines (how to access redundant RE)
    Best Answer

     
    Posted 06-07-2015 23:08

    Unless I have understood incorrectly what you are trying to achieve, this is not supported:

     

    http://www.juniper.net/techpubs/en_US/junos14.1/topics/concept/logical-systems-restrictions.html

     

    Configuring the out-of-band management interface, such as em0 or fxp0, in a logical system is not supported.

     

    Hence it might work with unexpected side effects or it might partially work.

     



    =====

    If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.



  • 8.  RE: Logical Systems with Multiple Routing Engines (how to access redundant RE)

    Posted 07-06-2015 15:51

    Sorry for the delay, I was out of touch for a while.  Thank you for all of your responses.  I have indeed set up the "backup-router function, but my question is probably misleading.  I really just want to have private management IPs assigned to RE0 and RE1, do not want them in the primary routing instance.  I do not want public IPs assigned from this router to have reachability to the private out of band IPs.  By default, the IPs assigned to FXP0 shows up in the primary forwarding table.  I can create a VRF if I use any other port, but cannot do this for FXP0, hence why I went down the logical-system path.

     

    Unless someone can elaborate on MarcTB's comment of: 

    "No you can configure the fxp interface so you have out of band management..."

     

    I guess I will just chalk this up to "not yet implemented by Juniper".

     

    Anyhow, thanks again to everyone who chimed in.