Routing

Expand all | Collapse all

Assistance for route advertisement in MPLS

Jump to Best Answer
  • 1.  Assistance for route advertisement in MPLS

    Posted 01-20-2021 22:01
    I have the following topology
    MXR-2
    set routing-instances branch1 instance-type vrf
    set routing-instances branch1 interface gr-0/0/10.0
    set routing-instances branch1 route-distinguisher 192.168.0.2:2
    set routing-instances branch1 vrf-target target:10458:1
    set routing-instances branch1 routing-options interface-routes rib-group inet branch12inet
    set routing-instances branch1 routing-options static route 0.0.0.0/0 next-table inet.0
    set routing-instances branch1 protocols ospf rib-group branch12inet
    set routing-instances branch1 protocols ospf export exp2Branch1
    set routing-instances branch1 protocols ospf area 0.0.0.0 interface gr-0/0/10.0 interface-type p2p

    set protocols bgp group DC type internal
    set protocols bgp group DC local-address 192.168.0.2
    set protocols bgp group DC advertise-inactive
    set protocols bgp group DC family inet-vpn unicast
    set protocols bgp group DC export exp2DC
    set protocols bgp group DC neighbor 192.168.0.3

    set policy-options policy-statement exp2DC term 1 from route-filter 0.0.0.0/0 exact
    set policy-options policy-statement exp2DC term 1 then accept

    I need to advertise 0.0.0.0/0 to MXR-3, is it possible in the way as I did above ?

    I got the following:
    root@vMX2# run show route advertising-protocol bgp 192.168.0.3 extensive 0.0.0.0

    branch1.inet.0: 28 destinations, 29 routes (28 active, 0 holddown, 0 hidden)
    * 0.0.0.0/0 (1 entry, 1 announced)
    BGP group DC type Internal
    Route Distinguisher: 192.168.0.2:2
    BGP label allocation failure: Need an interface
    Nexthop: Not advertised
    Flags: Nexthop Change
    Localpref: 100
    AS path: [10458] I
    Communities: target:10458:1

    thanks a lot for coaching !!!









  • 2.  RE: Assistance for route advertisement in MPLS
    Best Answer

     
    Posted 01-21-2021 13:52
    No, that does not work. Try sharing the default route between inet.0 and  branch1.inet.0 with rib-groups.

    Regards, 


    ------------------------------
    Yasmin Lara
    Juniper Ambassador
    JNCIE-SP, JNCIE-ENT, JNCIE-DC, JNCIE-SEC
    JNCDS-DC, JNCIA-DevOps, JNCIP-CLOUD, CCNP-ENT
    ------------------------------



  • 3.  RE: Assistance for route advertisement in MPLS

    Posted 01-21-2021 14:25
    thanks so much !!


  • 4.  RE: Assistance for route advertisement in MPLS

    Posted 01-21-2021 16:06
    I have the following, but I can't get prefixes in inet.0 into branch2.inet.0

    root@vMX3# run show route 10.200/16

    inet.0: 27 destinations, 28 routes (27 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    10.200.0.7/32 *[BGP/170] 16:43:07, localpref 100
    AS path: 65007 I, validation-state: unverified
    > to 192.168.37.7 via ge-0/0/4.0
    10.200.0.8/32 *[BGP/170] 03:09:16, localpref 100, from 192.168.0.2
    AS path: 65008 I, validation-state: unverified
    > to 192.168.34.4 via ge-0/0/2.0
    10.200.100.0/24 *[BGP/170] 16:43:07, localpref 100
    AS path: 65007 I, validation-state: unverified
    > to 192.168.37.7 via ge-0/0/4.0
    10.200.101.0/24 *[BGP/170] 16:43:07, localpref 100
    AS path: 65007 I, validation-state: unverified
    > to 192.168.37.7 via ge-0/0/4.0

    branch2.inet.0: 14 destinations, 21 routes (14 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    10.200.0.8/32 *[BGP/170] 00:54:39, localpref 100, from 192.168.0.2
    AS path: 65008 I, validation-state: unverified
    > to 192.168.34.4 via ge-0/0/2.0

    set routing-options rib-groups inet2Branch2 import-rib inet.0
    set routing-options rib-groups inet2Branch2 import-rib branch2.inet.0

    set protocols bgp group DC type internal
    set protocols bgp group DC local-address 192.168.0.3
    set protocols bgp group DC family inet unicast rib-group inet2Branch2
    set protocols bgp group DC family inet-vpn unicast
    set protocols bgp group DC export NHS
    set protocols bgp group DC neighbor 192.168.0.2
    set protocols bgp group DC neighbor 192.168.0.1

    I expected to see the two prefixes in red in inet.0 in branch2.inet.0, but I don't.

    What did I miss here ?

    thanks a lot for assistance !!








  • 5.  RE: Assistance for route advertisement in MPLS

     
    Posted 01-21-2021 19:09
    Can you post the output of show route 10.200.100.0/24 extensive? 

    Regards, 


    ------------------------------
    Yasmin Lara
    Juniper Ambassador
    JNCIE-SP, JNCIE-ENT, JNCIE-DC, JNCIE-SEC
    JNCDS-DC, JNCIA-DevOps, JNCIP-CLOUD, CCNP-ENT
    ------------------------------



  • 6.  RE: Assistance for route advertisement in MPLS

    Posted 01-21-2021 19:21
    Here is my topology
    I need to advertise 10.200/16 to Customer router.

    After applied rib-group as follows, vMX4 is what I expect to see,  I am lost why  not vMX3 too.

    root@vMX3# show protocols bgp | display set
    set protocols bgp group DC type internal
    set protocols bgp group DC local-address 192.168.0.3
    set protocols bgp group DC family inet unicast rib-group inet2Branch2
    set protocols bgp group DC family inet-vpn unicast
    set protocols bgp group DC export NHS
    set protocols bgp group DC neighbor 192.168.0.2
    set protocols bgp group DC neighbor 192.168.0.1

    root@vMX3# run show route 10.200/16

    inet.0: 27 destinations, 28 routes (27 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    10.200.0.7/32 *[BGP/170] 23:12:11, localpref 100
    AS path: 65007 I, validation-state: unverified
    > to 192.168.37.7 via ge-0/0/4.0
    10.200.0.8/32 *[BGP/170] 09:38:20, localpref 100, from 192.168.0.2
    AS path: 65008 I, validation-state: unverified
    > to 192.168.34.4 via ge-0/0/2.0
    10.200.100.0/24 *[BGP/170] 23:12:11, localpref 100
    AS path: 65007 I, validation-state: unverified
    > to 192.168.37.7 via ge-0/0/4.0
    10.200.101.0/24 *[BGP/170] 23:12:11, localpref 100
    AS path: 65007 I, validation-state: unverified
    > to 192.168.37.7 via ge-0/0/4.0

    branch2.inet.0: 14 destinations, 21 routes (14 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    10.200.0.8/32 *[BGP/170] 00:00:05, localpref 100, from 192.168.0.2
    AS path: 65008 I, validation-state: unverified
    > to 192.168.34.4 via ge-0/0/2.0

    root@vMX4# show protocols bgp | display set
    set protocols bgp group DC type internal
    set protocols bgp group DC local-address 192.168.0.4
    set protocols bgp group DC family inet unicast
    set protocols bgp group DC family inet-vpn unicast
    set protocols bgp group DC export NHS
    set protocols bgp group DC neighbor 192.168.0.2
    set protocols bgp group DC neighbor 192.168.0.1

    root@vMX4# run show route 10.200/16

    inet.0: 27 destinations, 30 routes (27 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    10.200.0.7/32 *[BGP/170] 09:38:59, localpref 100, from 192.168.0.2
    AS path: 65007 I, validation-state: unverified
    > to 192.168.34.3 via ge-0/0/2.0
    10.200.0.8/32 *[BGP/170] 23:10:58, localpref 100
    AS path: 65008 I, validation-state: unverified
    > to 192.168.48.8 via ge-0/0/4.0
    10.200.100.0/24 *[BGP/170] 23:10:58, localpref 100
    AS path: 65008 I, validation-state: unverified
    > to 192.168.48.8 via ge-0/0/4.0
    [BGP/170] 09:38:59, localpref 100, from 192.168.0.2
    AS path: 65007 I, validation-state: unverified
    > to 192.168.34.3 via ge-0/0/2.0
    10.200.101.0/24 *[BGP/170] 23:10:58, localpref 100
    AS path: 65008 I, validation-state: unverified
    > to 192.168.48.8 via ge-0/0/4.0
    [BGP/170] 09:38:59, localpref 100, from 192.168.0.2
    AS path: 65007 I, validation-state: unverified
    > to 192.168.34.3 via ge-0/0/2.0

    branch2.inet.0: 16 destinations, 23 routes (16 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    10.200.0.7/32 *[BGP/170] 00:00:03, localpref 100, from 192.168.0.2
    AS path: 65007 I, validation-state: unverified
    > to 192.168.34.3 via ge-0/0/2.0
    10.200.100.0/24 *[BGP/170] 00:00:03, localpref 100, from 192.168.0.2
    AS path: 65007 I, validation-state: unverified
    > to 192.168.34.3 via ge-0/0/2.0
    10.200.101.0/24 *[BGP/170] 00:00:03, localpref 100, from 192.168.0.2
    AS path: 65007 I, validation-state: unverified
    > to 192.168.34.3 via ge-0/0/2.0








    root@vMX3# run show route 10.200.100.0/24 extensive

    inet.0: 27 destinations, 28 routes (27 active, 0 holddown, 0 hidden)
    10.200.100.0/24 (1 entry, 1 announced)
    TSI:
    KRT in-kernel 10.200.100.0/24 -> {192.168.37.7}
    Page 0 idx 1, (group DC type Internal) Type 1 val 0x9557020 (adv_entry)
    Advertised metrics:
    Flags: Nexthop Change
    Nexthop: Self
    Localpref: 100
    AS path: [10458] 65007 I
    Communities:
    Path 10.200.100.0 from 192.168.37.7 Vector len 4. Val: 1
    *BGP Preference: 170/-101
    Next hop type: Router, Next hop index: 658
    Address: 0x960a5cc
    Next-hop reference count: 10
    Source: 192.168.37.7
    Next hop: 192.168.37.7 via ge-0/0/4.0, selected
    Session Id: 0xd
    State: <Active Ext>
    Local AS: 10458 Peer AS: 65007
    Age: 20:29:04
    Validation State: unverified
    Task: BGP_65007.192.168.37.7+179
    Announcement bits (3): 0-KRT 4-Resolve tree 4 5-BGP_RT_Background
    AS path: 65007 I
    Accepted
    Localpref: 100
    Router ID: 10.200.0.7

    [edit]

    thanks a lot !!



  • 7.  RE: Assistance for route advertisement in MPLS

     
    Posted 01-21-2021 22:49
    As I suspected, these routes are not coming from 192.168.0.1 or 192.168.0.2, but from a different router: 192.168.37.7 

    From the configuration  you shared, the rib-group in under group DC where only neighbors 192.168.0.1 or 192.168.0.2 are configured. Thus, the only routes the rib-group will be applied to, would be the BGP routes from these two neighbors. 

    set protocols bgp group DC type internal
    set protocols bgp group DC local-address 192.168.0.3
    set protocols bgp group DC family inet unicast rib-group inet2Branch2
    set protocols bgp group DC family inet-vpn unicast
    set protocols bgp group DC export NHS
    set protocols bgp group DC neighbor 192.168.0.2
    set protocols bgp group DC neighbor 192.168.0.1

    Regards, 


    ------------------------------
    Yasmin Lara
    Juniper Ambassador
    JNCIE-SP, JNCIE-ENT, JNCIE-DC, JNCIE-SEC
    JNCDS-DC, JNCIA-DevOps, JNCIP-CLOUD, CCNP-ENT
    ------------------------------



  • 8.  RE: Assistance for route advertisement in MPLS

    Posted 01-21-2021 22:57
    thanks so much for your pinpoint.  I got it.