Routing

IMPORTANT MODERATION NOTICE

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.



Expand all | Collapse all

sharing default route 0/0 from VRF table (test.inet.0) to master table inet.0

  • 1.  sharing default route 0/0 from VRF table (test.inet.0) to master table inet.0

    Posted 07-25-2021 05:33
    Hello Experts,

    Would it be possible to share routes present in a VRF routing instance to the default routing instance? I'm only interested in sharing the default route (0/0) present in the VRF routing instance to the default routing instance.

    Here is the route table of the VRF routing instance:

    leaf1> show route table test.inet.0

    test.inet.0: 26 destinations, 44 routes (26 active, 0 holddown, 0 hidden)
    @ = Routing Use Only, # = Forwarding Use Only
    + = Active Route, - = Last Active, * = Both

    0.0.0.0/0 *[EVPN/170] 2d 01:56:25
    > to 10.180.2.116 via et-0/0/49.0
    5.5.5.0/24 @[EVPN/170] 1d 09:48:43
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    #[Multipath/255] 1d 09:48:43, metric2 0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    6.6.6.0/24 @[EVPN/170] 1d 09:48:43
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    #[Multipath/255] 1d 09:48:43, metric2 0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    7.7.7.0/24 @[EVPN/170] 1d 09:48:43
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    #[Multipath/255] 1d 09:48:43, metric2 0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    8.8.8.0/24 @[EVPN/170] 1d 09:48:43
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    #[Multipath/255] 1d 09:48:43, metric2 0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    9.9.9.0/24 @[EVPN/170] 1d 09:48:43
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    #[Multipath/255] 1d 09:48:43, metric2 0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    10.10.10.0/24 @[EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    [EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    #[Multipath/255] 2d 01:56:28, metric2 0
    > to 10.180.2.12 via et-0/0/48.0
    > to 10.180.2.12 via et-0/0/48.0
    10.180.0.0/32 *[EVPN/170] 2d 01:56:28
    > to 10.180.2.12 via et-0/0/48.0
    10.180.0.8/32 *[Direct/0] 2d 06:01:16
    > via lo0.1
    10.180.0.9/32 *[EVPN/170] 2d 01:56:24
    > to 10.180.2.12 via et-0/0/48.0
    10.180.1.8/32 *[Direct/0] 01:36:36
    > via lo0.0
    10.180.2.12/31 *[Direct/0] 01:36:36
    > via et-0/0/48.0
    10.180.2.13/32 *[Local/0] 01:36:36
    Local via et-0/0/48.0
    10.180.2.116/31 *[Direct/0] 01:36:36
    > via et-0/0/49.0
    10.180.2.117/32 *[Local/0] 01:36:36
    Local via et-0/0/49.0
    10.180.122.0/23 *[Direct/0] 2d 05:24:23
    > via irb.122
    [EVPN/170] 1d 09:48:43
    > to 10.180.2.12 via et-0/0/48.0
    10.180.122.1/32 *[Local/0] 2d 05:24:23
    Local via irb.122
    10.180.122.2/32 *[EVPN/7] 2d 01:56:28
    > via irb.122
    10.180.123.241/32 *[EVPN/7] 1d 06:04:49
    > via irb.122
    10.180.123.242/32 *[EVPN/7] 2d 05:20:59
    > via irb.122
    10.180.123.243/32 *[EVPN/7] 1d 06:04:33
    > via irb.122
    10.180.123.244/32 *[EVPN/7] 2d 00:53:27
    > via irb.122
    10.180.123.247/32 *[EVPN/7] 1d 06:03:44
    > via irb.122
    10.180.123.248/32 *[EVPN/7] 2d 05:19:17
    > via irb.122
    10.180.123.249/32 *[EVPN/7] 1d 06:03:21
    > via irb.122
    100.100.100.100/32 *[Static/5] 2d 06:01:16
    Discard


    Here is the route table of inet.0 table:

    leaf1> show route table inet.0 | no-more

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

    10.180.1.0/32 *[BGP/170] 2d 01:58:46, localpref 100
    AS path: 64601 I, validation-state: unverified
    > to 10.180.2.12 via et-0/0/48.0
    [BGP/170] 2d 01:58:43, localpref 100
    AS path: 64602 64604 64601 I, validation-state: unverified
    > to 10.180.2.116 via et-0/0/49.0
    10.180.1.1/32 *[BGP/170] 2d 01:58:43, localpref 100
    AS path: 64602 I, validation-state: unverified
    > to 10.180.2.116 via et-0/0/49.0
    [BGP/170] 2d 01:58:46, localpref 100
    AS path: 64601 64604 64602 I, validation-state: unverified
    > to 10.180.2.12 via et-0/0/48.0
    10.180.1.2/32 *[BGP/170] 2d 01:58:46, localpref 100
    AS path: 64601 64603 I, validation-state: unverified
    > to 10.180.2.12 via et-0/0/48.0
    [BGP/170] 2d 01:58:43, localpref 100
    AS path: 64602 64603 I, validation-state: unverified
    > to 10.180.2.116 via et-0/0/49.0
    10.180.1.3/32 *[BGP/170] 2d 01:58:46, localpref 100
    AS path: 64601 64604 I, validation-state: unverified
    > to 10.180.2.12 via et-0/0/48.0
    [BGP/170] 2d 01:58:43, localpref 100
    AS path: 64602 64604 I, validation-state: unverified
    > to 10.180.2.116 via et-0/0/49.0
    10.180.1.6/32 *[BGP/170] 2d 01:58:46, localpref 100
    AS path: 64601 64607 I, validation-state: unverified
    > to 10.180.2.12 via et-0/0/48.0
    [BGP/170] 2d 01:58:43, localpref 100
    AS path: 64602 64607 I, validation-state: unverified
    > to 10.180.2.116 via et-0/0/49.0
    10.180.1.7/32 *[BGP/170] 2d 01:58:46, localpref 100
    AS path: 64601 64608 I, validation-state: unverified
    > to 10.180.2.12 via et-0/0/48.0
    [BGP/170] 2d 01:58:43, localpref 100
    AS path: 64602 64608 I, validation-state: unverified
    > to 10.180.2.116 via et-0/0/49.0
    10.180.1.8/32 *[Direct/0] 2d 06:03:26
    > via lo0.0
    10.180.1.9/32 *[BGP/170] 2d 01:58:42, localpref 100
    AS path: 64601 64610 I, validation-state: unverified
    > to 10.180.2.12 via et-0/0/48.0
    [BGP/170] 2d 01:58:39, localpref 100
    AS path: 64602 64610 I, validation-state: unverified
    > to 10.180.2.116 via et-0/0/49.0
    10.180.2.12/31 *[Direct/0] 2d 05:08:33
    > via et-0/0/48.0
    10.180.2.13/32 *[Local/0] 2d 05:08:33
    Local via et-0/0/48.0
    10.180.2.116/31 *[Direct/0] 2d 05:05:59
    > via et-0/0/49.0
    10.180.2.117/32 *[Local/0] 2d 05:05:59
    Local via et-0/0/49.0
    172.16.24.0/23 *[Direct/0] 2d 05:48:07
    > via em0.0
    [Static/5] 2d 05:48:07
    > to 172.16.24.1 via em0.0
    172.16.24.126/32 *[Local/0] 2d 05:48:07
    Local via em0.0


    I used rib groups to share the route 10.180.1.8 from the inet.0 table to the test.inet.0 table and thisworked fine. Here is the config:
     
    show configuration policy-options policy-statement loopback-routes
    term loopback {
    from {
    protocol direct;
    route-filter 10.180.1.8/32 exact;
    }
    to rib test.inet.0;
    then accept;
    }
    term REJECT {
    then reject;
    }


    set policy-options policy-statement loopback-routes term loopback to rib test.inet.0
    set routing-options interface-routes rib-group inet inet.0_to_test.inet.0
    set routing-options rib-groups inet.0_to_test.inet.0 import-rib inet.0
    set routing-options rib-groups inet.0_to_test.inet.0 import-rib test.inet.0
    set routing-options rib-groups inet.0_to_test.inet.0 import-policy loopback-routes


    However, I'm  not sure what configs will be necessary to share the default route (0/0) from the test.inet.0 table to the inet.0 table. Here is what I tried and it didn't work:

    set routing-options rib-groups test.inet.0_to_inet.0 import-rib [test.inet.0 inet.0]
    set routing-options rib-groups test.inet.0_to_inet.0 import-policy defaultroute


    set policy-options policy-statement defaultroute term direct from protocol [bgp evpn]
    set policy-options policy-statement defaultroute term direct from route-filter 0/0 exact
    set policy-options policy-statement defaultroute term direct to rib inet.0
    set policy-options policy-statement defaultroute term direct then accept
    set policy-options policy-statement defaultroute term REJECT then reject


    set routing-instances test protocols bgp family inet unicast rib-group test.inet.0_to_inet.0

    Any help would be much appreciated.

    Thanks,
    B


  • 2.  RE: sharing default route 0/0 from VRF table (test.inet.0) to master table inet.0

    Posted 08-06-2021 05:28
    Have you check rib-groups? https://www.juniper.net/assets/fr/fr/local/pdf/books/day-one-poster-rib-groups.pdf

    Elvin