Lacp trunk enhancements, Layer 2 failover enhancements, Acl precedence enhancement – Blade ICE BLADEOS BMD00098 User Manual

Page 14: Forwarding database enhancements

Advertising
background image

BLADE OS 5.1 Release Notes

14

BMD00098, December 2009

LACP Trunk Enhancements

BLADEOS 5.1 now supports up to eight links in each LACP Link Aggregation Group (LAG).

Layer 2 Failover Enhancements

BLADEOS 5.1 includes multiple enhancements to the Layer 2 Failover feature to support advanced
NIC teaming:

In addition to the automatic monitoring triggers for trunk links, the switch software now
supports new manual monitoring triggers. This allows you to define a list of ports and/or static
or dynamic trunks to disable when a link failure thresdhold is reached on set of trigger ports
and/or static or dynamic trunks.

Up to two LACP keys can be used for each failover trigger. Previously, only one per trigger was
supported.

ACL Precedence Enhancement

With BLADEOS 5.1, the implementation of Access Control Lists (ACLs) has been standardized to
use ascending order of precedence.

ACLs that are assigned to a port are now processed in numeric sequence, based on ACL number.
Lower-numbered ACLs take precedence over higher-numbered ACLs within each precedence
group. For example, ACL 1 (if assigned to the port) is evaluated first and has top priority within
precedence group 1.

When upgrading from an earlier version of BLADEOS, the ACLs are automatically renumbered to
maintain prior function within the new order of precedence.

Forwarding Database Enhancements

Configuration of the Forwarding Database (FDB) aging feature has been simplified. Because FDB
aging required the same value configured in all Spanning Tree Groups (STGs), the per-STG aging
parameters have been replaced with a single, global configuration command:

# /cfg/l2/stg

<STG number>

/brg/aging

<value>

(old per-STG command)

-replaced by-

# /cfg/l2/fdb/aging

<value>

(new global command)

Advertising