OSPF point-to-multipoint behavior on FR hub and spoke

From: keith tokash (ktokash@hotmail.com)
Date: Sun Nov 04 2007 - 17:11:42 ART


Hey *, I'm a tad befuddled regarding something. I have three routers set up
in a hub & spoke fashion, with R5 the hub and R4 and R2 the spokes. The OSPF
network type is point-to-multi, and the spokes have neighbored up rather
nicely with R5. However R2 and R4 are constantly trying to form an adjacency,
which always fails. A debug ip packet detail (isolated to OSPF) shows an
encapsulation failure of unicasted hellos. But I'm unclear as to why since
the network type is point-to-multi, and pings across work just fine.

From R4:
*Nov 4 00:59:51.084: IP: s=136.1.245.4 (local), d=136.1.245.2 (Serial1/0),
len 64, sending, proto=89
*Nov 4 00:59:51.084: IP: s=136.1.245.4 (local), d=136.1.245.2 (Serial1/0),
len 64, encapsulation failed, proto=89

Rack1R4#sh ip ospf inter s1/0 | i Type
  Process ID 3, Router ID 150.1.4.4, Network Type POINT_TO_MULTIPOINT, Cost:
781

Rack1R4#ping 136.1.245.2 source 136.1.245.4
<snip>
Packet sent with a source address of 136.1.245.4
!!!!!

To be honest I'm confused about two things here:
1. Why the routers are attempting to form an adjacency in the first place.
2. Why the L2/L3 mapping is required since this is point-to-multi and the
routing table shows R5 as the next-hop, and that is mapped to a DLCI and
working fine.

With a few exceptions, secrecy is deeply incompatible with democracy and with
science.
        --Carl Sagan



This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:28 ART