Hi list, Today I spend a lot of time debugging why BIRD doesn't get our IPSO VRRP cluster in 2WAY state, while junos and IOS routers do. Here's the setup. 1 VLAN with all OSPF routers. Network is X.Y.0.0/28 .1 and .2 are the IPSO nodes, .3 is the VRRP address. IPSO nodes run OSPF priority 0. At this moment .2 is the VRRP "master". .4 and .5 are junos routers and are DR and BDR respectively. .7 is an IOS Version 12.0(28c) router .8 is an other junos router. .14 is Debian linux + BIRD. Both IPSO routers send OSPF messages with RID .3, see below. 17:45:37.773176 O 802.1Q vlan#10 P0 X.53.0.1 > X.53.0.4: OSPFv2-ls_upd 64: RID X.Y.0.3 backbone { rtr X.Y.0.3 E S 80023430 age 6 } [|ospf] [tos 0xc0] [ttl 1] (id 6121) 17:47:57.888864 O 802.1Q vlan#10 P0 X.Y.0.2 > X.Y.0.4: OSPFv2-ls_upd 64: RID X.Y.0.3 backbone { rtr X.Y.0.3 E S 80023467 age 4 } [|ospf] [tos 0xc0] [ttl 1] (id 35846) Bird doesn't handle this setup.... bird> show ospf neighbors MyOSPF: Router ID Pri State DTime Interface Router IP X.Y.0.8 0 2way/other 00:32 eth0 X.Y.0.8 X.Y.0.3 0 init/other 00:39 eth0 X.Y.0.1 X.Y.0.7 0 2way/other 00:32 eth0 X.Y.0.7 X.Y.0.5 128 full/dr 00:39 eth0 X.Y.0.5 X.Y.0.4 128 full/bdr 00:39 eth0 X.Y.0.4 bird> And in the logs 25-04-2010 17:58:03 <TRACE> MyOSPF: LSA Type: 0001, Id: X.Y.0.3, Rt: X.Y.0.3, Age: 2, Seq: 80023552, Sum: 8856 Working on router X.Y.0.3 Found :-) Next hop calculating for id: X.Y.0.3 rt: X.Y.0.3 type: 1 25-04-2010 17:58:05 <WARN> Cannot find next hop for LSA (Type: 0001, Id: X.Y.0.3, Rt: X.Y.0.3) Working on router X.Y.0.3 Found :-) Next hop calculating for id: X.Y.0.3 rt: X.Y.0.3 type: 1 and OSPF: RX hook called (iface eth0, src X.Y.0.2, dst 224.0.0.5) 25-04-2010 18:00:45 <TRACE> MyOSPF: HELLO packet received from X.Y.0.2 via eth0 Neighbor state machine for neighbor X.Y.0.1, event 'hello received' Neighbor state machine for neighbor X.Y.0.1, event '1-way received' Neighbor state machine for neighbor X.Y.0.1, event 'hello received' MyOSPF: RXMT timer fired on interface eth0 for neigh: X.Y.0.1. OSPF: RX hook called (iface eth0, src X.Y.0.1, dst 224.0.0.5) 25-04-2010 18:00:49 <TRACE> MyOSPF: HELLO packet received from X.Y.0.1 via eth0 Neighbor state machine for neighbor X.Y.0.1, event 'hello received' Neighbor state machine for neighbor X.Y.0.1, event '1-way received' Neighbor state machine for neighbor X.Y.0.1, event 'hello received' MyOSPF: RXMT timer fired on interface eth0 for neigh: X.Y.0.1. My guess is that neighbors are created based on their address instead of their RID. Looking at the info below I'm guessing this is not correct. Can this be fixed? from junos epping@BR1> show ospf neighbor X.Y.0.3 extensive Address Interface State ID Pri Dead X.Y.0.1 ge-0/0/0.0 Full X.Y.0.3 0 32 Area 0.0.0.0, opt 0x2, DR X.Y.0.5, BDR X.Y.0.4 Up 00:24:38, adjacent 00:24:33 X.Y.0.2 ge-0/0/0.0 Full X.Y.0.3 0 37 Area 0.0.0.0, opt 0x2, DR X.Y.0.5, BDR X.Y.0.4 Up 4d 05:22:13, adjacent 4d 05:22:13 Link state retransmission list: Type LSA ID Adv rtr Seq Router X.Y.0.3 X.Y.0.3 0x8002349e epping@BR1> and IOS BR3#sh ip ospf neighbor detail X.Y.0.3 Neighbor X.Y.0.3, interface address X.Y.0.2 In the area 0.0.0.0 via interface Ethernet0 Neighbor priority is 0, State is 2WAY, 2 state changes DR is X.Y.0.5 BDR is X.Y.0.4 Options 2 Dead timer due in 00:00:30 Neighbor X.Y.0.3, interface address X.Y.0.1 In the area 0.0.0.0 via interface Ethernet0 Neighbor priority is 0, State is 2WAY, 2 state changes DR is X.Y.0.5 BDR is X.Y.0.4 Options 2 Dead timer due in 00:00:35 BR3# GRTNX, RobJE -- Home is near Enter. ((c) RonA) ======================================================================== Tel: +31 - 317 - 399800 s-mail: P.O. box 617 Fax: +31 - 317 - 423164 6700 AP Wageningen MailTo: r.epping@meteo.nl WWW: http://www.meteo.nl/ -- This e-mail is from Meteo Consult B.V., a MeteoGroup company. For more information, see http://www.weer.nl/gebruiksvoorwaarden. This e-mail may contain confidential information. Only the addressee is permitted to read, copy, distribute or otherwise use this e-mail or any attachments. If you have received it in error, please contact the sender immediately. Any opinion expressed in this e-mail is personal to the sender and may not reflect the opinion of MeteoGroup. Any e-mail reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.