Confused about forwarding rate spec of cisco/nortel/3com
I am currently comparing the specs of 3com,cisco,nortel for a new requirement ( Layer 2 edge switches)
These are the forwarding rates of these models obtained form website and brouchures.
3com Superstack 4200 G = 101.2 Mpps
Nortel 425-24/48 T = 10.2 Mpps
Catalyst 2960G-48 = 38.0 Mpps
I think the units are in million Packets per second.
I am surprised that 3com has better forwading rate than comparable cisco and nortel model .So is there a mistake in the way i am reading the specs? Also i know that cisco uses default modified cut-through forwarding method taking in first 64k of frame and then forwarding. So could the reason be they have a lower forwarding rate listed being that 3com is listing their fast forward method spec. Same goes more Nortel who got it way lower than the rest. I know they make switches for ISPs but why the low specs.
Re: Confused about forwarding rate spec of cisco/nortel/3com
The Forwarding rate based on 64-byte packets for Catalyst 2960G-48TC is 39.0 Mpps, where Mpps stands for Millions of Packets Per Second.
Adaptive Cut-Through mode is the default switching mode in Catalyst 2600 series switches. The Catalyst 2600 operates in cut-through mode until it reaches the error rate high threshold set in the Switching Mode. Then, the Catalyst 2600 changes to store-and-forward mode. It will change back to cut-through mode when it falls below the error rate low threshold.
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 ...