Nokia 7210 SAS-M Configuration Guide

LAG Hashing Fields used for 7210 SAS-Mxp
Page 88 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide
NOTES:
1 In the LSR case, incoming labels are used for hashing.
2 ‘Learnt’ wherever mentioned corresponds to Destination MAC.
3 Source/Destination MAC refer to ‘Customer Source/Destination MACs’ unless otherwise
specified.
4 ‘service_id’ refers to the service id of the egressing VPLS/EPIPE/IES/VPRN service.
5 ‘lag_index’ refers to the Lag-IfIndex of the egressing lag.
6 'encap_value' and 'service_vlan' are based on the inner/outer VLAN values of the egressing
LAG SAP.
7 'sap_index' is a value assigned uniquely for each SAP internally.
8 Parameters used for LAG hashing are the same in both SAP egress queue mode (SAP Based
Egress Scheduling) or Port egress queue mode (also known as Port Based Egress Scheduling
mode), unless otherwise specified above.
9 Hash function is implemented in software. Does not use hash-1 or hash-2.
Network port IPv4
interface:
IPv4 network interface to
IPv4 network interface
All traffic: Based on traffic
parameters: Source-IP, Destination-
IP, Source and destination L4 ports.
All traffic: Based on traffic parameters:
Source-IP, Destination-IP, Source and
destination L4 ports.
, Ingress port-Id
Network port IPv6
interface:
IPv6 network interface to
IPv6 network interface
All traffic: Based on traffic
parameters: Source-IP, Destination-
IP, Source and destination L4 ports.
All traffic: Based on traffic parameters:
Source-IP, Destination-IP, Source and
destination L4 ports.
, Ingress port-Id
Table 14: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices (Continued)
Services and Traffic
direction (For example-
SAP to SDP)
Packet fields used for Hashing for
different traffic types with hash-1
Packet fields used for Hashing for dif-
ferent traffic types with hash-2

Nokia 7210 SAS-M Specifications

General

Brand	Nokia
Model	7210 SAS-M
Category	Cell Phone
Language	English