Alcatel-Lucent 7210 SAS M Interface Configuration Manual page 70

LAG
Table 11: LAG Hashing mechanism for services configured on 7210 SAS-R6 devices
Services
Network Port Interface (IP
traffic)
Network Interface to Network
Interface
IES (6PE) (IPv6 traffic)
SAP to SDP
IES (6PE) (IPv6 traffic)
Network Port to SDP
IES (6PE) (IPv6 traffic)
SDP to SAP
IES (Multicast IP traffic)
IP interface (Network or SAP)
to IP interface (SAP)
Network Port IP interface
(Multicast IP traffic)
IP interface (Network or SAP)
to IP interface (Network)
1. VPLS service, SAP to SAP, SDP to SAP (that is, egressing on a SAP): For Unlearnt
2. VPLS service, SDP to SDP: Test has been performed only for VC label variation with the
3. 'Learnt' wherever mentioned corresponds to Destination MAC.
4. Source/Destination MAC refer to 'Customer Source/Destination MACs' unless otherwise
5. In case of a lag with 2 ports at the egress, different Ingress port-Ids may result in the
Page 64
Guide
Packet fields used for Hashing for differ-
Source, Destination IP address, Source,
Destination port (L4), Ingress portId
Source, Destination IP address, Source,
Destination port (L4), Ingress portId
Source, Destination IP address, Source,
Destination port (L4), Ingress portId
Source, Destination IP address, Source,
Destination port (L4).
IPv4 Multicast traffic: Software picks a port
IPv4 Multicast
Destination IP, Source and Destination L4
ports, Ingress Port-Id.
traffic, load-balancing does not happen (for both L2 and L3).Traffic always egresses on
Flood-port (shown in "show lag <lag-id> detail").
same Tunnel label.
specified.
same hash-index, resulting in traffic always getting hashed to only one of the ports. With
more than 2 ports in the lag, load- balancing is expected to take place.
ent traffic types
traffic: Source
7210 SAS M, T, X, R6, Mxp Interface Configuration
and