Re: [Vyatta-users] latency tool
Hello Dave, Ken, Jonathon Many many thanks for your answers Very interesting Thanks Troopy -- Original Message -- From: "Ken Felix (C)" <[EMAIL PROTECTED]> Date: Thu, 17 Jan 2008 18:24:17 -0500 >I've used D-ITG also, great for simulation of VOIP/SIP traffic. > > > >One other tools that has a longer history Mgen/Drec. Just like ITG you >will need sync clocks between sender ( mgen ) and receiver ( drec ). > > > >Both pkgs allows for creation by >src/dst/port/ttl/pps/kbps/etc... > > > >Mgen was mainly used for multicast generation hence the name mGen, >but it does support unicast flows also. > > > >Using udp you can easily obtain one-way latency results. Also you can >watch how certain task effect latency. > > > >i.e > > > >copy tftp flash: on a cisco router will cause the latency to growth on >very low end routers ;) > > > >or > > > >squezze a flash partition: > > > > > >btw, if your very strong in scripting both pkgs are easy to script for >automation and controls. > > > > > >Hope this helps. > > > > > > __ Désirez vous une adresse éléctronique @suisse.com? Visitez la Suisse virtuelle sur http://www.suisse.com ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] Clonezilla Multicast Imaging
I bet it has nothing todo with STP. Since your imaging with mcast, was igmp-snooping enable or not? Suprisely cisco switches works very good with mcast traffic when configured correctly. ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] Clonezilla Multicast Imaging
For those of you trying to image computers with Clonezilla and have any (*dare I say the name*) Cisco switches, you will have timeout issues. I've recently figured out a resolution and I'd like to share it with everyone so that in the future someone else does not have to work as hard to get it accomplished. [ It's sad - we had to drop to using a 10Mbps hub to get the Linux lab imaged due to timeout issues - rather slow! Elapsed time has been cut down from upwards of an hour or more (80GB drive or so) to the *new record of 20-25 min!!!* ] I just turned off STP for the whole switch and voila - Clonezilla harmony. Thanks again, Mike PS: Vyatta Devs, when does the Vyatta Switch debut??? Commands for anyone wondering or wanting how this is done. *All ports/whole switch * enable configure terminal no spanning-tree vlan 1 end show spanning-tree (check to see that it's off) *Single port(s)* enable configure terminal interface fastethernet 4 no spanning-tree vlan 1 end show spanning-tree (check to see that it's off) -- // SilverTip257 // == ~ · · /V\ // \\ /( )\ ^`~´^ ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
I think you've hit bug 2390: RIB: xorp_rib crashed after a static
route with a nextop through an unxisted interface or a route being
configured and committed
See https://bugzilla.vyatta.com/show_bug.cgi?id=2390 ; it's fixed in
the supported version.
Best,
Justin
On Jan 17, 2008 5:19 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
>
>
>
> #1 - No, but I do have a static interface-route with XX.128.128.0/20 - the
> actual interface is XX.128.128.0/24 -- the reason I have this is for proper
> BGP exporting
> #2 - Invalid, my mistake
> #3 - Dido to #1
>
> My interface-routes are last on my static routes list in the config --
> could this be the issue?
>
> -Shane
>
>
>
>
> Are they all assigned to a system that's on a network that's directly
> connected to the router?
>
> On Jan 17, 2008 3:59 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > None of these next-hop addresses are assigned to an interface on the
> router.
> >
> > Shane
> >
> >
> > -Original Message-
> > From: Justin Fletcher [mailto:[EMAIL PROTECTED]
> > Sent: Thu 1/17/2008 6:46 PM
> > To: Shane McKinley
> >
> > Cc: vyatta-users@mailman.vyatta.com
> > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr...
> >
> > Are the next hops directly connected? There was an issue with
> > recursive route lookup --
> >
> > On Jan 17, 2008 2:56 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
> > > I have found the static routes causing the issue:
> > >
> > > route XZ.85.142.64/26 {
> > > next-hop: XX.128.129.18
> > > metric: 1
> > > }
> > > route XX.128.136.216/29 {
> > > next-hop: XZ.85.140.254
> > > metric: 1
> > > }
> > > route XX.128.140.16/29 {
> > > next-hop: XX.128.140.26
> > > metric: 1
> > > }
> > >
> > > Now, the question is why? How can I dig further to find out why these
> > > are causing the rtrmgr to crash?
> > >
> > > Shane McKinley
> > > Habersham EMC
> > >
> > > -Original Message-
> > > From: Dave Roberts [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, January 17, 2008 5:16 PM
> > >
> > > To: Shane McKinley; vyatta-users@mailman.vyatta.com
> > > Subject: RE: [Vyatta-users] Waiting for xorp_rtrmgr...
> > >
> > > > (SIDE NOTE: (No offense meant) Why should changing interface
> notations
> > >
> > > > and static routes cause anything to crash?)
> > >
> > > It shouldn't. That's one of the big things we're fixing in Glendale.
> The
> > > Routermanager process did not handle errors well at all. It has been
> > > eliminated entirely in Glendale.
> > >
> > > -- Dave
> > >
> > > ___
> > > Vyatta-users mailing list
> > > Vyatta-users@mailman.vyatta.com
> > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users
> > >
> >
> >
>
>
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] vmware server and live CD
Can you provide just a bit more information? Justin On Jan 17, 2008 4:41 PM, Rick Mitchell <[EMAIL PROTECTED]> wrote: > I cannot get the live cd to successfully boot up it tries to but > fails any suggestions > > -- > Rick Mitchell > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
#1 - No, but I do have a static interface-route with XX.128.128.0/20 - the
actual interface is XX.128.128.0/24 -- the reason I have this is for proper BGP
exporting
#2 - Invalid, my mistake
#3 - Dido to #1
My interface-routes are last on my static routes list in the config -- could
this be the issue?
-Shane
Are they all assigned to a system that's on a network that's directly
connected to the router?
On Jan 17, 2008 3:59 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
>
>
>
> None of these next-hop addresses are assigned to an interface on the router.
>
> Shane
>
>
> -Original Message-
> From: Justin Fletcher [mailto:[EMAIL PROTECTED]
> Sent: Thu 1/17/2008 6:46 PM
> To: Shane McKinley
>
> Cc: vyatta-users@mailman.vyatta.com
> Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr...
>
> Are the next hops directly connected? There was an issue with
> recursive route lookup --
>
> On Jan 17, 2008 2:56 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
> > I have found the static routes causing the issue:
> >
> > route XZ.85.142.64/26 {
> > next-hop: XX.128.129.18
> > metric: 1
> > }
> > route XX.128.136.216/29 {
> > next-hop: XZ.85.140.254
> > metric: 1
> > }
> > route XX.128.140.16/29 {
> > next-hop: XX.128.140.26
> > metric: 1
> > }
> >
> > Now, the question is why? How can I dig further to find out why these
> > are causing the rtrmgr to crash?
> >
> > Shane McKinley
> > Habersham EMC
> >
> > -Original Message-
> > From: Dave Roberts [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, January 17, 2008 5:16 PM
> >
> > To: Shane McKinley; vyatta-users@mailman.vyatta.com
> > Subject: RE: [Vyatta-users] Waiting for xorp_rtrmgr...
> >
> > > (SIDE NOTE: (No offense meant) Why should changing interface notations
> >
> > > and static routes cause anything to crash?)
> >
> > It shouldn't. That's one of the big things we're fixing in Glendale. The
> > Routermanager process did not handle errors well at all. It has been
> > eliminated entirely in Glendale.
> >
> > -- Dave
> >
> > ___
> > Vyatta-users mailing list
> > Vyatta-users@mailman.vyatta.com
> > http://mailman.vyatta.com/mailman/listinfo/vyatta-users
> >
>
>
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] vmware server and live CD
I cannot get the live cd to successfully boot up it tries to but fails any suggestions -- Rick Mitchell ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
Are they all assigned to a system that's on a network that's directly
connected to the router?
On Jan 17, 2008 3:59 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
>
>
>
> None of these next-hop addresses are assigned to an interface on the router.
>
> Shane
>
>
> -Original Message-
> From: Justin Fletcher [mailto:[EMAIL PROTECTED]
> Sent: Thu 1/17/2008 6:46 PM
> To: Shane McKinley
>
> Cc: vyatta-users@mailman.vyatta.com
> Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr...
>
> Are the next hops directly connected? There was an issue with
> recursive route lookup --
>
> On Jan 17, 2008 2:56 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
> > I have found the static routes causing the issue:
> >
> > route XZ.85.142.64/26 {
> > next-hop: XX.128.129.18
> > metric: 1
> > }
> > route XX.128.136.216/29 {
> > next-hop: XZ.85.140.254
> > metric: 1
> > }
> > route XX.128.140.16/29 {
> > next-hop: XX.128.140.26
> > metric: 1
> > }
> >
> > Now, the question is why? How can I dig further to find out why these
> > are causing the rtrmgr to crash?
> >
> > Shane McKinley
> > Habersham EMC
> >
> > -Original Message-
> > From: Dave Roberts [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, January 17, 2008 5:16 PM
> >
> > To: Shane McKinley; vyatta-users@mailman.vyatta.com
> > Subject: RE: [Vyatta-users] Waiting for xorp_rtrmgr...
> >
> > > (SIDE NOTE: (No offense meant) Why should changing interface notations
> >
> > > and static routes cause anything to crash?)
> >
> > It shouldn't. That's one of the big things we're fixing in Glendale. The
> > Routermanager process did not handle errors well at all. It has been
> > eliminated entirely in Glendale.
> >
> > -- Dave
> >
> > ___
> > Vyatta-users mailing list
> > Vyatta-users@mailman.vyatta.com
> > http://mailman.vyatta.com/mailman/listinfo/vyatta-users
> >
>
>
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
None of these next-hop addresses are assigned to an interface on the router.
Shane
-Original Message-
From: Justin Fletcher [mailto:[EMAIL PROTECTED]
Sent: Thu 1/17/2008 6:46 PM
To: Shane McKinley
Cc: vyatta-users@mailman.vyatta.com
Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr...
Are the next hops directly connected? There was an issue with
recursive route lookup --
On Jan 17, 2008 2:56 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
> I have found the static routes causing the issue:
>
> route XZ.85.142.64/26 {
> next-hop: XX.128.129.18
> metric: 1
> }
> route XX.128.136.216/29 {
> next-hop: XZ.85.140.254
> metric: 1
> }
> route XX.128.140.16/29 {
> next-hop: XX.128.140.26
> metric: 1
> }
>
> Now, the question is why? How can I dig further to find out why these
> are causing the rtrmgr to crash?
>
> Shane McKinley
> Habersham EMC
>
> -Original Message-
> From: Dave Roberts [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 17, 2008 5:16 PM
>
> To: Shane McKinley; vyatta-users@mailman.vyatta.com
> Subject: RE: [Vyatta-users] Waiting for xorp_rtrmgr...
>
> > (SIDE NOTE: (No offense meant) Why should changing interface notations
>
> > and static routes cause anything to crash?)
>
> It shouldn't. That's one of the big things we're fixing in Glendale. The
> Routermanager process did not handle errors well at all. It has been
> eliminated entirely in Glendale.
>
> -- Dave
>
> ___
> Vyatta-users mailing list
> Vyatta-users@mailman.vyatta.com
> http://mailman.vyatta.com/mailman/listinfo/vyatta-users
>
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
Are the next hops directly connected? There was an issue with
recursive route lookup --
On Jan 17, 2008 2:56 PM, Shane McKinley <[EMAIL PROTECTED]> wrote:
> I have found the static routes causing the issue:
>
> route XZ.85.142.64/26 {
> next-hop: XX.128.129.18
> metric: 1
> }
> route XX.128.136.216/29 {
> next-hop: XZ.85.140.254
> metric: 1
> }
> route XX.128.140.16/29 {
> next-hop: XX.128.140.26
> metric: 1
> }
>
> Now, the question is why? How can I dig further to find out why these
> are causing the rtrmgr to crash?
>
> Shane McKinley
> Habersham EMC
>
> -Original Message-
> From: Dave Roberts [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 17, 2008 5:16 PM
>
> To: Shane McKinley; vyatta-users@mailman.vyatta.com
> Subject: RE: [Vyatta-users] Waiting for xorp_rtrmgr...
>
> > (SIDE NOTE: (No offense meant) Why should changing interface notations
>
> > and static routes cause anything to crash?)
>
> It shouldn't. That's one of the big things we're fixing in Glendale. The
> Routermanager process did not handle errors well at all. It has been
> eliminated entirely in Glendale.
>
> -- Dave
>
> ___
> Vyatta-users mailing list
> Vyatta-users@mailman.vyatta.com
> http://mailman.vyatta.com/mailman/listinfo/vyatta-users
>
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
I commented out all static routes and enabled each one by one. The rtrmgr will not start will these specific static routes entered. When they are commented out, rtrmgr starts fine. Shane McKinley Habersham EMC -Original Message- From: Ken Felix (C) [mailto:[EMAIL PROTECTED] Sent: Thu 1/17/2008 6:19 PM To: vyatta-users@mailman.vyatta.com Subject: [Vyatta-users] Waiting for xorp_rtrmgr... Have you tried to removed the statics or upload a save config.boot and make 100% sure these are the culprit? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] latency tool
I've used D-ITG also, great for simulation of VOIP/SIP traffic. One other tools that has a longer history Mgen/Drec. Just like ITG you will need sync clocks between sender ( mgen ) and receiver ( drec ). Both pkgs allows for creation by src/dst/port/ttl/pps/kbps/etc... Mgen was mainly used for multicast generation hence the name mGen, but it does support unicast flows also. Using udp you can easily obtain one-way latency results. Also you can watch how certain task effect latency. i.e copy tftp flash: on a cisco router will cause the latency to growth on very low end routers ;) or squezze a flash partition: btw, if your very strong in scripting both pkgs are easy to script for automation and controls. Hope this helps. ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] Waiting for xorp_rtrmgr...
Have you tried to removed the statics or upload a save config.boot and make 100% sure these are the culprit? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
I have found the static routes causing the issue:
route XZ.85.142.64/26 {
next-hop: XX.128.129.18
metric: 1
}
route XX.128.136.216/29 {
next-hop: XZ.85.140.254
metric: 1
}
route XX.128.140.16/29 {
next-hop: XX.128.140.26
metric: 1
}
Now, the question is why? How can I dig further to find out why these
are causing the rtrmgr to crash?
Shane McKinley
Habersham EMC
-Original Message-
From: Dave Roberts [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 17, 2008 5:16 PM
To: Shane McKinley; vyatta-users@mailman.vyatta.com
Subject: RE: [Vyatta-users] Waiting for xorp_rtrmgr...
> (SIDE NOTE: (No offense meant) Why should changing interface notations
> and static routes cause anything to crash?)
It shouldn't. That's one of the big things we're fixing in Glendale. The
Routermanager process did not handle errors well at all. It has been
eliminated entirely in Glendale.
-- Dave
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
> (SIDE NOTE: (No offense meant) Why should changing interface > notations and static routes cause anything to crash?) It shouldn't. That's one of the big things we're fixing in Glendale. The Routermanager process did not handle errors well at all. It has been eliminated entirely in Glendale. -- Dave ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
FYI, I found this: 'Shutting down fatally wounded process (static_routes)' I am now running a process of elimination. Shane McKinley Habersham EMC -Original Message- From: Justin Fletcher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 17, 2008 4:50 PM To: Shane McKinley Cc: vyatta-users@mailman.vyatta.com Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... Unfortunately, not all the log entries are nicely categorized -- "Failed to resolve" is normal on startup, as are the other logged entries. Try looking for "assert", "exiting" (use "grep -i" so it's case-insensitive) to see what else you find. Sometimes, it's a matter of commenting out (you can use the C style /* */) portions of the configuration until it comes up, and adding in elements bit by bit to isolate where the error is. FYI, the upcoming version will handle configuration file issues in a much friendlier manner. Justin On Jan 17, 2008 1:40 PM, Shane McKinley <[EMAIL PROTECTED]> wrote: > This is what I have for this command -- 'cat /var/log/messages | grep > ERROR' > > == > == = > > Jan 17 16:35:56 localhost xorp_rtrmgr: [ 2008/01/17 16:35:55 ERROR > xorp_rtrmgr:5628 FINDER +1079 > /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxipc/fi > nd er.cc announce_new_instance ] Failed to resolve > finder://[EMAIL PROTECTED]/find > er > _event_observer/0.1/xrl_target_birth?target_class:txt=fea&target_insta > nc > e:[EMAIL PROTECTED] > Jan 17 16:36:05 localhost xorp_rtrmgr: [ 2008/01/17 16:36:05 ERROR > xorp_rtrmgr:5628 FINDER +85 > /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxipc/fi > nd er_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed > out > > == > == = > > And for this command 'cat /var/log/messages | grep WARNING' > > == > == = > > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth0 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth0/eth0 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: > eth0.504 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: > eth0.504/eth0.504 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.504/eth0.504/69.40.11.198 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.504/eth0.504/69.40.11.210 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: > eth0.514 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: > eth0.514/eth0.514 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.514/eth0.514/66.128.134.130 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth1 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth1/eth1 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/10.0.0.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.69.63.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.80.121.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.85.140.33 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.85.143.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.128.143.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.128.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update f
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
Unfortunately, not all the log entries are nicely categorized -- "Failed to resolve" is normal on startup, as are the other logged entries. Try looking for "assert", "exiting" (use "grep -i" so it's case-insensitive) to see what else you find. Sometimes, it's a matter of commenting out (you can use the C style /* */) portions of the configuration until it comes up, and adding in elements bit by bit to isolate where the error is. FYI, the upcoming version will handle configuration file issues in a much friendlier manner. Justin On Jan 17, 2008 1:40 PM, Shane McKinley <[EMAIL PROTECTED]> wrote: > This is what I have for this command -- 'cat /var/log/messages | grep > ERROR' > > > = > > Jan 17 16:35:56 localhost xorp_rtrmgr: [ 2008/01/17 16:35:55 ERROR > xorp_rtrmgr:5628 FINDER +1079 > /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxipc/find > er.cc announce_new_instance ] Failed to resolve > finder://[EMAIL PROTECTED]/finder > _event_observer/0.1/xrl_target_birth?target_class:txt=fea&target_instanc > e:[EMAIL PROTECTED] > Jan 17 16:36:05 localhost xorp_rtrmgr: [ 2008/01/17 16:36:05 ERROR > xorp_rtrmgr:5628 FINDER +85 > /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxipc/find > er_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out > > > = > > And for this command 'cat /var/log/messages | grep WARNING' > > > = > > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth0 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth0/eth0 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: > eth0.504 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: > eth0.504/eth0.504 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.504/eth0.504/69.40.11.198 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.504/eth0.504/69.40.11.210 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: > eth0.514 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: > eth0.514/eth0.514 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.514/eth0.514/66.128.134.130 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth1 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth1/eth1 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/10.0.0.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.69.63.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.80.121.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.85.140.33 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.85.143.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.128.143.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.128.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.130.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.135.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.139.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
This is what I have for this command -- 'cat /var/log/messages | grep ERROR' = Jan 17 16:35:56 localhost xorp_rtrmgr: [ 2008/01/17 16:35:55 ERROR xorp_rtrmgr:5628 FINDER +1079 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxipc/find er.cc announce_new_instance ] Failed to resolve finder://[EMAIL PROTECTED]/finder _event_observer/0.1/xrl_target_birth?target_class:txt=fea&target_instanc e:[EMAIL PROTECTED] Jan 17 16:36:05 localhost xorp_rtrmgr: [ 2008/01/17 16:36:05 ERROR xorp_rtrmgr:5628 FINDER +85 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxipc/find er_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out = And for this command 'cat /var/log/messages | grep WARNING' = Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth0 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth0/eth0 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth0.504 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth0.504/eth0.504 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth0.504/eth0.504/69.40.11.198 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth0.504/eth0.504/69.40.11.210 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth0.514 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth0.514/eth0.514 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth0.514/eth0.514/66.128.134.130 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth1 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth1/eth1 Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/10.0.0.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/63.69.63.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/63.80.121.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/63.85.140.33 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/63.85.143.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/63.128.143.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/66.128.128.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/66.128.130.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/66.128.135.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: eth1/eth1/66.128.139.1 Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for interface not in libfeaclient tree: lo Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for vif not in libfeaclient tree: lo/lo Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING xorp_fea FEA ] Got update for address no in libfeaclient tree: lo/lo/63.69.63.6 Jan 17 16:35:20 localhost xorp_rib: [ 2008/01/17 16:35:19 WARNING xorp_rib LIBFEACLIENT ] NetlinkHead::io_event(), iface is empty Jan 17 16:35:20 localhost xorp_rib: [ 2008/01/17 16:35:19 WARNING xorp_rib LIBFEACLIENT ] NetlinkHead::io_event(), iface is empty Jan 17 16:35:40 localhost xorp_static_routes: [ 2008/01/17 16:35:39 WARNING xorp_static_routes LIBFEACLIENT ] NetlinkHead::io_event(), iface
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
You can enable verbose debugging by changing VERBOSERTRMGR= on line 51 of /opt/vyatta/sbin/rtrmgr.init to VERBOSERTRMGR=-v As a caution, this will generate a LOT of output in your log files!! Justin On Jan 17, 2008 1:31 PM, Shane McKinley <[EMAIL PROTECTED]> wrote: > I did. I am trying to comment out my static routes to see if that will > help. > > Any other suggestions? > > > Shane McKinley > Habersham EMC > > -Original Message- > > From: Michael Larson [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 17, 2008 4:27 PM > To: Shane McKinley > Cc: vyatta-users@mailman.vyatta.com > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... > > Hi Shane, > > Did you restart the syslog daemon after you modified the syslog.conf > file? > > /etc/init.d/sysklogd restart > > Mike > > - Original Message - > From: "Shane McKinley" <[EMAIL PROTECTED]> > To: vyatta-users@mailman.vyatta.com > Sent: Thursday, January 17, 2008 1:23:06 PM (GMT-0800) > America/Los_Angeles > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... > > I have changed /etc/syslog.conf to *.* and restarted the vyatta-ofr. I > don't see anything that just pops out at me in /var/log/messages since > the restart. I did truncate the file before attempting to restart the > vyatta-ofr service. > > Any way to pinpoint which line in my config is causing the issue? > > (SIDE NOTE: (No offense meant) Why should changing interface notations > and static routes cause anything to crash?) > > Shane McKinley > Habersham EMC > > -Original Message- > From: Justin Fletcher [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 17, 2008 3:58 PM > To: Marat Nepomnyashy > Cc: Shane McKinley; vyatta-users@mailman.vyatta.com > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... > > You'll also want to edit /etc/syslog.conf and change *.warning to *.* to > record all log messages; otherwise, lower-level messages will be > discared > > You can check startup by hand by running "/etc/init.d/vyatta-rtrmgr > start" which will save you the physical reboot -- > > Justin > > On Jan 17, 2008 12:54 PM, Marat Nepomnyashy <[EMAIL PROTECTED]> wrote: > > Hi Shane, > > > > Most likely the rtrmgr did not start. The best log file to check when > > > that happens is '/var/log/messages'. > > > > Which Vyatta version are you using? > > > > Thanks, > > Marat > > > > > > - Original Message - > > From: "Shane McKinley" <[EMAIL PROTECTED]> > > To: > > Sent: Thursday, January 17, 2008 12:51 PM > > Subject: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > > > > After entering some static routes and changing some subnetting > > > around I rebooted. Now the rtrmgr won't start -- the commit took > > > fine before I rebooted. > > > > > > Is there a way I can pull the proper error messages to troubleshoot > > > this problem? What log files would be best to look at? > > > > > > Any more ideas on why this would happen? I really am dedicated to > > > getting this router into production, but the odds seem against me > > > this round. > > > > > > Thanks, > > > > > > Shane McKinley > > > Habersham EMC > > > Tel: 706-839-4130 > > > Cel: 706-968-3186 > > > ___ > > > Vyatta-users mailing list > > > Vyatta-users@mailman.vyatta.com > > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > > > > ___ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
I did. I am trying to comment out my static routes to see if that will help. Any other suggestions? Shane McKinley Habersham EMC -Original Message- From: Michael Larson [mailto:[EMAIL PROTECTED] Sent: Thursday, January 17, 2008 4:27 PM To: Shane McKinley Cc: vyatta-users@mailman.vyatta.com Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... Hi Shane, Did you restart the syslog daemon after you modified the syslog.conf file? /etc/init.d/sysklogd restart Mike - Original Message - From: "Shane McKinley" <[EMAIL PROTECTED]> To: vyatta-users@mailman.vyatta.com Sent: Thursday, January 17, 2008 1:23:06 PM (GMT-0800) America/Los_Angeles Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... I have changed /etc/syslog.conf to *.* and restarted the vyatta-ofr. I don't see anything that just pops out at me in /var/log/messages since the restart. I did truncate the file before attempting to restart the vyatta-ofr service. Any way to pinpoint which line in my config is causing the issue? (SIDE NOTE: (No offense meant) Why should changing interface notations and static routes cause anything to crash?) Shane McKinley Habersham EMC -Original Message- From: Justin Fletcher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 17, 2008 3:58 PM To: Marat Nepomnyashy Cc: Shane McKinley; vyatta-users@mailman.vyatta.com Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... You'll also want to edit /etc/syslog.conf and change *.warning to *.* to record all log messages; otherwise, lower-level messages will be discared You can check startup by hand by running "/etc/init.d/vyatta-rtrmgr start" which will save you the physical reboot -- Justin On Jan 17, 2008 12:54 PM, Marat Nepomnyashy <[EMAIL PROTECTED]> wrote: > Hi Shane, > > Most likely the rtrmgr did not start. The best log file to check when > that happens is '/var/log/messages'. > > Which Vyatta version are you using? > > Thanks, > Marat > > > - Original Message - > From: "Shane McKinley" <[EMAIL PROTECTED]> > To: > Sent: Thursday, January 17, 2008 12:51 PM > Subject: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > After entering some static routes and changing some subnetting > > around I rebooted. Now the rtrmgr won't start -- the commit took > > fine before I rebooted. > > > > Is there a way I can pull the proper error messages to troubleshoot > > this problem? What log files would be best to look at? > > > > Any more ideas on why this would happen? I really am dedicated to > > getting this router into production, but the odds seem against me > > this round. > > > > Thanks, > > > > Shane McKinley > > Habersham EMC > > Tel: 706-839-4130 > > Cel: 706-968-3186 > > ___ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
Hi Shane, Did you restart the syslog daemon after you modified the syslog.conf file? /etc/init.d/sysklogd restart Mike - Original Message - From: "Shane McKinley" <[EMAIL PROTECTED]> To: vyatta-users@mailman.vyatta.com Sent: Thursday, January 17, 2008 1:23:06 PM (GMT-0800) America/Los_Angeles Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... I have changed /etc/syslog.conf to *.* and restarted the vyatta-ofr. I don't see anything that just pops out at me in /var/log/messages since the restart. I did truncate the file before attempting to restart the vyatta-ofr service. Any way to pinpoint which line in my config is causing the issue? (SIDE NOTE: (No offense meant) Why should changing interface notations and static routes cause anything to crash?) Shane McKinley Habersham EMC -Original Message- From: Justin Fletcher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 17, 2008 3:58 PM To: Marat Nepomnyashy Cc: Shane McKinley; vyatta-users@mailman.vyatta.com Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... You'll also want to edit /etc/syslog.conf and change *.warning to *.* to record all log messages; otherwise, lower-level messages will be discared You can check startup by hand by running "/etc/init.d/vyatta-rtrmgr start" which will save you the physical reboot -- Justin On Jan 17, 2008 12:54 PM, Marat Nepomnyashy <[EMAIL PROTECTED]> wrote: > Hi Shane, > > Most likely the rtrmgr did not start. The best log file to check when > that happens is '/var/log/messages'. > > Which Vyatta version are you using? > > Thanks, > Marat > > > - Original Message - > From: "Shane McKinley" <[EMAIL PROTECTED]> > To: > Sent: Thursday, January 17, 2008 12:51 PM > Subject: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > After entering some static routes and changing some subnetting > > around I rebooted. Now the rtrmgr won't start -- the commit took > > fine before I rebooted. > > > > Is there a way I can pull the proper error messages to troubleshoot > > this problem? What log files would be best to look at? > > > > Any more ideas on why this would happen? I really am dedicated to > > getting this router into production, but the odds seem against me > > this round. > > > > Thanks, > > > > Shane McKinley > > Habersham EMC > > Tel: 706-839-4130 > > Cel: 706-968-3186 > > ___ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
I have changed /etc/syslog.conf to *.* and restarted the vyatta-ofr. I don't see anything that just pops out at me in /var/log/messages since the restart. I did truncate the file before attempting to restart the vyatta-ofr service. Any way to pinpoint which line in my config is causing the issue? (SIDE NOTE: (No offense meant) Why should changing interface notations and static routes cause anything to crash?) Shane McKinley Habersham EMC -Original Message- From: Justin Fletcher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 17, 2008 3:58 PM To: Marat Nepomnyashy Cc: Shane McKinley; vyatta-users@mailman.vyatta.com Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... You'll also want to edit /etc/syslog.conf and change *.warning to *.* to record all log messages; otherwise, lower-level messages will be discared You can check startup by hand by running "/etc/init.d/vyatta-rtrmgr start" which will save you the physical reboot -- Justin On Jan 17, 2008 12:54 PM, Marat Nepomnyashy <[EMAIL PROTECTED]> wrote: > Hi Shane, > > Most likely the rtrmgr did not start. The best log file to check when > that happens is '/var/log/messages'. > > Which Vyatta version are you using? > > Thanks, > Marat > > > - Original Message - > From: "Shane McKinley" <[EMAIL PROTECTED]> > To: > Sent: Thursday, January 17, 2008 12:51 PM > Subject: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > After entering some static routes and changing some subnetting > > around I rebooted. Now the rtrmgr won't start -- the commit took > > fine before I rebooted. > > > > Is there a way I can pull the proper error messages to troubleshoot > > this problem? What log files would be best to look at? > > > > Any more ideas on why this would happen? I really am dedicated to > > getting this router into production, but the odds seem against me > > this round. > > > > Thanks, > > > > Shane McKinley > > Habersham EMC > > Tel: 706-839-4130 > > Cel: 706-968-3186 > > ___ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
You'll also want to edit /etc/syslog.conf and change *.warning to *.* to record all log messages; otherwise, lower-level messages will be discared You can check startup by hand by running "/etc/init.d/vyatta-rtrmgr start" which will save you the physical reboot -- Justin On Jan 17, 2008 12:54 PM, Marat Nepomnyashy <[EMAIL PROTECTED]> wrote: > Hi Shane, > > Most likely the rtrmgr did not start. The best log file to check when that > happens is '/var/log/messages'. > > Which Vyatta version are you using? > > Thanks, > Marat > > > - Original Message - > From: "Shane McKinley" <[EMAIL PROTECTED]> > To: > Sent: Thursday, January 17, 2008 12:51 PM > Subject: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > After entering some static routes and changing some subnetting around I > > rebooted. Now the rtrmgr won't start -- the commit took fine before I > > rebooted. > > > > Is there a way I can pull the proper error messages to troubleshoot this > > problem? What log files would be best to look at? > > > > Any more ideas on why this would happen? I really am dedicated to > > getting this router into production, but the odds seem against me this > > round. > > > > Thanks, > > > > Shane McKinley > > Habersham EMC > > Tel: 706-839-4130 > > Cel: 706-968-3186 > > ___ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Waiting for xorp_rtrmgr...
Hi Shane, Most likely the rtrmgr did not start. The best log file to check when that happens is '/var/log/messages'. Which Vyatta version are you using? Thanks, Marat - Original Message - From: "Shane McKinley" <[EMAIL PROTECTED]> To: Sent: Thursday, January 17, 2008 12:51 PM Subject: [Vyatta-users] Waiting for xorp_rtrmgr... > After entering some static routes and changing some subnetting around I > rebooted. Now the rtrmgr won't start -- the commit took fine before I > rebooted. > > Is there a way I can pull the proper error messages to troubleshoot this > problem? What log files would be best to look at? > > Any more ideas on why this would happen? I really am dedicated to > getting this router into production, but the odds seem against me this > round. > > Thanks, > > Shane McKinley > Habersham EMC > Tel: 706-839-4130 > Cel: 706-968-3186 > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] RFC 1918 Private IP addresses
> You'll want to create a firewall rule. By default, a router > just forwards the traffic it's sent (assuming it can find a > route to use for forwarding . . .) > > Best, > Justin > > On Jan 17, 2008 11:39 AM, Ben Speckien <[EMAIL PROTECTED]> wrote: > > I am using Vyatta as a gateway to the internet and have > noticed that > > it passes un-NATed private addresses out the public interface. Is > > there a way to turn this feature off or should I make a > firewall rule? This may also be the result of some sort of misconfiguration. As Justin says, by default the router just forwards on to what it thinks is the next hop. If you just configure your Internet router with a default route to your provider, then when any packet shows up destined to any private network that it doesn't know about inside your company, it will forward it to your provider. Rather than (just) installing a set of filters to block that traffic (although that would probably be a good idea, too), you might want to examine the routes on all of the routing equipment in your network to determine how private addresses are reaching your router in the first place. You might need to add some static routes somewhere, possibly on your Internet router, to make sure things are going where they are supposed to. -- Dave ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] Waiting for xorp_rtrmgr...
After entering some static routes and changing some subnetting around I rebooted. Now the rtrmgr won't start -- the commit took fine before I rebooted. Is there a way I can pull the proper error messages to troubleshoot this problem? What log files would be best to look at? Any more ideas on why this would happen? I really am dedicated to getting this router into production, but the odds seem against me this round. Thanks, Shane McKinley Habersham EMC Tel: 706-839-4130 Cel: 706-968-3186 ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] NetFlow
I do use ntop, it works pretty well for the price :) Flows from Vyatta are not an absolute requirement for me, but I would like to have a seamless transition from some of our Cisco gear to Vyatta (feature wise, vrrp across multi vifs, some type of glbp, flows, etc) You guys have been doing fantastic so far, I can wait to see how things develop :) On Jan 17, 2008 2:41 PM, Robert Bays <[EMAIL PROTECTED]> wrote: > There are methods for doing this in kernel using ip_conntrack_netlink > and ulogd2, but last time I looked they weren't incredibly mature. I > should probably browse the code again and see what the current state of > the state is. > > Until then, you can add userspace applications that use libpcap to > generate flow information. Check out ntop or netramet. Both of these > applications will require more processor and memory than your average > Vyatta router. Ntop should include nProbe which allows you to export > the flow data. Ntop is available as a debian package. Just add the > debian lenny repo to your config, apt-get update, apt-get install ntop > to check it out. As a bonus, it generates pretty graphs... > > > Max wrote: > > I am looking for Vyatta to be an exporter. Right now I just have a > > span/mirror port configured on a switch that gives me pretty good > > visibility, but I rather work in flows right off the router. > > All of our routers send flow data out to one of our collectors at the > > moment. > > > > On Jan 17, 2008 1:41 PM, Robert Bays <[EMAIL PROTECTED]> wrote: > >> Max, > >> > >> Are you looking for an x-flow collector or are you looking for the > >> Vyatta to be a flow exporter? > >> > >> Cheers, > >> Robert. > >> > >> > >> > >> Peter Wohlers wrote: > >>> netflow == nice > >>> sflow == better (imho, at least) > >>> > >>> sflow is open, and gives L2 info as well as full bgp path stats rather > >>> than just srcAS and peerAS info. Or you could totally blow our socks off > >>> and do both ;) > >>> > >>> But then again, you don't *really* wanna be writing royalty checks to > >>> crisco now, do you? > >>> > >>> --Peter > >>> > >>> Max wrote: > Wooo! Very nice! Man Vyatta sure is going to be one power house of a > router here soon :D > > On Jan 17, 2008 1:23 PM, Dave Roberts <[EMAIL PROTECTED]> wrote: > >> Are there any plans to build NetFlow support into Vyatta? > > Yup. It's something we're looking at over the next three releases or so. > > Don't hold me to this, but hopefully sometime in the summer timeframe. > > > > -- Dave > > > > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > >>> ___ > >>> Vyatta-users mailing list > >>> Vyatta-users@mailman.vyatta.com > >>> http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] NetFlow
There are methods for doing this in kernel using ip_conntrack_netlink and ulogd2, but last time I looked they weren't incredibly mature. I should probably browse the code again and see what the current state of the state is. Until then, you can add userspace applications that use libpcap to generate flow information. Check out ntop or netramet. Both of these applications will require more processor and memory than your average Vyatta router. Ntop should include nProbe which allows you to export the flow data. Ntop is available as a debian package. Just add the debian lenny repo to your config, apt-get update, apt-get install ntop to check it out. As a bonus, it generates pretty graphs... Max wrote: > I am looking for Vyatta to be an exporter. Right now I just have a > span/mirror port configured on a switch that gives me pretty good > visibility, but I rather work in flows right off the router. > All of our routers send flow data out to one of our collectors at the moment. > > On Jan 17, 2008 1:41 PM, Robert Bays <[EMAIL PROTECTED]> wrote: >> Max, >> >> Are you looking for an x-flow collector or are you looking for the >> Vyatta to be a flow exporter? >> >> Cheers, >> Robert. >> >> >> >> Peter Wohlers wrote: >>> netflow == nice >>> sflow == better (imho, at least) >>> >>> sflow is open, and gives L2 info as well as full bgp path stats rather >>> than just srcAS and peerAS info. Or you could totally blow our socks off >>> and do both ;) >>> >>> But then again, you don't *really* wanna be writing royalty checks to >>> crisco now, do you? >>> >>> --Peter >>> >>> Max wrote: Wooo! Very nice! Man Vyatta sure is going to be one power house of a router here soon :D On Jan 17, 2008 1:23 PM, Dave Roberts <[EMAIL PROTECTED]> wrote: >> Are there any plans to build NetFlow support into Vyatta? > Yup. It's something we're looking at over the next three releases or so. > Don't hold me to this, but hopefully sometime in the summer timeframe. > > -- Dave > > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users >>> ___ >>> Vyatta-users mailing list >>> Vyatta-users@mailman.vyatta.com >>> http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] NetFlow
I am looking for Vyatta to be an exporter. Right now I just have a span/mirror port configured on a switch that gives me pretty good visibility, but I rather work in flows right off the router. All of our routers send flow data out to one of our collectors at the moment. On Jan 17, 2008 1:41 PM, Robert Bays <[EMAIL PROTECTED]> wrote: > Max, > > Are you looking for an x-flow collector or are you looking for the > Vyatta to be a flow exporter? > > Cheers, > Robert. > > > > Peter Wohlers wrote: > > netflow == nice > > sflow == better (imho, at least) > > > > sflow is open, and gives L2 info as well as full bgp path stats rather > > than just srcAS and peerAS info. Or you could totally blow our socks off > > and do both ;) > > > > But then again, you don't *really* wanna be writing royalty checks to > > crisco now, do you? > > > > --Peter > > > > Max wrote: > >> Wooo! Very nice! Man Vyatta sure is going to be one power house of a > >> router here soon :D > >> > >> On Jan 17, 2008 1:23 PM, Dave Roberts <[EMAIL PROTECTED]> wrote: > Are there any plans to build NetFlow support into Vyatta? > >>> Yup. It's something we're looking at over the next three releases or so. > >>> Don't hold me to this, but hopefully sometime in the summer timeframe. > >>> > >>> -- Dave > >>> > >>> > >> ___ > >> Vyatta-users mailing list > >> Vyatta-users@mailman.vyatta.com > >> http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > ___ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] RFC 1918 Private IP addresses
You'll want to create a firewall rule. By default, a router just forwards the traffic it's sent (assuming it can find a route to use for forwarding . . .) Best, Justin On Jan 17, 2008 11:39 AM, Ben Speckien <[EMAIL PROTECTED]> wrote: > I am using Vyatta as a gateway to the internet and have noticed that it > passes un-NATed private addresses out the public interface. Is there a > way to turn this feature off or should I make a firewall rule? > > Thanks, > > Ben > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] NetFlow
Max, Are you looking for an x-flow collector or are you looking for the Vyatta to be a flow exporter? Cheers, Robert. Peter Wohlers wrote: > netflow == nice > sflow == better (imho, at least) > > sflow is open, and gives L2 info as well as full bgp path stats rather > than just srcAS and peerAS info. Or you could totally blow our socks off > and do both ;) > > But then again, you don't *really* wanna be writing royalty checks to > crisco now, do you? > > --Peter > > Max wrote: >> Wooo! Very nice! Man Vyatta sure is going to be one power house of a >> router here soon :D >> >> On Jan 17, 2008 1:23 PM, Dave Roberts <[EMAIL PROTECTED]> wrote: Are there any plans to build NetFlow support into Vyatta? >>> Yup. It's something we're looking at over the next three releases or so. >>> Don't hold me to this, but hopefully sometime in the summer timeframe. >>> >>> -- Dave >>> >>> >> ___ >> Vyatta-users mailing list >> Vyatta-users@mailman.vyatta.com >> http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] NetFlow
netflow == nice sflow == better (imho, at least) sflow is open, and gives L2 info as well as full bgp path stats rather than just srcAS and peerAS info. Or you could totally blow our socks off and do both ;) But then again, you don't *really* wanna be writing royalty checks to crisco now, do you? --Peter Max wrote: > Wooo! Very nice! Man Vyatta sure is going to be one power house of a > router here soon :D > > On Jan 17, 2008 1:23 PM, Dave Roberts <[EMAIL PROTECTED]> wrote: >>> Are there any plans to build NetFlow support into Vyatta? >> Yup. It's something we're looking at over the next three releases or so. >> Don't hold me to this, but hopefully sometime in the summer timeframe. >> >> -- Dave >> >> > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] RFC 1918 Private IP addresses
I am using Vyatta as a gateway to the internet and have noticed that it passes un-NATed private addresses out the public interface. Is there a way to turn this feature off or should I make a firewall rule? Thanks, Ben ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] NetFlow
Wooo! Very nice! Man Vyatta sure is going to be one power house of a router here soon :D On Jan 17, 2008 1:23 PM, Dave Roberts <[EMAIL PROTECTED]> wrote: > > Are there any plans to build NetFlow support into Vyatta? > > Yup. It's something we're looking at over the next three releases or so. > Don't hold me to this, but hopefully sometime in the summer timeframe. > > -- Dave > > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] NetFlow
> Are there any plans to build NetFlow support into Vyatta? Yup. It's something we're looking at over the next three releases or so. Don't hold me to this, but hopefully sometime in the summer timeframe. -- Dave ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] NetFlow
Are there any plans to build NetFlow support into Vyatta? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] latency tool
If you aren't all that worried about microsecond accuracy, then NTP can be made reasonably accurate, somewhere around +/- 10ms if yoou use multiple clock sources. See http://www.ijs.si/time/ for more info. A latency measurement tool that might be useful is D-ITG from http://www.grid.unina.it/software/ITG/index.php Jonathon ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] latency tool
Hi Troopy, You want to look at netperf... http://www.netperf.org/ Cheers, Robert. Troopy . wrote: > Hello, > > i have a question not directy related to Vyatta but more to networking. > > I am looking for a tool that is able to measure the (one-way) latency or > delay. >>From what i know ping or traceroute are only able to measure the RTT. > > Thanks > > Troopy > > > __ > Désirez vous une adresse éléctronique @suisse.com? > Visitez la Suisse virtuelle sur http://www.suisse.com > > ___ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] latency tool
> I am looking for a tool that is able to measure the (one-way) > latency or delay. > >From what i know ping or traceroute are only able to measure the RTT. There is no widely-used, standard tool that I know of. Im sure there is some code you could snarf from somewhere, though. I think the reason that a standard tool doesnt exist is that the problem of latency testing essentially degenerates to one of clock synchronization between the source and the destination. If you do RTT measurements, the transmitter and receiver are the same box, so the clocks are automatically synchronized. If you do one-way testing, you need to get clock synchronization between the source and dest nodes. If you need highly accurate measurements, then you might need something like GPS to help you synchronize (as opposed to NTP, which is great for basic date/time stuff, but wont help you much with microsecond resolution timing). Once you have the clock synchronization issue nailed, the code to do the measurement is only about half a page of C on both the source and test: take a timestamp, transmit a UDP packet out, receive it sometime later, and take another timestamp. -- Dave ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] latency tool
Hello, i have a question not directy related to Vyatta but more to networking. I am looking for a tool that is able to measure the (one-way) latency or delay. >From what i know ping or traceroute are only able to measure the RTT. Thanks Troopy __ Désirez vous une adresse éléctronique @suisse.com? Visitez la Suisse virtuelle sur http://www.suisse.com ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
