Bfd Over Lag Links; Mixed Port-Speed Lag Support - Alcatel-Lucent 7750 Configuration Manual

BFD over LAG Links

The routersupports the application of BFD to monitor individual LAG link members to speed up
the detection of link failures. When BFD is associated with an Ethernet LAG, BFD sessions are
setup over each link member, and are referred to as micro-BFD sessions. A link is not operational
in the associated LAG until the associated micro-BFD session is fully established. In addition, the
link member is removed from the operational state in the LAG if the BFD session fails.
When configuring the local and remote IP address for the BFD over LAG link sessions, the local-
ip parameter should always match an IP address associated with the IP interface to which this
LAG is bound. In addition, the remote-ip parameter should match an IP address on the remote
system and should also be in the same subnet as the local-ip address. If the LAG bundle is re-
associated with a different IP interface, the local-ip and remote-ip parameters should be modified
to match the new IP subnet.

Mixed Port-Speed LAG Support

SROS routers support mixing different speed member ports in a single LAG. The LAG must be
configured explicitly to allow mixed port-speed operation through the port-weight-speed
command. The port-weight-speed defines both the lowest port speed for a member port in that
LAG and the type of higher speed ports allowed to be mixed in the same LAG. For example, port-
weight-speed 10 defines the minimum member port speed of 10GE and allows addition of any
port that has a speed, which is a multiple of 10GE as long as the mix is supported by a given
release, refer to specific Release Notes. Any LAG can be configured to support mixed port-speed
operation.
For mixed port-speed LAGs:
•
•
•
•
•
7750 SR Interface Configuration Guide
Both LACP and non-LACP configurations are supported. With LACP enabled, LACP is
unaware of physical port differences.
QoS is distributed proportionally to port-speed, unless explicitly configured not to do so
(see internal-scheduler-weight-mode)
User data traffic is hashed proportionally to port speed when any per-flow hash is
deployed.
CPM-originated OAM control traffic that requires per LAG hashing is hashed per
physical port.
It is recommended operators use weight-threshold instead of port-threshold to control
LAG operational status. For example, when 10GE and 100GE ports are mixed in a LAG,
each 10GE port will have a weight of 1, while each 100GE port will have a weight of 10.
Note that the weight-threshold can also be used for LAGs not in mixed port-speed mode
Interface Configuration
Page 137