[Xorp-users] XORP RIP enabled. Why are static routes required?
Swati Sinha Deb
Swati.SinhaDeb@bristol.ac.uk
Sat, 23 Apr 2005 23:31:01 +0100
Hi Pavlin,
Please find below the following:
1. I have done a tcpdump on the interface connecting the two routers. With
only RIP enabled I cannot see the RIP traffic from the peer router.
However, with static route I can see the peer RIP traffic with the correct
routes.
2. I have enabled #define DEBUG_LOGGING
With RIP enabled on the remote XORP server (and static route disabled) I
get the following debug messages:
[ 2005/04/23 23:09:45 INFO xorp_rtrmgr:18231 RTRMGR +404 module_manager.cc
run ] Running module: rip (/usr/local/xorp/rip/xorp_rip)
[ 18237 +381 xrl_target_common.hh ] Status Update 0 -> 1: Awaiting start
up of: FEA/RIB Process Watcher
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, RIB Updater
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, RIB Updater, FEA Interface Mirror
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, RIB Updater, FEA Interface Mirror, RIP Port
Manager
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, RIB Updater, FEA Interface Mirror, RIP Port
Manager
[ 18237 +146 xrl_process_spy.cc ] Registered interest in fea
[ 18237 +71 xrl_process_spy.cc ] Birth event: class fea instance
fea-dae8e37f3ae4abfc173fbf406d8a46dc@127.0.0.1
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, FEA Interface Mirror, RIP Port Manager
[ 18237 +146 xrl_process_spy.cc ] Registered interest in rib
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA Interface Mirror, RIP Port Manager
[ 18237 +71 xrl_process_spy.cc ] Birth event: class rib instance
rib-b8a4c408451a38a985a7cb8be3ad0c85@127.0.0.1
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA Interface Mirror, RIP Port Manager
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA Interface Mirror, RIP Port Manager
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: RIP Port Manager
[ 18237 +246 xrl_port_manager.cc ] XrlPortManager<IPv4>::tree_complete
notification
[ 18237 +381 xrl_target_common.hh ] Status Update 1 -> 3:
[ 18237 +434 xrl_target_common.hh ] rip_x_1_add_rip_address
eth4/eth4/172.20.1.1
[ 18237 +48 xrl_port_manager.cc ] Looking for eth4/eth4/172.20.1.1
[ 18237 +67 xrl_port_manager.cc ] Found
[ 18237 +309 xrl_port_io.cc ] Created RIP I/O Port on eth4/eth4/172.20.1.1
[ 18237 +442 xrl_port_manager.cc ] XXX 0x8218c3c status -> Starting
[ 18237 +442 xrl_port_manager.cc ] XXX 0x8218c3c status -> Running
[ 18237 +434 xrl_target_common.hh ] rip_x_1_add_rip_address
eth3/eth3/172.20.2.1
[ 18237 +48 xrl_port_manager.cc ] Looking for eth3/eth3/172.20.2.1
[ 18237 +67 xrl_port_manager.cc ] Found
[ 18237 +309 xrl_port_io.cc ] Created RIP I/O Port on eth3/eth3/172.20.2.1
[ 18237 +442 xrl_port_manager.cc ] XXX 0x8219724 status -> Starting
[ 18237 +442 xrl_port_manager.cc ] XXX 0x8219724 status -> Running
[ 18237 +538 xrl_redist_manager.cc ] Dispatched Redistribution enable
protocol "connected"
[ 2005/04/23 23:09:48 INFO xorp_rtrmgr:18231 RTRMGR +1420 task.cc run_task
] No more tasks to run
[ 18237 +180 xrl_redist_manager.cc ] XrlRedistEnable for "connected" - 100
Okay
[ 18237 +413 xrl_redist_manager.cc ] got redist add_route for "connected"
172.20.1.0/24 172.20.1.1
[ 18237 +413 xrl_redist_manager.cc ] got redist add_route for "connected"
172.20.2.0/24 172.20.2.1
[ 18237 +321 xrl_port_io.cc ] eth4/eth4/172.20.1.1 pending 0
[ 18237 +162 xrl_port_io.cc ] Sent 24 bytes to 224.0.0.9/520 from
172.20.1.1
[ 18237 +462 xrl_port_io.cc ] SendCB 100 Okay
[ 18237 +321 xrl_port_io.cc ] eth4/eth4/172.20.1.1 pending 0
[ 18237 +321 xrl_port_io.cc ] eth3/eth3/172.20.2.1 pending 0
[ 18237 +162 xrl_port_io.cc ] Sent 24 bytes to 224.0.0.9/520 from
172.20.2.1
With static route enabled on the remote XORP server I get the following
debug messages:
[ 2005/04/23 23:17:47 INFO xorp_rtrmgr:18285 RTRMGR +404 module_manager.cc
run ] Running module: rip (/usr/local/xorp/rip/xorp_rip)
[ 18291 +381 xrl_target_common.hh ] Status Update 0 -> 1: Awaiting start
up of: FEA/RIB Process Watcher
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, RIB Updater
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, RIB Updater, FEA Interface Mirror
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, RIB Updater, FEA Interface Mirror, RIP Port
Manager
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, RIB Updater, FEA Interface Mirror, RIP Port
Manager
[ 18291 +146 xrl_process_spy.cc ] Registered interest in fea
[ 18291 +71 xrl_process_spy.cc ] Birth event: class fea instance
fea-37a06288e9cd4e221d33726cb5338719@127.0.0.1
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA/RIB Process Watcher, FEA Interface Mirror, RIP Port Manager
[ 18291 +146 xrl_process_spy.cc ] Registered interest in rib
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA Interface Mirror, RIP Port Manager
[ 18291 +71 xrl_process_spy.cc ] Birth event: class rib instance
rib-baa5866a57cb6d215f8d7e795a5e27bd@127.0.0.1
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA Interface Mirror, RIP Port Manager
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: FEA Interface Mirror, RIP Port Manager
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 1: Awaiting start
up of: RIP Port Manager
[ 18291 +246 xrl_port_manager.cc ] XrlPortManager<IPv4>::tree_complete
notification
[ 18291 +381 xrl_target_common.hh ] Status Update 1 -> 3:
[ 18291 +434 xrl_target_common.hh ] rip_x_1_add_rip_address
eth4/eth4/172.20.1.1
[ 18291 +48 xrl_port_manager.cc ] Looking for eth4/eth4/172.20.1.1
[ 18291 +67 xrl_port_manager.cc ] Found
[ 18291 +309 xrl_port_io.cc ] Created RIP I/O Port on eth4/eth4/172.20.1.1
[ 18291 +442 xrl_port_manager.cc ] XXX 0x8218c3c status -> Starting
[ 18291 +442 xrl_port_manager.cc ] XXX 0x8218c3c status -> Running
[ 18291 +434 xrl_target_common.hh ] rip_x_1_add_rip_address
eth3/eth3/172.20.2.1
[ 18291 +48 xrl_port_manager.cc ] Looking for eth3/eth3/172.20.2.1
[ 18291 +67 xrl_port_manager.cc ] Found
[ 18291 +309 xrl_port_io.cc ] Created RIP I/O Port on eth3/eth3/172.20.2.1
[ 18291 +442 xrl_port_manager.cc ] XXX 0x8219724 status -> Starting
[ 18291 +442 xrl_port_manager.cc ] XXX 0x8219724 status -> Running
[ 18291 +538 xrl_redist_manager.cc ] Dispatched Redistribution enable
protocol "connected"
[ 2005/04/23 23:17:49 INFO xorp_rtrmgr:18285 RTRMGR +1420 task.cc run_task
] No more tasks to run
[ 18291 +180 xrl_redist_manager.cc ] XrlRedistEnable for "connected" - 100
Okay
[ 18291 +538 xrl_redist_manager.cc ] Dispatched Redistribution enable
protocol "static"
[ 18291 +180 xrl_redist_manager.cc ] XrlRedistEnable for "static" - 100
Okay
[ 18291 +413 xrl_redist_manager.cc ] got redist add_route for "connected"
172.20.1.0/24 172.20.1.1
[ 18291 +413 xrl_redist_manager.cc ] got redist add_route for "static"
172.20.2.0/24 172.20.2.2
[ 18291 +413 xrl_redist_manager.cc ] got redist add_route for "connected"
172.20.2.0/24 172.20.2.1
[ 18291 +413 xrl_redist_manager.cc ] got redist add_route for "static"
172.20.3.0/24 172.20.2.2
[ 18291 +321 xrl_port_io.cc ] eth4/eth4/172.20.1.1 pending 0
[ 18291 +162 xrl_port_io.cc ] Sent 24 bytes to 224.0.0.9/520 from
172.20.1.1
[ 18291 +462 xrl_port_io.cc ] SendCB 100 Okay
[ 18291 +321 xrl_port_io.cc ] eth4/eth4/172.20.1.1 pending 0
[ 18291 +321 xrl_port_io.cc ] eth3/eth3/172.20.2.1 pending 0
[ 18291 +162 xrl_port_io.cc ] Sent 24 bytes to 224.0.0.9/520 from
172.20.2.1
[ 18291 +462 xrl_port_io.cc ] SendCB 100 Okay
[ 18291 +321 xrl_port_io.cc ] eth3/eth3/172.20.2.1 pending 0
[ 18291 +321 xrl_port_io.cc ] eth4/eth4/172.20.1.1 pending 0
[ 18291 +162 xrl_port_io.cc ] Sent 24 bytes to 224.0.0.9/520 from
172.20.1.1
[ 18291 +462 xrl_port_io.cc ] SendCB 100 Okay
[ 18291 +321 xrl_port_io.cc ] eth4/eth4/172.20.1.1 pending 0
[ 18291 +321 xrl_port_io.cc ] eth3/eth3/172.20.2.1 pending 0
[ 18291 +162 xrl_port_io.cc ] Sent 24 bytes to 224.0.0.9/520 from
172.20.2.1
[ 18291 +462 xrl_port_io.cc ] SendCB 100 Okay
Regards,
Swati
--On 19 April 2005 14:23 -0700 Pavlin Radoslavov <pavlin@icir.org> wrote:
>> I have tried what you have suggested but unfortunately it did not work.
>> I have also tried changing the Metric to 1 without any success.
>>
>> Further, xorpsh "show route table ipv4 unicast rip" and "show route
>> table ipv4 unicast final" command displays only the connected routes on
>> that server.
>>
>> Is there any log files which I can see in order to check the routes
>> coming into XORP and routes being forwarded to fea?
>
> If there were any log messages from RIP, they should have been
> printed in the window with the running rtrmgr.
> If there is no useful info there, you could try to enable some of
> the debug statements in the RIP source code itself. To do so you
> have to add (or uncomment) the following at the beginning of the RIP
> files that have debug_msg() statements:
>
># define DEBUG_LOGGING
>
> Though, before doing so you may want to run tcpdump on the link
> between the two routers to see whether there is actually any RIP
> traffic.
>
> Pavlin
----------------------
Swati Sinha Deb, Research Fellow
Wireless and Networks Research Laboratory,
Electrical & Electronic Engineering, University of Bristol,
Merchant Venturers Building, Woodland Road,
Bristol BS8 1UB
E-mail: Swati.SinhaDeb@bristol.ac.uk
Tel.: +44 (0)117 331 5058