[Xorp-users] BGP: error while starting xorpsh

arvind arvind at macil.in
Wed Jun 4 20:14:40 PDT 2008 

Yes It was unable to register with the router manager What may be the 
reason. If i enable only OSPF it was working fine. If i enable BGP it 
came to that error. I have started the the xorpsh after the xorp_rtrmgr.

I feel the xorp_rtrmgr was not fully executed, because in OSPF the 
following line is printed
	No more tasks to run
But in BGP it was not printed
	
But unfortunately it was started to work sometimes at that time "No more 
tasks to run" is printed in the xorp_rtrmgr terminal.


Atanu Ghosh wrote:
> Hi,
> 
> I don't see a BGP error, what I see is the xorpsh printing warning (and error)
> messages because it is unable to register with the router
> mananger. While the router manager is starting the routing processes it
> may not be listening for xorpsh requests. Although the xorpsh prints
> warning messages if it is started before the router manager has
> completed starting the routing processes I have never seen a problem,
> eventually you should see the xorpsh prompt.
> 
> Did the xorpsh fail to start correctly?
> 
>       Atanu.
> 
> arvind <arvind at macil.in> wrote:
> 
>> While running xorp_rtrmgr i have the following om the terminal:
>>
>>
>> [root at localhost xorp.cvs.org]# ./rtrmgr/xorp_rtrmgr
>> [ 2008/06/04 09:16:57  INFO xorp_rtrmgr:9504 RTRMGR +239 
>> master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, 
>> policy, static_routes, bgp
>> [ 2008/06/04 09:16:57  INFO xorp_rtrmgr:9504 RTRMGR +96 
>> module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea)
>> [ 2008/06/04 09:16:58 INFO xorp_fea MFEA ] MFEA enabled
>> [ 2008/06/04 09:16:58 INFO xorp_fea MFEA ] CLI enabled
>> [ 2008/06/04 09:16:58 INFO xorp_fea MFEA ] CLI started
>> [ 2008/06/04 09:16:58 INFO xorp_fea MFEA ] MFEA enabled
>> [ 2008/06/04 09:16:58 INFO xorp_fea MFEA ] CLI enabled
>> [ 2008/06/04 09:16:58 INFO xorp_fea MFEA ] CLI started
>> [ 2008/06/04 09:16:59  INFO xorp_rtrmgr:9504 RTRMGR +96 
>> module_manager.cc execute ] Executing module: fea (fea/xorp_fea)
>> [ 2008/06/04 09:17:03  INFO xorp_rtrmgr:9504 RTRMGR +96 
>> module_manager.cc execute ] Executing module: rib (rib/xorp_rib)
>> [ 9505 +2333 xrl_fea_target.cc ] redist_transaction4_0_1_add_route(): 
>> dst = 192.168.49.0/24 nexthop = 192.168.49.16 ifname = eth0 vifname = 
>> eth0 metric = 0 admin_distance = 0 protocol_origin = connected
>> [ 2008/06/04 09:17:05  INFO xorp_rtrmgr:9504 RTRMGR +96 
>> module_manager.cc execute ] Executing module: policy (policy/xorp_policy)
>> [ 2008/06/04 09:17:07  INFO xorp_rtrmgr:9504 RTRMGR +96 
>> module_manager.cc execute ] Executing module: static_routes 
>> (static_routes/xorp_static_routes)
>> [ 9506 +1395 xrl_target.cc ] Target Birth: class = static_routes 
>> instance = static_routes-de9f2f65f9bf1184f3632c0bbd526285 at 127.0.0.1
>> [ 2008/06/04 09:17:09  INFO xorp_rtrmgr:9504 RTRMGR +96 
>> module_manager.cc execute ] Executing module: bgp (bgp/xorp_bgp)
>> [ 9509   +54 bgp.cc ] BGPMain object created
>> [ 9509   +75 main.cc ] By default assume there is a rib running
>>
>> [ 9509 +1698 bgp.cc ] BGPMain::register_ribname
>> [ 9509 +1699 bgp.cc ] rib
>> [ 9506 +1395 xrl_target.cc ] Target Birth: class = bgp instance = 
>> bgp-3bcaa06ba79c588b0f6eb1f438827b2c at 127.0.0.1
>> [ 9509  +682 bgp.cc ] interface eth0 vif eth0 address 192.168.49.16 
>> prefix_len 24 state true
>> [ 9509  +777 bgp.cc ] BGPMain::main_loop started
>> [ 9509 +1009 bgp.cc ] Creating new Peer: {192.168.49.16(179) 
>> 192.168.49.16(179)}
>> [ 9509 +1011 bgp.cc ] Using local address 10.10.1.2 for our nexthop
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +988 bgp.cc ] No match
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +988 bgp.cc ] No match
>> [ 9509  +946 bgp.cc ] Peer added (fd -1)
>> [ 9509 +1203 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509 +1960 bgp.cc ] IPv4 Unicast
>> [ 9509 +1977 bgp.cc ] Peer {192.168.49.16(179) 192.168.49.16(179)}. true
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509 +1963 bgp.cc ] IPv4 Multicast
>> [ 9509 +1977 bgp.cc ] Peer {192.168.49.16(179) 192.168.49.16(179)}. false
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509 +1966 bgp.cc ] IPv6 Unicast
>> [ 9509 +1977 bgp.cc ] Peer {192.168.49.16(179) 192.168.49.16(179)}. false
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 9509 +1969 bgp.cc ] IPv6 Multicast
>> [ 9509 +1977 bgp.cc ] Peer {192.168.49.16(179) 192.168.49.16(179)}. false
>> [ 9509  +974 bgp.cc ] Searching for: {192.168.49.16(179) 192.168.49.16(179)}
>> [ 9509  +979 bgp.cc ] Trying: {192.168.49.16(179) 192.168.49.16(179)} [ 
>> 9509  +982 bgp.cc ]  Succeeded
>> [ 2008/06/04 09:17:11  WARNING xorp_policy:9507 XifFinderEventNotifier 
>> +275 filter_manager.cc birth ] XXX HACK: PUSHING ROUTES OF connected FOR bgp
>> [ 2008/06/04 09:17:11  WARNING xorp_policy:9507 XifFinderEventNotifier 
>> +275 filter_manager.cc birth ] XXX HACK: PUSHING ROUTES OF static FOR bgp
>> [ 9509 +1820 bgp.cc ] nlri 192.168.49.0/24 next hop 192.168.49.16 
>> unicast 1 multicast 0
>> [ 9509 +1820 bgp.cc ] nlri 192.168.49.0/24 next hop 192.168.49.16 
>> unicast 0 multicast 1
>> [ 9506 +1141 xrl_target.cc ] register_interest4 target = bgp addr = 
>> 192.168.49.16
>>
>>
>> When i started to run the Xorpsh then i got the following error on my 
>> terminal(xorp_rtrmgr):
>>
>>
>> [ 2008/06/04 09:24:17  WARNING xorp_rtrmgr:9504 XrlFinderTarget +668 
>> ../xrl/targets/finder_base.cc 
>> handle_finder_event_notifier_0_1_register_class_event_interest ] 
>> Handling method for 
>> finder_event_notifier/0.1/register_class_event_interest failed: 
>> XrlCmdError 102 Command failed failed to add watch
>> [ 2008/06/04 09:24:17  ERROR xorp_rtrmgr:9504 RTRMGR +326 
>> xrl_rtrmgr_interface.cc finder_register_done ] Failed to register with 
>> finder about XRL xorpsh-9524-localhost (err: Command failed)
>> [ 2008/06/04 09:24:19  WARNING xorp_rtrmgr:9504 XrlFinderTarget +668 
>> ../xrl/targets/finder_base.cc 
>> handle_finder_event_notifier_0_1_register_class_event_interest ] 
>> Handling method for 
>> finder_event_notifier/0.1/register_class_event_interest failed: 
>> XrlCmdError 102 Command failed failed to add watch
>> [ 2008/06/04 09:24:19  ERROR xorp_rtrmgr:9504 RTRMGR +326 
>> xrl_rtrmgr_interface.cc finder_register_done ] Failed to register with 
>> finder about XRL xorpsh-9524-localhost (err: Command failed)
>> [ 2008/06/04 09:24:21  WARNING xorp_rtrmgr:9504 XrlFinderTarget +668 
>> ../xrl/targets/finder_base.cc 
>> handle_finder_event_notifier_0_1_register_class_event_interest ] 
>> Handling method for 
>> finder_event_notifier/0.1/register_class_event_interest failed: 
>> XrlCmdError 102 Command failed failed to add watch
>> [ 2008/06/04 09:24:21  ERROR xorp_rtrmgr:9504 RTRMGR +326 
>> xrl_rtrmgr_interface.cc finder_register_done ] Failed to register with 
>> finder about XRL xorpsh-9524-localhost (err: Command failed)
>>
>>
>> Can any one give the solution/idea for the above problem. I have also 
>> run the xorpsh from the user "xorp" but still same problem
>>
>> Configuration file has the following:(config.boot)
>>
>> interfaces {
>>      restore-original-config-on-shutdown: true
>>      interface eth0 {
>>          mtu: 1500
>>          description: "data interface"
>>          disable: false
>>          /* default-system-config */
>>          vif eth0 {
>>              disable: false
>>              address 192.168.49.16 {
>>                  prefix-length: 24
>>                  broadcast: 192.168.49.255
>>                  disable: false
>>              }
>>          }
>>      }
>> }
>>
>> protocols {
>> 	static {
>>          	disable: false
>>             	route 172.16.2.0/24 {
>>                  	next-hop: 172.16.2.1
>>                  	metric: 1
>>              	}
>> 	}
>> 	bgp {
>>          	bgp-id: 192.168.49.16
>> 	        local-as: 10
>>          	peer 192.168.49.16 {
>> 	            local-ip: 192.168.49.16
>>          	    as: 8
>> 	            next-hop: 10.10.1.2
>>          	}
>>
>> 	        export: "connected,static"
>>        }
>> }
>> policy {
>>      /* Describe connected routes for redistribution */
>>      policy-statement connected {
>>          term export {
>>              from {
>>                  protocol: "connected"
>>              }
>>          }
>>      }
>> }
>>
>> policy {
>>      /* Describe static routes for redistribution */
>>      policy-statement static {
>>          term export {
>>              from {
>>                  protocol: "static"
>>              }
>>          }
>>      }
>> }
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Xorp-users mailing list
>> Xorp-users at xorp.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> 
>

More information about the Xorp-users mailing list