Search results for query: *

LACP works a little differently than normal MLT. In normal MLT you add ports and VLAN to the MLT definition directly. With LACP, the VLAN set is defined exclusively on the ports and the MLT gets nothing but a designation as a trunk and the “LACP-key” definition (along with “aggregation enabled”...

Just as a conclusion to this; After much study though many manuals I have determined that this catastrophic effect is, in fact, caused by a fundamental incompatibility between Cisco proprietary features (PVST+ and EtherChannel Guard) and the IEEE 802.1q VLAN trunking standard. Because 802.1q...

Just to update my own question; I have found a decent document from Cisco that discusses some of this. That document is here; http://www.cisco.com/en/US/tech/tk389/tk213/technologies_tech_note09186a008009448d.shtml According to this document, “Etherchannel Misconfiguration” is a proprietary...

We have had an odd situation with Cisco 3750 edge switches attached to a Nortel 8600 core. The Nortel is running 4.1 software. We have done this successfully for years using legacy EtherChannel on the Cisco and basic MLT/SMLT on the 8600. The thing is that for this to work properly, the...

We have a mixed-vendor environment with Cisco on the edge and Nortel in the core. We are experiencing issues with an Error-Disable link shutdown on one Cisco edge switch being propagated through to every-single Cisco edge switch in the shop. More details, diagrams and a theory are in the...

We had a similar issue recently. This happened to us when there was Nortel equipment in between two pieces of Cisco gear and I think it is caused by Cisco-proprietary communications. Cisco-1 had a VLAN on a trunk. Then there was a Nortel box. Then Cisco-2 was connected to the Nortel on the...