Ospf not forming over hwic

sivakumaranmaruthaipillai · ‎02-13-2013

Hi All

I' ve come across an weird ospf issue between my router connected via layer 2 service provider link, details as below

Overview : We have a base station router for satelite termination at service provider end connected via Layer 2 vlan link to a head end C3945, current interface for head end is a layer 2 vlan and layer 3 ip address lives under sub interface, config as below

conf t

Head End router

Cisco 33945

interface GigabitEthernet0/1.655

bandwidth 6144

encapsulation dot1Q 655

ip ospf authentication-key7 xxxxxxxxxxxxxxxxx

ip address 192.168.2.118 255.255.255.248

ip ospf network point-to-point

IOS:

c3900-universalk9-mz.SPA.151-4.M2.bin

Cisco IOS Software, C3900 Software (C3900-UNIVERSALK9-M), Version 15.1(4)M2,

Remote End

Cisco 2811

interface FastEthernet0/0

bandwidth 6144

ip address 192.168.2.113 255.255.255.248

ip ospf authentication-key 7 xxxxxxxxxxxxxxxxxxx

ip ospf network point-to-point

ip ospf mtu-ignore

duplex full

speed 100

ios:

Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(24)T5,

c2800nm-advipservicesk9-mz.124-24.T5.bin

Problem

This setup absolutely work with above configuration all the ospf route are exchaged no issue, bu what im try to achieve is moving away from subinterface based routing , so we bought a spare HWIC-2FE to be used as primary layer 3 termination point fo this link , all the suinterface configuration has been migrated to hwic as below

interface FastEthernet0/0/1

bandwidth 6144

ip address 192.168.2.113 255.255.255.248

ip ospf authentication-key 7 xxxxxxxxxxx

ip ospf network point-to-point

ip ospf mtu-ignore

duplex full

speed 10

Layer 1/2 connectivity between site are up and working, interface is pingable but ospf neigbhor is not forming, tried clear ip ospf as well no go, debug ip ospf aj & events show this logs

13 20:23:43: %LINK-5-CHANGED: Interface FastEthernet0/0/1, changed state to administratively down

Feb 13 20:23:47: %LINK-3-UPDOWN: Interface FastEthernet0/0/1, changed state to up

Feb 13 20:23:48: %SYS-5-CONFIG_I: Configured from console by kpillai on vty1 (192.168.12.116)

Feb 13 20:23:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0/1, changed state to up

Feb 13 12:23:49.935: OSPF-100 ADJ Fa0/0/1: Route adjust notification: UP/UP

Feb 13 12:23:49.935: OSPF-100 ADJ Fa0/0/1: Interface going Up

Feb 13 12:23:49.935: OSPF-100 ADJ Fa0/0/1: Interface state change to UP, new ospf state P2P

Feb 13 12:23:59.631: OSPF-100 ADJ Fa0/0/1: 2 Way Communication to 192.168.2.113, state 2WAY

Feb 13 12:23:59.631: OSPF-100 ADJ Fa0/0/1: Nbr 192.168.2.113: Prepare dbase exchange

Feb 13 12:23:59.631: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:23:59.635: OSPF-100 ADJ Fa0/0/1: Rcv DBD from 192.168.2.113 seq 0x252D opt 0x52 flag 0x7 len 32 mtu 1500 state EXSTART

Feb 13 12:23:59.635: OSPF-100 ADJ Fa0/0/1: First DBD and we are not SLAVE

Feb 13 12:24:04.199: OSPF-100 ADJ Fa0/0/1: Rcv DBD from 192.168.2.113 seq 0x252D opt 0x52 flag 0x7 len 32 mtu 1500 state EXSTART

Feb 13 12:24:04.199: OSPF-100 ADJ Fa0/0/1: First DBD and we are not SLAVE

Feb 13 12:24:04.423: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:04.423: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [1]

Feb 13 12:24:09.115: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:09.115: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [2]

Feb 13 12:24:13.919: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:13.919: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [3]

Feb 13 12:24:18.515: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:18.515: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [4]

Feb 13 12:24:23.455: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:23.455: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [5]

Feb 13 12:24:28.063: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:28.063: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [6]

Feb 13 12:24:32.959: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:32.959: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [7]

Feb 13 12:24:37.699: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:37.699: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [8]

Feb 13 12:24:42.411: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:42.411: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [9]

Feb 13 12:24:47.060: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:47.060: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [10]

Feb 13 12:24:51.900: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:51.900: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [11]

Feb 13 12:24:56.504: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:24:56.504: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [12]

Feb 13 12:25:01.064: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:25:01.064: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [13]

Feb 13 12:25:05.856: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:25:05.856: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [14]

Feb 13 12:25:10.636: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:25:10.636: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [15]

Feb 13 12:25:15.392: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:25:15.392: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [16]

Feb 13 12:25:20.220: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:25:20.220: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [17]

Feb 13 12:25:25.120: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:25:25.120: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [18]

Feb 13 12:25:30.052: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:25:30.052: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [19]

Feb 13 12:25:34.828: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0x686 opt 0x52 flag 0x7 len 32

Feb 13 12:25:34.828: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [20]

Feb 13 20:25:37: %LINK-3-UPDOWN: Interface FastEthernet0/0/1, changed state to down

Feb 13 12:25:37.080: OSPF-100 ADJ Fa0/0/1: Route adjust notification: DOWN/DOWN

Feb 13 12:25:37.080: OSPF-100 ADJ Fa0/0/1: Interface going Down

Feb 13 12:25:37.080: OSPF-100 ADJ Fa0/0/1: 192.168.2.113 address 192.168.2.113 is dead, state DOWN

Feb 13 20:25:37: %OSPF-5-ADJCHG: Process 100, Nbr 192.168.2.113 on FastEthernet0/0/1 from EXSTART to DOWN, Neighbor Down: Interface down or detached

Feb 13 12:25:37.080: OSPF-100 ADJ Fa0/0/1: Nbr 192.168.2.113: Clean-up dbase exchange

Feb 13 12:25:37.080: OSPF-100 ADJ Fa0/0/1: 192.168.254.40 address 192.168.2.118 is dead, state DOWN

Feb 13 12:25:37.080: OSPF-100 ADJ Fa0/0/1: Interface state change to DOWN, new ospf state DOWN

Feb 13 12:25:39.332: OSPF-100 ADJ Fa0/0/1: Route adjust notification: UP/UP

Feb 13 12:25:39.332: OSPF-100 ADJ Fa0/0/1: Interface going Up

Feb 13 12:25:39.332: OSPF-100 ADJ Fa0/0/1: Interface state change to UP, new ospf state P2P

Feb 13 12:25:39.332: OSPF-100 ADJ Fa0/0/1: 2 Way Communication to 192.168.2.113, state 2WAY

Feb 13 12:25:39.336: OSPF-100 ADJ Fa0/0/1: Nbr 192.168.2.113: Prepare dbase exchange

Feb 13 12:25:39.336: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 20:25:41: %SYS-5-CONFIG_I: Configured from console by kpillai on vty1 (192.168.12.116)

Feb 13 12:25:44.000: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:25:44.000: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [1]

Feb 13 12:25:44.004: OSPF-100 ADJ Fa0/0/1: Rcv DBD from 192.168.2.113 seq 0x687 opt 0x52 flag 0x7 len 32 mtu 1500 state EXSTART

Feb 13 12:25:44.004: OSPF-100 ADJ Fa0/0/1: First DBD and we are not SLAVE

Feb 13 12:25:48.940: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:25:48.940: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [2]

Feb 13 12:25:53.592: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:25:53.592: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [3]

Feb 13 12:25:58.212: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:25:58.212: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [4]

Feb 13 12:26:03.172: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:03.172: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [5]

Feb 13 12:26:07.980: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:07.980: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [6]

Feb 13 12:26:12.556: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:12.556: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [7]

Feb 13 12:26:17.148: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:17.148: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [8]

Feb 13 12:26:21.964: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:21.964: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [9]

Feb 13 12:26:26.540: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:26.540: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [10]

Feb 13 12:26:31.284: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:31.284: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [11]

Feb 13 12:26:36.216: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:36.216: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [12]

Feb 13 12:26:41.200: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:41.200: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [13]

Feb 13 12:26:46.140: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:46.140: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [14]

Feb 13 12:26:50.824: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:26:50.824: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [15]

Can some one please help, tried everthing i know about ospf routing not sure whether hardware or software fault

K

tobyarnett · ‎02-13-2013

I recently ran into an issue with the IOS on one of my routers not recognizing the HWIC. Looking at the code your using it is possible you have a bug. You may want to look at the release notes and bug IDs for your hardware and feature sets. It may be worth while to step down to a 12.4 code if possible to test with a known good IOS. Are you using that code foot any reason specifically or just cause it is the latest?

Toby

Sent from Cisco Technical Support Android App

-Toby

Please don't forget to rate any helpful post.

_____________________________________
There are no great limits to growth because there are no limits of human intelligence, imagination, and wonder.
- Ronald Reagan

sivakumaranmaruthaipillai · ‎02-13-2013

Hi Toby

when we purchased this kit it came with current ios from our supplier, some voip and security feature needed as well , but not sure whether i'll be able to test with 12.x as this is a 3945 UC ?? is this usual behaviour ?

Giuseppe Larosa · ‎02-14-2013

Hello Sivakumaran,

the debug messages say that after OSPF negotiation the OSPF neighbor state machine reaches the EXSTART state, the local node ( the head end) is the master and tries to send the first database packet DBD.

This packet should be acknowledged by remote end router, but this does not happen or the OSPF LSA Ack is lost in the path back to the head end.

The head end makes multiple attempts to send the same database packet with no ACK received

Feb 13 12:25:44.004: OSPF-100 ADJ Fa0/0/1: First DBD and we are not SLAVE

Feb 13 12:25:48.940: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:25:48.940: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [2]

Feb 13 12:25:53.592: OSPF-100 ADJ Fa0/0/1: Send DBD to 192.168.2.113 seq 0xFE8 opt 0x52 flag 0x7 len 32

Feb 13 12:25:53.592: OSPF-100 ADJ Fa0/0/1: Retransmitting DBD to 192.168.2.113 [3]

It would be wise to get the log/debug messages from the remote end router to see what happens.

In any case, there is no real issue in using a Vlan based subinterface like you did up to now. You may need a switch in the middle but the OSPF protocol allows to deal with this scenario.

I would revert to old configuration, so all the voice related features will be unaffected I would not try to downgrade the IOS.

Hope to help

Giuseppe

sivakumaranmaruthaipillai · ‎02-18-2013

Thanks

Giuseppe

I'm going to try debug on remote end this time to check whats going on, will post the results soon but its seem to be rather strange based on Cisco docs this is normally related to MTU or duplexing issue but none exist in this scene atm

Kumar