Routing

 View Only
last person joined: yesterday 

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.  OSPF Type 2 LSA not in routing table

    Posted 15 days ago

    I am trying to get an OSPF Area 0 type 2 LSA (received from remote OSPF router) to be installed in the routing table C.inet.0 (The inet.0 for the routing table in which OSPF is configured).   The route is not being exported.  I've tried route import and route import to a rib group with no luck.  Any idea what I'm doing wrong?   This is an evpn-vxlan fabric underneath and the OSPF configuration is built inside one of the routing instances (C).  

    root@S2ompute-001-leaf2# show routing-instances C
    instance-type vrf;
    routing-options {
        graceful-restart;
        multipath;
        auto-export;
    }
    protocols {
        ospf {
            area 0.0.0.0 {
                network-summary-import 10.160;
                interface et-0/0/3.0;
                interface lo0.6;
            }
            rib-groups {
                inet VRF_C;
            }
            export STATIC;
            import 10.160;
        }
    }
    description "Routing Zone C";
    interface et-0/0/0.0;
    interface et-0/0/3.0;
    interface irb.330;
    interface irb.410;
    interface irb.420;
    interface irb.430;
    interface lo0.6;
    route-distinguisher 172.23.0.139:499;
    vrf-target target:100499L:1;
     
    [edit]
    root@S2compute-001-leaf2#
     
    root@S2ompute-001-leaf2# run show ospf database instance C
     
        OSPF database, Area 0.0.0.0
     Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
    Router   10.201.201.9     10.201.201.9     0x8000008d   514  0x2  0x8c4c  72
    Router   172.23.0.146     172.23.0.146     0x80000023  1222  0x22 0x7684  60
    Router  *172.23.0.159     172.23.0.159     0x8000005c   857  0x22 0xc58d  48
    Network *10.201.201.6     172.23.0.159     0x80000050   560  0x22 0xe1f8  32
        OSPF AS SCOPE link state database
     Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
    Extern  *10.3.30.100      172.23.0.159     0x80000037  2560  0x22 0x2e5b  36
    Extern   10.160.0.0       172.23.0.146     0x80000001  1222  0x22 0xbcf4  36.  <-----  Trying to import this route to the C.inet.0 routing table. 
     
    root@S2compute-001-leaf2# run show route table C.inet.0
     
    C.inet.0: 20 destinations, 40 routes (20 active, 0 holddown, 0 hidden)
    Restart Complete
    @ = Routing Use Only, # = Forwarding Use Only
    + = Active Route, - = Last Active, * = Both
    ... TRUNCATED
                   to 172.23.1.134 via et-0/0/54.0
                        >  to 172.23.1.146 via et-0/0/55.0
                        [EVPN/170] 4d 22:23:22
                           to 172.23.1.134 via et-0/0/54.0
                        >  to 172.23.1.146 via et-0/0/55.0
                        [EVPN/170] 4d 22:23:22
                           to 172.23.1.134 via et-0/0/54.0
                        >  to 172.23.1.146 via et-0/0/55.0
                        [EVPN/170] 4d 22:23:24
                           to 172.23.1.134 via et-0/0/54.0
                        >  to 172.23.1.146 via et-0/0/55.0
    10.4.20.1/32       *[Local/0] 3d 17:42:29
                           Local via irb.420
    10.4.30.0/24       *[Direct/0] 3d 17:42:29
                        >  via irb.430
                        [EVPN/170] 4d 22:23:24
                        >  to 172.23.1.134 via et-0/0/54.0
                           to 172.23.1.146 via et-0/0/55.0
                        [EVPN/170] 4d 22:23:26
                        >  to 172.23.1.134 via et-0/0/54.0
                           to 172.23.1.146 via et-0/0/55.0
                        [EVPN/170] 4d 22:23:22
                        >  to 172.23.1.134 via et-0/0/54.0
                           to 172.23.1.146 via et-0/0/55.0
                        [EVPN/170] 4d 22:23:22
                        >  to 172.23.1.134 via et-0/0/54.0
                           to 172.23.1.146 via et-0/0/55.0
                        [EVPN/170] 4d 22:23:24
                        >  to 172.23.1.134 via et-0/0/54.0
                           to 172.23.1.146 via et-0/0/55.0
    10.4.30.1/32       *[Local/0] 3d 17:42:29
                           Local via irb.430
    10.201.201.0/31    *[EVPN/170] 4d 22:23:22
                           to 172.23.1.134 via et-0/0/54.0
                        >  to 172.23.1.146 via et-0/0/55.0
    10.201.201.4/32    *[Local/0] 2d 18:23:54
                           Reject
    10.201.201.6/31    *[Direct/0] 2d 18:00:38
                        >  via et-0/0/3.0
    224.0.0.5/32       *[OSPF/10] 3w3d 14:24:47, metric 1
                           MultiRecv
     
    [edit]


    ------------------------------
    Todd Ritchie
    ------------------------------


  • 2.  RE: OSPF Type 2 LSA not in routing table

    Posted 14 days ago

    OSPF in an instance type of VRF can be a little misleading.  While you may be running OSPF w/in the VRF, for the routes(LSA's) to be learned from another site, the routing info is announced from VRF to VRF via BGP.  So route redistribution from BGP to OSPF ends up happening, and when doing so, it causes OSPF to place the routes received from another site as Type 5 LSA's.  A work around is to use a sham-link that creates a "tunnel" (so to speak) that allows LSA's to be exchanged from VRF to VRF as if they  were on the same site or LAN.  


    Original Message


  • 3.  RE: OSPF Type 2 LSA not in routing table

    Posted 14 days ago

    My issue wasn't so much with peering across VRFs.. I can export routes easily enough.  The issue is, a firewall is sitting between VRF A and B..   That firewall is doing the ospf peering with each vrf.    I ended up fixing the problem and am still chasing root cause.  The firewall is a Fortigate and it was bringing the ospf neighbor to full status.  There was a interface-type mismatch, though, so the neighbor should have never gone to full status.   Fixing the mismatch resolved the problem.  


    Juniper Business Use Only




    Original Message