OSPF neighbor flapping

Unanswered Question
May 5th, 2010
User Badges:

Hi All,


There is an OSPF neighbor continuously changing state between Down and Full. I recieve the following output from log:


May  5 10:43:29.253: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 10:44:44.053: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 10:45:50.265: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 10:48:12.677: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 10:50:26.140: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 10:52:29.612: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 10:53:45.420: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 10:54:51.636: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 10:55:57.532: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done


Router#sh clock
12:56:50.328 utc Wed May 5 2010


Where I should look for the solution? I would appreciate any suggestions. Thank you in advance.


Regards,

Jopeti.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
spremkumar Wed, 05/05/2010 - 05:57
User Badges:
  • Red, 2250 points or more

hi


can you post the show run and show ip route outputs taken from your router.


Might be a case of 2 routes to reach the tunnel destination using which the tunnel is formed and flapping now.


regds

francisco_1 Wed, 05/05/2010 - 06:08
User Badges:
  • Gold, 750 points or more

might be a recursive issue!




Make sure that the tunnel end points (ie. tunnel source and destination) are not advertised in OSPF as this would definitely create instability as well.



Also good to  configure the RID statically on all routers using the router-id command under the ospf process as follow:


router ospf 1

router-id x.x.x.x



Francisco

jopetik09 Wed, 05/05/2010 - 07:47
User Badges:

Hi,


The tunnel end points not advertised in ospf at all.

It was running fine before, recently we have migrated on to new public IP pool at hub site and the changed the crypto map & nhrp pointing to new IP. Hence we are facing this flapping issue.


Please find the attached sh run and ip route (below in the file)

Attachment: 
spremkumar Wed, 05/05/2010 - 07:57
User Badges:
  • Red, 2250 points or more

Hi


can you post the output of show logs from both the routers?


regds

jopetik09 Wed, 05/05/2010 - 09:01
User Badges:

Hi,


Please find the below logs from spoke & hub router.


SPOKE:


#sh log
Syslog logging: enabled (1 messages dropped, 6 messages rate-limited,
                0 flushes, 0 overruns, xml disabled, filtering disabled)
    Console logging: level debugging, 125579 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging: level debugging, 125584 messages logged, xml disabled,
                    filtering disabled
    Logging Exception size (4096 bytes)
    Count and timestamp logging messages: disabled

No active filter modules.

    Trap logging: level informational, 125699 message lines logged
        Logging to 10.246.6.40(global) (udp port 514, audit disabled,  link up), 125699 message lines logged, xml disabled,
               filtering disabled
        Logging to 10.246.6.50(global) (udp port 514, audit disabled,  link up), 125699 message lines logged, xml disabled,
               filtering disabled

Log Buffer (4096 bytes):
2.535: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:27:29.904: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:28:28.176: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:30:02.028: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:30:34.720: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:30:44.009: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:31:09.441: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:31:27.341: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:31:42.137: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:32:14.777: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:33:40.761: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:34:32.065: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:35:05.950: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:36:11.514: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:36:52.306: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:37:18.970: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:37:47.554: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:38:24.450: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:39:29.911: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:39:58.359: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:40:20.171: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:40:53.243: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:41:13.271: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:41:14.543: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:43:43.984: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:44:50.960: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:45:52.388: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:46:45.328: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:46:48.828: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:47:54.809: %CRYPTO-4-IKE_DEFAULT_POLICY_ACCEPTED: IKE default policy was matched and is being used.
May  5 15:47:59.989: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:49:25.413: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:51:01.426: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:53:34.698: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:54:32.566: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:55:38.331: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.99.22 on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:56:36.603: %PARSER-5-CFGLOG_LOGGEDCMD: User:gua  logged command:!exec: enable


HUB:


#sh log
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited,
                0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.


No Inactive Message Discriminator.


    Console logging: disabled
    Monitor logging: disabled
    Buffer logging:  level debugging, 11009 messages logged, xml disabled,
                     filtering disabled
    Logging Exception size (4096 bytes)
    Count and timestamp logging messages: disabled
    Persistent logging: disabled

No active filter modules.

ESM: 0 messages dropped

    Trap logging: level informational, 11015 message lines logged
        Logging to 10.246.6.40  (udp port 514,  audit disabled,
              authentication disabled, encryption disabled, link up),
              11015 message lines logged,
              0 message lines rate-limited,
              0 message lines dropped-by-MD,
              xml disabled, sequence number disabled
              filtering disabled
        Logging to 10.246.6.50  (udp port 514,  audit disabled,
              authentication disabled, encryption disabled, link up),
              11015 message lines logged,
              0 message lines rate-limited,
              0 message lines dropped-by-MD,
              xml disabled, sequence number disabled
              filtering disabled

Log Buffer (10000 bytes):
15:50:56.971: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:50:57.743: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xxx on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:50:57.795: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:50:57.815: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:51:01.447: %OSPF-5-ADJCHG: Process 1, Nbr 10.30.x.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:51:01.531: %OSPF-5-ADJCHG: Process 1, Nbr 10.27.x.xxx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:51:01.663: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:51:06.895: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:51:07.187: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:51:07.615: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xxx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:51:44.247: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/0 (not full duplex), with DKIGNFW02.ignordic.com FastEthernet0/0 (full duplex).
May  5 15:51:49.067: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:52:44.247: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/0 (not full duplex), with DKIGNFW02.ignordic.com FastEthernet0/0 (full duplex).
May  5 15:54:32.587: %OSPF-5-ADJCHG: Process 1, Nbr 10.30.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:54:32.643: %OSPF-5-ADJCHG: Process 1, Nbr 10.27.x.xxx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:54:32.771: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:54:37.731: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:54:37.827: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xxx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:54:38.235: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:54:44.251: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/0 (not full duplex), with DKIGNFW02.ignordic.com FastEthernet0/0 (full duplex).
May  5 15:55:29.191: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:55:32.643: %OSPF-5-ADJCHG: Process 1, Nbr 10.30.x.x on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:55:32.659: %OSPF-5-ADJCHG: Process 1, Nbr 10.27.x.xxx on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:55:32.667: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:55:33.335: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:55:33.583: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xxx on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:55:38.351: %OSPF-5-ADJCHG: Process 1, Nbr 10.30.x.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:55:38.423: %OSPF-5-ADJCHG: Process 1, Nbr 10.27.xx.xxx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:55:38.523: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:55:43.051: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:55:44.051: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:55:44.251: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/0 (not full duplex), with DKIGNFW02.ignordic.com FastEthernet0/0 (full duplex).
May  5 15:55:44.455: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xxx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:56:26.447: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:56:44.251: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/0 (not full duplex), with DKIGNFW02.ignordic.com FastEthernet0/0 (full duplex).
May  5 15:57:44.251: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/0 (not full duplex), with DKIGNFW02.ignordic.com FastEthernet0/0 (full duplex).
May  5 15:58:17.907: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:58:21.975: %OSPF-5-ADJCHG: Process 1, Nbr 10.27.x.xxx on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:58:22.051: %OSPF-5-ADJCHG: Process 1, Nbr 10.30.x.x on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:58:22.239: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:58:22.711: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xxx on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:58:22.767: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired
May  5 15:58:27.335: %OSPF-5-ADJCHG: Process 1, Nbr 10.30.x.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:58:27.419: %OSPF-5-ADJCHG: Process 1, Nbr 10.27.x.xxx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:58:27.527: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:58:31.851: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:58:33.071: %OSPF-5-ADJCHG: Process 1, Nbr 10.31.xx.x on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:58:33.327: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xxx on Tunnel0 from LOADING to FULL, Loading Done
May  5 15:58:44.255: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/0 (not full duplex), with DKIGNFW02.ignordic.com FastEthernet0/0 (full duplex).
May  5 15:58:53.123: %PARSER-5-CFGLOG_LOGGEDCMD: User:gua  logged command:!exec: enable

francisco_1 Wed, 05/05/2010 - 09:08
User Badges:
  • Gold, 750 points or more

Looks like the ospf is reloading after the duplex issue!!!


Sugegst you fix duplex issue fand see what the outcome is..


May  5 15:55:44.251: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/0 (not full duplex), with DKIGNFW02.ignordic.com FastEthernet0/0 (full duplex).
May  5 15:55:44.455: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.xxx.xxx on Tunnel0 from LOADING to FULL, Loading Done

jopetik09 Thu, 05/06/2010 - 02:24
User Badges:

Hi,


I dont think the duplex issues is causing OSPF reload / flap. Because duplex mismatch between (1841 IOSFW's DKIGNFW02 & DKIGNFW01) which are in hub site.

And we have number of s2s DMVPN tunnels from hub to spoke sites, remaining all are working fine except one site tunnel is flapping.


And one more thing the duplex mismatch is happening for every 1 hour hardly but tunnel flapping happening for every 2 minutes.

spremkumar Thu, 05/06/2010 - 02:36
User Badges:
  • Red, 2250 points or more

Hi Jopeti


Is the config between the other spoke sites and this one verified ? if not can you try and compare the config of a working spoke location with this location?


Also any change been done in the hub site with respect to this spoke ?


regds

jopetik09 Fri, 05/07/2010 - 07:59
User Badges:

Hi Prem,


The config is same as other spokes which are stable.

The last change is... We migrated on new internet line and new public IP pool at hub site, then the peer IP changed at spoke sites from old to new like below.


crypto isakmp key xxxxxxxxxxxxxx address 195.44.24.x no-xauth --- OLD

crypto isakmp key xxxxxxxxxxxxxx address 193.14.4.x no-xauth --- NEW


And in the tunnel "interface Tunnel0"


ip nhrp map 192.168.xxx.x 195.44.24.x --- OLD
ip nhrp map multicast 195.44.24.x


ip nhrp map 192.168.220.1 193.14.4.x --- NEW
ip nhrp map multicast 193.14.4.x


And this change done before 20 days back, we experiencing this issue since one week.

stonnet72 Fri, 05/07/2010 - 12:30
User Badges:

Just out of curiosity, have you performed a debug ip OSPF? Perhaps there is some information in there that can help you get to the root of your problem. Initially, I would have guessed that it was a duplex issue because of your logs. Also perform a sh ip os data. Perhaps there the routes are not in the database.


Hope that helps.

jopetik09 Wed, 05/12/2010 - 06:10
User Badges:

Hi,


Please find the below required details

I verified the ospf database and found routes are there.


Debug OSPF:


May 11 14:13:50.935:    Add External Route to 192.168.134.0. Metric: 20, Next Hop: 192.168.220.1

May 11 14:13:50.935: OSPF: insert route list LS ID 192.168.134.0, type 5, adv rtr 10.28.1.1

May 11 14:13:50.935: OSPF: Start processing Type 5 External LSA 192.168.220.0, mask 255.255.255.0, adv 10.28.1.1, age 512, seq 0x80003E68, metric 20, metric-type 2

May 11 14:13:50.935:    Add better path to LSA ID 192.168.220.0, gateway 192.168.220.1, dist 20

May 11 14:13:50.935:    Add path: next-hop 192.168.220.1, interface Tunnel0

May 11 14:13:50.935: OSPF: delete lsa id 192.168.220.0, type 5, adv rtr 10.28.1.1 from delete list

May 11 14:13:50.935:  network update dest_addr 192.168.220.0 mask 255.255.255.0 gateway 192.168.220.1

May 11 14:13:50.935: OSPF: insert route list LS ID 192.168.220.0, type 5, adv rtr 10.28.1.1

May 11 14:13:50.935: OSPF: Start processing Type 5 External LSA 193.163.208.0, mask 255.255.255.0, adv 10.28.1.1, age 512, seq 0x80003C50, metric 20, metric-type 2

May 11 14:13:50.935:    Add better path to LSA ID 193.163.208.0, gateway 192.168.220.1, dist 20

May 11 14:13:50.935:    Add path: next-hop 192.168.220.1, interface Tunnel0

May 11 14:13:50.935: OSPF: delete lsa id 193.163.208.0, type 5, adv rtr 10.28.1.1 from delete list

May 11 14:13:50.935:  network update dest_addr 193.163.208.0 mask 255.255.255.0 gateway 192.168.220.1

May 11 14:13:50.935: OSPF: insert route list LS ID 193.163.208.0, type 5, adv rtr 10.28.1.1

May 11 14:13:50.939: OSPF: Start processing Type 5 External LSA 193.163.209.0, mask 255.255.255.0, adv 10.28.1.1, age 512, seq 0x80003C50, metric 20, metric-type 2

May 11 14:13:50.939:    Add better path to LSA ID 193.163.209.0, gateway 192.168.220.1, dist 20

May 11 14:13:50.939:    Add path: next-hop 192.168.220.1, interface Tunnel0

May 11 14:13:50.939: OSPF: delete lsa id 193.163.209.0, type 5, adv rtr 10.28.1.1 from delete list

May 11 14:13:50.939:  network update dest_addr 193.163.209.0 mask 255.255.255.0 gateway 192.168.220.1

May 11 14:13:50.939:    Add External Route to 193.163.209.0. Metric: 20, Next Hop: 192.168.220.1

May 11 14:13:50.939: OSPF: insert route list LS ID 193.163.209.0, type 5, adv rtr 10.28.1.1

May 11 14:13:50.939: OSPF: Start processing Type 5 External LSA 194.117.106.129, mask 255.255.255.255, adv 10.28.1.1, age 512, seq 0x80003C1F, metric 20, metric-type 2

May 11 14:13:50.939:    Add better path to LSA ID 194.117.106.129, gateway 192.168.220.1, dist 20

May 11 14:13:50.939:    Add path: next-hop 192.168.220.1, interface Tunnel0

May 11 14:13:50.939: OSPF: delete lsa id 194.117.106.129, type 5, adv rtr 10.28.1.1 from delete list

May 11 14:13:50.939:  network update dest_addr 194.117.106.129 mask 255.255.255.255 gateway 192.168.220.1

May 11 14:13:50.939:    Add External Route to 194.117.106.129. Metric: 20, Next Hop: 192.168.220.1

May 11 14:13:50.939: OSPF: insert route list LS ID 194.117.106.129, type 5, adv rtr 10.28.1.1

May 11 14:13:50.939: OSPF: Start processing Type 5 External LSA 206.113.119.128, mask 255.255.255.192, adv 10.28.1.1, age 512, seq 0x80000566, metric 1, metric-type 2

May 11 14:13:50.939:    Add better path to LSA ID 206.113.119.128, gateway 192.168.220.1, dist 1

May 11 14:13:50.939:    Add path: next-hop 192.168.220.1, interface Tunnel0

May 11 14:13:50.939: OSPF: delete lsa id 206.113.119.128, type 5, adv rtr 10.28.1.1 from delete list

May 11 14:13:50.939:  network update dest_addr 206.113.119.128 mask 255.255.255.192 gateway 192.168.220.1

May 11 14:13:50.939:    Add External Route to 206.113.119.128. Metric: 1, Next Hop: 192.168.220.1

May 11 14:13:50.939: OSPF: insert route list LS ID 206.113.119.128, type 5, adv rtr 10.28.1.1

May 11 14:13:50.939: OSPF: ex_delete_old_routes

May 11 14:13:50.939: OSPF: Started Building Type 7 External Routes

May 11 14:13:50.939: OSPF: ex_delete_old_routes

May 11 14:13:50.939: OSPF: Detect change in LSA type 2, LSID 192.168.220.1, from 192.168.199.12 area 0

May 11 14:13:50.943: OSPF: Schedule SPF in area 0

      Change in LS ID 192.168.220.1, LSA type N, , spf-type Full

May 11 14:13:50.943: OSPF: Detect change in LSA type 2, LSID 192.168.220.2, from 192.168.199.11 area 0

May 11 14:13:50.943: OSPF: Schedule SPF in area 0

      Change in LS ID 192.168.220.2, LSA type N, , spf-type Full

May 11 14:13:50.943: OSPF: Detect change in LSA type 1, LSID 10.31.51.1, from 10.31.51.1 area 0

May 11 14:13:50.943: OSPF: Schedule SPF in area 0

      Change in LS ID 10.31.51.1, LSA type R, , spf-type Full

May 11 14:13:50.943: OSPF: Detect change in LSA type 1, LSID 10.31.53.1, from 10.31.53.1 area 0

May 11 14:13:50.943: OSPF: Schedule SPF in area 0

      Change in LS ID 10.31.53.1, LSA type R, , spf-type Full

May 11 14:13:50.943: OSPF: Detect change in LSA type 1, LSID 192.168.220.120, from 192.168.220.120 area 0

May 11 14:13:50.947: OSPF: Schedule SPF in area 0

      Change in LS ID 192.168.220.120, LSA type R, , spf-type Full

Anton Lyamzin Tue, 08/12/2014 - 00:54
User Badges:

Hi! I have same problem.

Be sure you have multicast trafic permitted on both sides.

Here some notes about OSPF neighboring process (on broadcast links):

1) one router send multicast hello

2) second router reply with unicast hello

3) DBD packets exchange

4) LSR/LSU/LSAck exchange

So, if you have multicast traffic blocked on one side, OSPF neighbors will flap, because on step 2 there is a unicast hello message and other messages are also unicast.

Before i study this case i can't realize that ACL could possible be a reason for routing protocol flapping. ACL simply blocks all defined packets, but OSPF blow my mind out.

HTH,

Anton.

Actions

This Discussion