[Xorp-users] Cannot start xorp_rtrmgr

Swati Sinha Deb Swati.Deb at bristol.ac.uk
Wed May 14 15:32:30 PDT 2008


Hi Pavlin,

Many thanks for the reply. Apparently the server did not support the IPv6. 
Once enabled I could install the XORP-1.4 successfully. But now I am 
getting Click related errors. Please advice.

-bash-2.05b$ sudo ./xorp_rtrmgr -b my_config.boot
[ 2008/05/14 23:10:03  INFO xorp_rtrmgr:6615 RTRMGR +239 
master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, 
policy, static_routes
[ 2008/05/14 23:10:03  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: interfaces (fea/xorp_fea)
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] MFEA enabled
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI enabled
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI started
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] MFEA enabled
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI enabled
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI started
[ 2008/05/14 23:10:05  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: fea (fea/xorp_fea)
[ 2008/05/14 23:10:11  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: rib (rib/xorp_rib)
[ 2008/05/14 23:10:11  ERROR xorp_fea:6621 FEA +331 
fticonfig_entry_set_click.cc add_entry ] User-level Click command error: 
510 No element named '_xorp_rt6'
[ 2008/05/14 23:10:11  ERROR xorp_fea:6621 FEA +71 fti_transaction.cc 
operation_result ] FTI transaction commit failed on AddEntry6: net = 
fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname = eth3 vifname = eth3 
metric = 0 admin_distance = 0 xorp_route = true is_deleted = false 
is_unresolved = false is_connected_route = true
[ 2008/05/14 23:10:11 WARNING xorp_fea XrlFeaTarget ] Handling method for 
redist_transaction6/0.1/commit_transaction failed: XrlCmdError 102 Command 
failed AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname 
= eth3 vifname = eth3 metric = 0 admin_distance = 0 xorp_route = true 
is_deleted = false is_unresolved = false is_connected_route = true
[ 2008/05/14 23:10:11  ERROR xorp_rib:6624 RIB +910 redist_xrl.cc 
dispatch_complete ] Failed to commit transaction: 102 Command failed 
AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname = eth3 
vifname = eth3 metric = 0 admin_distance = 0 xorp_route = true is_deleted = 
false is_unresolved = false is_connected_route = true
[ 2008/05/14 23:10:13  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: policy (policy/xorp_policy)
[ 2008/05/14 23:10:15  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: static_routes (static_routes/xorp_static_routes)
[ 2008/05/14 23:10:17  INFO xorp_rtrmgr:6615 RTRMGR +2228 task.cc run_task 
] No more tasks to run


Thanks in advance,
Swati

--On 13 May 2008 18:27 -0700 Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU> 
wrote:

> Swati Sinha Deb <Swati.Deb at bristol.ac.uk> wrote:
>
>> Hi,
>>
>> I have XORP-1.4 running successfully on two servers.
>>
>> I am trying to install this on another server. I have installed XORP-1.4
>> successfully. The linux version is 2.4.21. But when I try to start the
>> xorp_rtrmgr I am getting the following errors:
>>
>> [eessd at atherton bin]$ sudo ./xorp_rtrmgr - my_config.boot
>> [ 2008/05/13 18:16:27  ERROR xorp_rtrmgr:13753 RTRMGR +330
>> main_rtrmgr.cc  run ] rtrmgr shutting down due to an init error: Failed
>> to open config  file: /home/eessd/xorp/config.boot
>
> It looks like you fixed the above error, so I am not considering it
> an issue anymore.
>
>> [eessd at atherton bin]$ sudo ./xorp_rtrmgr -b my_config.boot
>> [ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +239
>> master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib,
>> policy, static_routes
>> [ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +96
>> module_manager.cc  execute ] Executing module: interfaces (fea/xorp_fea)
>> [ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c
>> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol =
>> 0): Address family not supported by protocol
>> [ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c
>> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol =
>> 0): Address family not supported by protocol
>
> On Linux, domain = 10 is AF_INET6, i.e. IPv6.
> It looks like that IPv6 is not enabled on that machine hence the
> above error.
> You have the following options to deal with this:
>
> a) Configure your system (kernel, and/or config files) to enable
> IPv6.
>
> b) Recompile XORP with IPv6 disabled:
> ./configure --disable-ipv6
> gmake clean
> gmake
>
> c) Do nothing.
>    I could be wrong, but as long as you don't try to use
>    any IPv6-specific configuration in your XORP config, the
>    rest of XORP should work.
>
> From the above three choices I'd recommend (a). Exactly how you do
> it is OS-specific.
>
> However, if you think that IPv6 is already enabled, it could be that
> the XORP ./configure script didn't discover IPv6; when running the
> script look for a line like the following:
>
> checking whether the system has IPv6 stack... yes
>
> If it says "no", then please send file config.log that should be
> generated after running ./configure
>
> Regards,
> Pavlin
>




More information about the Xorp-users mailing list