[Xorp-cvs] XORP cvs commit: xorp/ospf xorp/ospf/tools
Atanu Ghosh
atanu@icir.org
Wed, 28 Dec 2005 18:57:20 GMT
CVSROOT: /usr/local/www/data/cvs
Module name: xorp
Changes by: atanu@xorpc.icir.org 2005-12-28 18:57:20 UTC
XORP CVS repository
Modified files:
ospf area_router.cc auth.cc debug_io.hh external.cc
io.hh lsa.cc ospf.cc ospf.hh packet.cc peer.cc
peer_manager.cc policy_varrw.cc routing_table.cc
test_packet.cc test_peering.cc test_routing.cc
test_routing_table.cc vlink.cc xorp_ospfv2.cc
xorp_ospfv3.cc xrl_io.cc xrl_io.hh xrl_target.cc
ospf/tools print_lsas.cc print_neighbours.cc
Log message:
The router manager after starting a process will send it configuration
commands, once the process has declared itself ready.
The OSPF process was unconditionally declaring itself ready without
waiting for its interactions with the RIB and FEA to complete.
If the configuration commands arrived from the router manager before
the interaction were complete errors of this form would be the result:
----------------------------------------
[ 2005/12/28 10:42:26 WARNING xorp_ospfv2:2432 XrlOspfv2Target +473
ospfv2_base.cc handle_ospfv2_0_1_create_peer ] Handling method for
ospfv2/0.1/create_peer failed: XrlCmdError 102 Command failed BadPeer
from line 359 of peer_manager.cc: Unable to get prefix length for
en0/en0/172.16.0.1
----------------------------------------
OSPF now waits for the IO subsystem to be initialised before declaring
itself ready.
The IO subsystem is now using the ServiceBase class.
Revision Changes Path
1.159 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/area_router.cc
1.6 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/auth.cc
1.15 +4 -9; commitid: 451643b2e0097ea6; xorp/ospf/debug_io.hh
1.18 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/external.cc
1.19 +2 -19; commitid: 451643b2e0097ea6; xorp/ospf/io.hh
1.63 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/lsa.cc
1.57 +3 -2; commitid: 451643b2e0097ea6; xorp/ospf/ospf.cc
1.77 +10 -3; commitid: 451643b2e0097ea6; xorp/ospf/ospf.hh
1.31 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/packet.cc
1.195 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/peer.cc
1.95 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/peer_manager.cc
1.8 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/policy_varrw.cc
1.41 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/routing_table.cc
1.35 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/test_packet.cc
1.50 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/test_peering.cc
1.14 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/test_routing.cc
1.3 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/test_routing_table.cc
1.14 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/tools/print_lsas.cc
1.4 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/tools/print_neighbours.cc
1.7 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/vlink.cc
1.11 +2 -1; commitid: 451643b2e0097ea6; xorp/ospf/xorp_ospfv2.cc
1.11 +3 -1; commitid: 451643b2e0097ea6; xorp/ospf/xorp_ospfv3.cc
1.28 +4 -3; commitid: 451643b2e0097ea6; xorp/ospf/xrl_io.cc
1.18 +37 -16; commitid: 451643b2e0097ea6; xorp/ospf/xrl_io.hh
1.24 +3 -1; commitid: 451643b2e0097ea6; xorp/ospf/xrl_target.cc