Nokia 7210 SAS-M, 7210 SAS-Mxp, 7210 SAS-T, 7210 SAS-Sx, 7210 SAS-S Configuration Manual

...

Page 1

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

7210 SERVICE ACCESS SWITCH

7210 SAS OS Interface Configuration Guide 7210 SAS-M 7210 SAS-T 7210 SAS-X 7210 SAS-R6 7210 SAS-R12 7210 SAS-Mxp 7210 SAS-S 7210 SAS-Sx Release 9.0.R8

3HE11485AAHTQZZA

Issue: 01

September 2017

Nokia — Proprietary and confidential. Use pursuant to applicable agreements.

Page 2

Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or tradenames of their respective owners.

The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein.

Contains proprietary/trade secret information which is the property of Nokia and must not be made available to, or copied or used by anyone outside Nokia without its written authorization. Not to be used or disclosed except in accordance with applicable agreements.

Page 3

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About This Guide 11

Audience 12 List of Technical Publications 13

Getting Started

In This Chapter 15

Alcatel-Lucent 7210 SAS-M, T, X, R6, R12, Mxp, Sx/S Router Configuration Process . . . . . . . . . . . . . . .15

7210 SAS-Series Interfaces

In This Chapter 17

Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Chassis Slots and Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

MDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Provisioning of MDA on 7210 SAS-M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Digital Diagnostics Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Nokia SFPs and XFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Statistics Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Port Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Port Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Port Dot1q VLAN Etype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Configuration guidelines for Dot1q-etype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Support for Power over Ethernet (PoE) on 7210 SAS-T and 7210 SAS-Mxp ETR units . . . . . . . . . . .35

Support for PoE/PoE+ using combo-ports with 7210 SAS-Sx 1/10GE Fiber variant . . . . . . . . . . . . . .36

Support for PoE/PoE+ for 7210 SAS-Sx 1/10GE Copper PoE variant . . . . . . . . . . . . . . . . . . . . . . . . .36

Link Layer Discovery Protocol (LLDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

LLDP Protocol Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

LLDP Tunneling for Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Port loopback for Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Port loopback without MAC swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Port loopback with MAC swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

LAG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

LAG Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Configuring LAGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

LAG on Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

LAG and QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx

10/100GE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

LAG and QoS policies on 7210 SAS-Mxp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

LAG and QoS policies on 7210 SAS-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

LAG and QoS policies on 7210 SAS-R6 and 7210 SAS-R12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Port Link Damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

LAG Subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

LAG and ECMP Hashing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 3

Page 4

Table of Contents

LAG Hashing Fields used for 7210 SAS-M (Network mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

LAG Hashing Fields used for 7210 SAS-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

LAG Hashing Fields used for 7210 SAS-M (Access-Uplink mode). . . . . . . . . . . . . . . . . . . . . . . . . . . .66

LAG Hashing Fields used for 7210 SAS-T Access-Uplink mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

LAG Hashing Fields used for 7210 SAS-T Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

LAG Hashing Fields used for 7210 SAS-R6 and 7210 SAS-R12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

LAG Hashing Fields used for 7210 SAS-Mxp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

LAG Hashing Fields used for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE. . . . . . . . . . . . . .89

ECMP Hashing fields used for 7210 SAS devices in Network mode . . . . . . . . . . . . . . . . . . . . . . . .95

Multi-Chassis LAG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Point-to-Point (p2p) Redundant Connection Across Layer 2/3 VPN Network . . . . . . . . . . . . . . . .100

DSLAM Dual Homing in Layer 2 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Configuring Multi-Chassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

G.8032 Protected Ethernet Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

802.3ah OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

OAM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Remote Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

802.3ah OAM PDU Tunneling for Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

MTU Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Deploying Pre-provisioned Components for 7210 SAS-M, 7210 SAS-X, 7210 SAS-T,

7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE.. . . . . . . . . . . . . . . . . . . . .115

Deploying Pre-provisioned Components for 7210 SAS-R6 and 7210 SAS-R12 . . . . . . . . . . . . . . . . .115

Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Configuring Physical Ports with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Preprovisioning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Predefining Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Pre-provisioning a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

Basic Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

Configuring Cards and MDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Configuration Notes for provisioning of cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

Configuration Notes for provisioning of 7210 SAS-R6 IMMv2 (IMM-b) cards . . . . . . . . . . . . . . . . . . .124

Configuration Notes for provisioning of 7210 SAS-R6 IMM-c cards . . . . . . . . . . . . . . . . . . . . . . . . . .126

Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Configuring Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Configuring Ethernet Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Ethernet Network Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Ethernet Access uplink Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Ethernet Access Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Configuring 802.1x Authentication Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Configuring Channelized Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133

Configuring a Channelized DS1 Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133

Configuring LAG Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

CRC Error Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

Modifying a Card Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

Deleting a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Deleting Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Card, MDA, and Port Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

Page 4 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 5

Table of Contents

Command Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

Card and MDA Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

Hardware Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

MDA Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Port Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Port-based Split Horizon Group Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Port Configuration Commands for network mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

Port Loopback Commands for 7210 SAS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145

Ethernet Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

TDM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

LAG Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Multi-chassis Redundancy commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Ethernet Ring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

Monitor Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Standards and Protocol Support ................................................................................................ 371

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 5

Page 6

Table of Contents

Page 6 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 7

LIST OF TABLES

Table 1: Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Table 2: Real-Time DDM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Table 3: DDM Alarms and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Table 4: Supported Ethernet ports and TDM ports types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Table 5: Supported Ethernet ports and TDM ports types (continued) . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Table 6: 7210 SAS Platforms supporting port modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Table 7: Behavior for LLDP with different values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices .55

Table 9: LAG Hashing mechanism for services configured on 7210 SAS-X devices . . . . . . . . . . . . . . .63

Table 10: LAG Hashing mechanism for services configured in Access-Uplink mode on 7210 SAS-M . . .66

Table 11: LAG Hashing mechanism for services configured on 7210 SAS-T Access-Uplink mode . . . . .67

Table 12: LAG Hashing Fields used for 7210 SAS-T Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Table 13: LAG Hashing mechanism for services configured on 7210 SAS-R6 and 7210 SAS-R12

devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Table 14: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices . . . . . . . . . . . . .83

Table 15: LAG Hashing mechanism for services configured on 7210 SAS-Sx/S 1/10GE and

7210 SAS-Sx 10/100GE devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Table 16: ECMP Hashing mechanism for services configured on 7210 SAS devices in network. . . . . . .95

Table 17: MTU Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Table 18: Default values for sap-qos-marking in access and hybrid port modes . . . . . . . . . . . . . . . . . . .167

Table 19: Sap-qos-marking default value when port mode is changed . . . . . . . . . . . . . . . . . . . . . . . . . .167

Table 20: Internal port resources on different IMMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 7

Page 8

List of Tables

Page 8 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 9

LIST OF FIGURES

Figure 1: LLDP Internal Architecture for a Network Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Figure 2: Generic Customer Use Case For LLDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Figure 3: LAG Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Figure 4: MC-LAG L2 Dual Homing to Remote PE Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Figure 5: MC-LAG L2 Dual Homing to Local PE-Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Figure 6: P2P Redundant Connection Through a Layer 2 VPN Network. . . . . . . . . . . . . . . . . . . . . . . .100

Figure 7: DSLAM Dual-Homing Using MC-LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Figure 8: 802.1x Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Figure 9: 802.1x Authentication Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Figure 10: 802.1x EAPOL Timers (left) and RADIUS Timers (right) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Figure 11: Slot, Card, MDA, and Port Configuration and Implementation Flow . . . . . . . . . . . . . . . . . . . .117

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 9

Page 10

List of Figures

Page 10 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 11

About This Guide

All the variants of 7210 SAS-M, 7210 SAS-T, 7210 SAS-Mxp, and 7210 SAS-Sx can be configured in two modes, that is in network mode and in access-uplink mode. In network mode configuration 7210 SAS-M, 7210 SAS-T, and 7210 SAS-Mxp uses IP/MPLS to provide service transport. In access-uplink mode configuration 7210 SAS-M and 7210 SAS-T uses Ethernet QinQ technology to provide service transport. The mode can be selected by configuring the BOF appropriately.

The 7210 SAS-Mxp and 7210 SAS-Sx platforms is configured only in Network Mode. The BOF does not allow the user to configure bof-uplink mode. By default, the mode is set to Network mode. In network mode configuration 7210 SAS-Mxp and 7210 SAS-Sx platforms uses IP/MPLS to provide service transport.

Preface

The 7210 SAS-Sx can be operated in standalone mode and satellite mode. The user guide provides features and CLI commands supported in 7210 SAS-Sx standalone mode of operations. Only the Basics System Configuration User Guide contains information on how to boot the 7210 SAS-Sx in satellite mode of operation.

This guide also presents examples to configure and implement various tests.

Notes:

• This user guide is applicable to all 7210 SAS-M, 7210 SAS-T, 7210 SAS-R6, 7210 SASR12, 7210 SAS-X, 7210 SAS-Mxp, and 7210 SAS-Sx platforms, unless specified otherwise.

• In either mode, it is expected that the user will only configure the required CLI parameters appropriate for the mode that the user intends to use. Unless otherwise noted, most of the configuration is similar in both the network mode and Access uplink mode.

• Only 7210 SAS-M and 7210 SAS-T supports access-uplink mode. 7210 SAS-Mxp and 7210 SAS-Sx platforms support only Network mode. 7210 SAS-X, 7210 SAS-R6, and 7210 SAS-R12 does not support access-uplink mode. 7210 SAS-X, 7210 SAS-R6, and 7210 SAS-R12 supports only MPLS uplinks and implicitly operates in network mode.

• On 7210 SAS devices, not all the CLI commands are supported on all the platforms and in all the modes. In many cases, the CLI commands are mentioned explicitly in this

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 11

Page 12

Preface

Audience

document. In other cases, it is implied and easy to know the CLIs that are not supported on a particular platform.

This document is organized into functional chapters and provides concepts and descriptions of the implementation flow, as well as Command Line Interface (CLI) syntax and command usage.

This manual is intended for network administrators who are responsible for configuring the 7210 SAS-Series routers. It is assumed that the network administrators have an understanding of networking principles and configurations, routing processes, and protocols and standards, including:

• CLI concepts

• MDA, and port configuration

• QoS policies

• Services

Page 12 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 13

List of Technical Publications

The 7210 SAS-M, T, X, R6, R12, Mxp, S, Sx OS documentation set is composed of the following books:

• 7210 SAS-M, T, X, R6, R12, Mxp, S, Sx OS Basic System Configuration Guide

This guide describes basic system configurations and operations.

• 7210 SAS-M, T, X, R6, R12, Mxp, S, Sx OS System Management Guide

This guide describes system security and access configurations as well as event logging and accounting logs.

• 7210 SAS-M, T, X, R6, R12, Mxp, S, Sx OS Interface Configuration Guide

This guide describes card, Media Dependent Adapter (MDA), link aggregation group (LAG), and port provisioning.

• 7210 SAS-M, T, X, R6, R12, Mxp, S, Sx OS Router Configuration Guide

Preface

This guide describes logical IP routing interfaces and associated attributes such as an IP address, port, as well as IP and MAC-based filtering.

• 7210 SAS-M, T, Mxp, S, Sx OS Services Guide

This guide describes how to configure service parameters such as customer information, and user services.

• 7210 SAS-M, T, X, R6, R12, Mxp, S, Sx OS OAM and Diagnostic Guide

This guide describes how to configure features such as service mirroring and Operations, Administration and Management (OAM) tools.

• 7210 SAS-M,T, Mxp, S, Sx Quality of Service Guide

This guide describes how to configure Quality of Service (QoS) policy management.

• 7210-SAS-M, T, X, R6, R12, Mxp, S, Sx OS MPLS Guide

This guide describes how to configure Multiprotocol Label Switching (MPLS) and Label Distribution Protocol (LDP).

• 7210-SAS-M, T, X, R6, R12, Mxp, S, Sx OS Routing Protocols Guide

This guide provides an overview of routing concepts and provides configuration examples for OSPF, IS-IS, and route policies.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 13

Page 14

Preface

Page 14 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 15

GETTING STARTED

In This Chapter

This chapter provides process flow information to configure cards and ports.

Alcatel-Lucent 7210 SAS-M, T, X, R6, R12, Mxp, Sx/S Router Configuration Process

Table 1 lists the tasks necessary to provision cards, Media Dependent Adapters (MDAs), and

ports.

This guide is presented in an overall logical configuration flow. Each section describes a software area and provides CLI syntax and command usage to configure parameters for a functional area.

Table 1: Configuration Process

Area Task Chapter

Provisioning Chassis slots and

cards

MDAs MDAs on page 24

Ports Ports on page 30

Reference List of IEEE, IETF,

and other proprietary entities.

Chassis Slots and Cards on page 19

Standards and Protocol Support on page 371

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 15

Page 16

In This Chapter

Page 16 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 17

In This Chapter

This chapter provides information about configuring chassis slots, cards, and ports. Topics in this chapter include:

• Configuration Overview on page 18

− Chassis Slots and Cards on page 19

− MDAs on page 24

7210 SAS-SERIES INTERFACES

− Digital Diagnostics Monitoring on page 26

− Ports on page 30

− Port Types on page 30

− LAG on page 45

− 802.1x Network Access Control on page 105

− MTU Configuration Guidelines on page 114

− Deploying Pre-provisioned Components for 7210 SAS-M, 7210 SAS-X, 7210 SAS-T,

7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE. on page 115

• Configuration Notes on page 189

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 17

Page 18

In This Chapter

Configuration Overview

NOTE: This document uses the term preprovisioning in the context of preparing or preconfiguring entities such as chassis slots, Line cards (for example, SF/CPM - Switch Fabric and Control Plane Module, IMMs - Integrated Media Modules), and media dependent adapters (MDAs), ports, and interfaces, prior to initialization. These entities can be installed but not enabled. When the entity is in a no shutdown state (administratively enabled), then the entity is considered to be provisioned.

The 7210 SAS-M and its variants (that is, 7210 SAS-M 24F, 7210 SAS-M 24F 2XFP, 7210 SASM 24F 2XFP ETR), is a platform with a fixed port configuration and an additional expansion slot that accepts supported MDAs. 7210 software inherits the concept for CPM, IOM and MDA from 7x50 to represent the hardware logically. The software creates 2 logical cards, to represent the CPM and IOM and these are pre-provisioned on bootup. The IOM card, is modelled with 2 MDAs. One of the MDA, a non-removable logical entity, represents the fixed ports available on the platform, and it is pre-provisioned on bootup. The second MDA, represents the physical removable MDA that can be plugged into the available expansion slot and it must be provisioned by the user depending on the MDA they plan to use (see below for more information on provisioning MDA for the expansion slot on 7210 SAS-M). Ports and interfaces can also be preprovisioned.

The 7210 SAS-X, 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/ 100 GE and its variants, are platforms with a fixed port configuration, and no expansion slots. 7210 software inherits the concept of CPM, IOM and MDA from 7x50 to represent the hardware logically. These are fixed and are not removable. The software creates 2 logical cards, to represent the CPM and IOM and these are pre-provisioned on bootup. The IOM card, is modelled with a single MDA, a logical entity to represent the fixed ports on the system. This MDA is autoprovisioned on bootup and user does not need to provision them. Ports and interfaces can also be pre-provisioned.

The 7210 SAS-R6 is a chassis-based platforms that have 6 IMM slots that can accept media cards used for service delivery and 2 CPM slots that provide control-plane redundancy. The chassis slots must be provisioned to accept a specific line card and set the relevant configurations before the equipment is actually installed. The pre-provisioning ability allows you to plan your configurations as well as monitor and manage your router hardware inventory. Ports and interfaces can also be pre-provisioned. When the functionality is needed, the card(s) can be inserted into the appropriate chassis slots when required.

The 7210 SAS-R12 is a chassis-based platforms that have 12 IMM slots that can accept media cards used for service delivery and 2 CPM slots that provide control-plane redundancy. The chassis slots must be provisioned to accept a specific line card and set the relevant configurations before the equipment is actually installed. The pre-provisioning ability allows you to plan your configurations as well as monitor and manage your router hardware inventory. Ports and interfaces can also be pre-provisioned. When the functionality is needed, the card(s) can be inserted into the appropriate chassis slots when required.

Page 18 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 19

Chassis Slots and Cards

The 7210 SAS-M and its variants are platforms which has a set of fixed ports and supports one expansion slot. Software pre-provisions the cards on bootup. The expansion slot is represented as a MDA and supported MDAs can be plugged into the expansion slot. The list of MDAs supported on 7210 SAS-M is available in the 7210 SAS release notes.

The following display output of show card command lists the cards auto-provisioned on 7210 SAS-M chassis:

Sample output for 7210 SAS-M:

A:7210# show card state

Interface Configuration

=============================================================================== Card State =============================================================================== Slot/ Provisioned Equipped Admin Operational Num Num Comments Id Type Type State State Ports MDA

------------------------------------------------------------------------------1 iom-sas iom-sas up up 2 1/1 m24-1gb+2-10gb m24-1gb+2-10gb up up 24 1/2 m4-ds1-ces m4-ds1-ces up up 4 A sfm-sas sfm-sas up up Active

The 7210 SAS-T, 7210 SAS-X, 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE are platforms which has a set of fixed port. Software pre-provisions the cards on bootup. No expansion slots are supported on these platforms.

The following display output of show card command lists the cards auto-provisioned on 7210 SAS-X, 7210 SAS-T, 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE chassis:

The following display output of show card command lists the cards auto-provisioned on 7210 SAS-X chassis:

Sample output for 7210 SAS-X:

A:7210-SAS-X>show# card

=============================================================================== Card Summary ===============================================================================

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 19

Page 20

Chassis Slots and Cards

Slot Provisioned Equipped Admin Operational Card-type Card-type State State

------------------------------------------------------------------------------1 iom-sas iom-sas up up A sfm-sas sfm-sas up up/active =============================================================================== A:7210-SAS-X>show#

The following display output of show card command lists the cards auto-provisioned on 7210 SAS-T chassis:

Sample output for 7210 SAS-T:

A:7210SAST>show# card

=============================================================================== Card Summary =============================================================================== Slot Provisioned Type Admin Operational Comments Equipped Type (if different) State State

------------------------------------------------------------------------------1 iom-sas up up A sfm-sas up up/active =============================================================================== A:7210SAST>show#

The following display output of show card command lists the cards auto-provisioned on 7210 SAS-Mxp chassis:

Sample output for 7210 SAS-Mxp:

*A:sim_dutc>show# card state

=============================================================================== Card State =============================================================================== Slot/ Provisioned Type Admin Operational Num Num Comments Id Equipped Type (if different) State State Ports MDA

------------------------------------------------------------------------------1 iom-sas up up 2 1/1 m22-sfp+2-tx+4-sfpp up up 24 A sfm-sas up up Active =============================================================================== *A:sim_dutc>show#

The following display output of show card command lists the cards auto-provisioned on 7210 SAS-Sx/S 1/10GE 48-port 1GE variant chassis:

Sample output for 7210 SAS-Sx/S 1/10GE:

Page 20 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 21

Interface Configuration

*A:7210SAS>show# card state

=============================================================================== Card State =============================================================================== Slot/ Provisioned Type Admin Operational Num Num Comments Id Equipped Type (if different) State State Ports MDA

------------------------------------------------------------------------------1 iom-sas up up 2 1/1 s48-t4-sfpp up up 52 A sfm-sas up up Active =============================================================================== *A:7210SAS>show#

Sample output for 7210 SAS-Sx 10/100 GE:

*A:hw_sass_duth# show card state

=============================================================================== Card State =============================================================================== Slot/ Provisioned Type Admin Operational Num Num Comments Id Equipped Type (if different) State State Ports MDA

------------------------------------------------------------------------------1 up up 1 1/1 s48-t+4-sfpp up up 52 A sfm-sas up up Active =============================================================================== *A:hw_sass_duth#

The 7210 SAS-R6 is a chassis based platform with 6 IMM slots and 2 CPM slots. On a chassis based platform the slots must be provisioned. To pre-provision a chassis slot, the line card type must be specified. System administrators or network operators can enter card type information for each slot, allowing a range of card types in particular slots. From the range of card types, a card and accompanying MDAs (if any) are specified. When a card is installed in a slot and enabled, the system verifies that the installed card type matches the allowed card type. If the parameters do not match, the card remains offline. A pre-provisioned slot can remain empty without conflicting with populated slots. 7210 SAS-R6 supports only CPM and IMMs. It does not support any physical removable MDAs. Software uses logical MDAs internally to represent the ports on the IMMs and the MDA type is auto-provisioned by software when the IMMs are provisioned. Please check the latest release notes for a list of supported card types (that is, CPM and IMMs). For more information on installation of cards, see the 7210 SAS-R6 Installation Guides.

The 7210 SAS-R12 is a chassis based platform with 12 IMM slots and 2 CPM slots. On a chassis based platform the slots must be provisioned. To pre-provision a chassis slot, the line card type must be specified. System administrators or network operators can enter card type information for each slot, allowing a range of card types in particular slots. From the range of card types, a card

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 21

Page 22

Chassis Slots and Cards

and accompanying MDAs (if any) are specified. When a card is installed in a slot and enabled, the system verifies that the installed card type matches the allowed card type. If the parameters do not match, the card remains offline. A pre-provisioned slot can remain empty without conflicting with populated slots. 7210 SAS-R12 supports only CPM and IMMs. It does not support any physical removable MDAs. Software uses logical MDAs internally to represent the ports on the IMMs and the MDA type is auto-provisioned by software when the IMMs are provisioned. Please check the latest release notes for a list of supported card types (that is, CPM and IMMs). For more information on installation of cards, see the 7210 SAS-R12 Installation Guide.

NOTE:

• On 7210 SAS-R6, a mix of IMMv1 (identified as imm-sas-r) and IMMv2 (identified as imm-sas-r-b) cannot be used simultaneously in the same node. In other words, all the slots need to be populated with either IMMv1 or IMMv2, a mix is not supported. Additionally, the user must configure up front the type of IMMs they intend to populate in the node so that appropriate resources can be allocated on system bootup. Please see the command config>system>chassis> allow-imm-family in the Basics System Configuration User Guide.

• On 7210 SAS-R12, IMMv1 cards are not supported. Either IMMv2 (identified as IMM-b) or IMM-c cards can be used. For more information, see the Basics System Configuration User Guide.

The following show command samples is used to display the cards provisioned and equipped in the chassis:

Sample output for 7210 SAS-R6:

*A:sasr_dutb>show# card

------------------------------------------------------------------------------1 imm-sas-10sfp+1xfp up up 2 imm-sas-10sfp+1xfp up provisioned (not equipped) 3 imm-sas-10sfp up up 4 (not provisioned) up unprovisioned imm-sas-2xfp 5 imm-sas-2xfp up up 6 imm-sas-2xfp up up A cpm-sf-sas-R6 up up/active B cpm-sf-sas-R6 up up/standby =============================================================================== *A:sasr_dutb>show#

Page 22 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 23

Interface Configuration

Sample output for 7210 SAS-R12:

A:A6144909484>show# card

------------------------------------------------------------------------------8 (not provisioned) up unprovisioned imm-sas-b-4sfp+ A cpm-sf-sas-R12 up up/active B cpm-sf-sas-R12 up up/standby =============================================================================== A:A6144909484>show#

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 23

Page 24

Provisioning of MDA on 7210 SAS-M

MDAs

The 7210 SAS-R6, R12, 7210 SAS-X, 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100 GE platforms, as explained in the previous section, do not support any physical removable MDAs. Software uses the concept of MDA internally (as a logical entity) to represent the ports and the MDA type is either auto-provisioned on bootup or auto-provisioned automatically based on the configured IMM type.

On 7210 SAS-M, as explained in the previous section, in addition to the fixed ports, a expansion slot is available. It is represented as a physical MDA and needs to be provisioned. The section below talks about provisioning of MDAs and is applicable only to those platforms where physical MDAs are supported.

A chassis slot and card type must be specified and provisioned before an MDA can be preprovisioned. An MDA is provisioned when a type designated from the allowed MDA types is inserted. A preprovisioned MDA slot can remain empty without conflicting with populated slots. Once installed and enabled, the system verifies that the installed MDA type matches the configured parameters. If the parameters do not match, the MDA remains offline. An MDA is provisioned when a type designated from the allowed MDA type is inserted. A preprovisioned MDA slot can remain empty without conflicting with the populated slots.

•

Provisioning of MDA on 7210 SAS-M

Provisioning guidelines for MDA used with 7210 SAS-M:

• The device rejects the insertion of a CES card if the slot is provisioned for a 2* 10G MDA and vice versa.

• If a 2*10G MDA provisioned, it ensures that the BOF parameter "no-service-ports" is configured to specify two ethernet ports.

• Only on 7210 SAS-M 24F variant, the no-service-ports BOF parameter is not available for use.

• Change of value assigned to 'use-expansion-card-type' BOF parameter, requires a reboot so that a different MDA type can be used.

Provisioning 2 x 10G MDA and 4 x T1/E1 CES MDA on 7210 SAS-M

For 7210 SAS-M devices currently deployed or new deployments, to insert 2*10 MDA perform the following steps:

1. Configure the BOF parameter "use-expansion-card-type" to m2-xfp. This provisions the system to expect a 2 x 10G MDA for use in the expansion slot.

Page 24 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 25

Interface Configuration

2. Configure the BOF parameter "no-service-ports", if using a 7210 SAS-M 24F 2XFP and 7210 SAS-M 24F 2XFP ETR variants.

3. Re-boot the device.

4. The above steps are required for first-time use of 2 x 10G MDA or when changing the MDA type in use. It is not needed, if a MDA is being replaced with a MDA of the same type.

In 7210 devices using 2 x 10G MDA, to insert CES MDA perform the following steps:

1. Configure the BOF parameter "use-expansion-card-type" to m4-ds1-ces. This will provision the system to expect a 4 x T1/E1 CES MDA for use in the expansion slot.

2. Configure the BOF parameter "no-service-ports" to default, if using a 7210 SAS-M 24F 2XFP and 7210 SAS-M 24F 2XFP ETR variants.

3. Re-boot the device.

4. The above steps are required when changing the MDA type in use. It is not needed, if a MDA is being replaced with a MDA of the same type.

NOTE: Insertion and removal of the CES MDA at any point of time into the system is supported, if the BOF parameter configuration is set to default.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 25

Page 26

Provisioning of MDA on 7210 SAS-M

Digital Diagnostics Monitoring

Some Nokia SFP and XFP transponders have Digital Diagnostics Monitoring (DDM) capability. With DDM the transceiver module maintains information about its working status in device registers, such as:

• Temperature

• Supply voltage

• Transmit (TX) bias current

• TX output power

• Received (RX) optical power

The transceiver is also programmed with warning and alarm thresholds for low and high conditions that can generate system events. These thresholds are programmed by the transceiver manufacturer.

There are no CLI commands required for DDM operations, however, the show>port port-id detail command displays DDM information in the Transceiver Digital Diagnostics Monitoring output section.

The Tx and Rx power displayed in the DDM output are average optical power in dBm.

DDM information is populated into the router’s MIBs, so the DDM data can be retrieved by Network Management using SNMP. Also, RMON threshold monitoring can be configured for the DDM MIB variables to set custom event thresholds if the factory-programmed thresholds are not at the desired levels.

The following are potential uses of the DDM data:

• Optics degradation monitoring — With the information returned by the DDM-capable optics module, degradation in optical performance can be monitored and trigger events based on custom or the factory-programmed warning and alarm thresholds.

• Link/router fault isolation — With the information returned by the DDM-capable optics module, any optical problem affecting a port can be quickly identified or eliminated as the potential problem source.

Page 26 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 27

Supported real-time DDM features are summarized in Table 2.

Table 2: Real-Time DDM Information

Interface Configuration

Parameter User Units SFP/XFP

Units

SFP XFP

Temperature Celsius C Supported Supported

Supply

Volts µV Supported Supported

Voltage

TX Bias

mA µA Supported Supported

Current

TX Output Power

RX Received Optical Power4

AUX1 parameter dependent

dBm (converted from mW)

dBm (converted from dBm) (Avg Rx Power or OMA)

mW Supported Supported

- Not supported Supported

(embedded in transceiver)

AUX2 parameter dependent

- Not supported Supported

(embedded in transceiver)

The factory-programmed DDM alarms and warnings that are supported are summarized in

Table 3.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 27

Page 28

Provisioning of MDA on 7210 SAS-M

Table 3: DDM Alarms and Warnings

Parameter SFP/XFP Units SFP XFP Required?

Temperature

- High Alarm

- Low Alarm

- High Warning

- Low Warning

Supply Voltage

- High Alarm

- Low Alarm

- High Warning

- Low Warning

TX Bias Current

- High Alarm

- Low Alarm

- High Warning

- Low Warning

TX Output Power

- High Alarm

- Low Alarm

- High Warning

- Low Warning

C Yes Yes Yes

µV Yes Yes Yes

µA Yes Yes Yes

mW Yes Yes Yes

RX Optical Power

mW Yes Yes Yes

- High Alarm

- Low Alarm

- High Warning

- Low Warning

AUX1

- High Alarm

- Low Alarm

- High Warning

parameter dependent

(embedded in

transceiver)

No Yes Yes

- Low Warning

AUX2

- High Alarm

- Low Alarm

- High Warning

parameter dependent

(embedded in

transceiver)

No Yes Yes

- Low Warning

Page 28 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 29

Nokia SFPs and XFPs

The availability of the DDM real-time information and warning or alarm status is based on the transceiver. It may or may not indicate if DDM is supported, although some Nokia SFPs support DDM. Non-DDM and DDM-supported SFPs are distinguished by a specific ICS value.

For Nokia SFPs that do not indicate DDM support in the ICS value, DDM data is available although the accuracy of the information has not been validated or verified.

For non-Nokia transceivers, DDM information may be displayed, but Alcatel-Lucent is not responsible for formatting, accuracy, etc.

Statistics Collection

The DDM information and warnings/alarms are collected at one minute intervals, so the minimum resolution for any DDM events when correlating with other system events is one minute.

Interface Configuration

Note that in the Transceiver Digital Diagnostic Monitoring section of the show port port-id detail command output:

• If the present measured value is higher than the either or both High Alarm, High Warn thresholds; an exclamation mark “!” displays along with the threshold value.

• If the present measured value is lower than the either or both Low Alarm, Low Warn thresholds; an exclamation mark “!” displays along with the threshold value.

A:Dut-A# show port 2/1/6 detail

.........

=============================================================================== Transceiver Digital Diagnostic Monitoring (DDM), Internally Calibrated =============================================================================== Value High Alarm High Warn Low Warn Low Alarm

------------------------------------------------------------------------------Temperature (C) +39.3 +96.0 +94.0 -7.0 -8.0 Supply Voltage (V) 3.27 3.51 3.49 3.12 3.10 Tx Bias Current (mA) 18.8 77.0 70.0 5.5 4.5 Tx Output Power (dBm) 1.33 5.50 5.00 0.00 -0.50 Rx Optical Power (avg dBm) -40.00 -8.50 -9.00 -33.98! -35.23! ===============================================================================

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 29

Page 30

Port Types

Ports

Port Types

Supported port types on different 7210 platforms is listed in Table 4, “Supported Ethernet ports and TDM ports types,”below:

Table 4: Supported Ethernet ports and TDM ports types

Ports 7210 SAS-M 7210 SAS-M

24F 2XFP

Copper ports (10/ 100/1000 Base-T)

Fast Ethernet SFP Ports

10 Gigabit XFP/ SFP+ Ports

TDM ports (DS1/ E1)

Table 5: Supported Ethernet ports and TDM ports types (continued)

Ports 7210 SAS-R6 7210 SAS-R12 7210 SAS-Mxp 7210 SAS-

No No No No Yes

Yes Yes Yes Yes Yes

Yes, with 2 x

10G/XFP

MDA

Yes (only in

network mode

and with CES

MDA)

Yes-XFP Yes-XFP Yes-XFP Yes-XFP

Yes (only in

network mode

and with CES

MDA)

7210 SAS-M

24F 2XFP

ETR

Yes (only in

network mode and with CES

MDA)

7210 SAS-X 7210 SAS-T

No No

7210 SAS-Sx/

Sx/S 1/10GE

S 10/100GE

Copper ports (10/ 100/1000 Base-T)

Fast Ethernet SFP Ports

10 Gigabit XFP/ SFP+ Ports

Page 30 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

IMMv2 with

copper ports

Yes Yes Yes Yes No

IMMv1 - XFP

IMMv2 -

SFP+

IMMv2 with

copper ports

IMMv2 - SFP+ Yes-SFP+ Yes-SFP+

Yes Yes No

(See Note 8.)

Yes- SFP+

(See Note 8.)

Page 31

Table 5: Supported Ethernet ports and TDM ports types (continued)

Interface Configuration

Ports 7210 SAS-R6 7210 SAS-R12 7210 SAS-Mxp 7210 SAS-

TDM ports (DS1/

No No No No No

E1)

NOTES:

1. 10/100/1000 Base-T Copper SFPs can be used in the any of the SFP ports.

2. Copper SFPs speed 10Mbps and half-duplex is supported only on 7210 SAS-M and 7210 SAS-T platforms. It is not supported on 7210 SAS-Sx/S 1/10GE, 7210 SAS-Mxp, 7210 SASR6, and 7210 SAS-R12 platforms.

3. Combo port supports speed 10Mbps with full-duplex on both 7210 SAS-Mxp and 7210 SASSx/S 1/10GE, when the copper port is used.

4. Fixed copper ports on 16 x 10/100/1000 Base-T (RJ.5) IMMv2 card on 7210 SAS-R6 and 7210 SAS-R12 support speed of 10Mbps with full-duplex. They do not support 10Mbps speed with half-duplex.

5. Fixed copper ports on 7210 SAS-T support 10Mbps speed with full-duplex and half duplex.

6. For 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE the user is provided with an option to configure the connection type of the port, to allow the user to force the use of a particular connection type. By default, the combo port type must be set to ‘auto’. In auto mode, the software detects the type of port automatically based on the link availability of the media inserted into the port.

7. For TDM ports, only CES services (CESoPSN and SAToP based) are provided for the T1/E1 ports.

8. The SFP+ ports on 7210 SAS-Sx 10/100GE, 7210 SAS-S copper variants (non-PoE) allow use of SFP optics with SFP+ ports. Please check the release notes for more information. To know the list of supported SFP optics, contact your Nokia representative.

Sx/S 1/10GE

7210 SAS-Sx/

S 10/100GE

Port Modes

In 7210 SAS devices, port must be configured as either access, access uplink or network. The following paragraphs explain the significance of the different port modes and the support available on different platforms.

• Access ports — Configured for customer facing traffic on which services are configured.

If a Service Access Port (SAP) is to be configured on the port, it must be configured as an access port. When a port is configured for access mode, the appropriate encapsulation type must be configured to distinguish the services on the port. Once a port has been configured for access mode, one or more services can be configured on the port depending on the encapsulation value. Access ports can be configured on all the 7210 platforms.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 31

Page 32

Port Types

• Access-uplink ports — Access-uplink ports are used to provide native Ethernet connectivity in service provider transport or infrastructure network. This can be achieved by configuring port mode as access uplink. With this option, the encap-type can be configured to only qinq. Access-uplink SAPs, which are QinQ SAPs, can only be configured on an access uplink port to allow the operator to differentiate multiple services being carried over a single access uplink port. This is the default mode when a node is operating in access-uplink mode.

• Network ports — Configured for network facing traffic. These ports participate in the service provider transport or infrastructure network. Dot1q is supported on network ports. This is default for nodes operating in network mode.

• Hybrid ports — Configured for access and network facing traffic. While the default mode of an Ethernet port remains network, the mode of a port cannot be changed between the access/network/hybrid values unless the port is shut down and the configured SAPs and/or interfaces are deleted. Hybrid ports allow a single port to operate in both access and network modes. MTU of port in hybrid mode is the same as in network mode except for the 10/100 MDA. The default encap for hybrid port mode is dot1q, it also supports QinQ encapsulation on the port level. Null hybrid port mode is not supported. Once the port is changed to hybrid, the default MTU of the port is changed to match the value of 9212 bytes currently used in network mode (higher than an access port); this is to ensure that both SAP and network VLANs can be accommodated. The only exception is when the port is a 10/100 fast Ethernet. In those cases, the MTU in hybrid mode is set to 1522 bytes, which corresponds to the default access MTU with QinQ, which is larger than the network dot1q MTU or access dot1q MTU for this type of Ethernet port. The configuration of all parameters in access and network contexts will continue to be done within the port using the same CLI hierarchy as in existing implementation. The difference is that a port configured in mode hybrid allows both ingress and egress contexts to be configured concurrently. An Ethernet port configured in hybrid mode can have two values of encapsulation type: dot1q and QinQ. The NULL value is not supported since a single SAP is allowed, and can be achieved by configuring the port in the access mode, or a single network IP interface is allowed, which can be achieved by configuring the port in network mode. Hybrid mode can be enabled on a LAG port when the port is part of a single chassis LAG configuration. When the port is part of a multi-chassis LAG configuration, it can only be configured to access mode as MC-LAG is not supported on a network port and consequently is not supported on a hybrid port. The following port modes are supported on each of the 7210 SAS platforms:

Table 6: 7210 SAS Platforms supporting port modes

Port Mode

Platforms

7210 SAS-M Yes

Access Network Hybrid Access-

uplink

Yes

7210 SAS-X Yes Yes Yes No

Page 32 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 33

Table 6: 7210 SAS Platforms supporting port modes

Interface Configuration

Port Mode

Platforms

7210 SAS-T Yes

7210 SAS-R6 IMM

Access Network Hybrid Access-

uplink

Yes

Yes Yes Yes No (IMMv1) and IMM-b (IMMv2)

7210 SAS-R6 IMM-c

No Yes No No (also known as IMM-c 1CFP4 or IMM-c 1QSFP28)

7210 SAS-R12 IMM-b Yes Yes Yes No

7210 SAS-R12 IMM-c

No Yes No No 100GE 2 variants - IMM-c 1CFP4 or IMM-c 1QSFP28)

7210 SAS-Mxp Yes Yes Yes No

7210 SAS-Sx/S 1/ 10GE

7210 SAS-Sx 10/ 100GE

a Network ports can be configured only if the BOF is configured to operate the node in net-

work mode (also known as, MPLS mode). b Hybrid ports are supported only when the node is operating in network mode. c Access-uplink ports can be configured only if the BOF is configured to operate the node in

access-uplink mode (also known as, L2 mode).

Note: 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12 is configured in Network mode by default. It does not support accessuplink mode.

Port Dot1q VLAN Etype

Yes Yes Yes No

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 33

Page 34

Port Types

7210 supports an option to allow the user to use a different dot1q VLAN Ethernet Type (Etype). It allows for interoperability with third-party switches that use some pre-standard (other than 0x8100) dot1q VLAN etype.

Configuration guidelines for Dot1q-etype

The following are the configuration guidelines for Dot1q-etype configured for dot1q encap port:

• Dot1q-etype configuration is supported for all ports - Access, Hybrid and Network ports.

• Dot1q-preserve SAPs cannot be configured on dot1q encap ports configured to use ethertype other than 0x8100.

• Priority tagged packet received with etype 0x8100 on a dot1q port configured with etype 0x9100 are classified as priority tagged packet and mapped to a dot1q :0 SAP (if configured) and the priority tag is removed.

• Priority tagged packets received with etype 0x6666 (any value other than 0x8100) on a dot1q port configured with etype 0x9100 is classified as null-tagged packet and mapped to a dot1q :0 SAP (if configured) and the priority tag is retained and forwarded.

• The dot1q-etype is modified only for the dot1q encap port (access/hybrid port). The dot1q-etype cannot be modified on Network ports.

• During the non-default dot1q-rvpls and qinq-rvpls, the extra tagged packets is dropped even for an 0x8100 packets on an RVPLS SAP, this is applicable only for network mode (and not access-uplink mode).

Page 34 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 35

Interface Configuration

Support for Power over Ethernet (PoE) on 7210 SAS-T and 7210 SAS-Mxp ETR units

NOTE: PoE is not supported on any other 7210 SAS platform other than 7210 SAS-T ETR and 7210 SAS-Mxp ETR.

The 7210 SAS-T ETR unit and 7210 SAS-Mxp ETR unit supports Power over Ethernet (PoE) as per 802.3af and 802.3at standards. It allows these devices to be used to supply power to connected PoE devices, such as telephones, CCTV cameras, and other PoE standard compliant devices.

NOTE:

• On 7210 SAS-T ETR, up to four fixed copper ports are available to connect PoE/PoE+ devices. It can supply a maximum of up to 60W of power.

• On 7210 SAS-Mxp ETR unit, up to 2 ports are available to connect PoE/PoE+ devices. It can supply a maximum of up to 60W of power.

• On both 7210 SAS-T ETR and 7210 SAS-Mxp ETR, the maximum amount of power available is to be shared among all the PoE/PoE+ devices connected to the node. In other words, it is possible to have a mix of PoE devices (using 15W of power) and PoE+ devices (using 30W of power) as long as the total power drawn is within the system limits.

The following functionalities are available:

• Supports both 802.3af (PoE) and 802.3at (PoE+) on any of the ports. The ports can be used to connect either PoE devices or PoE+ devices or a combination of both simultaneously, as long as the power drawn is within the device’s system limits.

• Only Alternative A is supported on the supported 7210 SAS devices.

• Supports classification of both Type 1 and Type 2 PD using physical layer classification mechanism (using 1-event physical layer classification mechanism for Type 1 PD and 2event physical layer classification mechanism for Type 2 PD).

• Supports allocation of power based on the identified class (called as class-based power allocation method) using physical layer classification mechanism. The 802.3af and

802.3at standards define the power that can be allocated or requested by a particular class. There are four classes defined - Class 1, Class 2, Class 3 and Class 4 by standards. These are used to allow PoE devices to request power based on their needs. If enough power is not available to supply power based on the identified class, then power is denied to the connected PoE device. Each device has limit on the maximum amount of power it can provide. If the total of power requested by the devices connected to PoE enabled ports exceed this threshold, then the device denies power to the device. When power is denied to the PD, the port is operationally up, though power is not supplied to the port. If the power is applied successfully or power is denied to the port, the system logs an event.

• Only DC power is supplied to connected PoE devices (PDs). It works with PoE devices that use injectors where a AC/DC wall device is used to power a remote PoE device.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 35

Page 36

Support for PoE/PoE+ using combo-ports with 7210 SAS-Sx 1/10GE Fiber variant

• The software monitors the PoE port and detect faults and events and raises traps, along with displaying the same in the status of the port. Events and faults detected and notified to the user are:

− Supplying power event – This event is generated when power is supplied to a

connected PoE device after successful detection and classification.

− Denied power event – This event is generated when power is denied to a connected

PoE device after successful detection and classification.

− Disconnect event – This event is generated when a connected PoE device is

disconnected from the port and, stops drawing power from the node.

− Fault events are generated for events such as overload, short-circuit, and other events.

Software clears the fault when the fault no longer exists.

• If a port is enabled for PoE is shutdown, then the power supplied to the port is disabled. It restores when the no shutdown command is executed, if the request does not exceed the power budget.

Support for PoE/PoE+ using combo-ports with 7210 SAS-Sx 1/ 10GE Fiber variant

On the 24 port and 48 fiber variant of 7210 SAS-Sx 1/10GE, there are two PoE/PoE+ capable ports, namely, 1/1/1 and 1/1/2, the combo ports. To use PoE/poE+ these ports must be configured to use the copper interface. These two PoE/PoE+ ports cannot draw more than 60W of power. It allows users to use these two ports for either PoE or PoE+ devices or a combination of them.

Support for PoE/PoE+ for 7210 SAS-Sx 1/10GE Copper PoE variant

7210 SAS-Sx 1/10GE have two PoE variants - 7210 SAS-Sx 1/10GE 48Tp 4SFP+ PoE and 7210 SAS-Sx 1/10GE 24Tp 4SFP+ PoE. These variants support PoE/PoE+ on all the fixed copper ports. All the ports can draw a maximum of 720W of power on both the variants. It allows users to have up to 24 port of PoE (15W each per port) or PoE+ (25W each per port) on the 24-port variant. On the 48-port variant of the device, it allows up to 48 ports of PoE (15W each per port) or 24 ports of PoE+ (25W each per port) or a mix of ports of PoE and PoE+ ports such that total draw across all ports does not exceed 720W.

Page 36 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 37

Interface Configuration

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 37

Page 38

Support for PoE/PoE+ for 7210 SAS-Sx 1/10GE Copper PoE variant

Link Layer Discovery Protocol (LLDP)

The IEEE 802.1ab Link Layer Discovery Protocol (LLDP) standard defines protocol and management elements suitable for advertising information to stations attached to the same IEEE 802 LAN. The protocol facilitates the identification of stations connected by IEEE 802 LANs or MANs, their points of interconnection, and access points for management protocols.

The LLDP helps the network operators to discover topology information. This information is used to detect and resolve network problems and inconsistencies in the configuration.

Listed below is the information included in the protocol defined by the IEEE 802.1ab standard:

• Connectivity and management information about the local station to adjacent stations on the same IEEE 802 LAN is advertised.

• Network management information from adjacent stations on the same IEEE 802 LAN is received.

• Operates with all IEEE 802 access protocols and network media.

• Network management information schema and object definitions that suitable for storing connection information about adjacent stations is established.

• Provides compatibility with a number of MIBs. For more information, see Figure 1.

Page 38 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 39

Interface Configuration

OSSG262

Organizationally

Defined Local Device

LLDP MIB Extension

(Optional)

LLDP Local System

MIB

Organizationally

Defined Remote Device

LLDP MIB Extensions

(Optional)

LLDP Remote Systems

MIB

PTOPO MIB

(Optional)

Entity MIB

(Optional)

LLDP/LSAP

Remote Device InformationLocal Device Information

LLDP Frames

Interface MIB

(Optional)

Other MIBs

(Optional)

LLDP Agent

Figure 1: LLDP Internal Architecture for a Network Node

In order to detect and address network problems and inconsistencies in the configuration, the network operators can discover the topology information using LLDP. The Standard-based tools address the complex network scenarios where multiple devices from different vendors are interconnected using Ethernet interfaces.

The example displayed in Figure 2 depicts a MPLS network that uses Ethernet interfaces in the core or as an access/handoff interfaces to connect to different kind of Ethernet enabled devices such as service gateway/routers, QinQ switches DSLAMs or customer equipment.

The topology information of the network in Figure 2 can be discovered if, IEEE 802.1ab LLDP is running on each of the Ethernet interfaces in network.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 39

Page 40

Support for PoE/PoE+ for 7210 SAS-Sx 1/10GE Copper PoE variant

OSSG263

Ethernet Links - FE/GE/10GE

MPLS/Native ETH

Core

LAG

QinQ

SWs

DSLAMs

PE PE

SG/R

Figure 2: Generic Customer Use Case For LLDP

Page 40 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 41

LLDP Protocol Features

LLDP is an unidirectional protocol that uses the MAC layer to transmit specific information related to the capabilities and status of the local device. Separately from the transmit direction, the LLDP agent can also receive the same kind of information for a remote device which is stored in the related MIB(s).

LLDP itself does not contain a mechanism for soliciting specific information from other LLDP agents, nor does it provide a specific means of confirming the receipt of information. LLDP allows the transmitter and the receiver to be separately enabled, making it possible to configure an implementation so the local LLDP agent can either transmit only or receive only, or can transmit and receive LLDP information.

The information fields in each LLDP frame are contained in a LLDP Data Unit (LLDPDU) as a sequence of variable length information elements, that each include type, length, and value fields (known as TLVs), where:

• Type identifies what kind of information is being sent.

Interface Configuration

• Length indicates the length of the information string in octets.

• Value is the actual information that needs to be sent (for example, a binary bit map or an alphanumeric string that can contain one or more fields).

Each LLDPDU contains four mandatory TLVs and can contain optional TLVs as selected by network management:

•Chassis ID TLV

•Port ID TLV

• Time To Live TLV

• Zero or more optional TLVs, as allowed by the maximum size of the LLDPDU

• End Of LLDPDU TLV

The chassis ID and the port ID values are concatenated to form a logical identifier that is used by the recipient to identify the sending LLDP agent/port. Both the chassis ID and port ID values can be defined in a number of convenient forms. Once selected however, the chassis ID/port ID value combination remains the same as long as the particular port remains operable.

A non-zero value in the TTL field of the Time To Live TLV tells the receiving LLDP agent how long all information pertaining to this LLDPDU’s identifier will be valid so that all the associated information can later be automatically discarded by the receiving LLDP agent if the sender fails to update it in a timely manner. A zero value indicates that any information pertaining to this LLDPDU’s identifier is to be discarded immediately.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 41

Page 42

LLDP Tunneling for Epipe Service

Note that a TTL value of zero can be used, for example, to signal that the sending port has initiated a port shutdown procedure. The End Of LLDPDU TLV marks the end of the LLDPDU.

The implementation defaults to setting the port-id field in the LLDP OAMPDU to tx-local. This encodes the port-id field as ifIndex (sub-type 7) of the associated port. This is required to support some releases of SAM. SAM may use the ifIndex value to properly build the Layer Two Topology Network Map. However, this numerical value is difficult to interpret or readily identify the LLDP peer when reading the CLI or MIB value without SAM. Including the port-desc option as part of the tx-tlv configuration allows an ALU remote peer supporting port-desc preferred display logic to display the value in the port description TLV instead of the port-id field value. This does not change the encoding of the port-id field. That value continues to represent the ifIndex. In some environments, it may be important to select the specific port information that is carried in the portid field. The operator has the ability to control the encoding of the port-id information and the associated subtype using the port-id-subtype option. Three options are supported for the portidsubtype:

tx-if-alias — Transmit the ifAlias String (subtype 1) that describes the port as stored in the IFMIB, either user configured description or the default entry (ie 10/100/Gig ethernet SFP)

tx-if-name — Transmits the ifName string (subtype 5) that describes the port as stored in the IFMIB, ifName info.

tx-local — The interface ifIndex value (subtype 7)

IPv6 (address subtype 2) and IPv4 (address subtype 1) LLDP System Management addresses are supported.

LLDP Tunneling for Epipe Service

Customers who subscribe to Epipe service consider the Epipe as a wire, and run LLDP between their devices which are located at each end of the Epipe. To facilitate this, the 7210 devices support tunneling of LLDP frames that use the nearest bridge destination MAC address.

If enabled using the command tunnel-nearest-bridge-dest-mac, all frames received with the matching LLDP destination mac address are forwarded transparently to the remote end of the Epipe service. To forward these frames transparently, the port on which tunneling is enabled must be configured with NULL SAP and the NULL SAP must be configured in an Epipe service. Tunneling is not supported for any other port encapsulation or other services.

Additionally, before enabling tunneling, admin status for LLDP dest-mac nearest-bridge must be set to disabled or Tx only, using the command admin-status available under configure> port> ethernet> lldp> destmac-nearest-bridge. If admin-status for dest-mac nearest-bridge is set to receive and process nearest-bridge LLDPDUs (that is, if either rx or tx-rx is set) then it overrides the tunnel-nearest-bridge-dest-mac command.

Page 42 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 43

Interface Configuration

The following table lists the behavior for LLDP with different values set in use for admin-status and when tunneling is enabled or disabled:

Table 7: Behavior for LLDP with different values

Nearest-bridge-mac Admin status Tunneling Enabled Tunneling Disabled

Rx Process/Peer Process/Peer

Tx Tunnel Drop

Rx-Tx Process/Peer Process/Peer

Disabled Process/Peer Drop

NOTE: Transparent forwarding of LLDP frames can be achieved using the standard defined mechanism when using the either nearest-non-tmpr or the nearest-customer as the destination MAC address in the LLDP frames. It is recommended that the customers use these MAC address where possible to conform to standards. This command allows legacy LLDP implementations that do not support these additional destinations MAC addresses to tunnel LLDP frames that use the nearest-bridge destination MAC address.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 43

Page 44

Port loopback without MAC swap

Port loopback for Ethernet ports

7210 devices support port loopback for ethernet ports. There are two flavors of port loopback commands - port loopback without mac-swap and port loopback with mac-swap. Both these commands are helpful for testing the service configuration and measuring performance parameters such as throughput, delay, and jitter on service turn-up. Typically, a third-party external test device is used to inject packets at desired rate into the service at a central office location.

The following sections describe the port loopback functionality

Port loopback without MAC swap

When the Port loopback command is enabled, the system enables PHY/MAC loopback on the specified port. All the packets are sent out the port configured for loopback and received back by the system. On ingress to the system after the loopback, the node processes the packets as per the service configuration for the SAP.

This is recommended for use with only VLL services. This command affects all the services configured on the port, therefore the user is advised to ensure all the configuration guidelines mentioned for this feature in the command description are followed.

Port loopback with MAC swap

The 7210 SAS provides port loop back support with MAC swap. When the Port loopback command is enabled, the system enables PHY/MAC loopback on the specified port. All the packets are sent out the port configured for loopback and received back by the system. On ingress to the system after the loopback, the node swaps the MAC addresses for the specified SAP and the service. It only processes packets that match the specified source MAC address and destination MAC address, while dropping packets that do not match. It processes these packets as per the service configuration for the SAP.

This is recommended for use with only VPLS and VLL services. This command affects all the services configured on the port, therefore the user is advised to ensure all the configuration guidelines mentioned for this feature in the command description are followed.

Page 44 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 45

LAG

Interface Configuration

Based on the IEEE 802.3ax standard (formerly 802.3ad), Link Aggregation Groups (LAGs) can be configured to increase the bandwidth available between two network devices, depending on the number of links installed. LAG also provides redundancy in the event that one or more links participating in the LAG fail. All physical links in a given LAG links combine to form one logical interface.

Packet sequencing must be maintained for any given session. The hashing algorithm deployed by Alcatel-Lucent routers is based on the type of traffic transported to ensure that all traffic in a flow remains in sequence while providing effective load sharing across the links in the LAG.

LAGs must be statically configured or formed dynamically with Link Aggregation Control Protocol (LACP). The optional marker protocol described in IEEE 802.3ax is not implemented. LAGs can be configured on network and access ports.

LAG Features

Hardware capabilities:

• The LAG load sharing is executed in hardware, which provides line rate forwarding for all

Software capabilities:

• The Nokia solution conforms to the IEEE LAG implementation including dynamic

port types.

costing and LAG port threshold features. The dynamic cost and LAG port threshold features can be enabled even if the second node is not an Alcatel-Lucent router.

− Dynamic cost

Dynamic cost can be enabled with the config>lag dynamic-cost action specified in the config>lag>port-threshold command.

If dynamic cost is enabled and the number of active links is greater than the port threshold value (0-7 or 0-15), depending on chassis-mode and IOM type), then the path cost is dynamically calculated whenever there is a change in the number of active

command or by the

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 45

Page 46

LAG Features

links regardless of the specified port threshold action. If the port-threshold is met and the action is set to dynamic cost, then the path cost is dynamically recalculated regardless of the global dynamic cost configuration.

Enabling dynamic costing causes the physical link metrics used by OSPF to be applied based on the operational or aggregate link bandwidth in the LAG that is available at the time, providing the number of links that are up exceeds the configured LAG port threshold value. If the number of available links falls below the configured threshold, the configured threshold action determines if and at what cost this LAG will be advertised.

For example, assume a single link in OSPF has an associated cost of 100 and the LAG consists of four physical links. The cost associated with the logical link is 25. If one link fails then the cost would automatically be adjusted to 33.

If dynamic cost is not configured then costing is applied based on the total number of links configured. The cost would be calculated at 25. This will remain static provided the number of links that are up exceeds the configured LAG threshold.

− LAG port threshold

The LAG port threshold feature allows configuration of the behavior, once the number of available links in a LAG falls below or is equal to the specified threshold. Two options are available:

1. If the number of links available (up) in a LAG is less than the configured threshold, then the LAG is regarded as operationally down. For example, assume a LAG consists of four physical links. The threshold is set to two and dynamic costing is not configured. If the operational links is equal to or drops below two, the link is regarded as operationally down until the number of operational links is two or more.

2. When the number of links available in a LAG is less than the configured threshold, the LAG starts using the dynamic-cost allowing other nodes to adjust their routing tables according to the revised costs. In this case, when the threshold is not crossed, a fixed metric (all links operational) is advertised.

Page 46 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 47

Configuring LAGs

OSSG011

ALA-1 ALA-4

ALA-2

LAG-1

LAG-2

ALA-3

LAG configuration guidelines include:

• Ports can be added or removed from the LAG while the LAG and its ports (other than the port being removed) remain operational. When ports to and/or from the LAG are added or removed, the hashing algorithm is adjusted for the new port count.

•The show commands display physical port statistics on a port-by-port basis or the entire LAG can be displayed.

• LAG is supported on Ethernet ports.

• Ports of a particular LAG can be of different types but they must be the same speed and duplex. To guarantee the same port speed is used for all ports in a LAG, auto-negotiation must be disabled or in limited mode to ensure only a specific speed is advertised.

Figure 3 displays traffic routed between ALA-1 and ALA-2 as a LAG consisting of four ports.

Interface Configuration

LAG on Access

Link Aggregation Groups (LAG) is supported on access ports and access-uplink ports. This is treated the same as LAG on network ports which provides a standard method to aggregate Ethernet links. The difference lies in how QoS is handled.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 47

Figure 3: LAG Configuration

Page 48

LAG and QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/

LAG and QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE

In the 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE an ingress QoS policy is applied to the aggregate traffic that is received on all the member ports of the LAG. For example, if an ingress policy is configured with a policier of PIR 100Mbps, for a SAP configured on a LAG with two ports, then the policer limits the traffic received through the two ports to a maximum of 100Mbps.

In the 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE an egress QoS policy parameters are applied to all the ports that are members of the LAG (all ports get the full SLA). For example, if an egress policy is configured with a queue shaper rate of PIR 100Mbps, and applied to an access-uplink or access LAG configured with two port members, then each port would send out 100 Mbps of traffic for a total of 200Mbps of traffic out of the LAG. The advantage of this method over a scheme where the PIR is divided equally among all the member ports of the LAG is that, a single flow can use the entire SLA. The disadvantage is that, the overall SLA can be exceeded if the flows span multiple ports.

LAG and QoS policies on 7210 SAS-Mxp

In 7210 SAS-Mxp, a SAP ingress QoS policy or network port ingress QoS policy or network IP interface ingress QoS policy is applied to the aggregate traffic that enters the traffic through all the ports of the system. For example, if an ingress policy is configured with a policier of PIR 100Mbps, for a SAP configured on a LAG with two ports, then the policer limits the traffic entering the system through the two ports to a maximum of 100Mbps.

In 7210 SAS-Mxp, SAP egress QoS policy shaper parameters are applied to all the ports that are members of the LAG (all ports get the full SLA). For example, if an SAP egress policy is configured with a shaper of PIR 100Mbps, each port would get a PIR of 100 Mbps. The advantage of this method over a scheme where the PIR is divided equally among all the member ports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is that the overall SLA can be exceeded if the flows span multiple ports.

In 7210 SAS-Mxp, network port egress QoS policy shaper parameters are applied to all the ports that are members of the LAG (all ports get the full SLA). For example, if an network port egress policy is configured with a shaper of PIR 100Mbps, each port would get a PIR of 100 Mbps. The advantage of this method over a scheme where the PIR is divided equally among all the member

Page 48 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 49

ports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is that the overall SLA can be exceeded if the flows span multiple ports.

LAG and QoS policies on 7210 SAS-X

In 7210 SAS-X, a SAP ingress QoS policy or network port ingress QoS policy or network IP interface ingress QoS policy is applied to the aggregate traffic that enters the traffic through all the ports of the system. For example, if an ingress policy is configured with a policier of PIR 100Mbps, for a SAP configured on a LAG with two ports, then the policer limits the traffic entering the system through the two ports to a maximum of 100Mbps.

In 7210 SAS-X, SAP egress QoS policy shaper parameters are applied to all the ports that are members of the LAG (all ports get the full SLA). For example, if an SAP egress policy is configured with a shaper of PIR 100Mbps, each port would get a PIR of 100 Mbps. The advantage of this method over a scheme where the PIR is divided equally among all the member ports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is that the overall SLA can be exceeded if the flows span multiple ports.

Interface Configuration

In 7210 SAS-X, network port egress QoS policy shaper parameters are applied to all the ports that are members of the LAG (all ports get the full SLA). For example, if an network port egress policy is configured with a shaper of PIR 100Mbps, each port would get a PIR of 100 Mbps. The advantage of this method over a scheme where the PIR is divided equally among all the member ports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is that the overall SLA can be exceeded if the flows span multiple ports.

LAG and QoS policies on 7210 SAS-R6 and 7210 SAS-R12

In 7210 SAS-R6 and 7210 SAS-R12, a SAP ingress QoS policy or network port ingress QoS policy or network IP interface ingress QoS policy is applied to the aggregate traffic that enters through all the ports on a IMM. If the LAG has member ports on different IMMs, then the policy is created for each IMM and is applied to the aggregate traffic that enters through all the ports on a given IMM. For example, if an ingress policy is configured with a policier of PIR 100Mbps, for a SAP configured on a LAG with two ports, then the policer limits the traffic entering through the two ports of the IMM to a maximum of 100Mbps. If the LAG has two ports on 2 different IMMs,

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 49

Page 50

Port Link Damping

then policy is applied each IMM individually, and the policer on each IMM allows a maximum of 100Mbps for a total of 200Mbps.

In 7210 SAS-R6 and 7210 SAS-R12, SAP egress QoS policy shaper parameters are applied to all the ports that are members of the LAG (all ports get the full SLA), irrespective of whether they are located on a single IMM or two different IMMs. For example, if an SAP egress policy is configured with a shaper of PIR 100Mbps, each port would get a PIR of 100Mbps. The advantage of this method over a scheme where the PIR is divided equally among all the member ports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is that the overall SLA can be exceeded if the flows span multiple ports.

In 7210 SAS-R6 and 7210 SAS-R12, network port egress QoS policy shaper parameters are applied to all the ports that are members of the LAG (all ports get the full SLA), irrespective of whether they are located on a single IMM or two different IMMs.. For example, if an network port egress policy is configured with a shaper of PIR 100Mbps, each port would get a PIR of 100 Mbps. The advantage of this method over a scheme where the PIR is divided equally among all the member ports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is that the overall SLA can be exceeded if the flows span multiple ports.

Port Link Damping

Hold time controls enable port link damping timers that reduce the number of link transitions reported to upper layer protocols.

The 7210 SAS OS port link damping feature guards against excessive port transitions. Any initial port transition is immediately advertised to upper layer protocols, but any subsequent port transitions are not advertised to upper layer protocols until a configured timer has expired.

An “up” timer controls the dampening timer for link up transitions, and a “down” timer controls the dampening timer for link down transitions.

LACP

Generally, link aggregation is used for two purposes: provide an increase in bandwidth and/or provide redundancy. Both aspects are addressed by aggregating several Ethernet links in a single LAG.

Under normal operation, all non-failing links in a given LAG will become active and traffic is load balanced across all active links. In some circumstances, however, this is not desirable. Instead, it desired that only some of the links are active and the other links be kept in stand-by condition.

Page 50 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 51

LACP enhancements allow active lag-member selection based on particular constrains. The mechanism is based on the IEEE 802.3ax standard so interoperability is ensured.

Active-Standby LAG Operation without LACP

Active/standby LAG is used to provide redundancy while keeping consistency of QOS enforcement. Some devices do not support LACP and hence an alternative solution is required.

The active/standby decision for LAG member links is local decision driven by pre-configured selection-criteria. This decision was communicated to remote system using LACP signalling.

As an alternative, the operator can disable the signal transmitted by using power-off option for standby-signalling in the CLI command at the LAG level at the port member level. As a consequence, the transmit laser will be switched off for all LAG members in standby mode. On switch over (active-links failed) the laser will be switched on all LAG members will become active.

Interface Configuration

Note that this mode of operation cannot detect physical failures on the standby link, which means that the network operator cannot be certain that the standby links are capable to take over in case of active-links failure. This is an inherit limitation of this operational mode.

When LACP goes down on a standby link, a warning message announcing that LACP has expired on the corresponding member port is printed in log 99 on the other end.

The operation where standby ports are powered down is mutually exclusive with LACP and, therefore, is modelled as separate mode of LACP operation of power-off. For this mode, the selection-criteria best-port can be used. This criteria means that it will be always a sub-group with the best-port (the highest priority port) which will be chosen to be used as active sub-group.

It will not be possible to have an active LACP in power-off mode before the correct selection criteria is selected.

LAG Subgroups

LACP is used to make selection of active links predictable and compatible with any vendor equipment. Refer to the IEEE STD 802.3-2002, Section 3, Clause 43.6.1 standard which describes how LACP allows stand-by and active signalling.

The 7210 SAS-M,X,T, R6, R12, and Mxp implementation of LACP supports the following:

• A given LAG member can be assigned to sub-groups. The selection algorithm then assures that only members of a single sub-group are selected as active links.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 51

Page 52

LACP

• The selection algorithm is effective only if LACP is enabled on a given LAG. At the same time, it is assumed that connected system has also LACP enabled (active or passive mode).

• The algorithm will select active links based on following criteria:

− Depending on selection-criteria setting either the sub-group with the highest number

of eligible links or the sub-group with the highest aggregate weight of all eligible members is selected first.

− If multiple groups satisfy the selection criteria, the sub-group being currently active

remains active. Initially, the sub-group containing the highest priority eligible link is selected.

− Only links pertaining to a single sub-group are active at any time.

− An eligible member refers to a LAG member link which can potentially become

active. This means it is operationally up, and if the slave-to-partner flag is set, the remote system did not disable its use (by signalling stand-by).

• The selection algorithm works in a reverting mode. This means that every time the configuration or status of any link in a LAG changes, the selection algorithm is re-run. In case of a tie between two groups (one of them being currently active) the active group remains active (no reverting).

Page 52 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 53

LAG and ECMP Hashing

Note: ECMP hashing is supported only on 7210 SAS devices in network mode. Not all 7210 platforms support ECMP. Please check the Release notes and the Router Configuration user guide to know the 7210 SAS platforms that support ECMP.

When a requirement exists to increase the available bandwidth for a logical link that exceeds the physical bandwidth or add redundancy for a physical link, typically one of the methods is applied; equal cost multi-path (ECMP) or Link Aggregation (LAG). A 7210 SAS can deploy both at the same time, meaning, using ECMP of two or more Link Aggregation Groups (LAG) and/or single links.The Nokia implementation supports per flow hashing used to achieve uniform loadspreading and per service hashing designed to provide consistent per service forwarding. Depending on the type of traffic that needs to be distributed into an ECMP and/or a LAG, different variables are used as input to the hashing algorithm.

An option is provided per LAG to select the hashing function to be used for load-balancing flows on the member ports of the LAG. Users can use one of the available options based on the flows they have in their network and select an option that helps improve the load-balancing of flows in their network. The packets fields selected by the hashing function is different for some flows with the two hashing functions and is provided in the tables below.

Interface Configuration

The tables below provides the packet fields used for hashing for different services and different traffic types for different platforms.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 53

Page 54

LAG and ECMP Hashing

Page 54 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 55

Interface Configuration

LAG Hashing Fields used for 7210 SAS-M (Network mode)

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices

Traffic direction (For example SAP to SDP)

VPLS Service:

SAP to SAP

Packet fields used for Hashing for different traffic types with hash-1

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt): BDA, BSA, VLAN. PBB traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

MPLS traffic (Learnt): Source and Destination MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet), VLAN. MPLS traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for different traffic types with hash-2

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic (Learnt and Unlearnt): BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic (Learnt and Unlearnt): MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC, EtherType, VLAN, Ingress Port-Id.

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN. Non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 55

Page 56

LAG Hashing Fields used for 7210 SAS-M (Network mode)

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices (Continued)

Traffic direction (For example SAP to SDP)

Epipe Service:

SAP to SAP

Packet fields used for Hashing for different traffic types with hash-1

IP traffic: Source and Destination IP, Source and Destination L4 ports

PBB traffic: BDA, BSA, VLAN.

MPLS traffic: Source and Destination MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet), VLAN.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN.

Packet fields used for Hashing for different traffic types with hash-2

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic: BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic: MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN, Ingress Port-Id.

Page 56 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 57

Interface Configuration

LAG Hashing Fields used for 7210 SAS-M (Network mode)

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices (Continued)

Traffic direction (For example SAP to SDP)

VPLS Service:

SAP to SDP

Packet fields used for Hashing for different traffic types with hash-1

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt): BDA, BSA, VLAN PBB traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

MPLS traffic (Learnt): Source and Destination MAC,VLAN MPLS traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN Non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for different traffic types with hash-2

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic (Learnt and Unlearnt): BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic (Learnt and Unlearnt): MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC, EtherType, VLAN, Ingress Port-Id.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 57

Page 58

LAG Hashing Fields used for 7210 SAS-M (Network mode)

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices (Continued)

Traffic direction (For example SAP to SDP)

Epipe Service:

SAP to SDP

VPLS Service:

SDP to SAP

Packet fields used for Hashing for different traffic types with hash-1

IP traffic: Source and Destination IP, Source and Destination L4 ports

PBB traffic: BDA, BSA, VLAN

MPLS traffic: Source and Destination MAC,VLAN

Non-IP traffic: Source and Destination MAC, EtherType, VLAN

Learnt traffic

: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header)

Unlearnt traffic: Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for different traffic types with hash-2

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic: BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic: MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN, Ingress Port-Id.

All traffic (Learnt and Unlearnt)4.: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id.

Epipe Service:

SDP to SAP

All traffic Destination MAC (Outer MACs inside the payload, just after the MPLS header)

: Source and

All traffic4.: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id.

Page 58 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 59

Interface Configuration

LAG Hashing Fields used for 7210 SAS-M (Network mode)

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices (Continued)

Traffic direction (For example SAP to SDP)

VPLS Service:

SDP to SDP

Packet fields used for Hashing for different traffic types with hash-1

IP traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header) IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), ISID PBB traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Non-IP traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), EtherType Non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for different traffic types with hash-2

IP traffic (Learnt and Unlearnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id

PBB traffic (Learnt and Unlearnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), ISID, Ingress Port-Id

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), EtherType, Ingress PortId

MPLS – LSR All traffic: Source and Destination

MAC (Outer MACs of the ethernet

All traffic: MPLS label stack (Two

labels deep), Ingress Port-Id. packet that encapsulates MPLS packet)

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 59

Page 60

LAG Hashing Fields used for 7210 SAS-M (Network mode)

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices (Continued)

Traffic direction (For example SAP to SDP)

PBB VPLS service:

PBB BCB Traffic (that is, B-sap to Bsap)

PBB VPLS service:

Originating PBB BEB traffic (that is, I-SAP to B-SAP)

Packet fields used for Hashing for different traffic types with hash-1

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

L2/non-IP traffic (Learnt): BDA, BSA L2/non-IP traffic (Unlearnt): Hash2 and parameter under hash-2 used.

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

L2/non-IP traffic (Learnt): CSA, CDA, EtherType, VLAN L2/non-IP traffic (Unlearnt): Hash2 and parameter under hash-2 used.

Packet fields used for Hashing for different traffic types with hash-2

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

L2/non-IP traffic (Learnt and Unlearnt): BDA, BSA, ISID, Ingress Port-Id

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

L2/non-IP traffic (Learnt and Unlearnt): CSA, CDA, EtherType, VLAN, Ingress Port-Id.

PBB Epipe service:

Originating PBB

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

IP traffic: Source and Destination IP, Source and Destination L4

ports, Ingress Port-Id BEB traffic (that is, . PBB Epipe I-SAP to B-SAP)

L2/non-IP traffic: CSA, CDA, EtherType, VLAN, Ingress Port-Id

L2/non-IP traffic: CSA, CDA,

EtherType, VLAN, Ingress Port-Id

Page 60 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 61

Interface Configuration

LAG Hashing Fields used for 7210 SAS-M (Network mode)

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices (Continued)

Traffic direction (For example SAP to SDP)

PBB Epipe service:

Terminating PBB BEB traffic (PBB Epipe SAP to BSAP)

VPRN service:

SAP to SAP SDP to SAP

VPRN service:

SAP to SDP

IES service (IPv4):

IES SAP to IES SAP

Packet fields used for Hashing for different traffic types with hash-1

IP traffic: CSA, CDA

L2/non-IP traffic: CSA, CDA, EtherType

Source and Destination IP, Source and Destination L4 ports

Packet fields used for Hashing for different traffic types with hash-2

IP traffic: CSA, CDA

L2/non-IP traffic: CSA, CDA, EtherType

Source and Destination IP, Source and Destination L4 ports, Ingress port-Id

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 61

Page 62

LAG Hashing Fields used for 7210 SAS-M (Network mode)

Table 8: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices (Continued)

Traffic direction (For example SAP to SDP)

IES service (IPv4):

IES SAP to IPv4 network port interface

Network port IPv4 interface:

IPv4 network interface to IPv4 network interface

Network port IPv6 interface:

IPv6 network interface to IPv6 network interface

Packet fields used for Hashing for different traffic types with hash-1

Source and Destination IP, Source and Destination L4 ports

Source and Destination IP(v6), Source and Destination L4 ports

Packet fields used for Hashing

for different traffic types with

hash-2

Source and Destination IP, Source

and Destination L4 ports, Ingress

Port-Id.

Source and Destination IP, Source

and Destination L4 ports, Ingress

Port-Id.

Source and Destination IP(v6),

Source and Destination L4 ports,

Ingress Port-Id.

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. Applicable to non-IP, IP, PBB and MPLS traffic encapsulated in the MPLS packet received on the SDP Binding/SDP.

Page 62 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 63

Interface Configuration

LAG Hashing Fields used for 7210 SAS-X

Table 9: LAG Hashing mechanism for services configured on 7210 SAS-X devices

Services and Traffic Direction (For example: SAP to SDP)

VPLS service:

SAP to SAP SAP to SDP

Epipe service:

SAP to SAP SAP to SDP

Packet fields used for Hashing for different traffic types

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, VLAN, Ingress Port-Id.

PBB traffic: BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic: MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic (learnt and unlearnt): Source and Destination MAC, EtherType, Ingress Port-Id.

IP traffic : Source and Destination IP, Source and Destination L4 ports, VLAN, Ingress Port-Id.

PBB traffic: BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic: MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic: Source and Destination MAC, EtherType, Ingress Port-Id.

VPLS and Epipe service:

All traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS

SDP to SAP

VPLS service:

header), Ingress Port-Id.

All traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS

SDP to SDP

header), Ingress Port-Id.

MPLS – LSR All traffic: MPLS label stack (Two labels deep),

Ingress Port-Id.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 63

Page 64

LAG Hashing Fields used for 7210 SAS-X

Table 9: LAG Hashing mechanism for services configured on 7210 SAS-X devices (Continued)

Services and Traffic Direction (For example: SAP to SDP)

PBB VPLS service:

PBB BCB Traffic (that is, B-SAP to B-SAP)

PBB VPLS service:

Originating PBB BEB traffic (that is, I-SAP to B-SAP)

PBB VPLS service:

Terminating PBB BEB traffic (that is, B-SAP to I-SAP)

PBB Epipe service:

Originating PBB BEB traffic (that is, PBB Epipe I-SAP to B-SAP)

Packet fields used for Hashing for different traffic types

IP traffic (learnt and unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

L2/non-IP traffic (learnt and unlearnt): BDA, BSA, ISID, Ingress Port-Id.

IP traffic (learnt and unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id, VLAN.

L2/non-IP traffic (learnt and unlearnt): CSA, CDA, EtherType, Ingress Port-Id.

IP traffic (learnt and unlearnt): CSA, CDA, Ingress Port-Id.

L2/non-IP traffic (learnt and unlearnt): CSA, CDA, EtherType, Ingress Port-Id.

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id, VLAN.

L2/non-IP traffic: CSA, CDA, EtherType, Ingress Port-Id.

PBB Epipe service:

Terminating PBB BEB traffic (PBB Epipe SAP to B-SAP)

VPRN service:

IP traffic: CSA, CDA, Ingress Port-Id.

L2/non-IP traffic: CSA, CDA, EtherType, Ingress Port-Id.

IP traffic: Source and Destination IP, Source and

Destination L4 ports, Ingress Port-Id, VLAN. SAP to SAP SAP to SDP

VPRN service:

IP traffic: Source and Destination IP, Source and

Destination L4 ports, Ingress port-Id. SDP to SAP

Page 64 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 65

Interface Configuration

Table 9: LAG Hashing mechanism for services configured on 7210 SAS-X devices (Continued)

Services and Traffic Direction (For example: SAP to SDP)

IES service and IPv4 Network port interface:

IES SAP to IES SAP

IPv4 network port interface to IPv4 network port interface

IES SAP to IPv4 network port interface

Network port IPv6 interface:

IPv6 network interface to IPv6 network interface

IES (Multicast IP traffic)

IP interface (Network or SAP) to IP interface (SAP)

Packet fields used for Hashing for different traffic types

IPv4 unicast traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id, VLAN.

IPv6 unicast traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id, VLAN.

IPv4 Multicast traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

Network Port IP interface (Multicast IP traffic)

IP interface (Network or SAP) to IP interface (Network)

NOTES:

1. In the LSR case, incoming labels are used for hashing.

2. ‘Learnt’ wherever mentioned corresponds to Destination MAC.

3. Source/Destination MAC always refer to ‘Customer Source/Destination MACs’ unless otherwise specified.

IPv4 Multicast traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 65

Page 66

LAG Hashing Fields used for 7210 SAS-M (Access-Uplink mode)

Table 10: LAG Hashing mechanism for services configured in Access-Uplink mode on 7210 SAS-M

Services and Traffic Direction Packet fields used for Hashing for different traffic

types

VPLS service:

SAP to SAP

Epipe service:

SAP to SAP

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports. IP traffic (Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic (Learnt): BDA, BSA, VLAN PBB traffic (Unlearnt): BDA, BSA, ISID, Ingress Port-Id

MPLS traffic (Learnt): Source and Destination MAC (Outer MACs of the Ethernet packet that encapsulates MPLS packet), VLAN MPLS traffic (Unlearnt): MPLS label stack (Two labels deep), Ingress Port-Id

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN Non-IP traffic (Unlearnt): Source and Destination MAC, EtherType, Ingress Port-Id, VLAN

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic: BDA, BSA, ISID, Ingress Port-Id

MPLS traffic: MPLS label stack (Two labels deep), Ingress Port-Id

Non-IP traffic: Source and Destination MAC, EtherType, Ingress Port-Id, VLAN

IES service (IPv4):

IPv4 unicast traffic: Source and Destination IP, Source and Destination L4 ports.

IES SAP to IES SAP

Page 66 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 67

Interface Configuration

NOTES:

1. The term ‘Learnt’ mentioned corresponds to Destination MAC.

2. Source/Destination MAC refer to ‘Customer Source/Destination MACs’ unless otherwise specified.

3. VLAN ID is considered for Learnt - PBB, MPLS, Non-IP traffic in VPLS service only for traffic ingressing at dot1q, Q.*, Q1.Q2 SAPs.

4. Only outer VLAN tag is used for hashing.

LAG Hashing Fields used for 7210 SAS-T Access-Uplink mode

Table 11: LAG Hashing mechanism for services configured on 7210 SAS-T Access-Uplink mode

Services and Traffic Direction Packet fields used for Hashing for different

traffic types

VPLS service:

SAP to SAP

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports. IP traffic (Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic (Learnt): BDA, BSA, VLAN PBB traffic (Unlearnt): BDA, BSA, ISID, Ingress Port-Id

MPLS traffic (Learnt): Source and Destination MAC (Outer MACs of the Ethernet packet that encapsulates MPLS packet) MPLS traffic (Unlearnt-IP): MPLS label stack (Two labels deep), Source and Destination IP, Ingress Port-Id, VLAN MPLS traffic (Unlearnt-L2): MPLS label stack (Two labels deep), Ingress Port-Id

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN Non-IP traffic (Unlearnt): Source and Destination MAC, EtherType, Ingress Port-Id, VLAN

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 67

Page 68

LAG Hashing Fields used for 7210 SAS-T Access-Uplink mode

Table 11: LAG Hashing mechanism for services configured on 7210 SAS-T Access-Uplink mode

Services and Traffic Direction Packet fields used for Hashing for different

traffic types

Epipe service:

SAP to SAP

IES service (IPv4):

IES SAP to IES SAP

NOTES:

1. The term ‘Learnt’ mentioned corresponds to Destination MAC.

2. Source/Destination MAC refer to ‘Customer Source/Destination MACs’ unless otherwise specified.

3. VLAN ID is considered for Learnt - PBB, MPLS, Non-IP traffic in VPLS service only for traffic ingressing at dot1q, Q.*, Q1.Q2 SAPs.

4. Only outer VLAN tag is used for hashing.

IIP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic: BDA, BSA, ISID, Ingress Port-Id

MPLS traffic (IP): MPLS label stack (Two labels deep), Source and Destination IP, Ingress Port-Id MPLS traffic (L2): MPLS label stack (Two labels deep), Ingress Port-Id

Non-IP traffic: Source and Destination MAC, EtherType, Ingress Port-Id, VLAN

IPv4 unicast traffic: Source and Destination IP, Source and Destination L4 ports.

Page 68 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 69

Interface Configuration

LAG Hashing Fields used for 7210 SAS-T Network Mode

Table 12: LAG Hashing Fields used for 7210 SAS-T Network Mode

Services and Traffic direction (For example -SAP to SDP)

VPLS Service:

SAP to SAP

Packet fields used for Hashing for different traffic types With hash-1

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports.

IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt): BDA, BSA, VLAN.

PBB traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

MPLS traffic (Learnt): Source and Destination MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet), VLAN.

Packet fields used for Hashing for different traffic types With hash-2

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic (Learnt and Unlearnt): BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic (Learnt and Unlearnt): Source and Destination IP, MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC, EtherType, VLAN, Ingress Port-Id.

MPLS traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN.

Non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 69

Page 70

LAG Hashing Fields used for 7210 SAS-T Network Mode

Table 12: LAG Hashing Fields used for 7210 SAS-T Network Mode (Continued)

Services and Traffic direction (For example -SAP to SDP)

Epipe service:

SAP to SAP

VPLS service:

SAP to SDP

Packet fields used for Hashing for different traffic types With hash-1

IP traffic: Source and Destination IP, Source and Destination L4 ports

PBB traffic: BDA, BSA, VLAN.

MPLS traffic: Source and Destination MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet), VLAN.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN.

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports.

Packet fields used for Hashing for different traffic types With hash-2

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic: BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic: Source and Destination IP, MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN, Ingress PortId.

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt): BDA, BSA, VLAN PBB traffic (Unlearnt):Hash-2 and parameter under hash-2 used.

MPLS traffic (Learnt): Source and Destination MAC, VLAN MPLS traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN Non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt and Unlearnt): BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic (Learnt and Unlearnt): Source and Destination IP, MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC, EtherType, VLAN, Ingress Port-Id.

Page 70 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 71

Table 12: LAG Hashing Fields used for 7210 SAS-T Network Mode (Continued)

Interface Configuration

Services and Traffic direction (For example -SAP to SDP)

Epipe service:

SAP to SDP

VPLS service:

SDP to SAP

Packet fields used for Hashing for different traffic types With hash-1

IP traffic: Source and Destination IP, Source and Destination L4 ports

PBB traffic: BDA, BSA, VLAN

MPLS traffic: Source and Destination MAC, VLAN

Non-IP traffic: Source and Destination MAC, EtherType, VLAN

IP traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Source and Destination L4 ports, VLAN

Packet fields used for Hashing for different traffic types With hash-2

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

PBB traffic: BDA, BSA, ISID, Ingress Port-Id.

MPLS traffic: Source and Destination IP, MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN, Ingress PortId.

All traffic (Learnt and Unlearnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id.

PBB traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header).

Non-IP traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), EtherType.

All traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 71

Page 72

LAG Hashing Fields used for 7210 SAS-T Network Mode

Table 12: LAG Hashing Fields used for 7210 SAS-T Network Mode (Continued)

Services and Traffic direction (For example -SAP to SDP)

Epipe service:

SDP to SAP

VPLS service:

SDP to SDP

Packet fields used for Hashing for different traffic types With hash-1

IP traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Source and Destination L4 ports, VLAN

PBB traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header).

Non-IP traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), EtherType.

All traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header)

All traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for different traffic types With hash-2

All traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id.

All traffic (Learnt and Unlearnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id.

MPLS – LSR All traffic: Source and Destination MAC

(Outer MACs of the Ethernet packet that encapsulates MPLS packet)

All traffic: MPLS label stack (Two labels deep), Source and Destination IP (only when IP header immediately follows MPLS header without any Source and Destination MAC in between inside the MPLS encapsulation), Ingress Port-Id.

Page 72 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 73

Table 12: LAG Hashing Fields used for 7210 SAS-T Network Mode (Continued)

Interface Configuration

Services and Traffic direction (For example -SAP to SDP)

PBB VPLS service:

PBB BCB Traffic (that is, B-sap to B-sap)

PBB VPLS service:

Originating PBB BEB traffic (that is, I-SAP to B-SAP)

Packet fields used for Hashing for different traffic types With hash-1

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

L2/non-IP traffic (Learnt): BDA, BSA L2/non-IP traffic (Unlearnt):Hash-2 and parameter under hash-2 used.

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

L2/non-IP traffic (Learnt): CSA, CDA, EtherType, VLAN

Packet fields used for Hashing for different traffic types With hash-2

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

L2/non-IP traffic (Learnt and Unlearnt): BDA, BSA, ISID, Ingress Port-Id

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

L2/non-IP traffic (Learnt and Unlearnt): CSA, CDA, EtherType, VLAN, Ingress Port-Id.

PBB VPLS service:

Terminating PBB BEB traffic (that is, B-SAP to I-SAP)

L2/non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

IP traffic (Learnt): CSA, CDA IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

L2/non-IP traffic (Learnt): CSA, CDA, EtherType L2/non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

IP traffic (Learnt and Unlearnt): CSA, CDA, Ingress Port-Id

L2/non-IP traffic (Learnt and Unlearnt): CSA, CDA, EtherType, Ingress Port-Id.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 73

Page 74

LAG Hashing Fields used for 7210 SAS-T Network Mode

Table 12: LAG Hashing Fields used for 7210 SAS-T Network Mode (Continued)

Services and Traffic direction (For example -SAP to SDP)

PBB Epipe service:

Originating PBB BEB traffic (that is, PBB Epipe I-SAP to BSAP)

PBB Epipe service:

Terminating PBB BEB traffic (PBB Epipe SAP to B-SAP)

VPRN service:

SAP to SAP SDP to SAP

Packet fields used for Hashing for different traffic types With hash-1

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

L2/non-IP traffic: CSA, CDA, EtherType, VLAN, Ingress Port-Id

IP traffic: CSA, CDA

L2/non-IP traffic: CSA, CDA, EtherType

Source and Destination IP, Source and Destination L4 ports

Packet fields used for Hashing for different traffic types With hash-2

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

L2/non-IP traffic: CSA, CDA, EtherType, VLAN, Ingress Port-Id

IP traffic: CSA, CDA

L2/non-IP traffic: CSA, CDA, EtherType

Source and Destination IP, Source and Destination L4 ports, Ingress port-Id

VPRN service:

Source and Destination IP, Source and Destination L4 ports

Source and Destination IP, Source and Destination L4 ports, Ingress port-Id

SAP to SDP

IES service (IPv4):

Source and Destination IP, Source and Destination L4 ports

Source and Destination IP, Source and Destination L4 ports, Ingress port-Id

IES SAP to IES SAP

IES service (IPv4):

Source and Destination IP, Source and Destination L4 ports

Source and Destination IP, Source and

Destination L4 ports, Ingress Port-Id. IES SAP to IPv4 network port interface

Page 74 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 75

Table 12: LAG Hashing Fields used for 7210 SAS-T Network Mode (Continued)

Interface Configuration

Services and Traffic direction (For example -SAP to SDP)

Network port IPv4 interface:

IPv4 network interface to IPv4 network interface

Network port IPv6 interface:

IPv6 network interface to IPv6 network interface

NOTES:

Packet fields used for Hashing for different traffic types With hash-1

Source and Destination IP, Source and Destination L4 ports

Source and Destination IP(v6), Source and Destination L4 ports

Packet fields used for Hashing for different traffic types With hash-2

Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

Source and Destination IP(v6), Source and Destination L4 ports, Ingress PortId.

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.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 75

Page 76

LAG Hashing Fields used for 7210 SAS-R6 and 7210 SAS-R12

Table 13: LAG Hashing mechanism for services configured on 7210 SAS-R6 and 7210 SAS-R12 devices

Services and Traffic

direction (For example-

SAP to SDP)

VPLS service:

SAP to SAP

Packet fields used for Hashing for

different traffic types with hash-1

All Unlearnt Traffic

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, number of active ports.

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports

PBB traffic (Learnt): BDA, BSA, VLAN

MPLS traffic (Learnt): Source and Destination MAC (Outer MACs of the Ethernet packet that encapsulates MPLS packet), VLAN

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

All Unlearnt Traffic

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, number of active ports.

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic (Learnt): BDA, BSA, ISID, Ingress Port-Id

MPLS traffic (Learnt): MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN, Ingress Port-Id

EPIPE Service:

SAP to SAP

IP traffic: Source and Destination IP, Source and Destination L4 ports

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic: BDA, BSA, VLAN

PBB traffic: BDA, BSA, ISID, Ingress

MPLS traffic: Source and Destination

Port-Id

MAC (Outer MACs of the Ethernet packet that encapsulates MPLS packet), VLAN

Non-IP traffic: Source and Destination MAC, EtherType, VLAN

MPLS traffic: MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN, Ingress Port-Id

Page 76 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 77

Interface Configuration

Table 13: LAG Hashing mechanism for services configured on 7210 SAS-R6 and 7210 SAS-R12 devices

Services and Traffic

direction (For example-

SAP to SDP)

VPLS Service:

SAP to SDP

Packet fields used for Hashing for

different traffic types with hash-1

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt ): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt) : BDA, BSA, VLAN PBB traffic (Unlearnt ) : Hash-2 and parameter under hash-2 used.

MPLS traffic (Learnt): Source and Destination MAC, VLAN MPLS traffic (Unlearnt ): Hash-2 and parameter under hash-2 used.

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN Non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

IP traffic (Learnt and Unlearnt ): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic (Learnt and Unlearnt) : BDA, BSA, ISID, Ingress Port-Id

MPLS traffic (Learnt and Unlearnt): MPLS label stack (Two labels deep), Source and Destination IP (when IP header follows MPLS header), Ingress Port-Id.

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC, EtherType, VLAN, Ingress Port-Id.

Epipe Service:

SAP to SDP

IP traffic: Source and Destination IP, Source and Destination L4 ports

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic: BDA, BSA, VLAN

PBB traffic: BDA, BSA, ISID, Ingress

MPLS traffic:

Port-Id

Source and Destination MAC, VLAN

MPLS traffic: MPLS label stack (Two

labels deep), Source and Destination IP Non-IP traffic: Source and Destination MAC, EtherType, VLAN

(when IP header follows MPLS header),

Ingress Port-Id.

Non-IP traffic: Source and Destination

MAC, EtherType, VLAN, Ingress Port-

Id.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 77

Page 78

LAG Hashing Fields used for 7210 SAS-R6 and 7210 SAS-R12

Table 13: LAG Hashing mechanism for services configured on 7210 SAS-R6 and 7210 SAS-R12 devices

Services and Traffic

direction (For example-

SAP to SDP)

VPLS Service:

SDP to SAP

Epipe Service:

SDP to SAP

Packet fields used for Hashing for

different traffic types with hash-1

All traffic (Unlearnt)

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, number of active ports.

IP traffic (Learnt): Source and Destination MAC, MPLS Label Stack (Two labels deep), Source and Destination L4 ports, VLAN

All other traffic(Learnt): Source and Destination MAC(Outer MACs inside the payload, just after the MPLS header), EtherType.

IP traffic: Source and Destination MAC, MPLS Label Stack (Two labels deep), Source and Destination L4 ports, VLAN

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

All traffic (Unlearnt)

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, number of active ports.

All traffic (Learnt): Source and Destination MAC(Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id

All traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id

All other traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), EtherType.

VPLS service:

SDP to SDP

All traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header)

All traffic (Learnt and Unlearnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id

All traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Page 78 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 79

Interface Configuration

Table 13: LAG Hashing mechanism for services configured on 7210 SAS-R6 and 7210 SAS-R12 devices

Services and Traffic

direction (For example-

SAP to SDP)

Packet fields used for Hashing for

different traffic types with hash-1

MPLS – LSR All traffic: Source and Destination

MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet)

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

All traffic: MPLS label stack (Three labels deep), Ingress Port-Id, Source and Destination IP (if MPLS labels are <= 3, when IP header follows MPLS header), Ingress Port-Id

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 79

Page 80

LAG Hashing Fields used for 7210 SAS-R6 and 7210 SAS-R12

Table 13: LAG Hashing mechanism for services configured on 7210 SAS-R6 and 7210 SAS-R12 devices

Services and Traffic

direction (For example-

SAP to SDP)

VPLS Service (Multicast Traffic with IGMP Snooping Enabled)

SAP to SAP SDP to SAP

NOTES:

• VPLS service, Multicast traffic with IGMP snooping enabled for SAP to SDP flow and SDP to SDP flow is as described above.

• ‘mgid’ is the Multicast Group ID and is a software allocated number. A unique number is allocated per Layer-2 multicast MAC address.

• 7210 supports Layer-2 multicast in a VPLS service. A group of 32 multicast IP addresses maps to a single Layer2 multicast MAC address. The 'mgid' parameter remains the same for all the IP multicast address that map to the same Layer2 multicast MAC address

Packet fields used for Hashing for

different traffic types with hash-1

Based on LAG SAP parameters

: service-id, lag_index, encap_value, service_vlan, mgid, sap_index, number of active ports.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

Based on LAG SAP parameters9: serviceid, lag_index, encap_value, service_vlan, mgid, sap_index, number of active ports.

Page 80 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 81

Interface Configuration

Table 13: LAG Hashing mechanism for services configured on 7210 SAS-R6 and 7210 SAS-R12 devices

Services and Traffic

direction (For example-

SAP to SDP)

VPRN service:

SAP to SAP SDP to SAP

VPRN service:

SAP to SDP

IES service (IPv4):

IES SAP to IES SAP

IES service (IPv4):

IES SAP to IPv4 network port interface

Packet fields used for Hashing for

different traffic types with hash-1

Source and Destination IP, Source and Destination L4 ports

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

Source and Destination IP, Source and Destination L4 ports, Ingress port-Id

Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

Network port IPv4 interface:

Source and Destination IP, Source and Destination L4 ports

Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

IPv4 network interface to IPv4 network interface

Network port IPv6 interface:

Source and Destination IP(v6), Source and Destination L4 ports

Source and Destination IP(v6), Source and Destination L4 ports, Ingress Port-Id.

IPv6 network interface to IPv6 network interface

1. ‘service_id’ refers to the service id of the egressing VPLS/EPIPE/IES/VPRN service.

2. ‘lag_index’ refers to the Lag-IfIndex of the egressing lag.

3. 'encap_value' and 'service_vlan' are based on the inner/outer VLAN values of the egressing LAG SAP.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 81

Page 82

LAG Hashing Fields used for 7210 SAS-R6 and 7210 SAS-R12

4. 'sap_index' is a value assigned uniquely for each SAP internally.

5. 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.

6. ‘Learnt’ wherever mentioned corresponds to Destination MAC.

7. Source/Destination MAC refer to ‘Customer Source/Destination MACs’ unless otherwise specified.

8. In case of a lag with 2 ports at the egress, different Ingress port-Ids may result in the 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.

9. Hash function is implemented in software. Does not use hash-1 or hash-2.

Page 82 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 83

Interface Configuration

LAG Hashing Fields used for 7210 SAS-Mxp

Table 14: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices

Services and Traffic

direction (For example-

SAP to SDP)

VPLS and Epipe Services:

SAP to SAP

Packet fields used for Hashing for

different traffic types with hash-1

Sap Based Egress Scheduling

All traffic (Learnt and Unlearnt): Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, , number of active ports.

Port Based Egress Scheduling:

All traffic(VPLS Unlearnt)

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, , number of active ports.

All other Traffic(VPLS Learnt and Epipe): IP traffic: Source and Destination IP, Source and Destination L4 ports.

MPLS and Non-IP traffic: Source and Destination MAC, EtherType, VLAN.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

Sap Based Egress Scheduling

All traffic (Learnt and Unlearnt): Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, , number of active ports.

Port Based Egress Scheduling:

All traffic(VPLS Unlearnt)

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, , number of active ports.

All other Traffic(VPLS Learnt and Epipe): IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

MPLS traffic: MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN, Ingress PortId

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 83

Page 84

LAG Hashing Fields used for 7210 SAS-Mxp

Table 14: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices (Continued)

Services and Traffic

direction (For example-

SAP to SDP)

VPLS Service:

SAP to SDP

Epipe Service:

SAP to SDP

Packet fields used for Hashing for

different traffic types with hash-1

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

MPLS traffic (Learnt): Source and Destination MAC, VLAN MPLS traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN Non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

IP traffic: Source and Destination IP, Source and Destination L4 ports

MPLS traffic: Source and Destination MAC, VLAN

Non-IP traffic: Source and Destination MAC, EtherType, VLAN

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

MPLS traffic (Learnt and Unlearnt): MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC, EtherType, VLAN, Ingress Port-Id.

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id.

MPLS traffic: MPLS label stack (Two labels deep), Ingress Port-Id.

Non-IP traffic: Source and Destination MAC, EtherType, VLAN, Ingress PortId.

Page 84 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 85

Interface Configuration

Table 14: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices (Continued)

Services and Traffic

direction (For example-

SAP to SDP)

VPLS and Epipe Services:

SDP to SAP

Packet fields used for Hashing for

different traffic types with hash-1

Sap Based Egress Scheduling:

All traffic (including VPLS Learnt

and Unlearnt)

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, , number of active ports.

Port Based Egress Scheduling:

All traffic (VPLS Unlearnt)

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, , number of active ports.

All other Traffic(VPLS Learnt and Epipe): Source and Destination MAC(Outer MACs inside the payload, just after the MPLS header)

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

Sap Based Egress Scheduling:

All traffic (including VPLS Learnt and

Unlearnt)

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, , number of active ports.

Port Based Egress Scheduling:

All traffic (VPLS Unlearnt)

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index, , number of active ports.

All other Traffic(VPLS Learnt and Epipe): Source and Destination MAC(Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id

VPLS Service:

SDP to SDP

All traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header

All traffic (Learnt and Unlearnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress PortId.

All traffic(Unlearnt): Hash-2 and parameter under hash-2 used.

MPLS – LSR All traffic: Source and Destination

MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet)

All traffic: MPLS label stack (Three labels deep), Ingress Port-Id, Source and Destination IP (if MPLS labels are <= 3, when IP header follows MPLS header), Ingress Port-Id

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 85

Page 86

LAG Hashing Fields used for 7210 SAS-Mxp

Table 14: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices (Continued)

Services and Traffic

direction (For example-

SAP to SDP)

VPLS Service (Multicast Traffic with IGMP Snooping Enabled)

SAP to SAP SDP to SAP

NOTES:

• VPLS service, Multicast traffic with IGMP snooping enabled for SAP to SDP flow and SDP to SDP flow is as described above.

• ‘mgid’ is the Multicast Group ID and is a software allocated number. A unique number is allocated per Layer-2 multicast MAC address.

Packet fields used for Hashing for

different traffic types with hash-1

Based on LAG SAP parameters

: service-id, lag_index, encap_value, service_vlan, mgid, sap_index, number of active ports.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

Based on LAG SAP parameters9: service-id, lag_index, encap_value, service_vlan, mgid, sap_index, number of active ports.

Page 86 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 87

Interface Configuration

Table 14: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices (Continued)

Services and Traffic

direction (For example-

SAP to SDP)

VPRN service:

SAP to SAP SDP to SAP

VPRN service:

SAP to SDP

IES service (IPv4):

IES SAP to IES SAP

Packet fields used for Hashing for

different traffic types with hash-1

Sap Based Egress Scheduling

All traffic: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index and number of active ports.

Port Based Egress Scheduling:

All traffic: Based on traffic parameters: Source-IP, DestinationIP, Source and destination L4 ports.

Sap Based Egress Scheduling:

All traffic

: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index and number of active ports.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

Sap Based Egress Scheduling9:

All traffic: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index and number of active ports.

Port Based Egress Scheduling:

All traffic: Based on traffic parameters: Source-IP, Destination-IP, Source and destination L4 ports, ingress port-Id

All traffic: Based on traffic parameters: Source-IP, Destination-IP, Source and destination L4 ports, Ingress port-Id

Sap Based Egress Scheduling:

All traffic9: Based on LAG SAP parameters: service-id, lag_index, encap_value, service_vlan, sap_index and number of active ports.

IES service (IPv4):

IES SAP to IPv4 network port interface

Port Based Egress Scheduling:

All traffic: Based on traffic parameters: Source-IP, DestinationIP, Source and destination L4 ports.

Port Based Egress Scheduling:

All traffic: Based on traffic parameters: Source-IP, Destination-IP, Source and destination L4 ports, ingress port-Id

All traffic: Based on traffic parameters: Source-IP, Destination-IP, Source and destination L4 ports , Ingress port-Id

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 87

Page 88

LAG Hashing Fields used for 7210 SAS-Mxp

Table 14: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices (Continued)

Services and Traffic

direction (For example-

SAP to SDP)

Network port IPv4 interface:

IPv4 network interface to IPv4 network interface

Network port IPv6 interface:

IPv6 network interface to IPv6 network interface

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.

Packet fields used for Hashing for

different traffic types with hash-1

All traffic: Based on traffic parameters: Source-IP, DestinationIP, Source and destination L4 ports.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

All traffic: Based on traffic parameters: Source-IP, Destination-IP, Source and destination L4 ports. , Ingress port-Id

Page 88 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 89

Interface Configuration

LAG Hashing Fields used for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE

Table 15: LAG Hashing mechanism for services configured on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices

Services and Traffic

direction (For example:

SAP to SDP)

VPLS Service:

SAP to SAP

Packet fields used for Hashing for

different traffic types with hash-1

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt): BDA, BSA, VLAN, EtherType PBB traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

MPLS traffic (Learnt): Source and Destination MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet), VLAN, EtherType MPLS traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Non-IP traffic (Learnt): Source and Destination MAC, VLAN, EtherType Non-IP traffic (Unlearnt): ): Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic (Learnt and Unlearnt): BDA, BSA, ISID, EtherType, Ingress Port-Id

MPLS traffic (Learnt and Unlearnt): MPLS label stack (Three labels deep), Source and Destination IP (if MPLS labels are <= 3, when IP header follows MPLS header), Ingress Port-Id

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC, VLAN, EtherType, Ingress Port-Id

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 89

Page 90

LAG Hashing Fields used for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE

Table 15: LAG Hashing mechanism for services configured on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices (Continued)

Services and Traffic

direction (For example:

SAP to SDP)

Epipe Service:

SAP to SAP

VPLS Service:

SAP to SDP

Packet fields used for Hashing for

different traffic types with hash-1

IP traffic: Source and Destination IP, Source and Destination L4 ports

PBB traffic: BDA, BSA, VLAN, EtherType

MPLS traffic: Source and Destination MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet), VLAN, EtherType

Non-IP traffic: Source and Destination MAC, VLAN, EtherType

IP traffic (Learnt): Source and Destination IP, Source and Destination L4 ports IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

PBB traffic (Learnt): BDA, BSA, EtherType PBB traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

MPLS traffic (Learnt): Source and Destination MAC, VLAN MPLS traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Non-IP traffic (Learnt): Source and Destination MAC, EtherType, VLAN Non-IP traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic: BDA, BSA, ISID, EtherType, Ingress Port-Id

MPLS traffic: MPLS label stack (Three labels deep), Source and Destination IP (if MPLS labels are <= 3, when IP header follows MPLS header), Ingress Port-Id

Non-IP traffic: Source and Destination MAC, VLAN, EtherType, Ingress PortId

IP traffic (Learnt and Unlearnt): Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic (Learnt and Unlearnt): BDA, BSA, ISID, EtherType, Ingress Port-Id

MPLS traffic (Learnt and Unlearnt): MPLS label stack (Three labels deep), Source and Destination IP (if MPLS labels are <= 3, when IP header follows MPLS header), Ingress Port-Id

Non-IP traffic (Learnt and Unlearnt): Source and Destination MAC, EtherType, VLAN, Ingress Port-Id

Page 90 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 91

Interface Configuration

Table 15: LAG Hashing mechanism for services configured on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices (Continued)

Services and Traffic

direction (For example:

SAP to SDP)

Epipe service:

SAP to SDP

VPLS service:

SDP to SAP

Packet fields used for Hashing for

different traffic types with hash-1

IP traffic: Source and Destination IP, Source and Destination L4 ports

PBB traffic: BDA, BSA, EtherType

MPLS traffic: Source and Destination MAC, VLAN

Non-IP traffic: Source and Destination MAC, EtherType, VLAN

IP traffic (Learnt): Source and Destination MAC, MPLS Label Stack (Two labels deep), Source and Destination L4 ports, VLAN

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

IP traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port-Id

PBB traffic: BDA, BSA, ISID, EtherType, Ingress Port-Id

MPLS traffic: MPLS label stack (Three labels deep), Source and Destination IP (if MPLS labels are <= 3, when IP header follows MPLS header), Ingress Port-Id

Non-IP traffic: Source and Destination MAC, EtherType, VLAN, Ingress PortId

All traffic (Learnt and Unlearnt): Src & dst MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id.

PBB traffic (Learnt): BDA, BSA, EtherType

Non-IP traffic(Learnt) : Source and Destination MAC, EtherType

All traffic(Unlearnt): Hash-2 and parameter under hash-2 used.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 91

Page 92

LAG Hashing Fields used for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE

Table 15: LAG Hashing mechanism for services configured on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices (Continued)

Services and Traffic

direction (For example:

SAP to SDP)

Epipe service:

SDP to SAP

VPLS service:

SDP to SDP

Packet fields used for Hashing for

different traffic types with hash-1

IP traffic: Source and Destination MAC, MPLS Label Stack (Two labels deep), Source and Destination L4 ports, VLAN

PBB traffic: BDA, BSA, EtherType

Non-IP traffic: src & dst MAC, EtherType

All Traffic (Learnt): Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header)

All Traffic (Unlearnt): Hash-2 and parameter under hash-2 used.

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

All traffic: Src & dst MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id.

All Traffic: Source and Destination MAC (Outer MACs inside the payload, just after the MPLS header), Ingress Port-Id

MPLS – LSR All traffic: Source and Destination

MAC (Outer MACs of the ethernet packet that encapsulates MPLS packet)

VPLS IGMP Snooping VPLS (Multicast traffic with IGMP snooping

IP Multicast traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port id

enabled)

L2 Multicast traffic: Source and

SAP to SAP

Destination MAC, EtherType, VLAN

SAP to SDP

All traffic: MPLS label stack (Three labels deep), Source and Destination IP (being used when IP header follows MPLS header), Ingress Port-Id

IP Multicast traffic: Source and Destination IP, Source and Destination L4 ports, Ingress Port id

L2 Multicast traffic: Source and Destination MAC, EtherType, VLAN

Page 92 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 93

Interface Configuration

Table 15: LAG Hashing mechanism for services configured on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices (Continued)

Services and Traffic

direction (For example:

SAP to SDP)

VPLS IGMP Snooping VPLS (Multicast traffic with IGMP snooping enabled)

SDP to SAP SDP to SDP

VPRN service:

SAP to SAP SDP to SAP

VPRN service:

SAP to SDP

IES service (IPv4):

IES SAP to IES SAP

Packet fields used for Hashing for

different traffic types with hash-1

Source and Destination MAC, Ingress Port Id

Source and Destination IP, Source and Destination L4 ports

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

Source and Destination MAC, Ingress Port Id

Source and Destination IP, Source and Destination L4 ports, Ingress port-Id

IES service (IPv4):

Source and Destination IP, Source and Destination L4 ports

Source and Destination IP, Source and

Destination L4 ports, Ingress Port-Id. IES SAP to IPv4 network port interface

Network port IPv4 interface:

Source and Destination IP, Source and Destination L4 ports

Source and Destination IP, Source and

Destination L4 ports, Ingress Port-Id.

IPv4 network interface to IPv4 network interface

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 93

Page 94

LAG Hashing Fields used for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE

Table 15: LAG Hashing mechanism for services configured on 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE devices (Continued)

Services and Traffic

direction (For example:

SAP to SDP)

Network port IPv6 interface:

IPv6 network interface to IPv6 network interface

Notes:

1. ‘Learnt’ wherever mentioned corresponds to Destination MAC.

2. Source/Destination MAC refer to ‘Customer Source/Destination MACs’ unless otherwise specified.

Packet fields used for Hashing for

different traffic types with hash-1

Source and Destination IP(v6), Source and Destination L4 ports

Packet fields used for Hashing for dif-

ferent traffic types with hash-2

Source and Destination IP(v6), Source and Destination L4 ports, Ingress PortId.

Page 94 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 95

Interface Configuration

ECMP Hashing fields used for 7210 SAS devices in Network mode

Table 16: ECMP Hashing mechanism for services configured on 7210 SAS devices in network.

Services Traffic Type A B ECMP Hashing

IP (For

routed

Unicast

traffic

Network Port

IP Interface

traffic)

IES IPv4 traffic SAP or

Network Port

IP interface

Network Port

Interface

SAP or

Network Port

IP interface

• Source and Destination IP

• Source and Destination L4 ports

• Ingress Port-Id

• Source and Destination IP

• Source and Destination L4 ports

• Ingress Port-Id

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 95

Page 96

Multi-Chassis LAG

This section describes the Multi-Chassis LAG (MC-LAG) concept. MC-LAG is an extension of a LAG concept that provides node-level redundancy in addition to link-level redundancy provided by “regular LAG”.

Note: This feature is supported only on 7210 SAS-R6, 7210 SAS-R12,7210 SAS-X, 7210 SAS-M, 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE network mode. It is not supported on 7210 SAS-T and 7210 SAS-M access-uplink mode.

Typically, MC-LAG is deployed in a network-wide scenario providing redundant connection between different end points. The whole scenario is then built by combination of different mechanisms (for example, MC-LAG and redundant pseudowire to provide e2e redundant p2p connection or dual homing of DSLAMs in Layer 2/3 TPSDA).

NOTE: The 7210 SAS platforms configured in access-uplink mode cannot peer with an MCLAG-enabled node since it does not implement MC-LAG protocol. In other words, 7210 SASM,T in access-uplink mode cannot provide MC-LAG server functionality. Instead they can be used as MC-LAG clients, with the platforms connected to a head-end node that support MC-LAG server functionality. These platforms connect to the head-end node using LAG.

Overview

Multi-chassis LAG is a method of providing redundant Layer 2/3 access connectivity that extends beyond link level protection by allowing two systems to share a common LAG end point.

The multi-service access node (MSAN) node is connected with multiple links towards a redundant pair of Layer 2/3 aggregation nodes such that both link and node level redundancy, are provided. By using a multi-chassis LAG protocol, the paired Layer 2/3 aggregation nodes (referred to as redundant-pair) appears to be a single node utilizing LACP towards the access node. The multichassis LAG protocol between redundant-pair ensures a synchronized forwarding plane to/from the access node and is used to synchronize the link state information between the redundant-pair nodes such that proper LACP messaging is provided to the access node from both redundant-pair nodes.

In order to ensure SLAs and deterministic forwarding characteristics between the access and the redundant-pair node, the multi-chassis LAG function provides an active/standby operation towards/from the access node. LACP is used to manage the available LAG links into active and standby states such that only links from 1 aggregation node are active at a time to/from the access node.

Characteristics related to MC are:

Page 96 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 97

Interface Configuration

• Selection of the common system ID, system-priority and administrative-key are used in LACP messages so partner systems consider all links as the part of the same LAG.

• Extension of selection algorithm in order to allow selection of active sub-group.

− The sub-group definition in LAG context is still local to the single box, meaning that

even if sub-groups configured on two different systems have the same sub-group-id they are still considered as two separate subgroups within given LAG.

− Multiple sub-groups per PE in a MC-LAG is supported.

− In case there is a tie in the selection algorithm, for example, two sub-groups with

identical aggregate weight (or number of active links) the group which is local to the system with lower system LACP priority and LAG system ID is taken.

• Providing inter-chassis communication channel allows inter-chassis communication to support LACP on both system. This communication channel enables the following:

− Supports connections at the IP level which do not require a direct link between two

nodes. The IP address configured at the neighbor system is one of the addresses of the system (interface or loop-back IP address).

− The communication protocol provides heartbeat mechanism to enhance robustness of

the MC-LAG operation and detecting node failures.

− Support for operator actions on any node that force an operational change.

− The LAG group-ids do not have to match between neighbor systems. At the same

time, there can be multiple LAG groups between the same pair of neighbors.

− Verification that the physical characteristics, such as speed and auto-negotiation is

configured and initiates operator notifications (traps) if errors exist. Consistency of MC-LAG configuration (system-id, administrative-key and system-priority) is provided. Similarly, load-balancing mode of operation must be consistently configured on both nodes.

− Traffic over the signalling link is encrypted using a user configurable message digest

key.

• MC-LAG function provides active/stand-by status to other software applications in order to built a reliable solutions.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 97

Page 98

Multi-Chassis LAG

MSANA

PE-A

PE-B

IP MPLS

Network

MG-

LAG

MSAN

PE-D

PE-C

MGLAG

MSANB

PE-A

PE-B

IP MPLS

Network

MG-

LAG

MSAN

PE-C

Figure 4: MC-LAG L2 Dual Homing to Remote PE Pairs

Figure 4 depicts different combinations of MC-LAG attachments supported. The supported

configurations can be sub-divided into following sub-groups:

• Dual-homing to remote PE pairs

− both end-points attached with MC-LAG

− one end-point attached

• Dual-homing to local PE pair

− both end-points attached with MC-LAG

− one end-point attached with MC-LAG

− both end-points attached with MC-LAG to two overlapping pairs

Page 98 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Page 99

Interface Configuration

MSANPW

MGLAG

MSANA

PE-A

PE-B

MGLAG

PWB

MSAN

PE-A

PE-B

MGLAG

PWMSANC

PE-A

MSAN

MGLAG

PE-B

MGLAG

PE-C

Figure 5: MC-LAG L2 Dual Homing to Local PE-Pairs

The forwarding behavior of the nodes abide by the following principles. Note that logical destination (actual forwarding decision) is primarily determined by the service (VPLS or VLL) and then principle below applies only if destination or source is based on MC-LAG:

• Packets received from the network will be forwarded to all local active links of the given destination-sap based on conversation hashing. In case there are no local active links, the packets will be cross-connected to inter-chassis pseudowire.

• Packets received from the MC-LAG sap will be forwarded to active destination pseudowire or active local links of destination-sap. In case there are no such objects available at the local node, the packets will be cross-connected to inter-chassis pseudowire.

7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide Page 99

Page 100

Multi-Chassis LAG

Aggregation

node

Aggregation

node

MSANMSAN

Aggregation

node

Aggregation

node

Inter-chassis PW for VLL

Active

Standby

TLDP

Standby Active

Active

Inter-chassis

PW for VLL

Aggregation

node

Aggregation

node

MSANMSAN

Aggregation

node

Aggregation

node

Inter-chassis PW for VLL

Active

Standby

TLDP

Active

Inter-chassis

PW for VLL

Point-to-Point (p2p) Redundant Connection Across Layer 2/3 VPN Network

Figure 6: P2P Redundant Connection Through a Layer 2 VPN Network

Figure 6 shows the connection between two multi-service access nodes (MSANs) across network

based on Layer 2/3 VPN pseudo-wires. The connection between MSAN and a pair of PE routers is realized by MC-LAG. From MSAN perspective, redundant pair of PE routers acts as a single partner in LACP negotiation. At any point in time, only one of the routers has an active link(s) in a given LAG. The status of LAG links is reflected in status signaling of pseudo-wires set between all participating PEs. The combination of active and stand-by states across LAG links as well and pseudo-wires give only 1 unique path between pair of MSANs.

Page 100 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide

Nokia 7210 SAS-M, 7210 SAS-Mxp, 7210 SAS-T, 7210 SAS-Sx, 7210 SAS-S Configuration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

TABLE OF CONTENTS

LIST OF TABLES

LIST OF FIGURES

About This Guide

Preface

Audience

List of Technical Publications

GETTING STARTED

In This Chapter

Alcatel-Lucent 7210 SAS-M, T, X, R6, R12, Mxp, Sx/S Router Configuration Process

In This Chapter

7210 SAS-SERIES INTERFACES

Configuration Overview

Chassis Slots and Cards

Provisioning of MDA on 7210 SAS-M

MDAs

Digital Diagnostics Monitoring

Nokia SFPs and XFPs

Statistics Collection

Port Types

Ports

Port Modes

Port Dot1q VLAN Etype

Configuration guidelines for Dot1q-etype

Support for Power over Ethernet (PoE) on 7210 SAS-T and 7210 SAS-Mxp ETR units

Support for PoE/PoE+ using combo-ports with 7210 SAS-Sx 1/10GE Fiber variant

Support for PoE/PoE+ for 7210 SAS-Sx 1/10GE Copper PoE variant

Link Layer Discovery Protocol (LLDP)

LLDP Protocol Features

LLDP Tunneling for Epipe Service

Port loopback without MAC swap

Port loopback for Ethernet ports

Port loopback with MAC swap

LAG Features

Configuring LAGs

LAG on Access

LAG and QoS Policies on 7210 SAS-M, 7210 SAS-T, 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE

LAG and QoS policies on 7210 SAS-Mxp

LAG and QoS policies on 7210 SAS-X

LAG and QoS policies on 7210 SAS-R6 and 7210 SAS-R12

Port Link Damping

LACP

LAG Subgroups

LAG and ECMP Hashing

LAG Hashing Fields used for 7210 SAS-M (Network mode)

LAG Hashing Fields used for 7210 SAS-X

LAG Hashing Fields used for 7210 SAS-M (Access-Uplink mode)

LAG Hashing Fields used for 7210 SAS-T Access-Uplink mode

LAG Hashing Fields used for 7210 SAS-T Network Mode

LAG Hashing Fields used for 7210 SAS-R6 and 7210 SAS-R12

LAG Hashing Fields used for 7210 SAS-Mxp

LAG Hashing Fields used for 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE

ECMP Hashing fields used for 7210 SAS devices in Network mode

Multi-Chassis LAG

Overview

Point-to-Point (p2p) Redundant Connection Across Layer 2/3 VPN Network