reuben-cisco-nsp at reub
May 19, 2012, 10:57 PM
Post #21 of 40
Yes - the 5548 does routing. We have 2x 5548UP's with the Layer 3
daughtercard in our small corporate DC.
It does routing, yes, but you need to be aware of caveats around the
feature. I suppose you could say that about any Cisco switch, but bear
in mind that NX-OS is aimed and targeted at the Data Centre market more
so than the Service Provider market so you you'll probably find it far
more feature rich in DC features such as Fibre Channel, than SP features
like EVCs (which btw it doesn't support).
You'll probably also find that there aren't a lot of choice of software
releases of code since the daughter card was introduced (and there are
now two variants of this, the second hardware revision has more onboard
resources). The quality of the code is reasonable but there aren't many
to choose from, and well, I'd be interested to know of anyone who has
really hammered the BGP code to the limits ;)
It's also nice to be able to go from 1G to 10G by just upgrading SFP's.
We've had to leave a 3560 in production to do IPv6 routing and policy
routing as it just can't be presently done on the Nexus 5000, and
there's no word when IPv6 routing will be supported on it, if ever.
On 20/05/2012 3:25 PM, Alexander Lim wrote:
> I think Nexus 5500 series support L3.
> Alexander Lim
> On May 20, 2012, at 12:54 PM, Skeeve Stevens <skeeve+cisconsp [at] eintellego> wrote:
>> Feature / Nexus 5010 / 3750X
>> VLANs / 507 / 1005
>> MAC / 16k / 4k-12k
>> L3 / N / Y
>> vPC / Y / N
>> Nexus 5010 - less VLANs, no Layer 3, vPC
>> 3750X - more VLAN, Layer 3, no vPC
>> *Skeeve Stevens, CEO*
>> eintellego Pty Ltd
>> skeeve [at] eintellego ; www.eintellego.net <http://www.eintellego.net.au>
>> Phone: 1300 753 383 ; Fax: (+612) 8572 9954
>> Cell +61 (0)414 753 383 ; skype://skeeve
>> twitter.com/networkceoau ; www.linkedin.com/in/skeeve
>> PO Box 7726, Baulkham Hills, NSW 1755 Australia
>> The Experts Who The Experts Call
>> Juniper - Cisco â€“ IBM
>> On Sun, May 20, 2012 at 10:03 AM, scott owens <scottowens12 [at] gmail>wrote:
>>> How about Nexus 5010s.
>>> I think they bundle them for less than 2 x 3750X .
>>> We have both but the 3750s are used where we needed L2/L3, the 5Ks for just
>>> L2 up to VSS or 7Ks.
>>> you can boot them separately and they do LACP / Etherchannel just fine.
>>>> 2. Stacking 3750X vs diverse 4948E (David Coulson)
>>>> Message: 2
>>>> Date: Fri, 18 May 2012 14:55:57 -0400
>>>> From: David Coulson <david [at] davidcoulson>
>>>> To: cisco-nsp [at] puck
>>>> Subject: [c-nsp] Stacking 3750X vs diverse 4948E
>>>> Message-ID: <4FB69B3D.3060802 [at] davidcoulson>
>>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>> In a datacenter environment, we typically deploy 4948 top-of-rack
>>>> switches with L2 uplinks to our 6500 core - Systems get connections into
>>>> two different switches and rely on OS NIC bonding (mostly Linux) to
>>>> support switch failures. Switches running STP and in the last four years
>>>> we've had no issues with this design (including failures of systems
>>>> connected to diverse switches).
>>>> A new proposed configuration utilizes stacked 3750X switches, where
>>>> servers would be connected to multiple switches within the same stack. I
>>>> have next to no experience in the low-end switches that do stacking, but
>>>> from a general risk management perspective, it seems like a many eggs
>>>> and single basket configuration.
>>>> Does anyone have any solid experience with 3750X switches, or stacking
>>>> in a datacenter in general? I've seen plenty of stacks for
>>>> closets/end-users, but I don't see many in a top-of-rack config. Is
>>>> Cisco stacking typically 'reliable', in that when a switch fails it will
>>>> leave the remainder of the stack functional? What about a software
>>>> issue? Does the whole stack crap out and reload, or does the master just
>>>> fail and a new one get elected?
>>>> I realize it's a pretty broad question, but it boils down to - Is a
>>>> stacked switch config significantly less reliable/resilient/available
>>>> than two TOR switches?
>>> cisco-nsp mailing list cisco-nsp [at] puck
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>> cisco-nsp mailing list cisco-nsp [at] puck
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
> cisco-nsp mailing list cisco-nsp [at] puck
> archive at http://puck.nether.net/pipermail/cisco-nsp/
cisco-nsp mailing list cisco-nsp [at] puck
archive at http://puck.nether.net/pipermail/cisco-nsp/