Alcatel-LucentService Access Switch| Release 7.0 Rev.017 2 1 0 S A S - M a n d 7 2 1 0 S A S - T O SS e r v i c e s G u i d e

3HE09513AAAA

3HE09513AAAA

Alcatel-Lucent ProprietaryThis document contains proprietary information of Alcatel-Lucent and is not to be disclosed

or used except in accordance with applicable agreements.Copyright 2014 Alcatel-Lucent. All rights reserved.

This document is protected by copyright. Except as specifically permitted herein, no portion of the provided information can be reproduced in any form, or by any means, without prior written permission from Alcatel-Lucent.Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.

The information presented is subject to change without notice.Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright 2013 Alcatel-Lucent. All rights reserved.

Table of Contents

Phase 2: Service Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .627210 SAS-M and 7210 SAS-T Services Guide Page 3Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Getting StartedAlcatel-Lucent 7210 SAS Services Configuration Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Services OverviewIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Service Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Alcatel-Lucent Service Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Service Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Service Access Points (SAPs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

SAP Encapsulation Types and Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Ethernet Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Services and SAP Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Default SAP on a Dot1q Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Default SAPs on a QinQ Port (supported only on 7210 SAS devices configured in access-uplink mode)

33Configuration Notes for use of Default QinQ SAPs for transit service in a ring deployment . . . . . .36SAP Configuration Considerations (applicable for both Network mode and access-uplink mode) .36

QinQ SAP Configuration restrictions for 7210 SAS in Network mode only . . . . . . . . . . . . . . . . . . . . . .37SAP configuration notes when operating the 7210 SAS devices in Access-Uplink mode only . . . .38

Service Distribution Points (SDPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41SDP Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Spoke and MESH SDPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43SDP Using BGP Route Tunnel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43SDP Keepalives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Mixed-LSP Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45G.8032 Ethernet Ring Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Overview of G.8032 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Ethernet Ring Sub-Rings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Virtual and Non-Virtual Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Ethernet Ring Sub Ring using non-virtual-link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Lag Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

OAM Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59QoS Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Support Service and Solution Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Configuration guidelines for G.8032 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Service Creation Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Deploying and Provisioning Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Phase 1: Core Network Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Table of Contents

Phase 3: Service Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Configuring Global Service Entities with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Service Model Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Basic Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Configuring Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69Customer Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Configuring an SDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71SDP Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Configuring an SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Configuring a Mixed-LSP SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Ethernet Connectivity Fault Management (ETH-CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Common Actionable Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78MEP and MIP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Configuring ETH-CFM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Applying ETH-CFM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88Modifying Customer Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88Deleting Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Modifying SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Deleting SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Layer 2 Control Processing (L2CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Global Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

VLL ServicesCircuit Emulation (Cpipe) Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Cpipe Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Cpipe Service Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Unstructured Mode (SAToP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Structured Mode (CESoPSN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129TDM Pseudowire Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Circuit Emulation Parameters and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Ethernet Pipe (Epipe) Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144Epipe Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Epipe with PBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Support for processing of packets received with more than 2 tags on a QinQ SAP in Epipe service (only on 7210 SAS devices configured in network mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146Feature Support, Configuration notes and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Configuration of Epipe service for processing of packets received with more than 2 tags on a QinQ SAP (only on 7210 SAS devices configured network mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Epipe Oper State decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Pseudowire Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Pseudowire Switching with Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153Pseudowire Switching Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Pseudowire Switching TLV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156Static-to-Dynamic Pseudowire Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Pseudowire Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157Page 4 7210 SAS-M and 7210 SAS-T Services Guide

Table of Contents

VLL Resilience with Two Destination PE Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

Master-Slave Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Access Node Resilience Using MC-LAG and Pseudowire Redundancy. . . . . . . . . . . . . . . . . . . . . . .167VLL Resilience for a Switched Pseudowire Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Pseudowire Redundancy Service Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173Redundant VLL Service Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173T-LDP Status Notification Handling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

Processing Endpoint SAP Active/Standby Status Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175Processing and Merging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

Epipe Configuration for MPLS-TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177VLL Spoke SDP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178Credit Based Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181

VLAN Range for SAPs in an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Processing behavior for SAPs using VLAN ranges in access-uplink mode . . . . . . . . . . . . . . . . .182VLAN Range SAPs feature Support and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Processing behavior for SAPs using VLAN ranges in network mode . . . . . . . . . . . . . . . . . . . . . .184VLL Service Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185QoS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185Filter Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186MAC Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186

Configuring a VLL Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Basic Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188Configuring VLL Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Creating a Cpipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190Creating an Epipe Service in Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196Creating an Epipe Service (for 7210 SAS-M and 7210 SAS-T in access uplink mode). . . . . . . . .196Creating an Epipe Service for 7210 SAS-M with range SAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . .198Configuring Default QinQ SAPs for Epipe Transit Traffic in a Ring Scenario. . . . . . . . . . . . . . . . .203

Using Spoke SDP Control Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Configuring VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Configuring VLL Resilience for a Switched Pseudowire Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212

Modifying a Cpipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213Deleting a Cpipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214Modifying Epipe Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215Disabling an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215Re-Enabling an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Deleting an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

VLL Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217

Virtual Private LAN ServiceVPLS Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

VPLS Packet Walkthrough in Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265VPLS Packet Walkthrough in Access Uplink Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268

VPLS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271VPLS Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271VPLS over MPLS in Network Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2727210 SAS-M and 7210 SAS-T Services Guide Page 5

Table of Contents

VPLS over QinQ Spokes for 7210 SAS devices Configured in Access Uplink Mode . . . . . . . . . . . . .273

VPLS MAC Learning and Packet Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274

IGMP Snooping in Network Mode and Access-uplink Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275Configuration Guidelines for IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277

Multicast VLAN Registration (MVR) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277Table Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278

FIB Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279FIB Size Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279Local and Remote Aging Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280Disable MAC Aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280Disable MAC Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280Unknown MAC Discard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280VPLS and Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281MAC Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281

VPLS and Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283Spanning Tree Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283Multiple Spanning Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285MSTP for QinQ SAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287Provider MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287Enhancements to the Spanning Tree Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289

VPLS Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292Spoke SDP Redundancy for Metro Interconnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292Spoke SDP Based Redundant Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294Inter-Domain VPLS Resiliency Using Multi-Chassis Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . .295

VPLS Access Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296STP-Based Redundant Access to VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296Redundant Access to VPLS Without STP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298

MAC Flush Message Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299MAC Flush with STP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301Selective MAC Flush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302Dual Homing to a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303

VPLS Service Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305SAP Encapsulations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305VLAN Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305

BGP Auto-Discovery for LDP VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306BGP AD Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306FEC Element for T-LDP Signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307BGP-AD and Target LDP (T-LDP) Interaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310SDP Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311Automatic Creation of SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311Manually Provisioned SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312Automatic Instantiation of Pseudowires (SDP Bindings) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312Mixing Statically Configured and Auto-Discovered Pseudowires in a VPLS service. . . . . . . . . . . . . .313Resiliency Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313

Routed VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314IES IP Interface Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314Assigning a Service Name to a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314Service Binding Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315Page 6 7210 SAS-M and 7210 SAS-T Services Guide

Table of Contents

Bound Service Name Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315

Binding a Service Name to an IP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315IP Interface Attached VPLS Service Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316IP Interface and VPLS Operational State Coordination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316IP Interface MTU and Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Unicast IP Routing into a VPLS Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317

ARP and VPLS FIB Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317Routed VPLS Specific ARP Cache Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318

The allow-ip-int-binding VPLS Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318Routed VPLS SAPs only Supported on Standard Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . .319

LAG Port Membership Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319VPLS Feature Support and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319

VPLS SAP Ingress IP Filter Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320QoS Support for VPLS SAPs and IP interface in a Routed VPLS service . . . . . . . . . . . . . . . . . . .323Routed VPLS Supported Routing Related Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323Spanning Tree and Split Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324

Routed VPLS support available and Caveats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325Epipe Emulation using Dot1q VLAN range SAP in VPLS with G8032 . . . . . . . . . . . . . . . . . . . . . . . . . . .326

Configuration guidelines and restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327Configuring a VPLS Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329

Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333Configuring VPLS Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334

Creating a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335Configuring a VPLS SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342Configuring SDP Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .353

Configuring VPLS Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355Creating a Management VPLS for SAP Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355Creating a Management VPLS for Spoke SDP Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357Configuring Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360Configuring Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362Configuring Selective MAC Flush. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368Configuring Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369

Configuring BGP Auto-Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371

Configuring AS Pseudo-wire in VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375

Modifying VPLS Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375Modifying Management VPLS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376Deleting a Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376Disabling a Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377

Deleting a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378Disabling a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378Re-Enabling a VPLS Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379

VPLS Services Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381

IEEE 802.1ah Provider Backbone BridgingIEEE 802.1ah Provider Backbone Bridging (PBB) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .470PBB Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4717210 SAS-M and 7210 SAS-T Services Guide Page 7

Table of Contents

Integrated PBB-VPLS Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .471

PBB Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .473PBB Mapping to Existing VPLS Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .474SAP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .476

PBB B-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .476PBB I-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .476

PBB Packet Walkthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .478PBB ELINE Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .480

PBB Resiliency for PBB epipe service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .480PBB Resiliency for B-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .480

Access Multi-Homing for Native PBB (B-VPLS over SAP Infrastructure) . . . . . . . . . . . . . . . . . . . . . .481PBB QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .482PBB ACL Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .483Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .483Configuration Guidelines (for 7210 SAS-M and 7210 SAS-T). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .484

Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .486PBB ELAN and ELINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .486MC-LAG Multihoming for Native PBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .487

PBB Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .489PBB Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .497

Internet Enhanced ServiceIES Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .532IES Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .533

IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .533. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .533

SAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .534Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .534

Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .534CPE Connectivity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .535

QoS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .535CPU QoS for IES interfaces in access-uplink mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .535CPU QoS for IES access interfaces in network mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .536

Filter Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .536IPv6 support for IES IP interfaces (applicable for only access-uplink mode) . . . . . . . . . . . . . . . . . . .537VRRP support for IES IP interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .537

Configuring an IES Service with CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .539Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .540Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .542Configuring IES Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .543

Configuring an IES Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .543Configuring IES Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .544Configuring SAP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .545Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .545

Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .546Modifying IES Service Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .546Deleting an IES Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .547Disabling an IES Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548Re-Enabling an IES Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548Page 8 7210 SAS-M and 7210 SAS-T Services Guide

Table of Contents

IES Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .549Virtual Private Routed Network ServiceVPRN Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .582

Routing Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .583BGP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .584Route Distinguishers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585

Route Reflector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585CE to PE Route Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .586

VPRN Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .589IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .590SAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .590

Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .590QoS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .591Filter Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .591

DSCP Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .592Default DSCP Mapping Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .593

CE to PE Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .595PE to PE Tunneling Mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .595Per VRF Route Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .595

Using OSPF in IP-VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .595Service Label Mode of a VPRN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .597

Configuring a VPRN Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .599Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .600Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .601Configuring VPRN Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .602

Creating a VPRN Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .602Configuring Global VPRN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .603

Configuring VPRN Protocols - OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .609VPRN OSPF CLI Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .610

Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .611Modifying VPRN Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .611Deleting a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .612Disabling a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .613Re-enabling a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .614

VPRN Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615

Service Global CommandsShow Command Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .719Show, Clear, Debug, Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .721

IES Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .745VPRN Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .765VPRN Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .837VPRN Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .841VLL Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .845VLL Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .900VLL Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .903VPLS Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .905VPLS Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9787210 SAS-M and 7210 SAS-T Services Guide Page 9

Table of Contents

VPLS Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .983Common CLI Command DescriptionsCommon Service Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .988

Appendix: Port-Based Split HorizonOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .990

Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .990Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .991

Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .993

Appendix: DHCP ManagementDHCP Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .996

DHCP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .998Using Option 82 Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .998Trusted and Untrusted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .999DHCP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .999

Common Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1001Configuration Guidelines for DHCP relay and snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1001Configuring Option 82 Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1001Page 10 7210 SAS-M and 7210 SAS-T Services Guide

List of Tables

Getting StartedTable 1: Configuration Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Services OverviewTable 2: Service and Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Table 3: SAP types in a service when QinQ SAP is in use (Network mode operation) . . . . . . . . . . . . . .38Table 4: SAP and Service Combinations for 7210 SAS-M and 7210 SAS-T in access-uplink mode . . . .38Table 5: Defect conditions and priority settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Table 6: ETH-CFM Support Matrix for 7210 SAS-M Network Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Table 7: ETH-CFM Support Matrix for 7210 SAS-M Access-Uplink Mode . . . . . . . . . . . . . . . . . . . . . . . .80Table 8: ETH-CFM Support Matrix for 7210 SAS-T Access-Uplink Mode . . . . . . . . . . . . . . . . . . . . . . . .80Table 9: ETH-CFM Support Matrix for 7210 SAS-T Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Table 10: CCM transmission interval for 7210 SAS-M and 7210 SAS-T (Network Mode) . . . . . . . . . . . .124Table 11: CCM transmission interval for 7210 SAS-M and 7210 SAS-T (Access-Uplink Mode) . . . . . . .124

VLL ServicesTable 12: T1 Framing for CAS (RBS) Support in a T1 ESF Multi-frame. . . . . . . . . . . . . . . . . . . . . . . . . .131Table 13: Unstructured Payload Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Table 14: Default and Minimum Payload Size for CESoPSN without CAS. . . . . . . . . . . . . . . . . . . . . . . .137Table 15: Payload Size for T1 and E1 CESoPSN with CAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139Table 16: Control Word Bit Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142Table 17: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .247

Virtual Private LAN ServiceTable 18: Routing behavior in RVPLS and interaction ARP Cache and MAC FIB . . . . . . . . . . . . . . . . . .318Table 19: ACL Lookup behavior with Ingress Override filter attached to an IES interface in a R-VPLS service.320Table 20: ACL Lookup behavior without Ingress Override filter attached to an IES interface in a R-VPLS service321Table 21: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323Table 22: SAP BPDU Encapsulation States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350Table 23: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .452

IEEE 802.1ah Provider Backbone Bridging

Internet Enhanced Service

Virtual Private Routed Network ServiceTable 24: DSCP/FC Marking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .592Table 25: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .6617210 SAS-M and 7210 SAS-T Services Guide Page 11

List of TablesPage 12 7210 SAS-M and 7210 SAS-T Services Guide

List of Figures

Figure 39: MVR and MVR by Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Services OverviewFigure 1: Service Entities for 7210 SAS devices configured in Network Mode . . . . . . . . . . . . . . . . . . . .28Figure 2: Service Access Point (SAP) for 7210 SAS configured in Network Mode . . . . . . . . . . . . . . . . .29Figure 3: Multiple SAPs in a service using QinQ uplinks in 7210 SAS configured in access-uplink mode 30Figure 4: Multiple SAPs on a Single Port (7210 in Network Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Figure 5: MPLS Service Distribution Point (SDP) Pointing From ALA-A to ALA-B . . . . . . . . . . . . . . . . .42Figure 6: G.8032 Ring in the Initial State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Figure 7: 0-1 G.8032 Ring in the Protecting State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Figure 8: 0-3 Ring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Figure 9: 0-4 G.8032 Sub-Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Figure 10: 0-6 Sub-Ring Homed to VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Figure 11: Service Creation and Implementation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Figure 12: Ethernet OAM Model for Broadband Access - Residential . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Figure 13: Ethernet OAM Model for Broadband Access - Wholesale . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

VLL ServicesFigure 14: E1 Framing for CAS Support in an E1 Multi-frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130Figure 15: SAToP MPLS Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Figure 16: CESoPSN MPLS Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Figure 17: CESoPSN Packet Payload Format for Trunk-Specific n x 64 kb/s (with and without CAS transport) 133Figure 18: Control Word Bit Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142Figure 19: Epipe/VLL Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Figure 20: Pseudowire Service Switching Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152Figure 21: VLL Resilience with Pseudowire Redundancy and Switching . . . . . . . . . . . . . . . . . . . . . . . . .153Figure 22: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Figure 23: Master-Slave Pseudowire Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161Figure 24: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Figure 25: VLL Resilience with Pseudowire Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166Figure 26: Access Node Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168Figure 27: VLL Resilience with Pseudowire Redundancy and Switching . . . . . . . . . . . . . . . . . . . . . . . . .171Figure 28: Redundant VLL Endpoint Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173Figure 29: Default QinQ SAP for Transit Traffic in a Ring Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203Figure 30: SDPs Uni-Directional Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Figure 31: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Figure 32: VLL Resilience with Pseudowire Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

Virtual Private LAN ServiceFigure 33: VPLS Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Figure 34: Access Port Ingress Packet Format and Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Figure 35: Network Port Egress Packet Format and Flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Figure 36: VPLS Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268Figure 37: Access Port Ingress Packet Format and Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Figure 38: Network Port Egress Packet Format and Flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2697210 SAS-M and 7210 SAS-T Services Guide Page 13

List of Figures

Figure 40: Access Resiliency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286

Figure 41: HVPLS with Spoke Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293Figure 42: HVPLS Resiliency Based on AS Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295Figure 43: Dual Homed MTU-s in Two-Tier Hierarchy H-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296Figure 44: HVPLS with SAP Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301Figure 45: Dual Homed CE Connection to VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303Figure 46: BGP AD NLRI versus IP VPN NLRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307Figure 47: Generalized Pseudowire-ID FEC Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308Figure 48: BGP-AD and T-LDP Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310Figure 49: Epipe Emulation in a ring using VPLS with G.8032 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326Figure 50: Example Configuration for Protected VPLS SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356Figure 51: Example Configuration for Protected VPLS Spoke SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . .358Figure 52: Example Configuration for Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . .360Figure 53: Example Configuration for Loadbalancing Across Two Protected VPLS Spoke SDPs . . . . .362Figure 54: Example Configuration for Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . .369Figure 55: BGP AD Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371Figure 56: BGP-AD CLI Command Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372Figure 57: Sample Topology-AS Pseudo-wire in VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373

IEEE 802.1ah Provider Backbone BridgingFigure 58: Large HVPLS Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .471Figure 59: Large PBB-VPLS Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .472Figure 60: QinQ Payload in Provider Header Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .473Figure 61: PBB Mapping to VPLS Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .474Figure 62: PBB Packet Walkthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .478Figure 63: Access Dual-Homing into PBB BEBs - Topology View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .481

Internet Enhanced ServiceFigure 64: Internet Enhanced Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .532

Virtual Private Routed Network ServiceFigure 65: Virtual Private Routed Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .582Figure 66: Route Distinguisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585Figure 67: Directly Connected IP Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .587Figure 68: Multiple Hops to IP Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .587Figure 69: OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .707Figure 70: Split Horizon Group Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .990Figure 71: IP Address Assignment with DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .996Page 14 7210 SAS-M and 7210 SAS-T Services Guide

On 7210 SAS devices, not all the CLI commands are supported on all the platforms and in all the modes. In many cases, the CLI commands are mentioned explicitly in this 7210 SAS-M and 7210 SAS-T Services Guide Page 15

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

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

About This GuideThis guide describes service mirroring and Operations, Administration and Management (OAM) and diagnostic tools provided by the 7210 SAS-M, T, platforms and presents examples to configure and implement various tests.

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

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

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 platforms, unless specified otherwise.

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

Only 7210 SAS-M and 7210 SAS-T supports access-uplink mode. 7210 SAS-X and 7210 SAS-R6 does not support access-uplink mode.

PrefaceAudience

This manual is intended for network administrators who are responsible for configuring the 7210 SAS M. It is assumed that the network administrators have an understanding of networking principles and configurations. Protocols, standards, and services described in this manual include the following:

CLI concepts Subscriber services Service mirroring Operation, Administration and Maintenance (OAM) operationsPage 16 7210 SAS-M and 7210 SAS-T Ser-vices Guide

PrefaceList of Technical Publications

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

7210 SAS M, T, X, R6 OS Basic System Configuration GuideThis guide describes basic system configurations and operations.

7210 SAS M, T, X, R6 OS System Management GuideThis guide describes system security and access configurations as well as event logging and accounting logs.

7210 SAS M, T, X, R6 OS Interface Configuration GuideThis guide describes card, Media Dependent Adapter (MDA), and port provisioning.

7210 SAS M, T, X, R6 OS Router Configuration GuideThis guide describes logical IP routing interfaces and associated attributes such as an IP address, port, link aggregation group (LAG) as well as IP and MAC-based filtering.

7210-SAS-M and 7210 SAS-T OS Services GuideThis guide describes how to configure service parameters such as customer information and user services.

7210 SAS-M, T, X, R6 OS MPLS GuideThis guide describes how to configure Multiprotocol Label Switching (MPLS),Resource Reservation Protocol (RSVP), and Label Distribution Protocol (LDP).

7210 SAS M, T, X, R6 OS OAM and Diagnostic GuideThis guide describes how to configure features such as service mirroring and Operations, Administration and Management (OAM) tools.

7210 SAS-M and 7210 SAS-T OS Quality of Service GuideThis guide describes how to configure Quality of Service (QoS) policy management.7210 SAS-M and 7210 SAS-T Services GuidePage 17

PrefaceTechnical Support

If you purchased a service agreement for your 7210 SAS-series router and related products from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you purchased an Alcatel-Lucent service agreement, contact your welcome center:

Web: http://www1.alcatel-lucent.com/comps/pages/carrier_support.jhtmlPage 18 7210 SAS-M and 7210 SAS-T Ser-vices Guide

IES service Internet Enhanced Service on page 4657210 SAS-M and 7210 SAS-T Services Guide Page 19

VPRN service Internet Enhanced Service on page 465Reference List of IEEE, IETF, and other

proprietary entities.Standards and Protocol Support on page 1003Getting Started

In This ChapterThis book provides process flow information to configure provision services.

Alcatel-Lucent 7210 SAS Services Configuration ProcessTable 1 lists the tasks necessary to configure subscriber services and configure mirroring.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 ProcessArea Task Chapter

Subscribers Subscriber servicesGlobal entities Configuring Global Service Entities with CLI on page 65VLL services Ethernet Pipe (Epipe) Services on page 144VPLS service Virtual Private LAN Service on page 263

Getting StartedPage 20 7210 SAS-M and 7210 SAS-T Services Guide

7210 SAS-M and 7210 SAS-T Services Guide Page 21Services Command Reference

In This ChapterThis chapter provides the command reference trees for the 7210 SAS services.

Topics include:

Global Services Commands Service Configuration Commands

Cpipe Service Configuration Commands on page 217 on page 218 VPLS Service Configuration Commands on page 382 IES Service Configuration Commands on page 549 VPRN Service Configuration Commands on page 616

Page 22 7210 SAS-M and 7210 SAS-T Services Guide

7210 SAS-M and 7210 SAS-T Services Guide Page 23SERVICES OVERVIEW

In This SectionThis section provides an overview of the 7210 SAS M-Series subscriber services, service model and service entities. Additional details on the individual subscriber services can be found in subsequent chapters.

Topics in this section include:

Introduction on page 24 Service Types on page 25 Service Policies on page 26

Alcatel-Lucent Service Model on page 27 Service Entities on page 28

Customers on page 29 Service Access Points (SAPs) on page 29 Service Distribution Points (SDPs) on page 41

Service Creation Process Overview on page 61 Deploying and Provisioning Services on page 62 Configuration Notes on page 63

IntroductionIntroductionA service is a globally unique entity that refers to a type of connectivity service for either Internet or VPN connectivity. Each service is uniquely identified by a service ID and an optional service name within a service area. The 7210 SAS-Series service model uses logical service entities to construct a service. In the service model, logical service entities provide a uniform, service-centric configuration, management, and billing model for service provisioning.

In the 7210 SAS-Series, services can provide Layer 2/bridged service between a service access point (SAP) on one router and another service access point (a SAP is where traffic enters and exits the service) on the same (local) router or another router (distributed). A distributed service spans more than one router

Note: SDPs are not supported on 7210 SAS-M and 7210 SAS-T devices configured in Access Uplink mode. Only local services can be configured on 7210 SAS-M and 7210 SAS-T configured in access-uplink mode.

Distributed services use service distribution points (SDPs) to direct traffic to another 7210 SAS-Mthrough a service tunnel. SDPs are created on each participating router, specifying the origination address (the router participating in the service communication) and the destination address of another router. SDPs are then bound to a specific customer service. Without the binding process, far-end router is not able to participate in the service (there is no service without associating an SDP with a service).Page 24 7210 SAS-M and 7210 SAS-T Services Guide

ServicesService Types

The 7210 SAS-M offers the following types of subscriber services which are described in more detail in the referenced chapters:

Virtual Leased Line (VLL) services: Ethernet pipe (Epipe) A Layer 2 point-to-point VLL service for Ethernet frames.

See Ethernet Pipe (Epipe) Services on page 144. Virtual Private LAN Service (VPLS) A Layer 2 multipoint-to-multipoint VPN. See

Virtual Private LAN Service on page 263. Internet Enhanced Service (IES) A routed connectivity service used to provide IP

services.This service is supported in 7210 SAS platforms operated in access-uplink mode for only inband management of the node (that is, it cannot be used as for configuring customer service in access-uplink mode). See Internet Enhanced Service on page 465.

Virtual Private Routed Network (VPRN) A Layer 3 IP multipoint-to-multipoint VPN service as defined in RFC 2547bis. See Virtual Private Routed Network Service on page 581.7210 SAS-M and 7210 SAS-T Services Guide Page 25

IntroductionService Policies

Common to all 7210 SAS-Series connectivity services are policies that are assigned to the service. Policies are defined at a global level and then applied to a service on the router. Policies are used to define 7210 SAS-Series service enhancements. The types of policies that are common to all 7210 SAS-Series connectivity services are:

SAP Quality of Service (QoS) policies which allow for different classes of traffic within a service at SAP ingress and SAP egress.QoS ingress and egress policies determine the QoS characteristics for a SAP. A QoS ingress policy applied to a SAP specifies the number of meters, meter characteristics (such as forwarding class, committed, and peak information rates, etc.) and the mapping of traffic to a forwarding class. A QoS egress policy defines the queue characteristics (such as CBS, CIR, PIR). A QoS policy must be created before it can be applied to a SAP. A single ingress and egress QoS policy can be associated with a SAP. A single access egress QoS policy can be associated with a port.

Filter policies allow selective blocking of traffic matching criteria from ingressing or egressing a SAP. Filter policies, also referred to as access control lists (ACLs), control the traffic allowed in or out of a SAP based on MAC or IP match criteria. Associating a filter policy on a SAP is optional. Filter policies are identified by a unique filter policy ID. A filter policy must be created before it can be applied to a SAP. A single ingress and single egress filter policy can be associated with a SAP.

Scheduler policies define the operating parameters (such as scheduling algorithm, weights per priority). They are associated with physical ports.

Accounting policies define how to count the traffic usage for a service for billing purposes.

The routers provide a comprehensive set of service-related counters. Accounting data can be collected on a per-service, per-forwarding class basis, which enables network operators to accurately measure network usage and bill each customer for each individual service using any of a number of different billing models.Page 26 7210 SAS-M and 7210 SAS-T Services Guide

ServicesAlcatel-Lucent Service ModelIn the Alcatel-Lucent service model, the service edge routers are deployed at the provider edge. Services are provisioned on the service routers and transported across an IP and/or IP/MPLS provider core network in encapsulation tunnels created using MPLS label switched paths (LSPs).

The 7210 SAS devices configured in access-uplink mode supports QinQ/Dot1q Layer 2 uplinks to transport the services to the provider edge in a hierarchical configuration, whereas 7210 SAS devices configured in network mode support MPLS uplinks to transport the services.

The service model uses logical service entities to construct a service. The logical service entities are designed to provide a uniform, service-centric configuration, management, and billing model for service provisioning. Some benefits of this service-centric design include:

Many services can be bound to a single customer. QoS policies, filter policies, and accounting policies are applied to each service instead of

correlating parameters and statistics from ports to customers to services.

Service provisioning uses logical entities to provision a service where additional properties can be configured for bandwidth provisioning, QoS, security filtering, accounting/billing to the appropriate entity. 7210 SAS-M and 7210 SAS-T Services Guide Page 27

Service EntitiesService EntitiesThe basic logical entities in the service model used to construct a service are:

Customers (see page 29) Service Access Points (SAPs) (see page 29) Service Distribution Points (SDPs) (see page 41) (for distributed services only)

Figure 1: Service Entities for 7210 SAS devices configured in Network Mode

OSSG001

SUBSCRIBERS SUBSCRIBERS

SERVICE

ACCESS

POINTS

SERVICE

ACCESS

POINTS

SERVICE

DISTRIBUTION

POINTS

Customer

27SAP Service

Cust-27

Cust-25

Service

Cust-7

Service

Service

Cust-27

Cust-25

Service

Cust-7

Service

SDP

ALA-A ALA-B

DEMUX SDP

DEMUX

SAP

SAP

SAP

SAP

SAP

Customer

25

Customer

7

Customer

27

Customer

25

Customer

7Page 28 7210 SAS-M and 7210 SAS-T Services Guide

ServicesCustomers

The terms customers and subscribers are used synonymously. The most basic required entity is the customer ID value which is assigned when the customer account is created. To provision a service, a customer ID must be associated with the service at the time of service creation.

Service Access Points (SAPs)Each subscriber service type is configured with at least one service access point (SAP). A SAP identifies the customer interface point for a service on an Alcatel-Lucent 7210 SAS M-Series router (Figure 3). The SAP configuration requires that slot, MDA, and port information be specified. The slot, MDA, and port parameters must be configured prior to provisioning a service (see the Cards, MDAs, and Ports sections of the 7210 SAS OS Interface Configuration Guide).

A SAP is a local entity to the router and is uniquely identified by:

The physical Ethernet port The encapsulation type The encapsulation identifier (ID)

Depending on the encapsulation, a physical port can have more than one SAP associated with it. SAPs can only be created on ports designated as access in the physical port configuration.

Figure 2: Service Access Point (SAP) for 7210 SAS configured in Network ModeOSSG002

Customer

27

IP/MPLS Network

SAP

3/1/6

dot1q

SAP

2/2/3

dot1q

Service

Cust-27

SDP

ALA-A

Customer

277210 SAS-M and 7210 SAS-T Services Guide Page 29

Service EntitiesFigure 3: Multiple SAPs in a service using QinQ uplinks in 7210 SAS configured in access-uplink mode

SAP Encapsulation Types and Identifiers

The encapsulation type is an access property of a service Ethernet port. The appropriate encapsulation type for the port depends on the requirements to support multiple services on a single port on the associated SAP and the capabilities of the downstream equipment connected to the port. For example, a port can be tagged with IEEE 802.1Q (referred to as dot1q) encapsulation in which each individual tag can be identified with a service. A SAP is created on a given port by identifying the service with a specific encapsulation ID.

Ethernet Encapsulations

The following lists encapsulation service options on Ethernet ports:

Null Supports a single service on the port. For example, where a single customer with a single service customer edge (CE) device is attached to the port. The encapsulation ID is always 0 (zero).

Dot1q Supports multiple services for one customer or services for multiple customers (Figure 4).. The encapsulation ID used to distinguish an individual service is the VLAN ID in the IEEE 802.1Q header. For example, the port is connected to a Ethernet switch (for example, a 7210 SAS E) with multiple downstream customers.

QinQ The QinQ encapsulation type adds a IEEE 802.1Q tag to the 802.1Q tagged packets entering the network to expand the VLAN space by tagging tagged packets, producing a double tagged frame. 7210 SAS M OS supports QinQ encapsulation for

OSSG002A

Customer

27

IP/MPLS Network

SAP

1/1/6

dot1q

SAP

1/1/3

dot1q

Service

Cust-27

SDPSAP

ALA-A

Customer

27Page 30 7210 SAS-M and 7210 SAS-T Services Guide

Services

access ports in network mode. In access-uplink mode, QinQ encapsulation is supported

for both access port and access uplink ports.

The following lists encapsulation service options on Ethernet access uplink ports:

QinQ The QinQ encapsulation type adds a IEEE 802.1Q tag to the 802.1Q tagged packets entering the network to expand the VLAN space by tagging tagged packets, producing a double tagged frame. On the 7210 SAS E, QinQ encapsulation is supported only on access uplink ports.

Figure 4: Multiple SAPs on a Single Port (7210 in Network Mode)

Services and SAP Encapsulations

Table 2 lists the service and SAP Encapsulation information for Ethernet ports:

OSSG003-7210M

Customer

27

Network

SAP

1/1/5

dot1q

PORT #1

SAP

1/1/6

dot1qService

Service

SDPCustomer

27

SAP

1/1/3

dot1q

Customer

9

Table 2: Service and Encapsulation

Port Type Encapsulation

Ethernet Null

Ethernet Dot1q

Ethernet QinQ7210 SAS-M and 7210 SAS-T Services Guide Page 31

Service EntitiesPage 32 7210 SAS-M and 7210 SAS-T Services Guide

ServicesDefault SAP on a Dot1q Port

This feature introduces default SAP functionality on Dot1q-encapsulated ports. On a dot1q-encapsulated port where a default SAP is configured, all packets with q-tags not matching any explicitly defined SAPs will be assigned to this SAP. SAPs with default Dot1q encapsulation are supported in VPLS and Epipe services. Dot1q Default SAP are not supported in VPRNs. In this context, the character * indicates default which means allow through. The default SAP also accepts untagged or priority tagged packets. A default SAP must be configured explicitly. When a default SAP is not configured explicitly, packets not matching any explicitly defined SAPs will be dropped.

One of the applications where this feature can be applicable is an access connection of a customer who uses the whole port to access Layer 2 services. The internal VLAN tags are transparent to the service provider. This can be provided by a null encapsulated port.

In this type of environment, logically two SAPs exist, a management SAP and a service SAP. The management SAP can be created by specifying a VLAN tag which is reserved to manage the CPE. The service SAP covers all other VLANs and behaves as a SAP on a null-encapsulated port.

There a few constraints related for the use of default SAP on a Dot1q-encapsulated port:

This type of SAP is supported only on VPLS and Epipe services and cannot be created in IES and VPRN services as it cannot preserve VLAN tag markings.

For VPLS SAPs with STP enabled, STP listens to untagged and null-tagged BPDUs only. All other tagged BPDUs are forwarded like other customer packets. This is the same behavior as null-encapsulated ports.

This type of SAP is mutually exclusive with a SAP defined by explicit null encapsulation (for example, 1/1/1:0). This avoids conflict as to which SAP untagged frames should be associated.

IGMP snooping is not supported on a default SAP. This would require remembering VLAN tags per hosts. By not allowing IGMP snooping of this SAP, all IGMP packets will be transparently forwarded.

Default SAPs on a QinQ Port (supported only on 7210 SAS devices config-ured in access-uplink mode)7210 SAS-M and 7210 SAS-T Services Guide Page 33

Service Entities

Default QinQ SAPs (notation - *.*) are used in ring ports to avoid the need to configure services

on all the intermediate nodes in the ring which are transiting the service. Default QinQ SAPs matches all VLAN tagged traffic which is not classified into any other SAP configured on the same port. Only one EPIPE service with default QinQ SAPs is needed for transit service traffic on access-uplink ports. Default QinQ SAPs are allowed only on access-uplink ports and access ports. It can co-exist with 0.* SAP on an access-uplink or access port. A default QinQ SAP accepts only tagged packets. Untagged packets or priority tagged packets are not accepted on Default QinQ SAPs.

When an EPIPE service With default QinQ SAPs on the ring ports is used for transit traffic in a ring deployment, no protection mechanism (example: STP or G.8032) is supported for Default QinQ SAPs. The upstream or head-end node on which the service originates must ensure the correct path on the ring is selected using either G.8032 or STP. When a VPLS service with default QinQ SAPs on the ring ports is used for transit traffic in a ring deployment, users can use either G8032 or M-VPLS with xSTP for ring protection. When using G8032, the state of the default QinQ SAPs in the VPLS service can be managed using a separate G8032 control instance. NOTE: G8032 control instance cannot use Default QinQ SAPs.

Default QinQ SAP is available for use only in an EPIPE and a VPLS service created with svc-saptype parameter set to "null-star". Default QinQ SAP can be configured along with other SAPs allowed in the same service (that is, service with svc-sap-type parameter set to "null-star").

Following features are available for use with Default QinQ SAPs configured in EPIPE and VPLS service (unless explicitly specified, below listed features are applicable for both EPIPE and VPLS service):

For Default QinQ SAPs on either access ports or access-uplink ports:

MAC learning and aging is available for use in a VPLS service Per SAP MAC limit is available for use in a VPLS service Mac-move detection and Mac-pinning is available for use in a VPLS service Discard-unknown and discard-unknown-source is available for use in a VPLS service ETH-CFM and Y.1731 is not available for use STP (and all its different flavors) cannot be enabled in the service with Default QinQ

SAPs MVPLS with xSTP can be used for loop prevention. The Default QinQ SAPs inherit the

state from the associated MVPLS instance. G.8032 control instance cannot be configured in a service with Default QinQ SAP G8032 can be used for loop prevention in ring deployments, where the Default QinQ

SAPs are configured on the ring ports in a VPLS service. A separate G8032 control instances needs to be configured for use on the ring ports and the service with Default QinQ ports needs to be associated with this G8032 control instance

IGMP snooping is not available for usePage 34 7210 SAS-M and 7210 SAS-T Services Guide

Services

L2PT and BPDU translation is not available for use

IP interface in a VPLS service is not supported in a service using this SAP

For Default QinQ SAPs created on Access-uplink Port:

Ingress qos policy applied on an access uplink port is available for classification and policing on ingress.

Egress qos policy applied on an access uplink port is available for egress queue shaping, scheduling and marking.

SAP Ingress ACLs are available for use SAP Egress ACLs are not available for use SAP Ingress received count and SAP Egress forwarded count are available for use

(appropriate accounting records can be used)

For Default QinQ SAPs created on access ports:

SAP ingress qos policy is available for use Egress qos policy applied on an access port is available for egress shaping, scheduling and

marking. SAP Ingress ACLs are available for use SAP egress ACLs are not available for use SAP Ingress Meter counters, SAP Ingress received count and SAP Egress forwarded

counter are available for use (appropriate accounting records can be used)7210 SAS-M and 7210 SAS-T Services Guide Page 35

Service EntitiesConfiguration Notes for use of Default QinQ SAPs for transit service in a ring deployment

If an Epipe service is used with Default QinQ SAPs on the ring ports for transit service in a ring deployment, no protection mechanism is available for the transit service (that is, Epipe service with the Default QinQ SAPs on ring ports). Both Epipe and VPLS services which are originating on different nodes in the ring can use the transit service. Protection/Loop-detection mechanisms can be implemented for VPLS service configured in the ring nodes, by using MVPLS with xSTP on the nodes where the VPLS service is configured. No protection mechanisms are available for use with Epipe services on the node that originates the service.

If a VPLS service is used with Default QinQ SAPs on the ring ports for transit service in a ring deployment, either MVPLS/xSTP or G8032 can be used to protect the transit service (that is, VPLS service with the Default QinQ SAPs on ring ports). In this case, VPLS service which are originating on different nodes in the ring and use the transit VPLS service are also protected. Epipe services which are originating on different nodes in the ring cannot use the transit VPLS service.

When using VPLS service with Default QinQ SAPs for transit service with either G8032 or MVPLS with xSTP configured for protection, load-balancing of the traffic based on the VLAN IDs is not possible. If load-balancing is desired then it is better to use Epipe service with Default QinQ SAPs as the transit service.

SAP Configuration Considerations (applicable for both Network mode and access-uplink mode)

When configuring a SAP, consider the following (applicable to both network mode and access-uplink mode):

A SAP is a local entity and only locally unique to a given device. The same SAP ID value can be used on another 7210 SAS-Series.

There are no default SAPs. All SAPs in subscriber services must be created. The default administrative state for a SAP at creation time is administratively enabled. When a SAP is deleted, all configuration parameters for the SAP will also be deleted. A SAP is owned by and associated with the service in which it is created in each router. A port with a dot1q encapsulation type means the traffic for the SAP is identified based on

a specific IEEE 802.1Q VLAN ID value. The VLAN ID i