OSPF Ethernet PtMP

sean_kndy · ‎07-01-2014

I am trying to get a PtMP network type running along side an existing broadcast network. I have a collection of routers connected to a VPLS service and all participating in vlan 80, network type broadcast. This is problematic if a random VC between a pair of routers decides to break within the VPLS, so PtMP would be more appropriate.

The problem is, I am having a heck of a time getting certain routers to form an adjacency and keep it. The issue appears to be related to the fact that PtMP advertises /32 routes for the IP on the PtMP interface. This /32 route is then chosen over the connected route and routed out the vlan 80 interface. I'm not really sure why this is breaking it, as I know hellos/lsas are multicast on the interface, not unicasted to the IP. But you can see below in debugging that the routers end up hearing OSPF packets on the vlan 80 sub-if that originated from the vlan 69 sub-if, and complains.

Below is config between two ASR1002 routers running 15.2(4)S2. The neighborships come up on Gi0/0/0.69 then later fail. This continually happens. Note that these 2 ASRs are connected directly between a switch and this adjacency is not even trying to formed across the VPLS service. I am simply trying to get 2 vlans, one broadcast and one ptmp, running between eachother across a switch. I labbed this up between a couple 2821s and I can't get the same behavior...

There is no MTU mismatch and full size packets work fine:

ip route 10.1.50.15 255.255.255.255 Gi0/0/0.69 // this is for over-riding ospf's /32 and routing over vlan 80 so we can ping across the 69 sub-interface itself

#ping 10.1.50.15 size 5000 df-bit
Type escape sequence to abort.
Sending 5, 5000-byte ICMP Echos to 10.1.50.15, timeout is 2 seconds:
Packet sent with the DF bit set
!!!!!

First ASR:

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

INT/OSPF config:

interface GigabitEthernet0/0/0.69

encapsulation dot1Q 69

ip address 10.1.50.14 255.255.255.0

ip mtu 5000

ip ospf network point-to-multipoint

mpls ip

!

interface GigabitEthernet0/0/0.80

encapsulation dot1Q 80

ip address 10.1.31.7 255.255.255.0

ip ospf priority 224

mpls ip

!

router ospf 100

router-id x.x.82.240

passive-interface default

no passive-interface GigabitEthernet0/0/0.69

no passive-interface GigabitEthernet0/0/0.80

no passive-interface GigabitEthernet0/0/1.3201

network 10.1.6.96 0.0.0.7 area 0

network 10.1.31.0 0.0.0.255 area 0

network 10.1.50.0 0.0.0.255 area 0

!

Jun 27 18:29:58.590: OSPF-100 ADJ Gi0/0/0.69: Interface going Up

Jun 27 18:29:58.590: OSPF-100 ADJ Gi0/0/0.69: Interface state change to UP, new ospf state P2MP

Jun 27 18:30:27.825: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:30:27.825: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE37 opt 0x52 flag 0x7 len 32 mtu 5000 state INIT

Jun 27 18:30:27.825: OSPF-100 ADJ Gi0/0/0.69: 2 Way Communication to x.x.82.241, state 2WAY

Jun 27 18:30:27.825: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241: Prepare dbase exchange

Jun 27 18:30:27.825: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xFF3 opt 0x52 flag 0x7 len 32

Jun 27 18:30:27.825: OSPF-100 ADJ Gi0/0/0.69: NBR Negotiation Done. We are the SLAVE

Jun 27 18:30:27.826: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241: Summary list built, size 642

Jun 27 18:30:27.826: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE37 opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.829: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE38 opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.829: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE38 opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.831: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE39 opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.832: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE39 opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.833: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE3A opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.834: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE3A opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.835: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE3B opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.836: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE3B opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.838: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE3C opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.838: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE3C opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.840: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE3D opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.840: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE3D opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.842: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE3E opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.842: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE3E opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.844: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE3F opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.844: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE3F opt 0x52 flag 0x2 len 1452

Jun 27 18:30:27.846: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE40 opt 0x52 flag 0x3 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.846: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE40 opt 0x52 flag 0x2 len 92

Jun 27 18:30:27.847: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.241 seq 0xE41 opt 0x52 flag 0x1 len 92 mtu 5000 state EXCHANGE

Jun 27 18:30:27.847: OSPF-100 ADJ Gi0/0/0.69: Exchange Done with x.x.82.241

Jun 27 18:30:27.847: OSPF-100 ADJ Gi0/0/0.69: Synchronized with x.x.82.241, state FULL

Jun 27 18:30:27.847: %OSPF-5-ADJCHG: Process 100, Nbr x.x.82.241 on GigabitEthernet0/0/0.69 from LOADING to FULL, Loading Done

Jun 27 18:30:27.848: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.241 seq 0xE41 opt 0x52 flag 0x0 len 32

Jun 27 18:30:28.350: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:30:33.294: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:32:26.927: OSPF-100 ADJ Gi0/0/0.69: Killing nbr x.x.82.241 due to excessive (25) retransmissions

Jun 27 18:32:26.927: OSPF-100 ADJ Gi0/0/0.69: x.x.82.241 address 10.1.50.15 is dead, state DOWN

Jun 27 18:32:26.927: %OSPF-5-ADJCHG: Process 100, Nbr x.x.82.241 on GigabitEthernet0/0/0.69 from FULL to DOWN, Neighbor Down: Too many retransmissions

Jun 27 18:32:26.927: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241: Clean-up dbase exchange

Jun 27 18:32:27.328: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:27.607: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:28.433: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:29.365: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:29.685: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:30.368: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:30.939: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:31.004: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:31.069: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:31.135: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:32.033: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:32.389: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.241 10.1.50.15 is currently ignored

Jun 27 18:32:33.176: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:32:34.073: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:32:34.207: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:32:34.944: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:32:35.503: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:32:35.724: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:32:35.787: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

Jun 27 18:32:35.909: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.15, area 0.0.0.0 : src not on the same network

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

Second ASR:

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

INT/OSPF config:

interface GigabitEthernet0/0/0.69

encapsulation dot1Q 69

ip address 10.1.50.15 255.255.255.0

ip mtu 5000

ip ospf network point-to-multipoint

mpls ip

!

interface GigabitEthernet0/0/0.80

encapsulation dot1Q 80

ip address 10.1.31.42 255.255.255.0

ip ospf priority 192

mpls ip

!

router ospf 100

router-id x.x.82.241

redistribute static subnets route-map ospf-static-redist

passive-interface default

no passive-interface GigabitEthernet0/0/0.69

no passive-interface GigabitEthernet0/0/0.80

no passive-interface GigabitEthernet0/0/1.766

no passive-interface GigabitEthernet0/0/1.767

no passive-interface GigabitEthernet0/0/1.768

no passive-interface GigabitEthernet0/0/1.769

no passive-interface GigabitEthernet0/0/1.770

no passive-interface GigabitEthernet0/0/1.3203

no passive-interface GigabitEthernet0/0/1.3204

no passive-interface GigabitEthernet0/0/1.3205

no passive-interface GigabitEthernet0/0/1.3206

no passive-interface GigabitEthernet0/0/1.3207

no passive-interface GigabitEthernet0/0/1.3208

no passive-interface GigabitEthernet0/0/3.60

no passive-interface GigabitEthernet0/0/3.2600

network 10.1.0.49 0.0.0.0 area 0

network 10.1.0.53 0.0.0.0 area 0

network 10.1.0.60 0.0.0.0 area 0

network 10.1.0.63 0.0.0.0 area 0

network 10.1.6.76 0.0.0.3 area 0

network 10.1.6.104 0.0.0.7 area 0

network 10.1.31.0 0.0.0.255 area 0

network 10.1.50.0 0.0.0.255 area 0

network 172.30.33.24 0.0.0.3 area 0

network 172.30.33.28 0.0.0.3 area 0

network 172.30.33.156 0.0.0.3 area 0

network 172.30.33.168 0.0.0.3 area 0

network 172.30.34.0 0.0.0.3 area 0

network 172.30.34.4 0.0.0.3 area 0

network 172.30.34.8 0.0.0.3 area 0

network 172.30.34.40 0.0.0.3 area 0

network 172.30.34.44 0.0.0.3 area 0

network 172.30.34.48 0.0.0.3 area 0

network 172.30.34.52 0.0.0.3 area 0

Jun 27 18:29:26.085: OSPF-100 ADJ Gi0/0/0.69: Interface state change to DOWN, new ospf state DOWN

Jun 27 18:29:58.978: OSPF-100 ADJ Gi0/0/0.69: Route adjust notification: UP/UP

Jun 27 18:29:58.978: OSPF-100 ADJ Gi0/0/0.69: Interface going Up

Jun 27 18:29:58.979: OSPF-100 ADJ Gi0/0/0.69: Interface state change to UP, new ospf state P2MP

Jun 27 18:30:27.506: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:27.827: OSPF-100 ADJ Gi0/0/0.69: 2 Way Communication to x.x.82.240, state 2WAY

Jun 27 18:30:27.827: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.240: Prepare dbase exchange

Jun 27 18:30:27.827: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE37 opt 0x52 flag 0x7 len 32

Jun 27 18:30:27.829: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xFF3 opt 0x52 flag 0x7 len 32 mtu 5000 state EXSTART

Jun 27 18:30:27.829: OSPF-100 ADJ Gi0/0/0.69: First DBD and we are not SLAVE

Jun 27 18:30:27.830: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE37 opt 0x52 flag 0x2 len 1452 mtu 5000 state EXSTART

Jun 27 18:30:27.830: OSPF-100 ADJ Gi0/0/0.69: NBR Negotiation Done. We are the MASTER

Jun 27 18:30:27.831: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.240: Summary list built, size 642

Jun 27 18:30:27.831: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE38 opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.833: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE38 opt 0x52 flag 0x2 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.833: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE39 opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.835: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE39 opt 0x52 flag 0x2 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.835: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE3A opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.837: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE3A opt 0x52 flag 0x2 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.837: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE3B opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.839: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE3B opt 0x52 flag 0x2 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.839: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE3C opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.841: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE3C opt 0x52 flag 0x2 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.841: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE3D opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.843: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE3D opt 0x52 flag 0x2 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.843: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE3E opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.845: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE3E opt 0x52 flag 0x2 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.845: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE3F opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.847: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE3F opt 0x52 flag 0x2 len 1452 mtu 5000 state EXCHANGE

Jun 27 18:30:27.847: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE40 opt 0x52 flag 0x3 len 1452

Jun 27 18:30:27.849: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE40 opt 0x52 flag 0x2 len 92 mtu 5000 state EXCHANGE

Jun 27 18:30:27.849: OSPF-100 ADJ Gi0/0/0.69: Send DBD to x.x.82.240 seq 0xE41 opt 0x52 flag 0x1 len 92

Jun 27 18:30:27.851: OSPF-100 ADJ Gi0/0/0.69: Rcv DBD from x.x.82.240 seq 0xE41 opt 0x52 flag 0x0 len 32 mtu 5000 state EXCHANGE

Jun 27 18:30:27.851: OSPF-100 ADJ Gi0/0/0.69: Exchange Done with x.x.82.240

Jun 27 18:30:27.851: OSPF-100 ADJ Gi0/0/0.69: Synchronized with x.x.82.240, state FULL

Jun 27 2014 19:30:27.851 dst: %OSPF-5-ADJCHG: Process 100, Nbr x.x.82.240 on GigabitEthernet0/0/0.69 from LOADING to FULL, Loading Done

Jun 27 18:30:27.851: OSPF-100 ADJ Gi0/0/0.69: Nbr x.x.82.240: Clean-up dbase exchange

Jun 27 18:30:28.353: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:33.051: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:37.229: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:37.607: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:37.815: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:42.185: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:42.316: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:42.640: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:43.738: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:43.801: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:46.907: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:46.946: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:47.199: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:47.229: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:47.264: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:47.560: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:48.342: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:48.737: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:51.594: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:51.680: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:51.993: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:52.127: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:52.186: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:53.172: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

Jun 27 18:30:53.377: OSPF-100 ADJ Gi0/0/0.80: Rcv pkt from 10.1.50.14, area 0.0.0.0 : src not on the same network

.. this same msg continues ...

Jun 27 18:32:35.911: OSPF-100 ADJ Gi0/0/0.69: Killing nbr x.x.82.240 due to excessive (25) retransmissions

Jun 27 18:32:35.911: OSPF-100 ADJ Gi0/0/0.69: x.x.82.240 address 10.1.50.14 is dead, state DOWN

Jun 27 2014 19:32:35.911 dst: %OSPF-5-ADJCHG: Process 100, Nbr x.x.82.240 on GigabitEthernet0/0/0.69 from FULL to DOWN, Neighbor Down: Too many retransmissions

sean_kndy · ‎07-03-2014

So I do believe this is a bug in IOS. I am running IOS-XE in this case, verison 03.07.02.S. But I've observed this issue on some older GSRs running IOS 12 as well.

Basically, I have a PtMP network along side a broadcast network between two routers. The PtMP interface should come up and send a multicast OSPF hello to discover any *directly connected* neighbors it has. After it receives replies, it then should know that the sender is adjacent and begin sending unicast OSPF packets *out the connected interface* and ignore the routing table. This isn't what it is doing. It's looking to the routing table and seeing the /32 route being announced via the other broadcast network between the two routers. So what happens is the OSPF packets end up hitting the wrong interface on the other side and are discarded.

Now if we change the PtMP to PtMP non-broadcast so that I can actually tell IOS what it's directly connected neighbors are -- it still mis-behaves. It still looks to the routing table and tries to send OSPF packets across the 'broadcast' network-type interface resulting in the adjacent router discarding those packets thus causing an adjacency to *never* form. As soon as I nail up a static host route to tell IOS that it should use the directly connected interface (ip route 10.1.50.15 255.255.255.255 Gi0/0/0.69) instead, the adjacency immediately forms and stays up.

I replicated this setup in GNS3 and locally with a couple C2821s and I cannot get this same behavior. It works fine. So I think this is a bug affecting some versions of IOS and not others.