Workflow to configure weighted per-link hashing on a LAG

Purpose

The following workflow describes the sequence of high-level tasks required to configure weighted per-link hashing on a LAG. This workflow assumes that the physical devices have been installed, commissioned, and discovered. See Chapter 8, Device commissioning and management for more information about device commissioning. See Chapter 9, Device discovery for more information about device discovery.

Note: LAG objects can be accessed using the equipment navigation tree. See Chapter 3, NFM-P navigation tree for more information about using the equipment navigation tree.

Stages


1	Configure a LAG object with weighted per-link hashing. See To create a LAG or To modify a LAG for more information. Configure the required service sites as LAG members.
2	If required, configure LAG weighted per-link hashing on a subscriber profile. See To configure a subscriber profile for more information.
3	As required, configure SAPs for weighted per-link hashing: Epipe and Ipipe L2 access interface. See To configure LAG per-link hashing on a VLL Epipe or Ipipe L2 access interface for more information. IES L3 access interface. See To configure LAG per-link hashing on an IES L3 access interface for more information. IES group interface SAP. See To configure LAG per-link hashing on an IES group interface SAP for more information. VPLS L2 access interface (B-VPLS, I-VPLS or M-VPLS). See To configure LAG per-link hashing on a VPLS L2 access interface for more information. VPRN L3 access interface. See To configure LAG per-link hashing on a VPRN L3 access interface for more information. VPRN group interface SAP. See To configure LAG per-link hashing on a VPRN group interface SAP for more information.