Several enhancements were made to the layer 2 loop prevention mechanism, the original STP (IEEE 802.1d). Examples are multiple spanning tree, rapid spanning tree.
One of the major drawbacks of spanning tree is - it prohibits the use of multiple paths in layer 2. After BPDU exchange, STP will put redundant ports in blocking mode.
Earlier solutions to disable SPT and to take advantage of multiple layer 2 paths were the use of PortChannel - FEC or GEC (Proprietary), PagP (Proprietary) and LACP (802.3ad, later 802.3AX).
Biggest limitation of PortChannel is that it can only be used between two adjacent devices.
Cisco came up with vPC (virtual PortChannel) in its Nexus platform (NX-OS) which will let multiple active layer 2 paths exist. See here for detail explanation.
vPC is Cisco solution before a standard based technology is agreed upon. That technology is in work in progress for a few years (since 2007 I think) and it has a weird sounding acronym. It is IETF's TRILL - Transparent Interconnection of Lots of Links. TRILL uses IS-IS (yes that L3 routing protocol) to manage L2MP management traffic.
L2MP - Layer 2 MultiPath
Wednesday, March 4, 2009
Wednesday, February 11, 2009
ASICs
- "show asic-version slot x" will show the count of ASICs like Rohini (Port ASIC), Janus (Fabric interface)
Took it from here.
There is no oversubscription built in to the Rohini-Janus interconnect. The oversubscription on these cards is from janus to the fabric. Also intra Janus there is a 26Mpps limitation.
To elaborate, 6748-GETX is as you say, 1-12, 13-24, etc. The port mapping for the fiber version of 6748, and for 6724, is a bit different, it is even & odd (so eg, 1-23 odd, 2-24 even, etc) but yes it is 12 ports per rohini in all cases.
WRT oversubscription, again, the oversub is at the fabric level, not the port level as you would see on some 4500 series cards & on the 6500 series 6148-GETX etc.
Took it from here.
There is no oversubscription built in to the Rohini-Janus interconnect. The oversubscription on these cards is from janus to the fabric. Also intra Janus there is a 26Mpps limitation.
To elaborate, 6748-GETX is as you say, 1-12, 13-24, etc. The port mapping for the fiber version of 6748, and for 6724, is a bit different, it is even & odd (so eg, 1-23 odd, 2-24 even, etc) but yes it is 12 ports per rohini in all cases.
WRT oversubscription, again, the oversub is at the fabric level, not the port level as you would see on some 4500 series cards & on the 6500 series 6148-GETX etc.
Notes on 6708
- There are 2 flavors - 3C and 3CXL.
- 6704 has 16MB per port buffer, 6708 has 200MB per port buffer
- 8 x 10G ports with 40Gbps (2 x 20Gbps) to Fabric (2:1 fabric oversubscription ?)
- 64Gbps local switching (1.25:1 local oversubscription ?)
- 48Mpps switching
- "no hw-module slot x oversubscription" will turn off oversubscription, effectively shutting down port 3,4,7 and 8.
- in non-oversubscribed mode, port 3,4,7 and 8 cannot be unshut and "show interface" output will be "disabled for performance" instead of normal admin disable
- "mac-address-table synchronize" is enabled by default (and fix PFC/DFC MAC synchronization problem )
- 6704 has 16MB per port buffer, 6708 has 200MB per port buffer
- 8 x 10G ports with 40Gbps (2 x 20Gbps) to Fabric (2:1 fabric oversubscription ?)
- 64Gbps local switching (1.25:1 local oversubscription ?)
- 48Mpps switching
- "no hw-module slot x oversubscription" will turn off oversubscription, effectively shutting down port 3,4,7 and 8.
- in non-oversubscribed mode, port 3,4,7 and 8 cannot be unshut and "show interface" output will be "disabled for performance" instead of normal admin disable
- "mac-address-table synchronize" is enabled by default (and fix PFC/DFC MAC synchronization problem )
Subscribe to:
Posts (Atom)
