[Xorp-users] Cannot start xorp_rtrmgr

[Pavlin Radoslavov]

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

> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] MFEA enabled
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI enabled
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI started
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] MFEA enabled
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI enabled
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI started
> [ 2008/05/13 18:16:44  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: fea (fea/xorp_fea)
> [ 2008/05/13 18:16:51  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: rib (rib/xorp_rib)
> [ 2008/05/13 18:16:53  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: policy (policy/xorp_policy)
> [ 2008/05/13 18:16:55  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: static_routes (static_routes/xorp_static_routes)
> [ 2008/05/13 18:16:57  INFO xorp_rtrmgr:13754 RTRMGR +2228 task.cc run_task 
> ] No more tasks to run
> 
> Any advice on the above issues will be highly appreciated.
> 
> Thanks in advance,
> Swati
> 
> 
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users