[Xorp-users] Re: help establishing OSPF adjacencies

[Nick Feamster]

Just to follow up with some more information:

I see messages such as:
[ 4251  +430 xrl_io.cc join_multicast_group ] Join Interface eth0 Vif eth0 mcast
 224.0.0.5 ]

in the logs.  I don't understand what's going on here, but I can't help
but wonder if this has anything to do with these messages:
[ 4251   +92 xrl_io.cc send ] send(interface = eth0, vif = eth0, src =
128.31.1.14, dst = 224.0.0.5, payload_size = 44

I'm puzzled, since I didn't configure anything having to do with
multicast.  Since these messages seem to disappear when I disable OSPF,
I'm wondering if XORP's OSPF somehow relies on multicast to distribute
LSAs, and, if so, how I should be configuring multicast to get these
adjacencies exchanged properly?

The only other clue I see in the logs is:
[ 2005/10/17 16:20:52 TRACE xorp_ospfv2 OSPF ] Event(InterfaceUp)
Interface(eth0/eth0) State(Down) 

which I'm not certain how to interpret.  Could "State(Down)" be the
reason I don't see anything in other OSPF LSA databases, for example?


thanks,
Nick

p.s. I also see the following error message when starting up:
[ 2005/10/17 16:20:37  INFO xorp_rtrmgr:20946 RTRMGR +485 module_manager.cc run ] Running module: fea (/usr/local/xorp/fea/xorp_fea) c user_click_command_done_cb ] User-level Click command (~/demo/click) failed.  

I did not see this problem when running XORP 1.1, but now it seems I'm
having to start click manually because XORP does not fire it up
properly.  Has the mechanism for starting up click in XORP changed since
version 1.1?



On Mon, Oct 17, 2005 at 01:43:26PM -0400, Nick Feamster wrote:
> Hi,
> 
> I can't seem to find much documentation on configuring OSPF in XORP,
> which is understandable since it is quite new.  btw, thanks for
> implementing this!
> 
> I am trying to get an adjacency established between two nodes.  Standard
> error/xorpsh shows me this on the two machines.  Both of the eth0
> interfaces below are configured with a prefix-length of /24 so they
> should, in theory, be in the same subnet.  
> 
> I'm wondering why the LSA databases below don't show the adjacency.  Any
> potential hangups I should know about?
> 
> Thanks,
> Nick
> 
> 
> Machine 1:
> ----------
> Standard error (LSA announcements)
> ...
> [ 22201   +92 xrl_io.cc send ] send(interface = eth0, vif = eth0, src =
> 128.31.1.14, dst = 224.0.0.5, payload_size = 44
> ...
> 
> 
> xorpsh
> Xorp> show ospf4 database 0.0.0.0 
> Type       ID               Adv Rtr           Seq      Age  Opt  Cksum Len
> Router  *128.31.1.14      128.31.1.14      0x80000001   326  0x2 0x3e12  36
> 
>  interface eth0 {
>         description "ethernet adapter"
>         disable: false
>         discard: true
>         vif eth0 {
>              disable: false
>              address 128.31.1.14 {
>                 prefix-length: 24
>                 disable: false
>              }
>         }
>     }
> 
> ....
> 
>     ospf4 {
>         router-id: 128.31.1.14
> 
>         area 0.0.0.0 {
>            interface eth0 {
>                 vif eth0 {
>                   address 128.31.1.14 {
>                     interface-cost: 5
>                   }
>                 }
>            }
>        }
>    }
> 
> 
> Machine 2:
> ----------
> [ 18333   +92 xrl_io.cc send ] send(interface = eth0, vif = eth0, src =
> 128.31.1.15, dst = 224.0.0.5, payload_size = 44
> 
> xorpsh
> Xorp> show ospf4 database 0.0.0.0 
> Type       ID               Adv Rtr           Seq      Age  Opt  Cksum Len
> Router  *128.31.1.15      128.31.1.15      0x80000001   326  0x2 0x3e12  36
> 
> 
>