7210_sas_m

All specifications, procedures, and information in this document are subject to change and revision at any time without notice. The information contained herein is believed to be accurate as of the date of publication. Alcatel-Luce nt provides no warranty, express or implied, regarding its contents. User s are fully responsible for application or use of the documentation. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Copyright 2015 Alcatel-Lucent. All rights reserved. Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, license d or otherwise distributed for use in any hazardous environme nts requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications. This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lu cent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-AlcatelLucent products. However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers. This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

All specifications, procedures, and information in this document are subject to change and revision at any time without notice. The information contained herein is believed to be accurate as of the date of publication. Alcatel-Luce nt provides no warranty, express or implied, regarding its contents. User s are fully responsible for application or use of the documentation. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Copyright 2015 Alcatel-Lucent. All rights reserved. Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, license d or otherwise distributed for use in any hazardous environme nts requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications. This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lu cent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-AlcatelLucent products. However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers. This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

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

7210 SAS-Series Interfaces Configuration Overview Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Chassis Slots and Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 MDAs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Provisioning Provisi oning of MDA on 7210 7210 SAS-M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Digital Diagnostic Diagnostics s Monitoring Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Alcatel-Lucent Alcatel -Lucent SFPs SFPs and XFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Statistics Statisti cs Collection Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Port Types Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Port Modes Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Configuration guidelines for Dot1q-etype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Support for Power over Ethernet (PoE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Link Layer Discovery Protocol (LLDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 LLDP Protocol Protocol Features Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 LLDP Tunneling Tunneling for Epipe Epipe Service Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 Port loopback loopback for Ethernet Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 . 33 Port loopback without MAC swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Port loopback with MAC swap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 LAG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 LAG Features Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Configuring Configu ring LAGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 LAG on Access Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 LAG and QoS Policies on 7210 SAS-M, and 7210 SAS-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 LAG and QoS policies on 7210 SAS-Mxp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 LAG and QoS policies policies on 7210 7210 SAS-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 LAG and QoS policies policies on 7210 7210 SAS-R6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Port Link Damping Damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 LAG Subgroups Subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 . 40 LAG and ECMP ECMP Hashing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 . 42 LAG Hashing Fields used for 7210 SAS-M (Network mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 LAG Hashing Fields used for 7210 SAS-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 LAG Hashing Fields used for 7210 SAS-M (Access-Uplink mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 LAG Hashing Fields used for 7210 SAS-T Access-Uplink mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 LAG Hashing Fields used for 7210 SAS-T Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 LAG Hashing Fields used for 7210 SAS-R6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 LAG Hashing Hashing Fields used used for 7210 SAS-Mxp SAS-Mxp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 ECMP Hashing fields used for 7210 SAS devices in Network mode . . . . . . . . . . . . . . . . . . . . . . . .69 Multi-Chassis Multi-Ch assis LAG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Overview Overvie w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Point-to-Point (p2p) Redundant Connection Across Layer 2/3 VPN Network . . . . . . . . . . . . . . . . .73 DSLAM Dual Dual Homing in Layer Layer 2 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

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

Page 1

Table of Contents Configuring Multi-Chassis Configuring Multi-Chassis Redunda Redundancy ncy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 G.8032 Protected Protected Ethernet Ethernet Rings Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 . 78 802.3ah OAM OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 . 84 OAM Events Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Remote Loopback Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 802.3ah 802.3a h OAM PDU Tunneling Tunneling for Epipe Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 MTU Configuration Configuration Guidelines Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Deploying Pre-provisioned Components for 7210 SAS-M, 7210 SAS-X, 7210 SAS-T, and 7210 SAS-Mxp. 88 Deploying Pre-provisioned Components for 7210 SAS-R6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Configuration Configu ration Process Process Overview Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 . 89 Configuring Physical Ports with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 Preprovisioning Preprovi sioning Guideline Guidelines s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 Predefining Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 Pre-provisionin Pre-pro visioning g a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Basic Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Configuring Configu ring Cards and and MDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Configuration Notes for provisioning of cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Configuration Notes for provisioning of 7210 SAS-R6 IMMv2 cards. . . . . . . . . . . . . . . . . . . . . . . . . . .96 Common Configuratio Configuration n Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Configuring Configu ring Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Configuring Configu ring Ethernet Ethernet Port Parameters Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Ethernett Network Port Etherne Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Ethernett Access uplink Etherne uplink Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Ethernet Access Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Configuring 802.1x Authentication Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Configuring Channelized Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Configuring Configu ring a Channelized Channelized DS1 Card Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Configuring Configu ring LAG Parameters Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 CRC Error Monitoring Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Service Managemen Managementt Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Modifying Modifyi ng a Card Type Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Deleting a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Deleting Deletin g Port Parameters Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Card, MDA, and Port Port Command Referenc Reference e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Page 2

7210 SAS M, T, X, R6, Mxp Interface Configu-

LIST OF TABLES Table Table Table Tab le Table Tab le Table Tab le Table Tabl e Table Tab le Table Tabl e Table Tab le Table Tabl e Table Tabl e Table Tab le Table Tab le Table Tabl e Table Tab le Table Tabl e

1:: 1 2: 3: 3: 4: 5: 6: 6: 7: 7: 8: 8: 9: 9: 10: 10: 11: 11: 12: 12: 13: 13: 14: 14: 15: 15:

Table Tabl e 16: 16: Table Tab le 17: 17:

Configurati Configu ration on Proce Process ss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Real-Tim Real -Time e DDM Info Informat rmation ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 DDM Alar Alarms ms and and Warn Warnings ings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Support Sup ported ed Ether Ethernet net ports ports and TDM TDM ports ports typ types es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 7210 721 0 SAS SAS Platfo Platforms rms supp supporti orting ng port mod modes es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Behavio Beh aviorr for LLD LLDP P with with differ different ent val values ues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 LAG Has Hashin hing g mechan mechanism ism for ser service vices s config configure ured d in Net Network work Mod Mode e on 721 7210 0 SAS-M SAS-M dev device ices s .44 LAG Has Hashin hing g mecha mechanis nism m for for servic services es con configu figured red on 721 7210 0 SAS-X SAS-X dev devices ices . . . . . . . . . . . . . . .50 .50 LAG Has Hashin hing g mech mechanis anism m for for servic services es con configu figured red in Acces Access-Up s-Uplink link mod mode e on 721 7210 0 SAS-M SAS-M . . .53 LAG Hash Hashing ing mech mechanis anism m for serv services ices con config figure ured d on 7210 7210 SAS-T SAS-T Acc Access ess-Up -Uplink link mode . . . . .54 .54 LAG Hash Hashing ing mech mechanis anism m for serv services ices con config figured ured on 7210 7210 SAS-R6 SAS-R6 dev devices ices . . . . . . . . . . . . . .61 LAG Hash Hashing ing mech mechanis anism m for serv services ices con configu figured red on on 7210 7210 SAS-M SAS-Mxp xp devi devices ces . . . . . . . . . . . . .65 ECMP ECM P Hashin Hashing g mechan mechanism ism for for servic services es confi configure gured d on 721 7210 0 SAS dev device ices s in netw network. ork. . . . . . .69 .69 MTU Defa Default ult Valu Values es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Default Def ault valu values es for for sap-qo sap-qos-ma s-markin rking g in acce access ss and and hybrid hybrid port mod modes es 138 Sap-qos Sap -qos-mar -markin king g defau default lt value value whe when n port port mod mode e is cha change nged d 138 Internal Inte rnal port reso resourc urces es on on differe different nt IMMs. IMMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 .149


Page 1

List of Tables

Page 2

7210 SAS M, T, T, X, R6, Mxp Interface Configuration

LIST OF FIGURES Figure 1: Figure 2: Figure 3: Figure 4: Figure 5: Figure 6: Figure 7: Figure 8: Figure 9: Figure 10: Figure 11:

LLDP Internal Architecture for a Network Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Generic Customer Use Case For LLDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 LAG Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 MC-LAG L2 Dual Homing to Remote PE Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 MC-LAG L2 Dual Homing to Local PE-Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 P2P Redundant Connection Through a Layer 2 VPN Network. . . . . . . . . . . . . . . . . . . . . . . . .73 DSLAM Dual-Homing Using MC-LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 802.1x Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 802.1x Authentication Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 802.1x EAPOL Timers (left) and RADIUS Timers (right) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Slot, Card, MDA, and Port Configuration and Implementation Flow . . . . . . . . . . . . . . . . . . . . .89


Page 1

List of Figures

Page 2

7210 SAS M, T, X, R6, Mxp Interface Configuration

Ports

supported on a hybrid port. The following port modes are supported on each of the 7210 SAS platforms: Table 5:

7210 SAS Platforms supporting port modes

Port Mode Platforms

Access

Network

Hybrid

Accessuplink

7210 SAS-M

Yes

Yesa

Yesb

Yesc

7210 SAS-X

Yes

Yes

Yes

No

7210 SAS-T

Yes

Yesa

Yesb

Yesc

7210 SAS-R6

Yes

Yes

Yes

No

7210 SAS-Mxp

No

Yes

No

No

a.

Network ports can be configured only if the BOF is configured to operate the node in network 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 is configured in Network mode by default. It does not support

access-uplink mode.

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

Page 22 Guide

•

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.


Interface Configuration

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+1x fp up up 2 imm-sas-10sfp+1x fp 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#

MDAs The 7210 SAS-R6, 7210 SAS-X, and 7210 SAS-T 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


Page 13

Configuration Overview

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. 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.

MDA port on 7210 SAS-Mxp:

Page 14 Guide



The following are the ports in 7210 SAS-Mxp: •

4 x 10G SFP+

•

22 x 1G SFP

•

2 x Combo (SFP or Copper)


Page 15

Digital Diagnostics Monitoring

Digital Diagnostics Monitoring Some Alcatel-Lucent 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:

Page 16 Guide

•

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.



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

Real-Time DDM Information

Parameter

User Units

Temperature

Celsius

Supply Voltage

SFP/XFP Units

SFP

XFP

C

Supported

Supported

Volts

µV

Supported

Supported

TX Bias Current

mA

µA

Supported

Supported

TX Output Power

dBm (converted from mW)

mW

Supported

Supported

RX Received Optical Power4

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

mW

Supported

Supported

AUX1

parameter dependent (embedded in transceiver)

-

Not supported

Supported

AUX2


-

Not supported

Supported

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


Page 17

Digital Diagnostics Monitoring

Table 3:

DDM Alarms and Warnings

Parameter

SFP/XFP Units

SFP

XFP

Required?

Temperature - High Alarm - Low Alarm - High Warning - Low Warning

C

Yes

Yes

Yes

Supply Voltage - High Alarm - Low Alarm - High Warning - Low Warning

µV

Yes

Yes

Yes

TX Bias Current - High Alarm - Low Alarm - High Warning - Low Warning

µA

Yes

Yes

Yes

TX Output Power - High Alarm - Low Alarm - High Warning - Low Warning

mW

Yes

Yes

Yes

RX Optical Power - High Alarm - Low Alarm - High Warning - Low Warning

mW

Yes

Yes

Yes

AUX1 - High Alarm - Low Alarm - High Warning - Low Warning


No

Yes

Yes

AUX2 - High Alarm - Low Alarm - High Warning - Low Warning


No

Yes

Yes

Page 18 Guide



Alcatel-Lucent 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 Alcatel-Lucent SFPs support DDM. Non-DDM and DDM-supported SFPs are distinguished by a specific ICS value. For Alcatel-Lucent 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-Alcatel-Lucent 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. 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.0 0 -8.50 -9.00 -33.98! -35 .23! ===============================================================================


Page 19

Ports

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 SASM 24F 2XFP

7210 SAS-M 24F 2XFP ETR

7210 SAS-X

7210 SAS-T

7210 SAS-R6

7210 SAS-Mxp

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

No

No

No

No

Yes

No

Yes

Fast Ethernet SFP Ports

Yes

Yes

Yes

Yes

Yes

Yes

Yes

10 Gigabit XFP/SFP+ Ports

Yes, with 2 x 10G/ XFP MDA

Yes-XFP

Yes-XFP

Yes-XFP

Yes-XFP

IMMv1 - XFP IMMv2 - SFP+

Yes-SFP+

TDM ports (DS1/E1)

Yes (only in network mode and with CES MDA)



No

No

No

No

NOTES:

•

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

•

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

Port Modes

Page 20 Guide



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 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.

•

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


Page 21

7210_sas_m

Recommend Documents