Nokia Proprietary and confidential.Use pursuant to applicable agreements.
7210 SERVICE ACCESS SWITCH
7210 SAS X, R6, R12 OS Services GuideRelease 9.0.R1
3HE11480AAAATQZZA
Issue: 01
November 2016
7210 SAS X, R6, R12 OS Services Guide Release 9.0.R1
2
7210 SAS X, R6, R12 OS Services Guide
3HE11479AAAATQZZA Issue: 01
Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or tradenames of their respective owners.
The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein.
2013, 2016 Nokia.
Contains proprietary/trade secret information which is the property of Nokia and must not be made available to, or copied or used by anyone outside Nokia without its written authorization. Not to be used or disclosed except in accordance with applicable agreements.
7210 SAS-X, R6, R12 OS Services Guide Page 3
TABLE OF CONTENTS
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Services and SAP Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31SAP Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
QinQ SAP Configuration restrictions for 7210 SAS in Network mode only . . . . . . . . . . . . . . . . . . . . .34Service Distribution Points (SDPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
SDP Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Spoke and MESH SDPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37SDP Using BGP Route Tunnel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37SDP Keepalives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37SDP Administrative Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Mixed-LSP Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40G.8032 Ethernet Ring Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Overview of G.8032 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Ethernet Ring Sub-Rings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Virtual and Non-Virtual Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Ethernet Ring Sub Ring using non-virtual-link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Support for Hardware-based 100ms CCM Timers for G.8032 MEPs . . . . . . . . . . . . . . . . . . . . . . . . . .53Configuration Guidelines for 7210 SAS-R6 and 7210 SAS-R12 . . . . . . . . . . . . . . . . . . . . . . . . . . .54Lag Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
OAM Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54QoS Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Support Service and Solution Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Configuration guidelines for G.8032 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Service Creation Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Table of Contents
Page 4 7210 SAS-X, R6, R12 OS Services Guide
Deploying and Provisioning Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Phase 1: Core Network Construction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Phase 2: Service Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Phase 3: Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configuring Global Service Entities with CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Service Model Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Common Configuration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuring Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Customer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuring an SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67SDP Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Configuring an SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Configuring a Mixed-LSP SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Ethernet Connectivity Fault Management (ETH-CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Common Actionable Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74MEP and MIP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configuring ETH-CFM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Applying ETH-CFM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Modifying Customer Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Deleting Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Modifying SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Deleting SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Layer 2 Control Processing (L2CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Global Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
VLL ServicesEthernet Pipe (Epipe) Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Epipe Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Epipe with PBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Support 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) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Feature Support, Configuration notes and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Epipe Oper State decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Pseudowire Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Pseudowire Switching with Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Pseudowire Switching Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Pseudowire Switching TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Static-to-Dynamic Pseudowire Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Pseudowire Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145VLL Resilience with Two Destination PE Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Dynamic Multi-Segment Pseudowire Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Pseudowire Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Configuring VLLs using Dynamic MS-PWs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Table of Contents
7210 SAS-X, R6, R12 OS Services Guide Page 5
Pseudowire Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158VCCV OAM for Dynamic MS-PWs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161VCCV-Ping on Dynamic MS-PWs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161VCCV-Trace on Dynamic MS-PWs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Example Dynamic MS-PW Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Master-Slave Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Access Node Resilience Using MC-LAG and Pseudowire Redundancy. . . . . . . . . . . . . . . . . . . . . . .173VLL Resilience for a Switched Pseudowire Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Pseudowire Redundancy Service Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178Redundant VLL Service Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178T-LDP Status Notification Handling Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
Processing Endpoint SAP Active/Standby Status Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Processing and Merging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
Epipe Configuration for MPLS-TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182VLL Spoke SDP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183Credit Based Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
VLAN Range for SAPs in an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Processing behavior for SAPs using VLAN ranges in access-uplink mode . . . . . . . . . . . . . . . . . .187VLAN Range SAPs feature Support and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Processing behavior for SAPs using VLAN ranges in network mode . . . . . . . . . . . . . . . . . . . . . .189
VLL Service Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191QoS Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Filter Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192MAC Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Configuring a VLL Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193Basic Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194Configuring VLL Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Creating an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196Creating an Epipe Service for 7210 SAS-X with range SAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Using Spoke SDP Control Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Pseudowire Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Configuring VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Configuring VLL Resilience for a Switched Pseudowire Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Modifying Epipe Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213Disabling an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213Re-Enabling an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214Deleting an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
VLL Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
Virtual Private LAN ServiceVPLS Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268
VPLS Packet Walkthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269 VPLS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
VPLS Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273VPLS over MPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274
Table of Contents
Page 6 7210 SAS-X, R6, R12 OS Services Guide
VPLS MAC Learning and Packet Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Configuration notes for VPLS forwarding: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Configuration Guidelines for IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Multicast VLAN Registration (MVR) support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278L2 Forwarding Table Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
FIB Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280FIB Size Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Local and Remote Aging Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Disable MAC Aging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Disable MAC Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Unknown MAC Discard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281VPLS and Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282MAC Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
VPLS and Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Spanning Tree Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Multiple Spanning Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286MSTP for QinQ SAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Provider MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Enhancements to the Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
VPLS Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Spoke SDP Redundancy for Metro Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Spoke 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Table of Contents
7210 SAS-X, R6, R12 OS Services Guide Page 7
Service Binding Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315Bound Service Name Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315Binding a Service Name to an IP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315
Routed VPLS Specific ARP Cache Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316The allow-ip-int-binding VPLS Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316
Routed VPLS SAPs only Supported on Standard Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . .316LAG Port Membership Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317VPLS Feature Support and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317
VPLS SAP Ingress IP Filter Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318QoS Support for VPLS SAPs and IP interface in a Routed VPLS service . . . . . . . . . . . . . . . . . . .321Routed VPLS Supported Routing Related Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321Spanning Tree and Split Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322
Routed VPLS support available and Caveats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323Configuring a VPLS Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325
Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328Configuring VPLS Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329
Creating a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330Configuring a VPLS SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337Configuring SDP Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347
Configuring VPLS Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349Creating a Management VPLS for SAP Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349Creating a Management VPLS for Spoke SDP Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351Configuring a BGP-Auto-Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .353Configuring Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355Configuring Selective MAC Flush. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360
Configuring BGP Auto-Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361
Configuring AS Pseudo-wire in VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365
Modifying VPLS Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365Modifying Management VPLS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366Deleting a Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366Disabling a Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367
Deleting a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368Disabling a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368Re-Enabling a VPLS Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369
VPLS Services Command Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371
Service Global CommandsShow Command Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .457Show, Clear, Debug, Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459
Table of Contents
Page 8 7210 SAS-X, R6, R12 OS Services Guide
VLL Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501VLL Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556VLL Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560VPLS Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563VPLS Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625VPLS Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
IEEE 802.1ah Provider Backbone BridgingIEEE 802.1ah Provider Backbone Bridging (PBB) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634PBB Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Integrated PBB-VPLS Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635PBB Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637PBB Mapping to Existing VPLS Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638SAP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
PBB B-VPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640PBB I-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
PBB Packet Walkthrough. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642PBB ELINE Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
PBB Resiliency for B-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644Access Multi-Homing for Native PBB (B-VPLS over SAP Infrastructure) . . . . . . . . . . . . . . . . . . . . . 645PBB QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646PBB ACL Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650PBB ELAN and ELINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650MC-LAG Multihoming for Native PBB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
PBB Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653PBB Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Internet Enhanced ServiceIES Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690IES Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
IP Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691IPv6 support for IES IP interfaces (in network mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
SAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693CPE Connectivity Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
QoS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693CPU QoS for IES access interfaces in network mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Filter Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694VRRP support for IES IP interfaces in network mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Configuring an IES Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697Configuring IES Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
Configuring an IES Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698Configuring IES Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Table of Contents
7210 SAS-X, R6, R12 OS Services Guide Page 9
Configuring SAP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .700Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .700
Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .702Modifying IES Service Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .702Deleting an IES Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .703Disabling an IES Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .704Re-Enabling an IES Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .704
IES Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .705IES Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .737
Virtual Private Routed Network ServiceVPRN Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .752
Routing Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .753BGP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .754Route Distinguishers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .755
Route Reflector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .755CE to PE Route Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .756
BGP Fast Reroute in a VPRN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .759BGP Fast Reroute in a VPRN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .759
VPRN Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .760IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .760IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .761SAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .761
IPv6 support for VPRN IP interfaces (in network mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .761Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .762
QoS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .763Filter Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .763
DSCP Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .764CE to PE Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .765
PE to PE Tunneling Mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .765Per VRF Route Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .765
Spoke SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .765Using OSPF in IP-VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .766Service Label Mode of a VPRN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .767
Multicast in IP-VPN Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .767Multicast Protocols Supported in the Provider Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .769
Inter-AS VPRNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .770Configuring a VPRN Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .775
Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .776Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .777Configuring VPRN Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .778
Creating a VPRN Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .778Configuring Global VPRN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .779
Configuring VPRN Protocols - OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .785VPRN OSPF CLI Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .786
Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .787Modifying VPRN Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .787Deleting a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .788
Table of Contents
Page 10 7210 SAS-X, R6, R12 OS Services Guide
Disabling a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789Re-enabling a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
VPRN Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791Command Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791VPRN Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933VPRN Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009VPRN Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
Common CLI Command DescriptionsCommon Service Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
Appendix: Port-Based Split HorizonOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020Configuration Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
Appendix: DHCP ManagementDHCP Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
DHCP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028Using Option 82 Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028Trusted and Untrusted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029DHCP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
Common Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031Configuration Guidelines for DHCP relay and snooping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031Configuring Option 82 Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
7210 SAS-X, R6, R12 OS Services Guide Page 11
List of Tables
Getting StartedTable 1: Configuration Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Services OverviewTable 2: Service and Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Table 3: SAP types in a service when QinQ SAP is in use (Network mode operation) . . . . . . . . . . . . . .34Table 4: Defect conditions and priority settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Table 5: ETH-CFM Support Matrix for 7210 SAS-R6 and 7210 SAS-R12 devices . . . . . . . . . . . . . . . . .76Table 6: ETH-CFM Support Matrix for 7210 SAS-X devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Table 7: L2CP support for 7210 SAS-X, 7210 SAS-R6 and 7210 SAS-R12 . . . . . . . . . . . . . . . . . . . . . .89Table 8: CCM transmission interval for 7210 SAS-X, 7210 SAS-R6 and 7210 SAS-R12 . . . . . . . . . . .125
VLL ServicesTable 9: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .246
Virtual Private LAN ServiceTable 10: Routing behavior in RVPLS and interaction ARP Cache and MAC FIB . . . . . . . . . . . . . . . . . .316Table 11: ACL Lookup behavior with Ingress Override filter attached to an IES interface in a R-VPLS
service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318Table 12: ACL Lookup behavior without Ingress Override filter attached to an IES interface in a
R-VPLS service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319Table 13: Routing Protocols on IP interfaces bound to a VPLS service. . . . . . . . . . . . . . . . . . . . . . . . . .321Table 14: SAP BPDU Encapsulation States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344Table 15: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .437
Virtual Private Routed Network ServiceTable 16: BGP Fast Reroute Scenarios (VPRN Context) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .759Table 17: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .864
Page 12 7210 SAS-X, R6, R12 OS Services Guide
List of Tables
7210 SAS-X, R6, R12 OS Services Guide Page 13
List of Figures
Services 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Figure 5: MPLS Service Distribution Point (SDP) Pointing From ALA-A to ALA-B . . . . . . . . . . . . . . . . .36Figure 6: G.8032 Ring in the Initial State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Figure 7: 0-1 G.8032 Ring in the Protecting State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Figure 8: 0-4 G.8032 Sub-Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Figure 9: 0-6 Sub-Ring Homed to VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Figure 10: Service Creation and Implementation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Figure 11: Ethernet OAM Model for Ethernet Access - Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Figure 12: Ethernet OAM Model for Ethernet Access - Wholesale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
VLL ServicesFigure 13: Epipe/VLL Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133Figure 14: Pseudowire Service Switching Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Figure 15: VLL Resilience with Pseudowire Redundancy and Switching . . . . . . . . . . . . . . . . . . . . . . . . .141Figure 16: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146Figure 17: Dynamic MS-PW Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148Figure 18: Figure 2 MS-PW Addressing using FEC129 AII Type 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Figure 19: Advertisement of PE Addresses by PW Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Figure 20: Signaling of Dynamic MS-PWs using T-LDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Figure 21: Mapping of AII to SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Figure 22: VLL Using Dynamic MS-PWs, Inter-AS Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152Figure 23: Pseudowire Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159Figure 24: Dynamic MS-PW Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Figure 25: Master-Slave Pseudowire Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167Figure 26: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170Figure 27: VLL Resilience with Pseudowire Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172Figure 28: Access Node Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174Figure 29: VLL Resilience with Pseudowire Redundancy and Switching . . . . . . . . . . . . . . . . . . . . . . . . .176Figure 30: Redundant VLL Endpoint Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178Figure 31: SDPs Uni-Directional Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203Figure 32: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Figure 33: VLL Resilience with Pseudowire Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
Virtual Private LAN ServiceFigure 34: VPLS Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Figure 35: Access Port Ingress Packet Format and Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270Figure 36: Network Port Egress Packet Format and Flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271Figure 37: MVR and MVR by Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279Figure 38: Access Resiliency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287Figure 39: HVPLS with Spoke Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294
Page 14 7210 SAS-X, R6, R12 OS Services Guide
Figure 40: HVPLS Resiliency Based on AS Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Figure 41: Dual Homed MTU-s in Two-Tier Hierarchy H-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296Figure 42: HVPLS with SAP Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Figure 43: Dual Homed CE Connection to VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Figure 44: BGP AD NLRI versus IP VPN NLRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307Figure 45: Generalized Pseudowire-ID FEC Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308Figure 46: BGP-AD and T-LDP Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Figure 47: Example Configuration for Protected VPLS SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Figure 48: Example Configuration for Protected VPLS Spoke SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352Figure 49: Example Configuration for Loadbalancing Across Two Protected VPLS Spoke SDPs . . . . . 355Figure 50: BGP AD Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Figure 51: BGP-AD CLI Command Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Figure 52: Sample Topology-AS Pseudo-wire in VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
IEEE 802.1ah Provider Backbone BridgingFigure 53: Large HVPLS Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635Figure 54: Large PBB-VPLS Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636Figure 55: QinQ Payload in Provider Header Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .637Figure 56: PBB Mapping to VPLS Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638Figure 57: PBB Packet Walkthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .642Figure 58: Access Dual-Homing into PBB BEBs - Topology View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Internet Enhanced ServiceFigure 59: Internet Enhanced Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Virtual Private Routed Network ServiceFigure 60: Virtual Private Routed Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752Figure 61: Route Distinguisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755Figure 62: Directly Connected IP Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757Figure 63: Multiple Hops to IP Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757Figure 64: Multicast in IP-VPN Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768Figure 65: Inter-AS Option-A: VRF-to-VRF Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771Figure 66: Inter-AS Option-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772Figure 67: Option C Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773Figure 68: OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921Figure 69: Split Horizon Group Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1020Figure 70: IP Address Assignment with DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1026
7210 SAS-X, R6, R12 OS Services Guide Page 15
Preface
About This GuideThis guide describes subscriber services, and mirroring support provided by the 7210 SAS-X and R6 presents examples to configure and implement various protocols and services.
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.
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.
Audience
This manual is intended for network administrators who are responsible for configuring the . 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) operations
Preface
Page 16 7210 SAS-X, R6, R12 OS Services Guide
List of Technical Publications
The 7210 SAS-M, T, Mxp, Sx, X, R6, R12 documentation set is composed of the following books:
7210 SAS M, T, Sx, X, R6, R12, Mxp Basic System Configuration GuideThis guide describes basic system configurations and operations.
7210 SAS M, T, Sx, X, R6, R12, Mxp System Management GuideThis guide describes system security and access configurations as well as event logging and accounting logs.
7210 SAS M, T, Sx, X, R6, R12, Mxp Interface Configuration GuideThis guide describes card, Media Dependent Adapter (MDA), link aggregation group (LAG), and port provisioning.
7210 SAS M, T, Sx, X, R6, R12, Mxp Router Configuration GuideThis guide describes logical IP routing interfaces and associated attributes such as an IP address, port, as well as IP and MAC-based filtering.
7210 SAS M, T, Sx, X, R6, R12, Mxp Routing Protocols GuideThis guide provides an overview of routing concepts and provides configuration examples for route policies.
7210 SAS-X, R6, R12 OS Services GuideThis guide describes how to configure service parameters such as customer information and user services.
7210 SAS M, T, Sx, X, R6, R12, Mxp OS OAM and Diagnostic GuideThis guide describes how to configure features such as service mirroring and Operations, Administration and Management (OAM) tools.
7210 SAS-X, R6, R12 OS Quality of Service GuideThis guide describes how to configure Quality of Service (QoS) policy management.
Preface
7210 SAS-X, R6, R12 OS Services Guide Page 17
Technical 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://www.alcatel-lucent.com/wps/portal/support
Preface
Page 18 7210 SAS-X, R6, R12 OS Services Guide
Getting 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 Process
Area Task Chapter
Subscribers Subscriber servicesGlobal entities Configuring Global Service Entities with CLI on page 61VLL services Ethernet Pipe (Epipe) Services on page 132VPLS service Virtual Private LAN Service on page 267VPRN service Virtual Private Routed Network Service on page 751
Reference List of IEEE, IETF, and other proprietary entities.
Standards and Protocol Support on page 1913
7210 SAS-X, R6, R12 OS Services Guide Page 19
Getting Started
Page 20 7210 SAS-X, R6, R12 OS Services Guide
7210 SAS-X, R6, R12 OS Services Guide Page 21
Services Command Reference
In This ChapterThis chapter provides the command reference trees for the 7210 SAS services.
Topics include:
Global Services Commands Service Configuration Commands
VPLS Service Configuration Commands on page 372 VPRN Service Configuration Commands on page 792
In This Chapter
Page 22 7210 SAS-X, R6, R12 OS Services Guide
7210 SAS-X, R6, R12 OS Services Guide Page 23
SERVICES OVERVIEW
In This SectionThis section provides an overview of the 7210 SAS X,R6, R12-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 35
Service Creation Process Overview on page 57 Deploying and Provisioning Services on page 58 Configuration Notes on page 59
Introduction
Page 24 7210 SAS-X, R6, R12 OS Services Guide
Introduction
A 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 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) 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.
Distributed services use service distribution points (SDPs) to direct traffic to another 7210 SAS or SR router or other routers that supports MPLS, through 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).
Services
7210 SAS-X, R6, R12 OS Services Guide Page 25
Service Types
The 7210 SAS-X, R6, R12 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 132. Virtual Private LAN Service (VPLS) A Layer 2 multipoint-to-multipoint VPN. See
Virtual Private LAN Service on page 267. 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 751.
Service Policies
Page 26 7210 SAS-X, R6, R12 OS Services Guide
Service 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.
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.
7210 SAS-X allows the scheduling parameters (that is, priority and weight) to be specified per queue. They are no scheduling policies available for use.
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.
Services
7210 SAS-X, R6, R12 OS Services Guide Page 27
Alcatel-Lucent Service Model
In 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 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.
Service Entities
Page 28 7210 SAS-X, R6, R12 OS Services Guide
Service Entities
The 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 35) (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
7
Services
7210 SAS-X, R6, R12 OS Services Guide Page 29
Customers
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 router (). 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 Mode
The Figure 2 shows a SAP used for customer service delivery with SDP used for service transport on 7210 SAS devices that support MPLS uplinks (also known as, network mode platforms).
OSSG002
Customer
27
IP/MPLS Network
SAP
3/1/6
dot1q
SAP
2/2/3
dot1q
Service
Cust-27
SDP
ALA-A
Customer
27
Service Access Points (SAPs)
Page 30 7210 SAS-X, R6, R12 OS Services Guide
Figure 3: Multiple SAPs in a service using QinQ uplinks in 7210 SAS configured in access-uplink mode
The Figure 3 shows a SAP used for customer service delivery with access-uplink SAPs (also known as, QinQ SAPs) used for service transport on 7210 SAS devices that support only L2 uplinks (also known as, access-uplink mode platforms).
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 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,
OSSG002A
Customer27
IP/MPLS Network
SAP1/1/6dot1q
SAP1/1/3dot1q
Service
Cust-27
SDPSAP
ALA-A
Customer27
Services
7210 SAS-X, R6, R12 OS Services Guide Page 31
producing a double tagged frame. 7210 SAS-X, R6, R12 supports QinQ encapsulation for 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
The Figure 4 shows multiple SAPs used for customer service delivery on the same port and belonging to the same service, along with SDP used for service transport on 7210 SAS devices that support MPLS uplinks (also known as, network mode platforms). This is supported only in network mode.
Services and SAP Encapsulations
Table 2 lists the service and SAP Encapsulation information for Ethernet ports:
OSSG003-7210M
Customer27
Network
SAP1/1/5dot1q
PORT #1
SAP1/1/6dot1q Service
Service
SDPCustomer
27
SAP1/1/3dot1q
Customer9
Service Access Points (SAPs)
Page 32 7210 SAS-X, R6, R12 OS Services Guide
With default QinQ SAPs on the ring ports 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 G.8032 or M-VPLS with xSTP for ring protection. When using G.8032, the state of the default QinQ SAPs in the VPLS service can be managed using a separate G.8032 control instance. NOTE: G.8032 control instance cannot use Default QinQ SAPs.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.
SAP Configuration Considerations
When configuring a SAP, consider the following:
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 configured on the node. 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 is stripped off at SAP ingress and the appropriate VLAN ID placed on at SAP egress. As a result, VLAN IDs only have local significance, so the VLAN IDs for the SAPs for a service need not be the same at each SAP.
If a port is administratively shutdown, all SAPs on that port will be operationally out of service.
QinQ access SAPs of type Q1.0 is not supported.
Table 2: Service and Encapsulation
Port Type Encapsulation
Ethernet Null
Ethernet Dot1q
Ethernet QinQ
Services
7210 SAS-X, R6, R12 OS Services Guide Page 33
A SAP cannot be deleted until it has been administratively disabled (shutdown). Each SAP can have one each of the following policies assigned:
Ingress filter policy Egress filter policy Ingress QoS policy Accounting policy
QinQ SAP Configuration restrictions for 7210 SAS in Network mode only
Page 34 7210 SAS-X, R6, R12 OS Services Guide
QinQ SAP Configuration restrictions for 7210 SAS in Network mode only
Listed below are the QinQ access SAP configuration guidelines for 7210 SAS in Network mode only.
Processing of tagged packets received on SAPs configured in a service in which a QinQ SAP is also in use (not applicable when a QinQ SAP is not provisioned in a service).
When a QinQ SAP is configured in a service, the number of VLAN tags in the packets received on NULL SAP, Dot1q SAP and QinQ SAP configured in the same service should match the number of VLAN tags implied by the port encapsulation mode. Packets that do not match are dropped by the hardware. That is, packets received with more than two VLAN tags on a QinQ SAP are dropped, packets received with more than one VLAN tag on a Dot1q SAP are dropped and packets received with tags (even packet with a priority tag) on a NULL SAP are dropped. Henceforth in this document, such packets are referred to as extra-tag packets.
When a QinQ SAP is configured in a service, the number of VLAN tags in the packets received on the VC/pseudowire of type vc-vlan should be exactly one and packets received on the VC/pseudowire of type vc-ether should contain no tags (not even priority tag). If either case, packets that contain more number of VLAN tags than the number mentioned above are dropped. Henceforth the document refers to such packets as extra-tag packets.
The system will provide a limited amount of counters to count the number of extra-tag packets dropped on SAP ingress. These counters are intended for diagnostic use.
Table 3 displays the SAP types allowed in a service when QinQ SAP is in use:
Table 3: SAP types in a service when QinQ SAP is in use (Network mode operation)
0.* QinQ SAP configured in the service will accept only untagged or priority tagged packets, irrespective of whether a QinQ SAP is configured in the service or not.
NOTE: 7210 supports a mechanism to transport QinQ packets in an Epipe with 2 or more tags, with some restrictions. For more information, see Ethernet Pipe (Epipe) Services on page 132.
SAP configured in the service
SAPs Not Allowed for configuration in the same service
QinQ Q.* SAP, Dot1q Default SAP
Q.* Q1.Q2
Dotq1 default SAP Q1.Q2
Services
7210 SAS-X, R6, R12 OS Services Guide Page 35
Service Distribution Points (SDPs)
A service distribution point (SDP) acts as a logical way to direct traffic from one router to another through a uni-directional (one-way) service tunnel. The SDP terminates at the far-end device which directs packets to the correct service egress SAPs on that device. A distributed service consists of a configuration with at least one SAP on a local node, one SAP on a remote node, and an SDP binding the service to the service tunnel.
An SDP has the following characteristics:
An SDP is locally unique to a participating routers. The same SDP ID can appear on other 7210 SAS-Series routers.
An SDP uses the system IP address to identify the far-end edge router. An SDP is not specific to any one service or any type of service. Once an SDP is created,
services are bound to the SDP. An SDP can also have more than one service type associated with it.
All services mapped to an SDP use the same transport encapsulation type defined for the SDP.
An SDP is a management entity. Even though the SDP configuration and the services carried within are independent, they are related objects. Operations on the SDP affect all the services associated with the SDP. For example, the operational and administrative state of an SDP controls the state of services bound to the SDP.
An SDP from the local device to a far-end router requires a return path SDP from the far-end 7210 SAS-Series back to the local router. Each device must have an SDP defined for every remote router to which it wants to provide service. SDPs must be created first, before a distributed service can be configured.
SDP Binding
To configure a distributed service from ALA-A to ALA-B, the SDP ID (1) must be specified in the service creation process in order to bind the service to the tunnel (the SDP). Otherwise, service traffic is not directed to a far-end point and the far-end device(s) cannot participate in the service (there is no service). To configure a distributed service from ALA-B to ALA-A, the SDP ID (5) must be specified.
Service Distribution Points (SDPs)
Page 36 7210 SAS-X, R6, R12 OS Services Guide
Figure 5: MPLS Service Distribution Point (SDP) Pointing From ALA-A to ALA-B
OSSG004-7210M
SUBSCRIBERS SUBSCRIBERS
SERVICEACCESSPOINTS
SERVICEACCESSPOINTS
SERVICEDISTRIBUTION
POINTS
SERVICEDISTRIBUTION
POINTS
Customer27
IP NETWORK
MPLSEncapsulation
SAP3/1/6dot1q
Service
Cust-27
Cust-25
Service
Cust-7
Service
Service
Cust-27
Cust-25
Service
Cust-7
Service
SDP-4
ALA-A ALA-B
DEMUXSAP2/2/2dot1q
SAP4/1/6dot1q
SAP
SAP
SAP
Customer25
Customer7
Customer7
Customer25
Customer27
Services
7210 SAS-X, R6, R12 OS Services Guide Page 37
Spoke and MESH SDPs
When an SDP is bound to a service, it is bound as either a spoke SDP or a mesh SDP. The type of SDP indicates how flooded traffic is transmitted.
A spoke SDP is treated like the equivalent of a traditional bridge port where flooded traffic received on the spoke SDP is replicated on all other ports and not transmitted on the port it was received.
All mesh SDPs bound to a service are logically treated like a single bridge port for flooded traffic where flooded traffic received on any mesh SDP on the service is replicated to other ports (spoke SDPs and SAPs) and not transmitted on any mesh SDPs.
SDP Using BGP Route Tunnel
SDP is enhanced to use BGP route tunnel to extend inter-AS support for L2 and L3 VPN services. An SDP can be configured to use MPLS transport method. MPLS SDP support is enhanced to allow a BGP route tunnel to reach the far-end PE. A single method of tunneling is allowed per SDP (for example, LDP, RSVP-TE LSP or BGP route tunnel). BGP route tunnel method is excluded if multi-mode transport is enabled for an SDP.
A single method of tunneling is allowed per SDP (for example: LDP, RSVP-TE LSP or BGP route tunnel). BGP route tunnel method is excluded if multi-mode transport is enabled for an SDP.
For inter-AS far-end PE, next-hop for BGP route tunnel must be one of the local ASBR. The LSP type selected to reach the local ASBR (BGP labeled route next-hop) must be configured under the BGP global context. LDP must be supported to provide transport LSP to reach the BGP route tunnel next-hop.
Only BGP route labels can be used to transition from ASBR to the next-hop ASBR. The global BGP route tunnel transport configuration option must be entered to select an LSP to reach the PE node from ASBR node. On the last BGP segment, both BGP+LDP and LDP routes may be available to reach the far-end PE from the ASBR node. LDP LSP must be preferred due to higher protocol priority. This leads to just one label besides other labels in stack to identify VC/VPN at far-end PE nodes.
SDP Keepalives
SDP keepalives actively monitor the SDP operational state using periodic Alcatel-Lucent SDP ping echo request and echo reply messages. Alcatel-Lucent SDP ping is a part of Alcatel-Lucents
Service Distribution Points (SDPs)
Page 38 7210 SAS-X, R6, R12 OS Services Guide
suite of service diagnostics built on an Alcatel-Lucent service-level OA&M protocol. When SDP ping is used in the SDP keepalive application, the SDP echo request and echo reply messages are a mechanism for exchanging far-end SDP status.
Configuring SDP keepalives on a given SDP is optional. SDP keepalives for a particular SDP have the following configurable parameters:
Admin up/admin down state Hello time Message length Max drop count Hold down time
SDP keepalive echo request messages are only sent when the SDP is completely configured and administratively up and SDP keepalives is administratively up. If the SDP is administratively down, keepalives for the SDP are disabled.
SDP keepalive echo request messages are sent out periodically based on the configured Hello Time. An optional message length for the echo request can be configured. If max drop count echo request messages do not receive an echo reply, the SDP will immediately be brought operationally down.
If a keepalive response is received that indicates an error condition, the SDP will immediately be brought operationally down.
Once a response is received that indicates the error has cleared and the hold down time interval has expired, the SDP will be eligible to be put into the operationally up state. If no other condition prevents the operational change, the SDP will enter the operational state.
For information about configuring keepalive parameters, refer to Configuring an SDP on page 67.
SDP Administrative Groups
This feature introduces the support of SDP administrative groups, referred to as SDP admin groups. SDP admin groups provide a way for services using a PW template to automatically include or exclude specific provisioned SDPs. SDPs sharing a specific characteristic or attribute can be made members of the same admin group.
The user first creates the admin groups that are to be used by SDPs on this node:
config>service>sdp-group>group-name group-name value group-value create
Services
7210 SAS-X, R6, R12 OS Services Guide Page 39
A maximum of 32 admin groups can be created. The no option is only allowed if the group-name is not referenced in a pw-template or SDP.
The group value ranges from zero (0) to 31. It is uniquely associated with the group name at creation time. If the user attempts to configure another group nam
Top Related