[c-nsp] Cisco Switch Packet Buffering Matrix?
Skeeve Stevens
Skeeve at eintellego.net
Mon May 24 18:16:14 EDT 2010
If it requires an NDA or me having to talk to Cisco to find out this basic information, then I will drop Cisco off the list for consideration as you rightly point out, the others all provide this detail upfront.
How does Cisco expect us to sell them as a superior product against other vendors if the information is not available?
...Skeeve
--
Skeeve Stevens, CEO/Technical Director
eintellego Pty Ltd - The Networking Specialists
skeeve at eintellego.net / www.eintellego.net
Phone: 1300 753 383, Fax: (+612) 8572 9954
Cell +61 (0)414 753 383 / skype://skeeve
www.linkedin.com/in/skeeve ; facebook.com/eintellego
--
NOC, NOC, who's there?
> -----Original Message-----
> From: tkapela at gmail.com [mailto:tkapela at gmail.com]
> Sent: Tuesday, 25 May 2010 1:04 AM
> To: Arie Vayner (avayner); cisco-nsp-bounces at puck.nether.net; Skeeve
> Stevens; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Cisco Switch Packet Buffering Matrix?
>
> Imho, one should not encourage this nonsense by signing any such NDA.
> Brocade, juniper, extreme, and others publish such data about their
> products right on their darn respective websites, and without
> demonstrable harm.
>
> Knowing if something has a shared+per-port limit vs per-port-asic vs
> per-port mac/asic buffering arch is inconsequential, and represents no
> competitive disadvantage--unless the (advantage?) purpose is, in fact,
> to obscure details.
>
> As for getting this data from the hardware itself, poke around MQC and
> MLS qos show commands, and attempt to configure mls/mqc QoS policies.
> These features usually will indicate what their "maxiums" are on the
> platforms in question, while you're configuring them.
>
> -Tk
>
> -----Original Message-----
> From: "Arie Vayner (avayner)" <avayner at cisco.com>
> Date: Mon, 24 May 2010 16:47:38
> To: Skeeve Stevens<Skeeve at eintellego.net>; <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] Cisco Switch Packet Buffering Matrix?
>
> Skeeve,
>
> If you want to get this info in the "right" way, then the best approach
> would be to talk to your local Cisco account team...
> Some of the info may require NDA etc.
>
> On the same point, you may want to also look at 4948E and Nexus5000
> switches, which could give you better latency performance, which is
> important for storage-related applications.
>
> Arie
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Skeeve Stevens
> Sent: Monday, May 24, 2010 16:04
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] Cisco Switch Packet Buffering Matrix?
>
> I don't think this email got through the other day... I didn't see it
> appear.
>
> ...Skeeve
>
>
> From: Skeeve Stevens
> Sent: Tuesday, 11 May 2010 10:27 PM
> To: cisco-nsp at puck.nether.net
> Subject: Cisco Switch Packet Buffering Matrix?
>
> Hey all,
>
> I am doing some iSCSI implementations are the moment and are looking at
> which switch models are best for different iSCSI rollouts we're doing.
>
> I am wanting to know which 29xx and 35xx/37xx series switches have the
> following:
>
>
> - Size of packet buffering per model
>
> - If the PB is per port or shared
>
> - Is there one or more classes of PB classification
>
> - If the PB is shared, is it per switching module (i.e. 8/12
> port block) or across the entire switch
>
> - If the 10GB model is plugged in, does it have its own PB, or
> does it share the main boards?
>
> I looked in the Portable Product Sheet -
> http://www.cisco.com/web/partners/tools/quickreference/index.html but
> found nothing, and Google and Cisco.com proved useless. Maybe there is
> a reason for this, or my searchfoo is weak.
>
> ...Skeeve
>
>
> --
> Skeeve Stevens, CEO/Technical Director
> eintellego Pty Ltd - The Networking Specialists
> skeeve at eintellego.net / www.eintellego.net
> Phone: 1300 753 383, Fax: (+612) 8572 9954
> Cell +61 (0)414 753 383 / skype://skeeve
> www.linkedin.com/in/skeeve ; facebook.com/eintellego
> --
> Disclaimer: Limits of Liability and Disclaimer: This message is for the
> named person's use only. It may contain sensitive and private
> proprietary or legally privileged information. You must not, directly
> or
> indirectly, use, disclose, distribute, print, or copy any part of this
> message if you are not the intended recipient. eintellego Pty Ltd and
> each legal entity in the Tefilah Pty Ltd group of companies reserve the
> right to monitor all e-mail communications through its networks. Any
> views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised
> to state them to be the views of any such entity. Any reference to
> costs, fee quotations, contractual transactions and variations to
> contract terms is subject to separate confirmation in writing signed by
> an authorised representative of eintellego. Whilst all efforts are made
> to safeguard inbound and outbound e-mails, we cannot guarantee that
> attachments are!
> virus-free or compatible with your systems and do not accept any
> liability in respect of viruses or computer problems experienced.
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list