View Only


This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.

  • 1.  Advertsing an Aggregate Route

    Posted 03-25-2014 06:13



       This is a simple advertisement of an aggregate route between two routers. Router3 is advertising the aggregate via BGP to Router2. I see that Router2 is receiving the route from Router3 but it's hidden it. When I check why it states that it's "looped". However, I don't see how that can be looped if the AS that Router3 is using is 3333 and the AS the Router2 is using is 2222. Can you guys please check what mistake you see? Just to be clear Router1 and Router2 are not two physical devices they are both routing instances within a single device. Thank you










    Router2 Output:


    root# bgp table Router2.inet.0 hidden

    Router2.inet.0: 5 destinations, 5 routes (4 active, 0 holddown, 1 hidden)
    Prefix Nexthop MED Lclpref AS path 3333 I



    root# run show route protocol bgp table Router2.inet.0 hidden extensive

    Router2.inet.0: 5 destinations, 5 routes (4 active, 0 holddown, 1 hidden) (1 entry, 0 announced)
    Next hop type: Router
    Address: 0x15c0944
    Next-hop reference count: 1
    Next hop: via lt-0/0/0.6, selected
    State: <Hidden Ext>
    Peer AS: 3333
    Age: 37:00
    Task: BGP_3333_2222.
    AS path: 3333 I (Looped: 3333) Aggregator: 3333
    Router ID:






    Router3 Output:


    root# show routing-instances Router3
    routing-options {
    aggregate {
    protocols {
    bgp {
    group ROUTER2 {
    type external;
    description "Advertise Router3 Loopbacks to Router2";
    export ADV_AGR;
    peer-as 2222;
    local-as 3333;




    root# run show interfaces terse routing-instance Router3
    Interface Admin Link Proto Local Remote
    lt-0/0/0.3 up up inet
    lt-0/0/0.7 up up inet
    lo0.102 up up inet





    root# show policy-options
    policy-statement ADV_AGR {
    from protocol aggregate;
    then accept;






  • 2.  RE: Advertsing an Aggregate Route

    Posted 03-25-2014 07:06

    Hi there,

    I see You are using routing instances, and most likely on the same physical router, and not separate physical boxes, is that correct?

    if yes, then please:

    1/ change Your misleading diagram, and

    2/ use either "as-loops" command, or "independent-domain"

    The root cause is that JUNOS checks for AS path loops _across_ ALL_AS_numbers configured on the box, be it inside VR/VRF/LS or in global instance.




  • 3.  RE: Advertsing an Aggregate Route

    Posted 03-25-2014 07:36

    Hi Alex,


      Sorry for the misleading diagram. Regarding the loop I was expericing this is only happens when one running routing instances within a single device since all routing instances belong to a single primary routing instance domain is that correct? Thank you



  • 4.  RE: Advertsing an Aggregate Route
    Best Answer

    Posted 03-25-2014 08:50


    If Your BGP peers are one inside VR and another in inet.0, and they use different AS numbers, then when announcing routes to each other both of them will detect a loop due to AS path check for own ASN being performed across _ALL_ ASN_ configured on local box.

    Consider using iBGP, "loops" or "independent-domain" to overcome this scenario.



  • 5.  RE: Advertsing an Aggregate Route

    Posted 03-25-2014 10:14

    Okay got it. Thank you