Re: which is the throughput of the 3560 in layer three?
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
To add a little to Arumugam's post . . .
Fabric bandwidths are often quoted duplex, so for example, a 3560's 32 Gbps fabric would support up to 16 gig duplex ports w/o oversubscription; more port bandwidth may need more fabric bandwidth.
Wire-rate Ethernet, for 64 byte size packets requires 1.488 Mpps per gig, so 38.7 Mpps supports 26 Gbps (non-duplex) or about 13 gig duplex ports. (NB: larger packets require a lower PPS, i.e. often same hardware's throughput increases with increased packet size.)
The later E and X series 3560s usually offer wire-rate perfomance for all ports.
Oh, and a 3560's L3 perforamance is often the same as it's L2 performance (if a packet's L3 done all by "hardware").
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...