twork to IPv6 for no real return on investment."
Stephen Kratzer
Network Engineer
CTI Networks, Inc.
On Thursday 11 June 2009 09:46:45 Justin Shore wrote:
> I'm in search of some information about Cogent, it's past, present and
> future. I've heard bits and pieces about Cogent
Should have said "And, they have no plans to deploy IPv6 in the immediate
future."
On Thursday 11 June 2009 10:33:25 Stephen Kratzer wrote:
> We've only recently started using Cogent transit, but it's been stable
> since its introduction 6 months ago. Turn-up was
ose statements then
> they should justify them with reputable evidence. I would be extremely
> surprised if Cogent engineering isn't working on a IPv6 plan or doesn't
> have one already in place.
>
> Bret
>
> On Thu, 2009-06-11 at 10:37 -0400, Steve Bertrand wrote:
&g
> On Thu, 2009-06-11 at 11:03 -0400, Stephen Kratzer wrote:
> > Perhaps you missed my quote:
> >
> > "Cogent's official stance on IPv6 is that we will deploy IPv6 when it
> > becomes a commercial necessity. We have tested IPv6 and we have our plan
> > for r
From your description, it doesn't sound like you're distributing subnets
across datacenters, and it's difficult to tell how, why, or if you're sharing
provider routes between your routers.
Stephen Kratzer
Network Engineer
CTI Networks, Inc.
On Tuesday 30 June 2009 09:54:29 neal
ple as possible but no simpler"
without good technical and (hence) business cases.
Stephen Kratzer
Network Engineer
CTI Networks, Inc.
On Wednesday 08 July 2009 06:01:20 Andre Oppermann wrote:
> A few time already I've wished for a fully standardized and vendor
> interoperable way
Use a /30 across the circuit and do multihop BGP using other IPs.
On Friday 10 July 2009 13:48:15 Jay Nakamura wrote:
> We are getting an Ethernet DIA circuit from AT&T but they insist that
> they can't BGP peer with 2 routers on our side. The WAN circuit can
> only have /30 they say. Has anyone
On Monday 12 January 2009 01:11:50 Aaron Imbrock wrote:
> Stop
in the name of love
got it
working. We want to know HOW you got it working. What protocols and policies
were implemented on what hardware for what kind of user base?
Stephen Kratzer
Network Engineer
CTI Networks, Inc.
On Friday 06 February 2009 08:51:04 Jack Bates wrote:
> Joe Loiacono wrote:
> > Indeed it does. And don't forget that the most basic data object in the
> > routing table, the address itself, is 4 times as big.
>
> Let's also not forget, that many organizations went from multiple
> allocations to a
nectivity is
required to establish and maintain adjacencies. However, layer 3 failures
aren't detected for, at most, 15 seconds by default on an Ethernet link.
Stephen Kratzer
Network Engineer
CTI Networks, Inc.
Be sure to differentiate between unicast and multicast reachability. Try 'ping
224.0.0.10'.
Stephen Kratzer
On Tuesday 23 September 2008 12:25:34 Philip Lavine wrote:
> What is really bizarre is that I am down for minutes not seconds and the
> timers never fire. If I don't
On Tuesday 23 September 2008 13:46:02 Joseph Doran wrote:
> EIGRP timers over WAN media default to 60 seconds. Neighborship will not
> expire for up to 180 seconds. To verify your EIGRP neighborship do a "show
> ip eigrp neighbor"
>
>
> Message: 6
> Date: Tue, 23 Sep 2008 09:25:34 -0700 (PDT)
> Fro
13 matches
Mail list logo
