He works in trading.

_________________
http://blog.alwaysthenetwork.com

Good post, but I hate this comment.

_________________
http://blog.alwaysthenetwork.com

Yeah, the NDA stuff bleh. If 3k's are going to support netflow in the future, I would really really consider going that route in the future.

Sorry I have not been active on this topic, My focus has been shifted to our wireless mesh deploy. Im posting this link becuase its relevent and a good source (Greg Ferro) and looks to apply to my situation. Also I dont want to loose the link

http://searchnetworking.techtarget.com/ ... -get-fancy

_________________
http://blog.movingonesandzeros.net/

If I had to consider the use of a 3750 in the data center, I'd expand my options to non-Cisco vendors.

I noticed that he omitted Cisco's Catalyst 4900E/M series, which IMO, is a much better choice than a 3750.

_________________
http://networking.ventrefamily.com

I couldn't disagree with Greg more. Putting an access switch in your "Data Center" and hanging production traffic off of it isn't a solid idea. The 7k is young and the 6500 is about to collect a retirement check. Cool. With the 2T, Cisco has said it will support the platform for a further 8-10 years. Alright, fair enough. The 7k, regardless of its age, is a scalable product with the focus in the right place. It's not perfect right now, but it's also learning to do new things that customers keep asking for. Growing pains are to be associated with that.

_________________
And actually I appreciate MS certified people quite a bit. Not in the " I wish I did what you did" kinda way, but in a "I'm glad you're doing that so I don't have to" kind way. - Infinite ca. 2010

If you're building a new Data Center, and don't need service modules or SIP/SPA support, it's tough to pick a 6500 over a 7000.

_________________
http://networking.ventrefamily.com

Interesting article. We are currently debating collapsing services such as firewall and edge routing back into our 6500 core via service modules, and if we want to continue putting money into that platform. We are looking into modules such as ASA-SM and WiSM2 as part of this decision.

edit: typo

3750 stack as a core? Uggggh. Just dealt with that mess yesterday.

_________________
http://blog.alwaysthenetwork.com

Unfortunately we have tons of 3750s deployed throughout and so I will have to work with integrating them into the design. I’m pushing though from here out for 4048's for anything in the DC. Ill push the 3750s as far to the access edge as possible.

_________________
http://blog.movingonesandzeros.net/

If you're looking for a use - ILO/RIB/RLO connectivity, where the very shallow buffers and other drawbacks are a less of an issue, would be my first choice.

_________________
http://networking.ventrefamily.com

Without a compelling technical reason to change I hope we stick with the 6509s in our core for our upcoming hardware refresh. Drop in some new sups if we have to but I hate to get rid of a rock-solid reliable core just to have something new for the sake of having something new.

We really don't have big bandwidth requirements anyway since most of our traffic is transactional.

3750's are like so EOL

_________________
"If you're good at anticipating the human mind. It leaves nothing to chance."
-Jigsaw

Not the V2's or the 3750-X's. Expect to see them in the access layer and also in the SMB "core", which I believe the article is hinting at, but it's debatable if 13 server racks is SMB.

When considering from Cisco, the 3750X stack can be a good choice at the access/distribution layer when the customer doesn't need the extra features and functionality of a 4900. At a cost/port basis it can make a lot of sense, especially at places where a 4900 would be an overkill.

_________________
"It can also be argued that DNA is nothing more than a program designed to preserve itself. Life has become more complex in the overwhelming sea of information. And life, when organized into species, relies upon genes to be its memory system."

For user access, they're fine. For DC access, they suck.

_________________
http://blog.alwaysthenetwork.com

Is this the span you are referring to? http://www.cisco.com/en/US/docs/switche ... l#wp280122

Also the N5k does support VTP, it just doesn't support being a NTP 'master' as there is no hardware clock. It can peer with anything though.

Just to update where Im at...

Im thinking I dont need a 7K for my enviroment. Way to overkill and I will most likley use my firewalls for routing since its crucial VLAN traffic pass through a firewall for inspection before going to another VLAN.

Honestly I have really not seen much of a need for the 7K outside of core routing and layer 3 functionality. Am I missing something?

_________________
http://blog.movingonesandzeros.net/

It's a data center switch right now and could be a used as a core switch in the future. Fabric Path is amazing; unifying the data center fabric is what it really does best; today.

_________________
And actually I appreciate MS certified people quite a bit. Not in the " I wish I did what you did" kinda way, but in a "I'm glad you're doing that so I don't have to" kind way. - Infinite ca. 2010

This entire conversation just shows how little experience I have and how unlikely I am to land a job in this field.... you guys are speaking Greek to me lol.

_________________
Regards,

Steven King
San Diego Cisco User Group - http://www.sdcug.com
"The only time something is impossible is when you think it is." - Kevin Corbin, CCIE #11577