Routing

last person joined: 3 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.  problem with inter-vrf on the same PE

    Posted 03-27-2013 15:53

    Hello everyone,

     

    I have to vrrf on the same PE, I need to export and import between the both vpn, but its failing, but I can see the routes on remotes PEs from the both vrf.

     

    these are the configuration

    One CE

    set policy-options policy-statement Salco_Brand_1-s term accept from community Salco_Brand_1-s
    set policy-options policy-statement Salco_Brand_1-s term accept then accept
    set policy-options policy-statement Salco_Brand_1-s term reject then reject
    set policy-options community Salco_Brand_1-s members target:16629:420


    set routing-instances V8040.Salco_Brand_1 instance-type vrf
    set routing-instances V8040.Salco_Brand_1 interface ae1.263
    set routing-instances V8040.Salco_Brand_1 route-distinguisher 16629:1844
    set routing-instances V8040.Salco_Brand_1 vrf-import Salco_Brand_1-s
    set routing-instances V8040.Salco_Brand_1 vrf-target export target:16629:475
    set routing-instances V8040.Salco_Brand_1 vrf-table-label
    set routing-instances V8040.Salco_Brand_1 protocols bgp group cliente type external
    set routing-instances V8040.Salco_Brand_1 protocols bgp group cliente peer-as 65000
    set routing-instances V8040.Salco_Brand_1 protocols bgp group cliente as-override
    set routing-instances V8040.Salco_Brand_1 protocols bgp group cliente neighbor 172.31.175.110


    soporte@PE96CHIO01-re0# run show route table V8040.Salco_Brand_1 protocol bgp source-gateway 172.31.175.110

    V8040.Salco_Brand_1.inet.0: 186 destinations, 373 routes (186 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    172.60.46.0/24      [BGP/170] 02:41:25, MED 0, localpref 100
                          AS path: 65000 I
                        > to 172.31.175.110 via ae1.263

    {master}[edit routing-instances V8040.Salco_Brand_1]

    soporte@PE96CHIO01-re0# run show route table V8040.Salco_Brand_1 172.60.46.0 detail

    V8040.Salco_Brand_1.inet.0: 186 destinations, 373 routes (186 active, 0 holddown, 0 hidden)
    172.60.46.0/24 (3 entries, 1 announced)
            *BGP    Preference: 170/-101
                    Route Distinguisher: 16629:5479
                    Next hop type: Indirect
                    Next-hop reference count: 11
                    Source: 10.20.0.211
                    Next hop type: Router, Next hop index: 1071581
                    Next hop: 10.37.13.173 via xe-0/2/0.0
                    Label operation: Push 3696, Push 518(top)
                    Next hop: 10.37.13.45 via xe-1/2/0.0, selected
                    Label operation: Push 3696, Push 1402(top)
                    Protocol next hop: 10.20.51.106
                    Push 3696
                    Indirect next hop: f85d0c0 1073022
                    State: <Secondary Active Int Ext>
                    Local AS: 16629 Peer AS: 16629
                    Age: 1:34:15    Metric: 0       Metric2: 1
                    Task: BGP_16629.10.20.0.211+179
                    Announcement bits (2): 0-KRT 1-BGP RT Background
                    AS path: ? (Originator) Cluster list:  0.0.0.10
                    AS path:  Originator ID: 10.251.10.65
                    Communities: target:16629:475
                    Import Accepted
                    VPN Label: 3696
                    Localpref: 100
                    Router ID: 10.20.0.211
                    Primary Routing Table bgp.l3vpn.0
             BGP    Preference: 170/-101
                    Route Distinguisher: 16629:5479
                    Next hop type: Indirect
                    Next-hop reference count: 11
                    Source: 10.20.0.212
                    Next hop type: Router, Next hop index: 1071581
                    Next hop: 10.37.13.173 via xe-0/2/0.0
                    Label operation: Push 3696, Push 518(top)
                    Next hop: 10.37.13.45 via xe-1/2/0.0, selected
                    Label operation: Push 3696, Push 1402(top)
                    Protocol next hop: 10.20.51.106
                    Push 3696
                    Indirect next hop: f85d0c0 1073022
                    State: <Secondary NotBest Int Ext>
                    Inactive reason: Not Best in its group - Update source
                    Local AS: 16629 Peer AS: 16629
                    Age: 1:34:15    Metric: 0       Metric2: 1
                    Task: BGP_16629.10.20.0.212+179
                    AS path: ? (Originator) Cluster list:  0.0.0.10
                    AS path:  Originator ID: 10.251.10.65
                    Communities: target:16629:475
                    Import Accepted
                    VPN Label: 3696
                    Localpref: 100
                    Router ID: 10.20.0.212
                    Primary Routing Table bgp.l3vpn.0
             BGP    Preference: 170/-101
                    Next hop type: Router, Next hop index: 64135
                    Next-hop reference count: 1
                    Source: 172.31.175.110
                    Next hop: 172.31.175.110 via ae1.263, selected
                    State: <Ext>
                    Inactive reason: AS path
                    Peer AS: 65000
                    Age: 2:42:31    Metric: 0
                    Task: BGP_65000.172.31.175.110+57472
                    AS path: 65000 I
                    Accepted
                    Localpref: 100
                    Router ID: 172.60.46.1

    {master}[edit routing-instances V8040.Salco_Brand_1]
    soporte@PE96CHIO01-re0#
    {master}[edit routing-instances V8040.Salco_Brand_1]
    soporte@PE96CHIO01-re0# run show route table V8040.Salco_Brand_1 0.0.0.0

    {master}[edit routing-instances V8040.Salco_Brand_1]
    soporte@PE96CHIO01-re0# run show route table V8040.Salco_Brand_1 10.150.86.0

    {master}[edit routing-instances V8040.Salco_Brand_1]
    soporte@PE96CHIO01-re0#

    --------------------------------------------------------------------------------------------


    Second CE

    set policy-options policy-statement Salco_Brand term accept from community Salco_Brand_3
    set policy-options policy-statement Salco_Brand term Concord then accept
    set policy-options policy-statement Salco_Brand term reject then reject
    set policy-options community Salco_Brand_3 members target:16629:475


    set routing-instances V1108.Salco_Brand instance-type vrf
    set routing-instances V1108.Salco_Brand interface ge-1/0/9.5000
    set routing-instances V1108.Salco_Brand interface ae1.92
    set routing-instances V1108.Salco_Brand route-distinguisher 16629:1207
    set routing-instances V1108.Salco_Brand vrf-import Salco_Brand
    set routing-instances V1108.Salco_Brand vrf-target export target:16629:420
    set routing-instances V1108.Salco_Brand vrf-table-label
    set routing-instances V1108.Salco_Brand routing-options static route 172.60.233.0/24 next-hop 172.15.241.158
    set routing-instances V1108.Salco_Brand protocols bgp group cliente type external
    set routing-instances V1108.Salco_Brand protocols bgp group cliente peer-as 65510
    set routing-instances V1108.Salco_Brand protocols bgp group cliente as-override
    set routing-instances V1108.Salco_Brand protocols bgp group cliente neighbor 172.31.21.226

    soporte@PE96CHIO01-re0#run show route table V1108.Salco_Brand protocol bgp next-hop 172.31.21.226

    V1108.Salco_Brand.inet.0: 729 destinations, 1470 routes (729 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    0.0.0.0/0          *[BGP/170] 3d 11:49:17, MED 0, localpref 100
                          AS path: 65510 ?
                        > to 172.31.21.226 via ae1.92
    10.150.86.0/24     *[BGP/170] 3d 11:49:17, MED 0, localpref 100
                          AS path: 65510 ?
                        > to 172.31.21.226 via ae1.92
    oporte@PE96CHIO01-re0# run show route table V1108.Salco_Brand 10.150.86.0 detail

    V1108.Salco_Brand.inet.0: 729 destinations, 1470 routes (729 active, 0 holddown, 0 hidden)
    10.150.86.0/24 (1 entry, 1 announced)
            *BGP    Preference: 170/-101
                    Next hop type: Router, Next hop index: 23723
                    Next-hop reference count: 6
                    Source: 172.31.21.226
                    Next hop: 172.31.21.226 via ae1.92, selected
                    State: <Active Ext>
                    Peer AS: 65510
                    Age: 3d 11:54:17        Metric: 0
                    Task: BGP_65510.172.31.21.226+11000
                    Announcement bits (2): 0-KRT 1-BGP RT Background
                    AS path: 65510 ?
                    Accepted
                    Localpref: 100
                    Router ID: 172.31.21.226
    soporte@PE96CHIO01-re0# run show route table V1108.Salco_Brand 0.0.0.0 detail

    V1108.Salco_Brand.inet.0: 729 destinations, 1470 routes (729 active, 0 holddown, 0 hidden)
    0.0.0.0/0 (1 entry, 1 announced)
            *BGP    Preference: 170/-101
                    Next hop type: Router, Next hop index: 23723
                    Next-hop reference count: 6
                    Source: 172.31.21.226
                    Next hop: 172.31.21.226 via ae1.92, selected
                    State: <Active Ext>
                    Peer AS: 65510
                    Age: 3d 11:54:46        Metric: 0
                    Task: BGP_65510.172.31.21.226+11000
                    Announcement bits (2): 0-KRT 1-BGP RT Background
                    AS path: 65510 ?
                    Accepted
                    Localpref: 100
                    Router ID: 172.31.21.226

    soporte@PE96CHIO01-re0# run show route table V1108.Salco_Brand 172.60.46.1

    V1108.Salco_Brand.inet.0: 729 destinations, 1470 routes (729 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    172.60.46.0/24     *[BGP/170] 13w0d 02:49:39, MED 0, localpref 100, from 10.20.0.211
                          AS path: ?
                          to 10.37.13.173 via xe-0/2/0.0, Push 3696, Push 518(top)
                        > to 10.37.13.45 via xe-1/2/0.0, Push 3696, Push 1402(top)
                        [BGP/170] 13w0d 02:49:22, MED 0, localpref 100, from 10.20.0.212
                          AS path: ?
                          to 10.37.13.173 via xe-0/2/0.0, Push 3696, Push 518(top)
                        > to 10.37.13.45 via xe-1/2/0.0, Push 3696, Push 1402(top)


    could you help me, any ideas?

    Thanks

     



  • 2.  RE: problem with inter-vrf on the same PE

    Posted 03-27-2013 16:08

    I believe you need to add auto-export under routing-options in each vrf

     

    set routing-instances xxxx routing-options auto-export



  • 3.  RE: problem with inter-vrf on the same PE
    Best Answer

    Posted 03-27-2013 16:11
    I suggest to use auto-export:

    set routing-instances <NAME> routing-options auto-export</NAME>


  • 4.  RE: problem with inter-vrf on the same PE

    Posted 03-28-2013 07:22

    cool works, thanks