nanog mailing list archives

Re: Nexus 7K usage w/VDC, vPC - anybody?


From: Ryan Hughes <rshughes () gmail com>
Date: Sun, 19 Jul 2009 13:37:53 -0400

It was an early implementation of Nexus for an enterprise customer for their
existing data center. We did the implementation of the Nexus very early on
(January) to aggregate HP bladecenter 10G server access. Honestly, N5K's
would have made more sense at the end of the day but that wasn't the initial
design when they bought the gear. Lots of layer8 issues prevented us from
making the Nexus the ASBR/ABR for the core - most specifically was training
for the NOC. Llack of service modules didn't win any favoritism either
(ACE/NAM).

Ryan
On Sun, Jul 19, 2009 at 1:23 PM, Stefan <netfortius () gmail com> wrote:

Thank you, Ryan, for the info. Interesting your choice of 6500s at the
core. I would have expected that layer to be the first "recipient" of
N7Ks, then slowly moving into aggr., access, .... You are not running
some services modules in the core chassis, are you?


On 7/18/09, Ryan Hughes <rshughes () gmail com> wrote:
Currenet 4.1 is a little flaky for vPC; running a set up with 4.1.5ES
(TAC
release) - recommendation is to wait and go with 4.2.1 when that
releases.
Haven't had any issues with the VDC features - still using 6500 in the
core
for the time being. Most installs I've seen have resulted in some TAC
case
or another. I've had pretty good results with the N5K platform as whole.

Ryan

On Fri, Jul 17, 2009 at 5:59 PM, Stefan <netfortius () gmail com> wrote:

I'd be interested to know if anybody has been using the Cisco N7K
platform, especially in vertical consolidation mode (aggr and core as
VDCs, and dual Nexus VPC-ed together)? Any comments on this system,
even outsde this narrow scope of my previous question? Anybody using
these as server access systems, in DCs?

Thank you,


--
Sent from my mobile device

***Stefan Mititelu
http://twitter.com/netfortius
http://www.linkedin.com/in/netfortius




--
Sent from my mobile device

***Stefan Mititelu
http://twitter.com/netfortius
http://www.linkedin.com/in/netfortius



Current thread: