[Xorp-users] xorp clearing routing table upon startup
Pavlin Radoslavov
pavlin at ICSI.Berkeley.EDU
Tue Oct 14 10:23:44 PDT 2008
Stegen Smith <stegen at owns.com> wrote:
> Hi Pavlin,
>
> Ooops... my head must have been in the wrong place in the previous email,
> then. I should have said, even though my grep was wrong (the grep would not
> have caught an entry for the 10.5.49 network), the routes are still NOT
> showing up in the routing table. I see the 10.3.48.0/20 and 10.5.49.0/24
> networks in bgp, but not in the systems routing table.
Could you clarify whether you see the BGP routes in the RIB table.
Also, could you double-check that the next-hop routers 10.3.14.39
and 10.3.14.7 are resolved (e.g., they are directly connected or
there is a static route or OSPR/RIP router to them).
If the answer of the second question is yes, then you need to
interact with the BGP folks to solve the issue.
Pavlin
> I'll submit another bug entry about the segfaults and we can figure out where
> to go after the other issue.
>
> thanks and sorry for the lack of clarity there
>
> stegen
> On Oct 13, 2008, at 2:24 PM, Pavlin Radoslavov wrote:
>
> > Stegen Smith <stegen at owns.com> wrote:
> >
> >> Hi Pavlin,
> >>
> >> Thanks for the update! I've grabbed the latest source from CVS and got it
> >> up. I'm no longer seeing
> >> those errors that I submitted the bug for; however, it does not seem that
> >> the latter issue of the
> >> routing table not being updated from bgp is resolved.
> >
> > OK, according to a later email on the subject this issue has been
> > resolved. However, the segmentation fault you get during a shutdown
> > seems like a real issue. Please submit another Bugzilla entry about
> > it.
> >
> > Thanks,
> > Pavlin
> >
> >> I can do the following:
> >> xorp at at-ig1.sv> show bgp routes
> >> Status Codes: * valid route, > best route
> >> Origin Codes: i IGP, e EGP, ? incomplete
> >>
> >> Prefix Nexthop Peer AS Path
> >> ------ ------- ---- -------
> >> * 10.3.48.0/20 10.3.14.7 10.3.14.99 65000 i
> >> * 10.3.48.0/20 10.3.14.39 10.3.14.99 65000 i
> >> * 10.5.49.0/24 10.3.14.39 10.3.14.99 65000 i
> >> * 10.5.49.0/24 10.3.14.7 10.3.14.99 65000 i
> >> xorp at at-ig1.sv>
> >>
> >> root0p7at-ig1.sv/usr/local/xorp netstat -nr|egrep "^10.[3,5].48"
> >> root1p7at-ig1.sv/usr/local/xorp
> >>
> >> Also, when I ^C out of xorp_rtrmgr, it still does not shut down so cleanly:
> >> ^C[ 2008/10/13 12:22:31 INFO xorp_rtrmgr:351 RTRMGR +1024 task.cc
> >> shutdown ] Shutting down module: bgp
> >> [ 2008/10/13 12:22:31 INFO xorp_bgp:15136 BGP +451 peer.cc
> >> send_notification ] Sending:
> >> Notification Packet: Cease(6)
> >> [ 2008/10/13 12:22:31 TRACE xorp_bgp:15136 BGP +456 peer.cc
> >> send_notification ] Peer
> >> {10.3.14.40(179) 10.3.14.39(179)}: Send: Notification Packet: Cease(6)
> >> [ 2008/10/13 12:22:31 TRACE xorp_bgp:15136 BGP +2062 peer.cc set_state ]
> >> Peer {10.3.14.40(179)
> >> 10.3.14.39(179)}: Previous state: ESTABLISHED(6) Current state: STOPPED(7)
> >> [ 2008/10/13 12:22:31 INFO xorp_bgp:15136 BGP +451 peer.cc
> >> send_notification ] Sending:
> >> Notification Packet: Cease(6)
> >> [ 2008/10/13 12:22:31 TRACE xorp_bgp:15136 BGP +456 peer.cc
> >> send_notification ] Peer
> >> {10.3.14.8(179) 10.3.14.7(179)}: Send: Notification Packet: Cease(6)
> >> [ 2008/10/13 12:22:31 TRACE xorp_bgp:15136 BGP +2062 peer.cc set_state ]
> >> Peer {10.3.14.8(179)
> >> 10.3.14.7(179)}: Previous state: ESTABLISHED(6) Current state: STOPPED(7)
> >> [ 2008/10/13 12:22:31 TRACE xorp_bgp:15136 BGP +2062 peer.cc set_state ]
> >> Peer {10.3.14.8(179)
> >> 10.3.14.7(179)}: Previous state: STOPPED(7) Current state: IDLE(1)
> >> [ 2008/10/13 12:22:31 TRACE xorp_bgp:15136 BGP +2062 peer.cc set_state ]
> >> Peer {10.3.14.40(179)
> >> 10.3.14.39(179)}: Previous state: STOPPED(7) Current state: IDLE(1)
> >> [ 2008/10/13 12:22:31 INFO xorp_bgp:15136 BGP +149 bgp.cc BGPMain ]
> >> EVENT: timers 4
> >> [ 2008/10/13 12:22:31 INFO xorp_bgp:15136 BGP +161 bgp.cc BGPMain ] xrl
> >> router still has pending
> >> operations
> >> [ 2008/10/13 12:22:31 INFO xorp_bgp:15136 BGP +167 bgp.cc BGPMain ] xrl
> >> router no more pending
> >> operations
> >> [ 2008/10/13 12:22:31 ERROR xorp_rib:30518 LIBXORP +222
> >> buffered_asyncio.cc io_event ] read error 54
> >> [ 2008/10/13 12:22:31 ERROR xorp_rib:30518 XRL +169 xrl_pf_stcp.cc
> >> read_event ] Read failed (error
> >> = 54)
> >> [ 2008/10/13 12:22:31 ERROR xorp_rib:30518 XRL +378 xrl_pf_stcp.cc die ]
> >> STCPRequestHandler died:
> >> read error
> >> [ 2008/10/13 12:22:31 INFO xorp_rtrmgr:351 RTRMGR +280 module_manager.cc
> >> module_exited ] Module
> >> normal exit: bgp
> >> [ 2008/10/13 12:22:31 INFO xorp_rib RIB ] Received death event for
> >> protocol bgp shutting down -------
> >> OriginTable: ebgp
> >> EGP
> >> next table = Merged:(ebgp)+(ibgp)
> >> [ 2008/10/13 12:22:31 INFO xorp_rib RIB ] Received death event for
> >> protocol bgp shutting down -------
> >> OriginTable: ebgp
> >> EGP
> >> next table = Merged:(ebgp)+(ibgp)
> >> [ 2008/10/13 12:22:32 WARNING xorp_rtrmgr:351 XrlFinderTarget +407
> >> ../xrl/targets/finder_base.cc
> >> handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/ resolve_xrl
> >> failed: XrlCmdError 102
> >> Command failed Target "bgp" does not exist or is not enabled.
> >> [ 2008/10/13 12:22:33 INFO xorp_rtrmgr:351 RTRMGR +1024 task.cc shutdown
> >> ] Shutting down module: policy
> >> [ 2008/10/13 12:22:33 INFO xorp_rtrmgr:351 XRL +432 xrl_router.cc
> >> get_sender ] Sender died
> >> (protocol = "stcp", address = "127.0.0.1:11045")
> >> [ 2008/10/13 12:22:33 ERROR xorp_rtrmgr:351 LIBCOMM +610 comm_sock.c
> >> comm_sock_connect4 ] Error
> >> connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port =
> >> 11045): Connection refused
> >> [ 2008/10/13 12:22:33 ERROR xorp_rtrmgr:351 XRL +63 xrl_pf_factory.cc
> >> create_sender ]
> >> XrlPFSenderFactory::create failed: XrlPFConstructorError from line 667 of
> >> xrl_pf_stcp.cc: Could not
> >> connect to 127.0.0.1:11045
> >>
> >> [ 2008/10/13 12:22:33 ERROR xorp_rtrmgr:351 XRL +451 xrl_router.cc
> >> get_sender ] Could not create
> >> XrlPFSender for protocol = "stcp" address = "127.0.0.1:11045"
> >> [1] 351 segmentation fault (core dumped) ./bin/xorp_rtrmgr
> >>
> >> Let me know what you would like me to do next =)
> >>
> >> thanks!
> >> stegen
> >>
> >> Pavlin Radoslavov wrote:
> >>> Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU> wrote:
> >>>
> >>>> Stegen Smith <stegen at owns.com> wrote:
> >>>>
> >>>>> Hi Pavlin,
> >>>>>
> >>>>> Yeah, it seems to occur when things sit idly. Ultimately something
> >>>>> gums up the works and I get
> >>>>> those error messages, so it's not only when I modified the routing
> >>>>> table myself. It should be
> >>>>> easily recreated. Odd... So with that, I'll get one submitted right
> >>>>> away with more detailed
> >>>>> information.
> >>>> I just saw the entry in Bugzilla. Thanks!
> >>>>
> >>>> The missing routes might be related to the XRL errors.
> >>>> The "life timer expired" indicates that the XRL communication has
> >>>> timed-out, and after that all bets are off.
> >>>> BTW, this particular timeout shouldn't happen under (very relaxed)
> >>>> normal circumstances, so there is something else happening.
> >>>> This probably also explains the shutdown problem with the leftover
> >>>> XORP processes.
> >>>>
> >>>> Re. the shutdown question: yes, if you are running XORP in
> >>>> foreground, Ctrl-C should be the way to stop it.
> >>>>
> >>>> I (or somebody else) should look at this problem very soon, because
> >>>> it looks critical.
> >>>
> >>> The problem is fixed in CVS:
> >>>
> >>> Revision Changes Path
> >>> 1.25 +9 -8; commitid: 7b5a48f2abbc41a7; xorp/libxipc/ test_stcp.cc
> >>> 1.72 +18 -20; commitid: 7b5a48f2abbc41a7; xorp/libxipc/
> >>> xrl_pf_stcp.cc
> >>> 1.36 +4 -4; commitid: 7b5a48f2abbc41a7; xorp/libxipc/
> >>> xrl_pf_stcp.hh
> >>>
> >>> Please checkout the latest code from CVS and verify whether it fixes
> >>> the problems on your side.
> >>>
> >>> Pavlin
> >>>
> >>>> Pavlin
> >>>>
> >>>>> Another note... I've got bgp peering setup and I see the following:
> >>>>> xorp at at-ig1.sv.atomz.com> show bgp routes
> >>>>> Status Codes: * valid route, > best route
> >>>>> Origin Codes: i IGP, e EGP, ? incomplete
> >>>>>
> >>>>> Prefix Nexthop Peer AS
> >>>>> Path
> >>>>> ------ ------- ----
> >>>>> -------
> >>>>> * 10.3.48.0/20 10.3.14.39 10.3.14.99 65000
> >>>>> i
> >>>>> * 10.5.49.0/24 10.3.14.39 10.3.14.99 65000
> >>>>> i
> >>>>> * 10.3.48.0/20 10.3.14.7 10.3.14.99 65000
> >>>>> i
> >>>>> * 10.5.49.0/24 10.3.14.7 10.3.14.99 65000
> >>>>> i
> >>>>>
> >>>>> yet no routes are inserted on the system:
> >>>>> root1paat-ig1.sv~ netstat -nr|grep 10.3.48
> >>>>> root1paat-ig1.sv~
> >>>>>
> >>>>> I'm guessing that this is another bug, or perhaps related to the first
> >>>>> issue I've noticed. I'll
> >>>>> submit a bug for the first one, and if you would like me to do the same
> >>>>> for this issue I'm seeing,
> >>>>> let me know. =)
> >>>>>
> >>>>> And one more side note... what's the cleanest way to shutdown the
> >>>>> routing software? I've been
> >>>>> letting xorp_rtrmgr run in the foreground while I do testing, and ^C
> >>>>> when I want to quit out.
> >>>>> Probably not the best way to do it, as it ends up crashing (cores) and
> >>>>> leaving other xorp processes
> >>>>> up and running:
> >>>>>
> >>>>> ^C[ 2008/10/10 11:13:26 INFO xorp_rtrmgr:8398 RTRMGR +1024 task.cc
> >>>>> shutdown ] Shutting down module: bgp
> >>>>> [ 2008/10/10 11:13:26 INFO xorp_bgp:18890 BGP +451 peer.cc
> >>>>> send_notification ] Sending:
> >>>>> Notification Packet: Cease(6)
> >>>>> [ 2008/10/10 11:13:26 TRACE xorp_bgp:18890 BGP +456 peer.cc
> >>>>> send_notification ] Peer
> >>>>> {10.3.14.40(179) 10.3.14.39(179)}: Send: Notification Packet: Cease(6)
> >>>>>
> >>>>> <cleared some cruft for email brevity>
> >>>>>
> >>>>> [ 2008/10/10 11:13:28 INFO xorp_rtrmgr:8398 XRL +432 xrl_router.cc
> >>>>> get_sender ] Sender died
> >>>>> (protocol = "stcp", address = "127.0.0.1:11810")
> >>>>> [ 2008/10/10 11:13:28 ERROR xorp_rtrmgr:8398 LIBCOMM +610 comm_sock.c
> >>>>> comm_sock_connect4 ] Error
> >>>>> connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port =
> >>>>> 11810): Connection refused
> >>>>> [ 2008/10/10 11:13:28 ERROR xorp_rtrmgr:8398 XRL +63 xrl_pf_factory.cc
> >>>>> create_sender ]
> >>>>> XrlPFSenderFactory::create failed: XrlPFConstructorError from line 668
> >>>>> of xrl_pf_stcp.cc: Could not
> >>>>> connect to 127.0.0.1:11810
> >>>>>
> >>>>> [ 2008/10/10 11:13:28 ERROR xorp_rtrmgr:8398 XRL +451 xrl_router.cc
> >>>>> get_sender ] Could not create
> >>>>> XrlPFSender for protocol = "stcp" address = "127.0.0.1:11810"
> >>>>> [1] 8398 segmentation fault (core dumped) ./bin/xorp_rtrmgr
> >>>>> root139p9at-ig1.sv/usr/local/xorp
> >>>>> root139p9at-ig1.sv/usr/local/xorp ps auxww|grep xorp
> >>>>> xorp 20544 0.0 0.1 3516 5484 p1 I+ 5:21PM 0:00.35
> >>>>> /usr/local/xorp/bin/xorpsh
> >>>>> root 2811 0.0 0.2 5076 6476 p9 S 11:09AM 0:00.75
> >>>>> xorp_fea
> >>>>> root 17533 0.0 0.1 2812 4452 p9 S 11:10AM 0:00.22
> >>>>> xorp_rib
> >>>>> root 16731 0.0 0.1 2188 3872 p9 I 11:10AM 0:00.18
> >>>>> xorp_fib2mrib
> >>>>> root 9111 0.0 0.1 2728 4268 p9 S 11:10AM 0:00.20
> >>>>> xorp_igmp
> >>>>> root 32406 0.0 0.1 4752 6028 p9 S 11:10AM 0:00.50
> >>>>> xorp_pimsm4
> >>>>> root 4331 0.0 0.0 848 692 p9 R+/1 11:16AM 0:00.00 grep
> >>>>> xorp (zsh)
> >>>>> root0p9at-ig1.sv/usr/local/xorp
> >>>>>
> >>>>> I'm just working hard at keeping you guys busy ;)
> >>>>>
> >>>>> thanks,
> >>>>> stegen
> >>>>>
> >>>>> Pavlin Radoslavov wrote:
> >>>>>> Stegen Smith <stegen at owns.com> wrote:
> >>>>>>
> >>>>>>> Also an interesting thing to note is that if a routing entry is added
> >>>>>>> manually, I see the following happening:
> >>>>>>>
> >>>>>>> [ 2008/10/09 16:31:35 ERROR xorp_fea:15980 XRL +379 xrl_pf_stcp.cc
> >>>>>>> die ] STCPRequestHandler died: life timer expired
> >>>>>>> [ 2008/10/09 16:31:35 ERROR xorp_fea:15980 XRL +379 xrl_pf_stcp.cc
> >>>>>>> die ] STCPRequestHandler died: life timer expired
> >>>>>> This issue is probably independent from the routing table cleanup,
> >>>>>> hence please submit a Bugzilla entry.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Pavlin
> >>>>>>
> >>>>>>> And also, I forgot to give the following information... I'm using the
> >>>>>>> latest xorp build from cvs, and this is openbsd 4.3.
> >>>>> _______________________________________________
> >>>>> Xorp-users mailing list
> >>>>> Xorp-users at xorp.org
> >>>>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >>>> _______________________________________________
> >>>> Xorp-users mailing list
> >>>> Xorp-users at xorp.org
> >>>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >>>
> >>
> >> _______________________________________________
> >> Xorp-users mailing list
> >> Xorp-users at xorp.org
> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >
>
> _______________________________________________
> 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