Call for Presentations: NANOG 57 in Orlando, FL

NANOG Community, I know that we all just left Dallas after NANOG 56, but the NANOG Program Committee is already hard at work preparing for NANOG 57 in Orlando! The North American Network Operators' Group (NANOG) will hold their 57th meeting in Orlando, FL on February 4th through the 6th. Of

Looking for a outside plant contact Zayo/AboveNet Manhattan

We're looking at some emergency office space in Manhattan and we identified an AboveNet/Zayo fiber panel in the space. Would like to see if someone could confirm if it is viable. Anyone from Abovenet lurking? Thanks, -cjp

route-views.eqix DC METRO AREA IX RENUMBERING

We have the renumber interface enabled and configured for any known peers to make the transition for the RouteViews EQUINIX ASHBURN route collector. OLD PEERING ADDRESS: 206.223.115.142 NEW PEERING ADDRESS: 206.126.236.142 Current v4 peer list looks like below. If you need to check, telnet to r

Re: MTU issues s0.wp.com

Same here too...i don't know if having a direct peering with Edgecast will solve the issue. -- Tassos Brian Keefer wrote on 8/11/2012 05:08: > On Nov 6, 2012, at 4:33 AM, Seth Mos wrote: > >> Hi, >> >> Since about a week or so it's become impossible to reach wp.com content over >> IPv6. >> >> I

RE: Sandy seen costing telco, cable hundreds of millions of dollars

Agreed... I live in the same general vicinity in NJ as Alex and ATT service was pretty much non-existent anywhere there was no power from what I experienced. I have friends on Verizon to whom I've spoken and they didn't seem to notice as large of an impact at all on their cellular service. -Vin

Whats so difficult about ISSU

Hello, We've been hearing about ISSU for so many years and i didnt hear that any vendor was able to achieve it yet. What is the technical reason behind that? If i understand correctly, the way it will be done would be simply to have extra ASICs/HW to be able to build dual circuits accessing the

Re: Whats so difficult about ISSU

Cisco Nexus platform does it pretty well so they have achieved it. Zaid On Nov 8, 2012, at 3:22 PM, Kasper Adel wrote: > Hello, > > We've been hearing about ISSU for so many years and i didnt hear that any > vendor was able to achieve it yet. > > What is the technical reason behind that? >

Re: Whats so difficult about ISSU

Juniper also offers it on the EX virtual switching platform. Works if you have the correct version of JunOS. On Thu, Nov 8, 2012 at 3:38 PM, Zaid Ali wrote: > Cisco Nexus platform does it pretty well so they have achieved it. > > Zaid > > On Nov 8, 2012, at 3:22 PM, Kasper Adel wrote: > > > Hel

Re: Whats so difficult about ISSU

The major vendors have figured it out for the most part by moving to stateful synchronization between control plane modules and implementing non-stop routing. ALU has supported ISSU on minor releases for many years and just added support for major releases. The Cisco Nexus ISSU works well,

Re: Whats so difficult about ISSU

What i was asking is full ISSU, even with micro code. I assume between Major release there will be microcode upgrade most of the time. On Fri, Nov 9, 2012 at 2:48 AM, Phil wrote: > The major vendors have figured it out for the most part by moving to > stateful synchronization between control pl

Re: Whats so difficult about ISSU

I have executed successfully on the MX960 with no issues.. EX on the other hand, really depends on your version of JunOS. On Thu, Nov 8, 2012 at 4:19 PM, Alex wrote: > http://www.juniper.net/**techpubs/en_US/junos/topics/** > concept/issu-oveview.html

Re: Whats so difficult about ISSU

I have performed micro code upgrades using ISSU on the Juniper platform. On Thu, Nov 8, 2012 at 4:52 PM, Kasper Adel wrote: > What i was asking is full ISSU, even with micro code. I assume between > Major release there will be microcode upgrade most of the time. > > > On Fri, Nov 9, 2012 at 2:48

Re: Whats so difficult about ISSU

Does that mean they are the only vendor capable of doing this today? I am interested in the technology behind this if this is something public, any ideas? Thx On Friday, November 9, 2012, Kenneth McRae wrote: > I have performed micro code upgrades using ISSU on the Juniper platform. > > On Thu,

Re: Whats so difficult about ISSU

I know some people here have mentioned good experiences with ISSU on Nexus. I don't doubt that it usually works right, but in my latest experience with upgrading NX-OS on dual-SUP'ed 7k's, it was "hitless" if, by "hitless", you mean ~20% packet loss while troubleshooting with TAC before we found

Re: Whats so difficult about ISSU

Heh you will find vendors avoid using the term hitless. I can't think of any router which supports ISSU that is truly hitless. The ASR9K ISSU states it will sustain less than 6 seconds of loss... ISSU is still rife with caveats and incompatibilities as well if you are doing more advanced thin

Re: Whats so difficult about ISSU

On Thu, 8 Nov 2012, Phil wrote: The major vendors have figured it out for the most part by moving to stateful synchronization between control plane modules and implementing non-stop routing. NSR isn't ISSU. ISSU contains the wording "in service". 6 seconds of outage isn't "in service". 0.5

Re: Whats so difficult about ISSU

On Thu, Nov 8, 2012 at 8:13 PM, Mikael Abrahamsson wrote: > On Thu, 8 Nov 2012, Phil wrote: > >> The major vendors have figured it out for the most part by moving to >> stateful synchronization between control plane modules and implementing >> non-stop routing. > > > NSR isn't ISSU. > > ISSU conta

Re: Whats so difficult about ISSU

In vendor-speak ISSU usually refers to 'minimal traffic impact' upgrade. Definition of minimal varies from vendor to vendor and from upgrade to upgrade, depending of which parts of the code need to be upgraded. In general, traffic loss during ISSU is an order of magnitude less than by reloading the

Re: Whats so difficult about ISSU

On (2012-11-09 01:22 +0200), Kasper Adel wrote: > We've been hearing about ISSU for so many years and i didnt hear that any > vendor was able to achieve it yet. > > What is the technical reason behind that? I'd say generally code quality in routers is really really bad, I'm not sure why this is.