Alcatel-Lucent 5620 - 9500 MPR LAG Object Configuration; Working with 9500 MPR Device LAG Objects; 9500 MPR Device LAG Objects

5 — 9500 MPR LAG object configuration
5-2 September 2013 Alcatel-Lucent 5620 Service Aware Manager, Release 11.0 R5
3HE 08459 AAAA TQZZA Edition 01
MPR User Guide
5.1 Working with 9500 MPR device LAG objects
LAGs are navigation tree objects located below a device icon that aggregate multiple
network connections in parallel to increase throughput beyond what a connection can
sustain, and to provide redundancy in case one of the links fails.
LAGs are configured manually using the configuration forms available when you
choose Create LAG from the LAG object navigation tree contextual menu.
9500 MPR device LAG objects
The 5620 SAM supports the configuration and discovery of the L1 LAG associations
from the 5620 SAM or NEtO external element manager for equipment functions on
the 9500 MPR (ANSI and ETSI), Release 3.4 or later. Service configuration is
supported across L1 and L2 LAGs using the suite of current service functionality.
For example, support is provided for detection of end-to-end bandwidth on the
VLAN path or correlation of link level alarms up to paths that include L1 LAGs.
You can configure the following LAG endpoint types on the 9500 MPR:
• Radio L1
• Radio L2
• Ethernet L2
The 9500 MPR LAG support includes:
• up to four L1 LAGs on an 9500 MPR device
• up to four L2 LAGs on an 9500 MPR device
• up to two LAGs (L1, L2, or both) on an 9500 MPR MSS-4 shelf
• up to eight LAGs (L1, L2 or both) on an 9500 MPR device
LAG utilization TCAs
You can enable TCA on a 9500 MPR device LAG object and determine whether the
LAG utilization value exceeds a TCA policy threshold. See the “Logical group
object configuration” chapter in the 5620 SAM User Guide and the 9500 MPR
Release Notice.
Radio L1 and Radio L2 LAG port deployment guidelines
A radio LAG L1 follows a similar deployment model as an L2 LAG except that the
L1 LAG functions are deployed at the radio layer. As a result, the L1 LAG has
different port associations, cross-connections, and validations from the L2 LAG. The
advantage of a radio L1 LAG is that highly correlated upper-layer traffic can be
hashed. For example, an LSP hashes to the same port in an L2 LAG.
Note — For Release 3.1 of the 9500 MPR (ANSI and ETSI), the
5620 SAM can discover 9500 MPR LAG objects, although the LAG
properties cannot be configured using the 5620 SAM. All LAGs and
their corresponding port terminations are created using CLI. Only
service creation and discovery are supported for radio LAGs.