Routing

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  questions for bgp next-hop for aggregate route

    Posted 03-11-2021 15:55
    I have the following topology
    I created an aggregate route on R2, then export to iBGP,  I expect to see that route in IPS router.
    Before I configured Area 1 to be nssa, it worked fine.
    After I configured the following :
    set protocols ospf3 realm ipv4-unicast area 0.0.0.1 nssa default-lsa default-metric 10
    set protocols ospf3 realm ipv4-unicast area 0.0.0.1 nssa no-summaries
    set protocols ospf3 area 0.0.0.1 nssa default-lsa default-metric 10
    set protocols ospf3 area 0.0.0.1 nssa no-summaries

    R2 still advertised that aggregate route

    root@vMX-2# run show route advertising-protocol bgp 172.30.15.8

    inet.0: 21 destinations, 21 routes (21 active, 0 holddown, 0 hidden)
    Prefix Nexthop MED Lclpref AS path
    * 172.30.0.0/16 Self 100 I

    but R3 hides that route

    root@vMX-3# run show route hidden extensive

    inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden)
    172.30.0.0/16 (1 entry, 0 announced)
    BGP Preference: 170/-101
    Next hop type: Unusable
    Address: 0x9293e84
    Next-hop reference count: 1
    State: <Hidden Int Ext>
    Local AS: 1234 Peer AS: 1234
    Age: 5:02
    Validation State: unverified
    Task: BGP_1234.172.30.15.5+61509
    AS path: I
    Aggregator: 1234 172.30.15.5
    Accepted
    Localpref: 100
    Router ID: 172.30.15.5
    Indirect next hops: 1
    Protocol next hop: 172.30.15.5
    Indirect next hop: 0x0 - INH Session ID: 0x0

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

    Is that because the no contributing routes any more on R3, so that aggregate route is hidden ?
    How to resolve this ? 

    thanks in advance !!!




  • 2.  RE: questions for bgp next-hop for aggregate route

    Posted 03-11-2021 16:01
    I added the following to resolve it.

    set policy-options policy-statement exp2iBGP term 1 then next-hop 172.30.0.5

    God, tricky !!