Re: [c-nsp] QoS on 837 using PPPoE

2009-07-08 Thread Dean Smith
In addition when working on QoS on PPPoA we found... With the SP on the physical vbr-nrt is indeed required. But that breaks the automatic tracking of the PVC size to the negotiated upstream rate on rate adaptive DSL. So we had to use TCL to track the DSL speed and change the VBR-NRT size to m

Re: [c-nsp] IOS XR BFD

2009-07-08 Thread Ivan Pepelnjak
I've been planning to document the shortcomings of "Fast Peering Session Deactivation" for a long time; thanks for the nudge. Summary: following an interface loss (on the BGP router) in an OSPF or IS-IS network, you might lose the route toward your BGP neighbor until SPF is run, resulting in BGP s

[c-nsp] round-trip differences towards google

2009-07-08 Thread Rens
Hi all, I'm having some difficulties understand some round-trip difference on the same router just by changing the source interface: Pings are done towards a resolved IP of www.google.be ping 209.85.227.103 repeat 50 Type escape sequence to abort. Sending 50, 100-byte ICMP Echos to

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread David Freedman
Rens wrote: > Hi all, > > > > I'm having some difficulties understand some round-trip difference on the > same router just by changing the source interface: > > your source address will of course become the destination address which google's equipment will want to send the ICMP replies back

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread Rens
I expect the return routing to be the same as for all my IP addresses since they are all advertised in the same way. I guess google doesn't handle them the same way? -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of David Fr

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread E. Versaevel
Is there a difference when you traceroute with different source ip's ? Rens schreef: > I expect the return routing to be the same as for all my IP addresses since > they are all advertised in the same way. > > I guess google doesn't handle them the same way? > > -Original Message- > From

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread Rens
They both leave my network via the same IP transit but then afterwards some hops are different... -Original Message- From: E. Versaevel [mailto:e...@infopact.nl] Sent: mercredi 8 juillet 2009 12:45 To: Rens Cc: 'David Freedman'; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] round-trip di

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread Irena Nikolova
Which would explain the differences between the round-trip times. You can see the latency value on every hop when you do traceroute, where does it increase? On Wed, Jul 8, 2009 at 2:38 PM, Rens wrote: > They both leave my network via the same IP transit but then afterwards some > hops are differ

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread Rens
When it goes from my IP transit provider to google it increases. _ From: Irena Nikolova [mailto:ire...@gmail.com] Sent: mercredi 8 juillet 2009 15:04 To: Rens Cc: E. Versaevel; David Freedman; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] round-trip differences towards google Whi

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread Rodney Dunn
If it's Cisco in the middle those packets in an equal cost routing scenario, which is typical in the core for redundancy, will most likely diverge to a different path due to the src/dst ip hashing. The traceroute would show you if the paths diverge in the forward direction but not in the reverse d

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread Brian Turnbow
As google is not a single server but a cloud of clusters of servers you are getting routed by a "load balancer" of some sort. In a nutshell this is what happens, the IP address 209.85.227.103 is a virtual address that gets sent to various real servers. As the source address changes the load ba

Re: [c-nsp] round-trip differences towards google

2009-07-08 Thread tkacprzynski
This relates to google, does anyone know how they do their global DNS resolution? I am having few issues resolving to the closest google datacenter webserver (i.e. Sydney users resolved to US servers [verified by traceroute])? Thanks -Original Message- From: cisco-nsp-boun...@puck.net

[c-nsp] SAMI Module

2009-07-08 Thread J Springer
I am interested in feedback regarding the SAMI module for Q-in-Q termination on the 7600 platform. The preference is to avoid the cost of the ES+ card as other configuration options are not needed at this time. Thanks in advance. ___ cisco-nsp mailin

[c-nsp] Multi-site single AS architecture

2009-07-08 Thread Andy Ashley
Hi, Apologies for this long post, I am hoping to explain in full: (there was a similar thread recently but Im looking for slighly different info) Background: We currently have a primary site which has two 7206 border routers, each has an uplink and ebgp session over that into our primary tran

[c-nsp] Extended demarc

2009-07-08 Thread james edwards
What is a real word limit on how far you can extend the demarc ? This is on Cat5e cable. I get wildly different figures from Google. Thanks, -- James H. Edwards Senior Network Systems Administrator Judicial Information Division jedwa...@nmcourts.gov _

Re: [c-nsp] Extended demarc

2009-07-08 Thread Walter Keen
You're supposed to be able to go 100meters(roughly 330ft) with ethernet over Cat5e, but the longest run we've had to date is approximately 260ft with no issues going through a shared vault space very close to power lines and have not yet seen any poor performance due to the length or interferen

Re: [c-nsp] Extended demarc

2009-07-08 Thread james edwards
On Wed, Jul 8, 2009 at 3:47 PM, Walter Keen wrote: > You're supposed to be able to go 100meters(roughly 330ft) with ethernet > over Cat5e, but the longest run we've had to date is approximately 260ft > with no issues going through a shared vault space very close to power lines > and have not yet s

Re: [c-nsp] Extended demarc

2009-07-08 Thread Paul G. Timmins
If you're asking about T1s, we've extended a demarc 23 stories over Category 0 building pair from the 70s or 80s and the circuit has run flawlessly. You have to test the cables when they're that old due to building sway causing shorts and things like that, but it works. T1s are designed to go sever

Re: [c-nsp] Extended demarc

2009-07-08 Thread Jay Hennigan
james edwards wrote: What is a real word limit on how far you can extend the demarc ? This is on Cat5e cable. I get wildly different figures from Google. What underlying protocol? Ethernet? T1? ADSL? BRI? That's why the figures are wildly different. :-) -- Jay Hennigan - CCIE #7880 - Net

Re: [c-nsp] Extended demarc

2009-07-08 Thread Tim Jackson
655 ft over 22awg, but probably just as fine over 24awg in cat5, too... You'll need to have the smartjack adjusted to a longer line build out, as well as your CSU. -- Tim On Wed, Jul 8, 2009 at 4:40 PM, james edwards wrote: > What is a real word limit on how far you can extend the demarc ? This

Re: [c-nsp] Baseline CoPP policies?

2009-07-08 Thread Justin Shore
One thing that the documentation always lacks is sufficient info on handling IS-IS with CoPP. The inability of IOS to match IS-IS traffic without using class-default is a major problem. Of all the people that would need CoPP (people with publicly exposed routers like SPs) one would think that

Re: [c-nsp] Baseline CoPP policies?

2009-07-08 Thread Siva Valliappan
the platform team should be able to work with the NSSTG QoS team to get this to happen. you might want to direct your account team at your platform team. they in turn can work with the QoS team to get the necessary MQC extensions. regards .siva On Wed, 8 Jul 2009, Justin Shore wrote: One thin

Re: [c-nsp] Extended demarc

2009-07-08 Thread Doug McIntyre
On Wed, Jul 08, 2009 at 03:49:28PM -0600, james edwards wrote: > On Wed, Jul 8, 2009 at 3:47 PM, Walter Keen > wrote: > > > You're supposed to be able to go 100meters(roughly 330ft) with ethernet > > over Cat5e, but the longest run we've had to date is approximately 260ft > > with no issues going

Re: [c-nsp] Multi-site single AS architecture

2009-07-08 Thread David Hughes
Hi So that you don't pollute the global table all the time you could use a conditional advertisement at the remote site and only advertise the more specific routes if you don't see your main aggregate in your table (i.e. the aggregate would be there via iBGP if the metro link was up).

Re: [c-nsp] Extended demarc

2009-07-08 Thread Roy
james edwards wrote: On Wed, Jul 8, 2009 at 3:47 PM, Walter Keen wrote: You're supposed to be able to go 100meters(roughly 330ft) with ethernet over Cat5e, but the longest run we've had to date is approximately 260ft with no issues going through a shared vault space very close to power lines

Re: [c-nsp] Extended demarc

2009-07-08 Thread Jon Lewis
On Wed, 8 Jul 2009, Paul G. Timmins wrote: Ethernet IIRC can only go 300 meters or something like that, regardless of how fancy your cable is due to timing issues and the speed of light. But I don't extend Ethernet very often so I'm not an expert in that part. AFAIK, the length limit for ether

Re: [c-nsp] Extended demarc

2009-07-08 Thread Clayton Zekelman
Typically DSX-1 signal outputs from the SIJ are limited to 655 feet. - Original Message --- Subject: Re: [c-nsp] Extended demarc From: Roy Date: Wed, 08 Jul 2009 15:34:16 -0700 To: Cc: cisco-nsp@puck.nether.net > >You can go several thousand feet from the sma

Re: [c-nsp] Baseline CoPP policies?

2009-07-08 Thread Daniel Dib
Information from ESET NOD32 Antivirus, version of virus signature database 4225 (20090708) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net

Re: [c-nsp] Multi-site single AS architecture

2009-07-08 Thread Ivan Pepelnjak
Almost identical setup has been discussed on Nanog mailing list in the beginning of June. Search the archives. XCONNECT probably won't work over the Internet without MPLS/GRE/IP setup and then you'll hit the MTU issues. Ivan http://www.ioshints.info/about http://blog.ioshints.info/ > -Orig