Link Aggregation Control Protocol

BLADE OS 5.1 Release Notes

If a static trunk on a GbESM is connected to another GbESM with LACP configured (but no active LACP trunk), the /info/l2/trunk command might erroneously report the static trunk as forwarding.

Since LACP trunks use LACPDU packet to maintain trunking with the partner, there is a possibility for those packets to be dropped from an extremely busy trunk. If this happens, some links in the LACP trunk might be removed, then aggregated back to the trunk if an LACPDU is received. To avoid this unstable LACP trunk link, you can add more links to the trunk to increase the bandwidth, or use regular static trunk if there are no more links available.

Linking at 10/100Mb

When the link speed for an external connection is forced (i.e. no Auto-Negotiation) to 100 Mbps and then changed to 10 Mbps, if the external device is changed first, the external device may erroneously report the link as DOWN even after the GbESM is changed to 10 Mbps.

Solution: At the external device, disconnect and reconnect the cable.

Static Mrouter

If a port has a static multicast router (Mrouter) configured, and you move the port to a different VLAN, the static Mrouter appears in the /info/l3/igmp/mrouter/dump output for the original VLAN.

Solution: When you move the port to a new VLAN, remove the static Mrouter from the port, and add it again.

QoS Metering

Traffic may exceed the configured maximum burst size of the ACL meter

(/cfg/port <x>/aclqos/meter/mbsize) by one packet, with that packet remaining In-Profile. Once the ACL meter has been exceeded, additional burst packets fall Out-of-Profile.

QoS and Trunking

When you assign an ACL (or ACL Group) to one port in a trunk, BLADEOS does not automatically assign the ACL to other ports in the trunk, and it does not prompt you to assign the ACL to other ports in the trunk.

Solution: Manually assign each ACL or ACL Group to all ports in a trunk.

24	BMD00098, December 2009