3HE10383AAACTQZZA_V1_7210 SAS M T X R6 R12 Mxp OS Interface Configuration Guide

7/26/2019 3HE10383AAACTQZZA_V1_7210 SAS M T X R6 R12 Mxp OS Interface Configuration Guide

1/348

Alcatel-LucentService Access Switch| Release 8.0 Rev.047 2 1 0 S A S M , T , X , R 6 , R 1 2 , M x p O S

I n t e r f a c e C o n f i g u r a t i o n G u i d e

3HE10383AAACTQZZA

3HE10383AAACTQZZA

Alcatel-Lucent Proprietary & ConfidentialContains proprietary/trade secret information which is the property of Alcatel-Lucent. Not to be made availableto, or copied or used by anyone who is not an employee of Alcatel-Lucent except when there is a valid nondisclosureagreement in place which covers such information and contains appropriate non-disclosure andlimited use obligations.Copyright 2015 Alcatel-Lucent. All rights reserved.All specifications, procedures, and information in this document are subject to change and revision at any timewithout notice. The information contained herein is believed to be accurate as of the date of publication. AlcatelLucent


2/348


3/348

7210 SAS M, T, X, R6, R12, Mxp Interface Configuration Guide Page 1

TABLEOFCONTENTS

Alcatel-Lucent 7210 SAS-M, T, X, R6, R12, and Mxp Router Configuration Process . . . . . . . . . . . . . . . . .7

7210 SAS-Series InterfacesConfiguration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Chassis Slots and Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11MDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Provisioning of MDA on 7210 SAS-M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Digital Diagnostics Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Alcatel-Lucent SFPs and XFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Statistics Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Port Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Port Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Configuration guidelines for Dot1q-etype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Support for Power over Ethernet (PoE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Link Layer Discovery Protocol (LLDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

LLDP Protocol Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

LLDP Tunneling for Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Port loopback for Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Port loopback without MAC swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Port loopback with MAC swap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34LAG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

LAG Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Configuring LAGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

LAG on Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37LAG and QoS Policies on 7210 SAS-M, and 7210 SAS-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38LAG and QoS policies on 7210 SAS-Mxp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

LAG and QoS policies on 7210 SAS-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39LAG and QoS policies on 7210 SAS-R6 and 7210 SAS-R12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Port Link Damping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

LAG Subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41LAG and ECMP Hashing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43LAG Hashing Fields used for 7210 SAS-M (Network mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

LAG Hashing Fields used for 7210 SAS-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51LAG Hashing Fields used for 7210 SAS-M (Access-Uplink mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

LAG Hashing Fields used for 7210 SAS-T Access-Uplink mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55LAG Hashing Fields used for 7210 SAS-T Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

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

LAG Hashing Fields used for 7210 SAS-Mxp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66ECMP Hashing fields used for 7210 SAS devices in Network mode . . . . . . . . . . . . . . . . . . . . . . . .70

Multi-Chassis LAG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Point-to-Point (p2p) Redundant Connection Across Layer 2/3 VPN Network . . . . . . . . . . . . . . . . .75DSLAM Dual Homing in Layer 2 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77


4/348

Page 2 7210 SAS M, T, X, R6, R12, Mxp Interface Con-

Table of Contents

Configuring Multi-Chassis Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78G.8032 Protected Ethernet Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

802.3ah OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86OAM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Remote Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

802.3ah OAM PDU Tunneling for Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88MTU Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Deploying Pre-provisioned Components for 7210 SAS-M, 7210 SAS-X, 7210 SAS-T, and 7210 SAS-Mxp.90

Deploying Pre-provisioned Components for 7210 SAS-R6 and 7210 SAS-R12. . . . . . . . . . . . . . . . . .90Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Configuring Physical Ports with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Preprovisioning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Predefining Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Pre-provisioning a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Basic Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Configuring Cards and MDAs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99Configuration Notes for provisioning of cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Configuration Notes for provisioning of 7210 SAS-R6 IMMv2 cards. . . . . . . . . . . . . . . . . . . . . . . . . .100Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103Configuring Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Configuring Ethernet Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Ethernet Network Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Ethernet Access uplink Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Ethernet Access Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Configuring 802.1x Authentication Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107Configuring Channelized Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Configuring a Channelized DS1 Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Configuring LAG Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110CRC Error Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Modifying a Card Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Deleting a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114Deleting Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

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


5/348


LISTOFTABLES

Table 1: Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Table 2: Real-Time DDM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Table 3: DDM Alarms and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Table 4: Supported Ethernet ports and TDM ports types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Table 5: 7210 SAS Platforms supporting port modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Table 6: Behavior for LLDP with different values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Table 7: LAG Hashing mechanism for services configured in Network Mode on 7210 SAS-M devices .45Table 8: LAG Hashing mechanism for services configured on 7210 SAS-X devices . . . . . . . . . . . . . . .51

Table 9: LAG Hashing mechanism for services configured in Access-Uplink mode on 7210 SAS-M . . .54Table 10: LAG Hashing mechanism for services configured on 7210 SAS-T Access-Uplink mode . . . . .55Table 11: LAG Hashing Fields used for 7210 SAS-T Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Table 12: LAG Hashing mechanism for services configured on 7210 SAS-R6 and 7210 SAS-R12 devices 62Table 13: LAG Hashing mechanism for services configured on 7210 SAS-Mxp devices . . . . . . . . . . . . .66

Table 14: ECMP Hashing mechanism for services configured on 7210 SAS devices in network. . . . . . .70

Table 15: MTU Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Table 16: Default values for sap-qos-marking in access and hybrid port modes

143Table 17: Sap-qos-marking default value when port mode is changed

143Table 18: Internal port resources on different IMMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153


6/348

Page 2 7210 SAS M, T, X, R6, R12, Mxp Interface Configu-

List of Tables


7/348


LISTOFFIGURES

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

Figure 2: Generic Customer Use Case For LLDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Figure 3: LAG Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Figure 4: MC-LAG L2 Dual Homing to Remote PE Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Figure 5: MC-LAG L2 Dual Homing to Local PE-Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Figure 6: P2P Redundant Connection Through a Layer 2 VPN Network. . . . . . . . . . . . . . . . . . . . . . . . .75

Figure 7: DSLAM Dual-Homing Using MC-LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Figure 8: 802.1x Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Figure 9: 802.1x Authentication Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Figure 10: 802.1x EAPOL Timers (left) and RADIUS Timers (right) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Figure 11: Slot, Card, MDA, and Port Configuration and Implementation Flow . . . . . . . . . . . . . . . . . . . . .92


8/348

Page 2 7210 SAS M, T, X, R6, R12, Mxp Interface Configu-

List of Figures


9/348

7210 SAS M, T, X, R6, R12, Mxp Interface Configuration GuidePage 3

Preface

About This Guide

This guide describes system concepts and provides configuration examples to provision input/output modules (IOMs), also referred to as cards, Media Dependent Adapters (MDAs), and portsprovided by 7210 SAS-M, T, X, R6, R12, and Mxp platforms.

On 7210 SAS devices, not all the CLI commands are supported on all the platforms and in all themodes. In many cases, the CLI commands are mentioned explicitly in this document. In othercases, it is implied and easy to know the CLIs that are not supported on a particular platform.

All the variants of 7210 SAS-M, 7210 SAS-T, and 7210 SAS-Mxp can be configured in twomodes, 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 toprovide service transport. The mode can be selected by configuring the BOF appropriately.

The 7210 SAS-Mxp platform is configured only in Network Mode. The BOF does not allow theuser to configure bof-uplink mode. By default, the mode is set to Network mode. In network mode

configuration 7210 SAS-Mxp uses IP/MPLS to provide service transport.

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 SAS-R12, 7210 SAS-X, and 7210 SAS-Mxp 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 theconfiguration 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-Mxpsupports 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 supportsonly MPLS uplinks and implicitly operates in network mode.

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


10/348

Preface

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

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

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

Audience

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

CLI concepts

MDA, and port configuration

QoS policies

Services


11/348

Preface

7210 SAS M, T, X, R6, R12, Mxp Interface Configuration GuidePage 5

List of Technical Publications

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

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

This guide describes basic system configurations and operations.

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

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

7210 SAS-M, T, X, R6, R12, Mxp 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 OS Router Configuration Guide

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

7210 SAS-M, T, Mxp and 7210 SAS-X, R6, R12 Services Guide

This guide describes how to configure service parameters such as customer informationand user services.

7210 SAS-M, T, X, R6, R12, Mxp 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 and 7210 SAS-X, R6, R12 Quality of Service GuideThis guide describes how to configure Quality of Service (QoS) policy management.

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

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

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

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


12/348

Preface

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

Technical Support

If you purchased a service agreement for your 7210 SAS series router and related products from adistributor or authorized re-seller, contact the technical support staff for that distributor or resellerfor assistance. If you purchased an Alcatel-Lucent service agreement, contact your welcomecenter:Web: http://www.alcatel-lucent.com/wps/portal/support


13/348


GETTINGSTARTED

In This Chapter

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

Alcatel-Lucent 7210 SAS-M, T, X, R6, R12, and Mxp RouterConfiguration Process

Table 1lists 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 andcards

Chassis Slots andCards on page 11

MDAs MDAs on page 15

Ports Ports on page 21

Reference List of IEEE, IETF,

and other proprietaryentities.

Standards and Proto-

col Support on page337


14/348

Getting Started

Page 8 7210 SAS M, T, X, R6, R12, Mxp Interface Configu-ration Guide


15/348


7210 SAS-SERIESINTERFACES

In This Chapter

This chapter provides information about configuring chassis slots, cards, and ports.

Topics in this chapter include:

Configuration Overview on page 10

Chassis Slots and Cards on page 11

MDAs on page 15

Digital Diagnostics Monitoring on page 17

Ports on page 21

Port Types on page 21

LAG on page 35

802.1x Network Access Control on page 80

MTU Configuration Guidelines on page 88

Deploying Pre-provisioned Components for 7210 SAS-M, 7210 SAS-X, 7210 SAS-T,and 7210 SAS-Mxp. on page 90

Configuration Notes on page 189


16/348

Configuration Overview

Page 10 7210

SAS M, T, X, R6, R12, Mxp Interface Configuration Guide


NOTE: This document uses the termpreprovisioningin the context of preparing orpreconfiguring 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 notenabled. When the entity is in a no shutdownstate (administratively enabled), then the entity isconsidered to beprovisioned.

The 7210 SAS-M and its variants (that is, 7210 SAS-M 24F, 7210 SAS-M 24F 2XFP, 7210 SAS-

M 24F 2XFP ETR), is a platform with a fixed port configuration and an additional expansion slotthat 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 theCPM 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 theplatform, and it is pre-provisioned on bootup. The second MDA, represents the physicalremovable MDA that can be plugged into the available expansion slot and it must be provisionedby the user depending on the MDA they plan to use (see below for more information onprovisioning MDA for the expansion slot on 7210 SAS-M). Ports and interfaces can also be pre-provisioned.

The 7210 SAS-X, 7210 SAS-T, and 7210 SAS-Mxp and its variants, are platforms with a fixedport 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. Thesoftware creates 2 logical cards, to represent the CPM and IOM and these are pre-provisioned onbootup. The IOM card, is modelled with a single MDA, a logical entity to represent the fixed portson the system. This MDA is auto-provisioned 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 cardsused for service delivery and 2 CPM slots that provide control-plane redundancy. The chassis slotsmust be provisioned to accept a specific line card and set the relevant configurations before theequipment is actually installed. The pre-provisioning ability allows you to plan yourconfigurations 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 theappropriate chassis slots when required.

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


17/348

Interface Configuration


Chassis Slots and Cards

The 7210 SAS-M 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 andsupported MDAs can be plugged into the expansion slot. The list of MDAs supported on 7210SAS-M is available in the 7210 SAS release notes.

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

Sample output for 7210 SAS-M:

A:7210# show card state

===============================================================================

Card State===============================================================================

Slot/ Provisioned Equipped Admin Operational Num Num Comments

Id Type Type State State Ports MDA-------------------------------------------------------------------------------

1 iom-sas iom-sas up up 21/1 m24-1gb+2-10gb m24-1gb+2-10gb up up 241/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, and 7210 SAS-Mxp 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 7210SAS-X, 7210 SAS-T, and 7210 SAS-Mxp chassis:

Sample output for 7210 SAS-X:

A:7210-SAS-X>show# card

===============================================================================

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

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

-------------------------------------------------------------------------------

1 iom-sas iom-sas up upA sfm-sas sfm-sas up up/active


18/348


Page 12 7210


===============================================================================A:7210-SAS-X>show#

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 upA sfm-sas up up/active

===============================================================================A:7210SAST>show#

Sample output for 7210 SAS-Mxp:

*A:sim_dutc>show# card state

===============================================================================Card State

===============================================================================

Slot/ Provisioned Type Admin Operational Num Num CommentsId Equipped Type (if different) State State Ports MDA

-------------------------------------------------------------------------------1 iom-sas up up 21/1 m22-sfp+2-tx+4-sfpp up up 24

A sfm-sas up up Active===============================================================================

*A:sim_dutc>show#

The 7210 SAS-R6 is a chassis based platform with 6 IMM slots and 2 CPM slots. On a chassisbased platform the slots must be provisioned. To pre-provision a chassis slot, the line card typemust be specified. System administrators or network operators can enter card type information foreach slot, allowing a range of card types in particular slots. From the range of card types, a cardand 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 notmatch, the card remains offline. A pre-provisioned slot can remain empty without conflicting withpopulated 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 andthe MDA type is auto-provisioned by software when the IMMs are provisioned. Please check thelatest release notes for a list of supported card types (that is, CPM and IMMs). For moreinformation on installation of cards, see the 7210 SAS-R6 Installation Guides.


19/348



The 7210 SAS-R12 is a chassis based platform with 12 IMM slots and 2 CPM slots. On a chassisbased platform the slots must be provisioned. To pre-provision a chassis slot, the line card typemust be specified. System administrators or network operators can enter card type information foreach slot, allowing a range of card types in particular slots. From the range of card types, a cardand accompanying MDAs (if any) are specified. When a card is installed in a slot and enabled, thesystem 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 withpopulated slots. 7210 SAS-R12 supports only CPM and IMMs. It does not support any physicalremovable MDAs. Software uses logical MDAs internally to represent the ports on the IMMs andthe MDA type is auto-provisioned by software when the IMMs are provisioned. Please check thelatest release notes for a list of supported card types (that is, CPM and IMMs). For moreinformation 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 asimm-sas-r-b) cannot be used simultaneously in the same node. In other words, all the slotsneed 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 sothat appropriate resources can be allocated on system bootup. Please see the commandconfig>system>chassis> allow-imm-familyin the 7210 SAS-M,X,T, R6, R12, MxpBasics System Configuration User Guide.

On 7210 SAS-R12, only IMMv2 (identified as imm-sas-r-b) is used. For moreinformation, see the 7210 SAS-M,X,T, R6, R12, Mxp Basics System Configuration UserGuide.

Sample output for 7210 SAS-R6:

*A:sasr_dutb>show# card

===============================================================================

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

Slot Provisioned Type Admin Operational Comments

Equipped Type (if different) State State

-------------------------------------------------------------------------------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 up6 imm-sas-2xfp up up

A cpm-sf-sas-R6 up up/activeB cpm-sf-sas-R6 up up/standby

===============================================================================

*A:sasr_dutb>show#


20/348


21/348



MDAs

The 7210 SAS-R6, R12, 7210 SAS-X, and 7210 SAS-T platforms, as explained in the previoussection, 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-provisionedon 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 expansionslot is available. It is represented as a physical MDA and needs to be provisioned. The sectionbelow 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 bepreprovisioned. 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 isprovisioned when a type designated from the allowed MDA type is inserted. A preprovisionedMDA 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 MDAand vice versa.

If a 2*10G MDA provisioned, it ensures that the BOF parameter "no-service-ports" isconfigured 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 rebootso 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 performthe following steps:

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


22/348


23/348


24/348


25/348


26/348


27/348



Ports

Port Types

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

NOTES:

10/100/1000 Base-T Copper SPFs can be used in the any of the SFP ports. It supports allspeeds.

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

Table 4: Supported Ethernet ports and TDM ports types

Ports 7210

SAS-M

7210 SAS-

M 24F2XFP

7210

SAS-M24F 2XFP

ETR

7210

SAS-X

7210

SAS-T

7210

SAS-R6

7210

SAS-R12

7210

SAS-Mxp

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

No No No No Yes IMMv2with

copperports

IMMv2 withcopperports

Yes

Fast EthernetSFP Ports

Yes Yes Yes Yes Yes Yes Yes Yes

10 GigabitXFP/SFP+Ports

Yes, with2 x 10G/

XFP

MDA

Yes-XFP Yes-XFP Yes-XFP Yes-XFP IMMv1- XFP

IMMv2

- SFP+

IMMv2 -

SFP+

Yes-SFP+

TDM ports(DS1/E1)

Yes(only innetwork

modeand with

CESMDA)

Yes (onlyin networkmode andwith CES

MDA)

Yes (onlyin

networkmode andwith CES

MDA)

No No No No No


28/348

Ports

Page 22 7210


Port Modes

In 7210 SAS devices, port must be configured as either access, access uplink or network.

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 anaccess port. When a port is configured for access mode, the appropriate encapsulation typemust be configured to distinguish the services on the port. Once a port has been configuredfor 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. Access-uplink ports Access-uplink ports are used to provide native Ethernet

connectivity in service provider transport or infrastructure network. This can be achievedby configuring port mode as access uplink. With this option, the encap-type can beconfigured to only qinq. Access-uplink SAPs, which are QinQ SAPs, can only beconfigured on an access uplink port to allow the operator to differentiate multiple servicesbeing carried over a single access uplink port. This is the default mode when a node isoperating in access-uplink mode.

Network ports Configured for network facing traffic. These ports participate in theservice 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 modeof an Ethernet port remains network, the mode of a port cannot be changed between theaccess/network/hybrid values unless the port is shut down and the configured SAPs and/orinterfaces are deleted. Hybrid ports allow a single port to operate in both access andnetwork modes. MTU of port in hybrid mode is the same as in network mode except forthe 10/100 MDA. The default encap for hybrid port mode is dot1q, it also supports QinQencapsulation 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 thevalue of 9212 bytes currently used in network mode (higher than an access port); this is toensure that both SAP and network VLANs can be accommodated. The only exception iswhen 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. Theconfiguration of all parameters in access and network contexts will continue to be donewithin the port using the same CLI hierarchy as in existing implementation. Thedifference is that a port configured in mode hybrid allows both ingress and egress contextsto be configured concurrently.


29/348



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 canbe achieved by configuring the port in the access mode, or a single network IP interface isallowed, which can be achieved by configuring the port in network mode. Hybrid modecan 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 notsupported on a hybrid port. The following port modes are supported on each of the 7210SAS platforms:

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 useethertype other than 0x8100.

Table 5: 7210 SAS Platforms supporting port modes

Port ModePlatforms

Access Network Hybrid Access-uplink

7210 SAS-M Yes Yesa

a Network ports can be configured only if the BOF is configured to operate the node innetwork mode (also known as, MPLS mode).

Yesb

b Hybrid ports are supported only when the node is operating in network mode.

Yesc

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 is configured in Network mode by default. It does not supportaccess-uplink mode.

7210 SAS-X Yes Yes Yes No

7210 SAS-T Yes Yesa Yesb Yesc

7210 SAS-R6 Yes Yes Yes No

7210 SAS-R12 Yes Yes Yes No

7210 SAS-Mxp No Yes Yes No


30/348

Ports

Page 24 7210


Priority tagged packet received with etype 0x8100 on a dot1q port configured with etype0x9100 are classified as priority tagged packet and mapped to a dot1q :0 SAP (ifconfigured) 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 toa 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). Thedot1q-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).


31/348


32/348


33/348




34/348

Link Layer Discovery Protocol (LLDP)

Page 28 7210



The IEEE 802.1ab Link Layer Discovery Protocol (LLDP) standard defines protocol andmanagement 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 orMANs, their points of interconnection, and access points for management protocols.

The LLDP helps the network operators to discover topology information. This information is usedto 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 onthe same IEEE 802 LAN is advertised.

Network management information from adjacent stations on the same IEEE 802 LAN isreceived.

Operates with all IEEE 802 access protocols and network media.

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

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


35/348



Figure 1: LLDP Internal Architecture for a Network Node

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

The example displayed in Figure 2depicts a MPLS network that uses Ethernet interfaces in thecore 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 2can be discovered if, IEEE 802.1ab LLDP isrunning on each of the Ethernet interfaces in network.

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


36/348


Page 30 7210


Figure 2: Generic Customer Use Case For LLDP

OSSG263

Ethernet Links - FE/GE/10GE

MPLS/Native ETH

Core

LAG

QinQSWs

DSLAMs

P

PE PE

PE PE

PE PE

P

SG/R

SG/R


37/348



LLDP Protocol Features

The IEEE 802.1ab Link Layer Discovery Protocol (LLDP) is a uni-directional protocol that usesthe MAC layer to transmit specific information related to the capabilities and status of the localdevice. The LLDP can send as well as receive information from a remote device stored in the

related MIB(s).

The LLDP does not contain a mechanism to solicit information received from other LLDP agents.The protocol also does not provide means to confirm the receipt of information. LLDP providesthe flexibility of enabling a transmitter and receiver separately, therefore the following LLDPconfigurations are allowed:

An LLDP agent can only transmit information.

An LLDP agent can only receive information.

An LLDP agent can transmit and receive information.

The information fields in each LLDP frame are contained in an LLDP Data Unit (LLDPDU) as asequence of variable length information elements. Each information element includes Type,

Length, and Value fields (TLVs).

Type indicates the nature of information being transmitted.

Length indicates the length of the information string in octets.

Value is the actual information that is transmitted. (For example, a binary bit map or analphanumeric string that can contain one or more fields).

Each LLDPDU contains four mandatory TLVs and optional TLVs selected by the Network

Management. Below is the format of a LLDPDU:

Chassis ID TLV

Port ID TLV

Time To Live TLV

Zero or more optional TLVs, depending on the maximum size of the LLDPDU allowed.

End Of LLDPDU TLV

An LLDP agent or port is identified by a concatenated string formed by the Chassis ID TLV and

the Port ID TLV. This string is used by a recipient to identify an LLDP port or agent. Thecombination of the Port ID and Chassis ID TLVs remains unchanged until the port or agent is

operational.

The TTL (Time To Live) field of an Time-To-Live TLV can be either zero or a non-zero value. A

zero value in the TTL field notifies the receiving LLDP agent to immediately discard allinformation related to the sending LLDP agent. A non-zero value in the TTL field indicates thetime duration for which the receiving LLDP agent should retain the sending LLDP agents


38/348


Page 32 7210


information. The receiving LLDP agent discards all information related to the sending LLDPagent after the time interval indicated in the TTL field is complete.

Note:A TTL value of zero can be used to signal that the sending LLDP port has initiated a portshutdown procedure.

The End Of LLDPDU TLV indicates the end of the LLDPDU.

LLDP Tunneling for Epipe Service

Customers who subscribe to Epipe service consider the Epipe as a wire, and run LLDP betweentheir devices which are located at each end of the Epipe. To facilitate this, the 7210 devicessupport 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 theEpipe service. To forward these frames transparently, the port on which tunneling is enabled mustbe 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 beset to disabled or Tx only, using the command admin-status available under configure> port>ethernet> lldp> destmac-nearest-bridge. If admin-statusfor dest-mac nearest-bridge is set toreceive and process nearest-bridge LLDPDUs (that is, if either rx or tx-rx is set) then it overridesthe tunnel-nearest-bridge-dest-maccommand.

The following table lists the behavior for LLDP with different values set in use for admin-status

and when tunneling is enabled or disabled:

NOTE: Transparent forwarding of LLDP frames can be achieved using the standard definedmechanism when using the either nearest-non-tmpr or the nearest-customer as the destinationMAC address in the LLDP frames. It is recommended that the customers use these MAC address

Table 6: 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


39/348



where possible to conform to standards. This command allows legacy LLDP implementations thatdo not support these additional destinations MAC addresses to tunnel LLDP frames that use thenearest-bridge destination MAC address.


40/348

Port loopback for Ethernet ports

Page 34 7210


Port loopback for Ethernet ports

7210 devices support port loopback for ethernet ports. There are two flavors of port loopbackcommands - port loopback without mac-swap and port loopback with mac-swap. Both these

commands are helpful for testing the service configuration and measuring performance parameterssuch as throughput, delay, and jitter on service turn-up. Typically, a third-party external test deviceis 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 thespecified 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 theservice configuration for the SAP.

This is recommended for use with only VLL services. This command affects all the servicesconfigured on the port, therefore the user is advised to ensure all the configuration guidelinesmentioned 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 thepackets are sent out the port configured for loopback and received back by the system. On ingressto the system after the loopback, the node swaps the MAC addresses for the specified SAP and theservice. 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 theservice configuration for the SAP.

This is recommended for use with only VPLS and VLL services. This command affects all theservices 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.


41/348



LAG

Based on the IEEE 802.3ax standard (formerly 802.3ad), Link Aggregation Groups (LAGs) canbe 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 linksparticipating in the LAG fail. All physical links in a given LAG links combine to form one logicalinterface.

Packet sequencing must be maintained for any given session. The hashing algorithm deployed byAlcatel-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 ControlProtocol (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

port types.

Software capabilities:

The Alcatel-Lucent solution conforms to the IEEE LAG implementation includingdynamic costing and LAG port threshold features. The dynamic cost and LAG portthreshold 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>lagdynamic-costcommand or by the

action specified in the config>lag>port-threshold command.If dynamic cost is enabled and the number of active links is greater than the portthreshold 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


42/348

LAG

Page 36 7210


links regardless of the specified port threshold action. If the port-threshold is met andthe action is set to dynamic cost, then the path cost is dynamically recalculatedregardless 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 isavailable at the time, providing the number of links that are up exceeds the configuredLAG port threshold value. If the number of available links falls below the configuredthreshold, 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 onelink 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 oflinks 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 thresholdThe LAG port threshold feature allows configuration of the behavior, once thenumber 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 theLAG is regarded as operationally down.For example, assume a LAG consists of four physical links. The threshold is set to two anddynamic costing is not configured. If the operational links is equal to or drops below two, thelink 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 LAGstarts 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 oper-ational) is advertised.


43/348



Configuring LAGs

LAG configuration guidelines include:

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

The showcommands display physical port statistics on a port-by-port basis or the entireLAG 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 andduplex. To guarantee the same port speed is used for all ports in a LAG, auto-negotiationmust be disabled or in limited mode to ensure only a specific speed is advertised.

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

Figure 3: LAG Configuration

LAG on Access

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

OSSG011

ALA-1 ALA-4

ALA-2

LAG-1

LAG-2

ALA-3


44/348

LAG

Page 38 7210


LAG and QoS Policies on 7210 SAS-M, and 7210 SAS-T

In the 7210 SAS-M and 7210 SAS-T an ingress QoS policy is applied to the aggregate traffic thatis received on all the member ports of the LAG. For example, if an ingress policy is configuredwith a policier of PIR 100Mbps, for a SAP configured on a LAG with two ports, then the policerlimits the traffic received through the two ports to a maximum of 100Mbps.

In the 7210 SAS-M and 7210 SAS-T an egress QoS policy parameters are applied to all the portsthat are members of the LAG (all ports get the full SLA). For example, if an egress policy isconfigured with a queue shaper rate of PIR 100Mbps, and applied to an access-uplink or accessLAG 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 thePIR is divided equally among all the member ports of the LAG is that, a single flow can use theentire SLA. The disadvantage is that, the overall SLA can be exceeded if the flows span multipleports.

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 IPinterface ingress QoS policy is applied to the aggregate traffic that enters the traffic through all theports of the system. For example, if an ingress policy is configured with a policier of PIR100Mbps, 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 aremembers of the LAG (all ports get the full SLA). For example, if an SAP egress policy isconfigured with a shaper of PIR 100Mbps, each port would get a PIR of 100 Mbps. The advantageof this method over a scheme where the PIR is divided equally among all the member ports of theLAG 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 portsthat are members of the LAG (all ports get the full SLA). For example, if an network port egresspolicy 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 memberports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is that the overallSLA can be exceeded if the flows span multiple ports.


45/348



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 IPinterface 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 PIR100Mbps, 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 aremembers of the LAG (all ports get the full SLA). For example, if an SAP egress policy isconfigured with a shaper of PIR 100Mbps, each port would get a PIR of 100 Mbps. The advantageof 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 canbe exceeded if the flows span multiple ports.

In 7210 SAS-X, network port egress QoS policy shaper parameters are applied to all the ports thatare members of the LAG (all ports get the full SLA). For example, if an network port egress policyis configured with a shaper of PIR 100Mbps, each port would get a PIR of 100 Mbps. Theadvantage of this method over a scheme where the PIR is divided equally among all the memberports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is that the overallSLA 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 entersthrough all the ports on a IMM. If the LAG has member ports on different IMMs, then the policyis created for each IMM and is applied to the aggregate traffic that enters through all the ports on agiven IMM. For example, if an ingress policy is configured with a policier of PIR 100Mbps, for aSAP 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,then policy is applied each IMM individually, and the policer on each IMM allows a maximum of100Mbps for a total of 200Mbps.

In 7210 SAS-R6 and 7210 SAS-R12, SAP egress QoS policy shaper parameters are applied to allthe ports that are members of the LAG (all ports get the full SLA), irrespective of whether they are


46/348

LAG

Page 40 7210


located on a single IMM or two different IMMs. For example, if an SAP egress policy isconfigured with a shaper of PIR 100Mbps, each port would get a PIR of 100Mbps. The advantageof this method over a scheme where the PIR is divided equally among all the member ports of theLAG is that, a single flow can uses the entire SLA. The disadvantage is that the overall SLA canbe exceeded if the flows span multiple ports.

In 7210 SAS-R6 and 7210 SAS-R12, network port egress QoS policy shaper parameters areapplied to all the ports that are members of the LAG (all ports get the full SLA), irrespective ofwhether they are located on a single IMM or two different IMMs.. For example, if an network portegress 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 themember ports of the LAG is that, a single flow can uses the entire SLA. The disadvantage is thatthe 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 transitionsreported to upper layer protocols.

The 7210 SAS OS port link damping feature guards against excessive port transitions. Any initialport transition is immediately advertised to upper layer protocols, but any subsequent porttransitions 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/orprovide redundancy. Both aspects are addressed by aggregating several Ethernet links in a singleLAG.

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

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.


47/348



Active-Standby LAG Operation without LACP

Active/standby LAG is used to provide redundancy while keeping consistency of QOSenforcement. 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-configuredselection-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 forstandby-signalling in the CLI command at the LAG level at the port member level. As aconsequence, the transmit laser will be switched off for all LAG members in standby mode. Onswitch over (active-links failed) the laser will be switched on all LAG members will becomeactive.

Note that this mode of operation cannot detect physical failures on the standby link, which meansthat the network operator cannot be certain that the standby links are capable to take over in caseof 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 expiredon 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, theselection-criteria best-portcan 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 selectioncriteria is selected.

LAG Subgroups

LACP is used to make selection of active links predictable and compatible with any vendorequipment. Refer to the IEEE STD 802.3-2002, Section 3, Clause 43.6.1 standard which describeshow 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 thenassures that only members of a single sub-group are selected as active links.

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


48/348

LAG

Page 42 7210


The algorithm will select active links based on following criteria:

Depending on selection-criteria setting either the sub-group with the highest numberof eligible links or the sub-group with the highest aggregate weight of all eligiblemembers is selected first.

If multiple groups satisfy the selection criteria, the sub-group being currently activeremains active. Initially, the sub-group containing the highest priority eligible link isselected.

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 becomeactive. This means it is operationally up, and if the slave-to-partner flag is set, theremote system did not disable its use (by signalling stand-by).

The selection algorithm works in a reverting mode. This means that every time theconfiguration 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 groupremains active (no reverting).


49/348



LAG and ECMP Hashing

Note: ECMP hashing is supported only on 7210 SAS devices in network mode.

When a requirement exists to increase the available bandwidth for a logical link that exceeds thephysical 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 thesame time, meaning, using ECMP of two or more Link Aggregation Groups (LAG) and/or singlelinks.The Alcatel-Lucent implementation supports per flow hashing used to achieve uniformloadspreading 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, differentvariables are used as input to the hashing algorithm.

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


50/348



LAG Hashing Fields used for 7210 SAS-M (Networkmode)

Table 7: LAG Hashing mechanism for services configured in Network Mode on 7210

SAS-M devices

Services and Traffic Direction

(For example: SAP to SDP)

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 DestinationIP, Source and Destination L4 ports, IngressPort-Id.

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

MPLS traffic (Learnt): Source and DestinationMAC (Outer MACs of the ethernet packet thatencapsulates MPLS packet), VLAN.

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

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

Non-IP traffic (Unlearnt): Source andDestination MAC, EtherType, VLAN, IngressPort-Id.


51/348

LAG

Page 46 7210


Epipe service:

SAP to SAP

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

PBB traffic: BDA, BSA, VLAN.

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

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

VPLS service:

SAP to SDP

IP traffic (learnt and unlearnt): Source and

Destination IP, Source and Destination L4ports, Ingress Port-Id.

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

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

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



SAS-M devices




traffic types


52/348



Epipe service:

SAP to SDP

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

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


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

VPLS service:

SDP to SAP

Learnt traffic (See Note 4.): Source and

Destination MAC (Outer MACs inside thepayload, just after the MPLS header),EtherType.

Unlearnt traffic (See Note 4.): Source and

Destination MAC (Outer MACs inside thepayload, just after the MPLS header), IngressPort-Id.

Epipe service:

SDP to SAP

All traffic (See Note 4.): Source andDestination MAC (Outer MACs inside the

payload, just after the MPLS header),EtherType

VPLS service:

SDP to SDP

Non-IP Traffic (Learnt): Source andDestination MAC (Outer MACs inside the

payload, just after the MPLS header), Ingress

Port-Id, EtherType.

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



SAS-M devices




traffic types


53/348

LAG

Page 48 7210


MPLS LSR All traffic: MPLS label stack (Two labelsdeep), Ingress Port-Id.

PBB VPLS service:

PBB BCB Traffic (that is, B-SAP

to B-SAP)

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

IP traffic (unlearnt): Source and DestinationIP, Source and Destination L4 ports, IngressPort-Id.

L2/non-IP traffic (learnt): BDA, BSA

L2/non-IP traffic (unlearnt): BDA, BSA,

ISID, Ingress Port-Id

PBB VPLS service:

Originating PBB BEB traffic

(that is, I-SAP to B-SAP)

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

IP traffic (unlearnt): Source and DestinationIP, Source and Destination L4 ports, IngressPort-Id

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

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



SAS-M devices




traffic types


54/348



PBB VPLS service:

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

IP traffic (learnt): CSA, CDA

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

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

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

PBB Epipe service:

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

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

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

PBB Epipe service:

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

IP traffic: CSA, CDA

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

VPRN service:

SAP to SAPSDP to SAP

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

VPRN service:

SAP to SDP

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

IES service (IPv4):

IES SAP to IES SAP

IPv4 unicast traffic: Source and DestinationIP, Source and Destination L4 ports



SAS-M devices




traffic types


55/348

LAG

Page 50 7210


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

specified4. Applicable to non-IP, IP, PBB and MPLS traffic encapsulated in the MPLS packet received on

the SDP Binding/SDP.

IES service (IPv4):

IES SAP to IPv4 network portinterface

IPv4 unicast traffic: Source and DestinationIP, Source and Destination L4 ports, Ingress

Port-Id.

Network port IPv4 interface:

IPv4 network interface to IPv4network interface

IPv4 unicast traffic: Source and Destination

IP, Source and Destination L4 ports, IngressPort-Id.

Network port IPv6 interface:

IPv6 network interface to IPv6network interface

IPv6 unicast traffic: Source and DestinationIP, Source and Destination L4 ports, IngressPort-Id.

IES (Multicast IP traffic)

IP interface (Network or SAP) toIP interface (SAP)

IPv4 Multicast traffic: Source and DestinationIP, Source and Destination L4 ports, IngressPort-Id.

Network Port IP interface(Multicast IP traffic)

IP interface (Network or SAP) toIP interface (Network)

IPv4 Multicast traffic: Source and DestinationIP, Source and Destination L4 ports, IngressPort-Id.



SAS-M devices




traffic types


56/348



LAG Hashing Fields used for 7210 SAS-X

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

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

Packet fields used for Hashing for differenttraffic types

VPLS service:

SAP to SAP

SAP to SDP

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



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

Epipe service:

SAP to SAPSAP to SDP

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



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

VPLS and Epipe service:

SDP to SAP

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

header), Ingress Port-Id.

VPLS service:

SDP to SDP

All traffic: Source and Destination MAC (OuterMACs inside the payload, just after the MPLSheader), Ingress Port-Id.

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

Ingress Port-Id.


57/348

LAG

Page 52 7210


PBB VPLS service:

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

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

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

PBB VPLS service:

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

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

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

PBB VPLS service:

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

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

L2/non-IP traffic (learnt and unlearnt): CSA,

3HE10383AAACTQZZA_V1_7210 SAS M T X R6 R12 Mxp OS Interface Configuration Guide

Documents

Transcript of 3HE10383AAACTQZZA_V1_7210 SAS M T X R6 R12 Mxp OS Interface Configuration Guide