06-08-2009 02:43 PM - edited 03-06-2019 06:09 AM
Hi
At a remote site on stub-no-summary Area 11 and I have 2 diff WAN-MPLS providers with an ethernet handoff. I have intermittent connectivity which doesn't occur to often but when it does, it last anywhere from minutes to less than 30 min. Logs show OSPF adjacency issues on most of these mini outages. A0 is Area 0. Any ideas?
(A0)HQ(R1)---ISP#1-WAN(A11)--10.253.1.X/24(R1)10.11.9.2/24 (Area11)
\
(A0)HQ(R2)---ISP#2-WAN(A0)--10.252.11.X/24(R2)10.11.9.3/24 (Area11)
R1 and R2 has HSRP of 10.11.9.1
(R1)router ospf 1
router-id 10.253.1.11
log-adjacency-changes
area 11 stub no-summary
area 11 range 10.11.0.0 255.255.0.0
passive-interface default
no passive-interface GigabitEthernet0/0.253
no passive-interface GigabitEthernet0/1.9
network 10.11.0.0 0.0.255.255 area 11
network 10.253.1.0 0.0.0.255 area 11
(R2)router ospf 1
log-adjacency-changes
area 11 stub no-summary
area 11 range 10.11.0.0 255.255.0.0
passive-interface default
no passive-interface GigabitEthernet0/1.9
no passive-interface FastEthernet1/0
network 10.11.0.0 0.0.255.255 area 11
network 10.252.11.0 0.0.0.3 area 11
network 10.254.1.0 0.0.0.255 area 0
-----HQ R1--
router ospf 1
router-id 10.1.254.254
log-adjacency-changes
area 11 stub no-summary
area 11 range 10.11.0.0 255.255.0.0
passive-interface default
no passive-interface GigabitEthernet0/0.253
no passive-interface GigabitEthernet0/1
network 10.1.0.0 0.0.255.255 area 0
network 10.253.1.0 0.0.0.255 area 11
06-08-2009 10:42 PM
Hello Tony,
you have a remote site with two routers in area 11 totally stub.
However, one link between HQ R1 and R1 is in area 11 making the area border on HQ R1 and HQ R1 ABR(0,11).
on the other link between HQ R2 and site R2 it looks like the link is in area 0 ?
if so:
you have no simmetry with HQ R1 and site R2 acting both as ABR (0,11)
you defeat the purpose of using a totally stub area link #2 being in area 0 requires exchange of full OSPF database.
I don't think site R2 should be ABR (0,11) it shouldn't have any network area command in area 0 like the one we see:
network 10.254.1.0 0.0.0.255 area 0
even if link#2 is in area 11 as it looks like in site R2 config, the above command creates a partitioned area 0.
so link #2 has to be in area 11 site R2 should be internal to area 11.
About the time of outage:
a time from few minutes up to 30 minutes makes me think of LSA refresh time that is 1800 seconds on average.
Like a wrong or offending LSA that until it doesn't expire creates the problem.
Hope to help
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide