cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
677
Views
0
Helpful
12
Replies

WAN MPLS providers router does not inject default route

Andrey128
Level 1
Level 1

WAN MPLS providers router does not inject default route via NSSA, the route is also absent in topology database

what could be cause(s)

12 Replies 12

Hello

can ypu elaborate on your issue- at present it vague as to what the problem is-

what type of mpls vpn are you connecting to?

Do you manage your CE router and if so where does the ospf Nssa relate to in your topology 

res

paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

L3 switch running OSPF, connected to WAN router (I assume no need to focus on MPLS) via NSSA area. On WAN router respective interface is in NSSA area and OSPF does has "default-information-originate"

Hello

so your are saying your connection into the mpls is via ospf and that your rtr is an opsf stub peer in an nssa and your not receiving a default route?

What type of nssa area is this?

res

paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

site is running L3 switch with local areas in it, the site is connected to WAN MPLS router via interface which is in NSSA area (I did not  get a question about NSSA area type), neighbourship between this switch and WAN router successfully established (L3 switch is "FULL/DR", WAN router is  "FULL/DROTHER"), on WAN router's OSPF topology database I see routes from L3 switch

Hello

Looking at the config you should be receiving a type 7 default

wan rtr
sh ip ospf database self-originate
sh ip ospf database nssa-external

Lan switch
sh ip ospf database nssa-external

res
Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

on the switch :

#sh ip ospf database nssa-external


 LS age: 1362
  Options: (No TOS-capability, Type 7/5 translation, DC, Upward)
  LS Type: AS External Link
  Link State ID: 0.0.0.0 (External Network Number )
  Advertising Router: 172.16.20.2      !-> it is a primary WAN router
  LS Seq Number: 80000052
  Checksum: 0x1E13
  Length: 36
  Network Mask: /0
        Metric Type: 2 (Larger than any link state path)
        MTID: 0
        Metric: 1
        Forward Address: 10.20.130.1  -> it is IP address of primary WAN router connected to primary L3 switch (that switch does receive default route)
        External Route Tag: 0
-------------------------------------------

on the WAN router which does not generate default route:

#sh ip ospf database self-originate

            OSPF Router with ID (172.16.20.1) (Process ID 65102)

                Router Link States (Area 10.10.130.0)

Link ID             ADV Router      Age         Seq#        Checksum Link count
172.16.20.1     172.16.20.1     954         0x80000918 0x00644D  1

----------

#sh ip ospf database nssa-external

            OSPF Router with ID (172.16.20.1) (Process ID 65102)

                Type-7 AS External Link States (Area 10.10.130.0)

  LS age: 428
  Options: (No TOS-capability, Type 7/5 translation, DC, Upward)
  LS Type: AS External Link
  Link State ID: 0.0.0.0 (External Network Number )
  Advertising Router: 172.16.20.2
  LS Seq Number: 80000053
  Checksum: 0x1C14
  Length: 36
  Network Mask: /0
        Metric Type: 2 (Larger than any link state path)
        MTID: 0
        Metric: 1
        Forward Address: 10.20.130.1
        External Route Tag: 0

And maybe post the contents of route-map BGP-to-LAN

#sh route-map BGP-to-LAN
route-map BGP-to-LAN, permit, sequence 10
  Match clauses:
    ip address prefix-lists: ALLOW-DEFAULT
  Set clauses:
    tag 65102
  Policy routing matches: 0 packets, 0 bytes

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

#sh ip prefix-list ALLOW-DEFAULT
ip prefix-list ALLOW-DEFAULT: 2 entries
   seq 5 permit 0.0.0.0/0
   seq 1000 deny 0.0.0.0/0 le 32

Hello

Can post a topology of your network -looking at the external SLA it  oils be that the switch doesn't have a sla for the forwarding address for the default route 

If this isn't a production network you couldnry suppressing the advertised forward address and see if the default get installed 

Area x nssa translate type 7 suppress-at 

res

paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Julio E. Moisa
VIP Alumni
VIP Alumni

Hi,

On your router are you using vrf?:

router ospf <proccess id> vrf <name>
capability vrf-lite




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

hi

I don't have configuration rights on router, OSPF settings on it are:

#sh run | b router ospf
router ospf 65102
 router-id 172.16.20.1
 area 10.10.130.0 nssa default-information-originate
 redistribute bgp 65102 metric 10000 metric-type 1 subnets route-map BGP-to-LAN
 passive-interface default
 no passive-interface GigabitEthernet0/0/1  ! -> connection towards L3 switch
 network 10.20.130.4 0.0.0.3 area 10.10.130.0
 default-information originate always metric 10000 metric-type 1 route-map OSPF-DR-OUT

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

vrf does exist but only unused interface is assigned into it.

Andrey128
Level 1
Level 1

any idea from the community ?

Review Cisco Networking for a $25 gift card