[Xorp-hackers] xorp error handling

[Chan, Anthony]

Hi,

 

We are running XORP with a custom routing protocol and are able to run
into the error situation where a SEND_FAILED error code is generated
("XrlPFSTCPSender died: Keepalive timeout").  After this occurs, XORP
basically becomes non operational, but all the processes are still
around and in a running state.  Our platform is resource constrained so
it is fairly easy for us to reproduce once we inject enough routes.

 

I believe what is happening is that the RIB process becomes too busy to
acknowledge the IPC keepalive between it and the routing process.
However the rtrmngr/Finder does not restart the RIB because the RIB
became responsive again and acknowledged the keepalive from the
rtrmngr/Finder process.  Since the IPC between the routing and RIB
process is now down, and rtrmngr/Finder cannot detect any process
issues, nothing can be done now to recover from this state.  Do you
believe this is a possible scenario with the current XORP error handling
process??

 

We are using 1.8.5 without setting the environment variable "
XORP_SENDER_KEEPALIVE_TIME", therefore using the default 10 seconds as
the keepalive interval.

 

Thanks,

Anthony

 



The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. 
Thank you. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20120822/5292930e/attachment.html