986
Alcatel-Lucent Service Access Switch| Release 6.0 Rev.06 7210 SAS-M and 7210 SAS-T OS Services Guide 93-0486-01-06 93-0486-01-06 Alcatel-Lucent Proprietary This 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.

7210 SAS-M and 7210 SAS-T OS Services Guide · 7210 SAS-M and 7210 SAS-T Services Guide Page 3 Table of Contents Preface

Embed Size (px)

Citation preview

  • Alcatel-LucentService Access Switch| Release 6.0 Rev.067 2 1 0 S A S - M a n d 7 2 1 0 S A S - T O S

    S e r v i c e s G u i d e

    93-0486-01-06

    93-0486-01-06

    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

    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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Default SAP on a Dot1q Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Default SAPs on a QinQ Port (supported only on 7210 SAS-M and 7210 SAS-T devices configured in ac-

    cess-uplink mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Configuration Notes for use of Default QinQ SAPs for transit service in a ring deployment . . . . . .35Services and SAP Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35SAP 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-M and 7210 SAS-T in Access-Uplink mode only

    . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Service Distribution Points (SDPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

    SDP Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Spoke and MESH SDPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42SDP Using BGP Route Tunnel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42SDP Keepalives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42G.8032 Ethernet Ring Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

    Overview of G.8032 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Ethernet Ring Sub-Rings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

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

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

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

    Phase 1: Core Network Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Phase 2: Service Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Phase 3: Service Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

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

  • Table of Contents

    Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

    Configuring Global Service Entities with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Service Model Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

    Basic Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

    Configuring Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Customer Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

    Configuring an SDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69SDP Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69Configuring an SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

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

    Configuring ETH-CFM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Applying ETH-CFM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

    Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Modifying Customer Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Deleting Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Modifying SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87Deleting SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

    Global Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

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

    Cpipe Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Cpipe Service Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

    Unstructured Mode (SAToP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Structured Mode (CESoPSN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121TDM Pseudowire Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Circuit Emulation Parameters and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

    Ethernet Pipe (Epipe) Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Epipe Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Epipe with PBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

    Support for processing of packets received with more than 2 tags on a QinQ SAP in Epipe service (only on 7210 SAS-M network mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

    Feature Support, Configuration notes and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139Configuration of Epipe service for processing of packets received with more than 2 tags on a QinQ SAP

    (only on 7210 SAS-M network mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Epipe Oper State decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142Pseudowire Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

    Pseudowire Switching with Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Pseudowire Switching Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147Pseudowire Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

    Master-Slave Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149VLL Resilience for a Switched Pseudowire Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

    Pseudowire Redundancy Service Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Redundant VLL Service Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158T-LDP Status Notification Handling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

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

  • Table of Contents

    Processing Endpoint SAP Active/Standby Status Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160Access Node Resilience Using MC-LAG and Pseudowire Redundancy (in Access-Uplink Mode). . .161

    Processing and Merging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163VLL Service Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

    SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165SAP Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166VLAN Range for SAPs in an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

    Processing behavior for SAPs using VLAN ranges in access-uplink mode . . . . . . . . . . . . . . . . .166VLAN Range SAPs feature Support and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167Processing behavior for SAPs using VLAN ranges in network mode . . . . . . . . . . . . . . . . . . . . . .168QoS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169Filter Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169MAC Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

    Access Node Resilience Using MC-LAG and Pseudowire Redundancy. . . . . . . . . . . . . . . . . . . . . . .171Configuring a VLL Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

    Basic Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174Configuring VLL Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

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

    Using Spoke SDP Control Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194Configuring VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196Configuring VLL Resilience for a Switched Pseudowire Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

    Modifying a Cpipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Deleting a Cpipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201Modifying Epipe Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Disabling an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Re-Enabling an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203Deleting an Epipe Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

    VLL Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205

    Virtual Private LAN ServiceVPLS Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

    VPLS Packet Walkthrough in Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255VPLS Packet Walkthrough in Access Uplink Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258

    VPLS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261VPLS Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261VPLS over MPLS in Network Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262VPLS over QinQ Spokes for 7210 SAS-M and 7210 SAS-T devices Configured in Access Uplink Mode263VPLS MAC Learning and Packet Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

    IGMP Snooping in Network Mode and Access-uplink Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Configuration Guidelines for IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

    Multicast VLAN Registration (MVR) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267Table Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268

    FIB Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269

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

  • Table of Contents

    FIB Size Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Local and Remote Aging Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270Disable MAC Aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270Disable MAC Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270Unknown MAC Discard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270VPLS and Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271MAC Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271

    VPLS and Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273Spanning Tree Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273Multiple Spanning Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275MSTP for QinQ SAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277Provider MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277Enhancements to the Spanning Tree Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279

    VPLS Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282Spoke SDP Redundancy for Metro Interconnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282Spoke SDP Based Redundant Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284Inter-Domain VPLS Resiliency Using Multi-Chassis Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . .285

    VPLS Access Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286STP-Based Redundant Access to VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286Redundant Access to VPLS Without STP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288

    MAC Flush Message Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289MAC Flush with STP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291Selective MAC Flush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292Dual Homing to a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

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

    BGP Auto-Discovery for LDP VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296BGP AD Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296FEC Element for T-LDP Signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297BGP-AD and Target LDP (T-LDP) Interaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300SDP Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301Automatic Creation of SDPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301Manually Provisioned SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302Automatic Instantiation of Pseudowires (SDP Bindings) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302Mixing Statically Configured and Auto-Discovered Pseudowires in a VPLS service. . . . . . . . . . . . . .303Resiliency Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303

    Routed VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304IES IP Interface Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304Assigning a Service Name to a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304Service Binding Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305

    Bound Service Name Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305Binding a Service Name to an IP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305IP Interface Attached VPLS Service Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306IP Interface and VPLS Operational State Coordination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306IP Interface MTU and Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306Unicast IP Routing into a VPLS Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307

    ARP and VPLS FIB Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307

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

  • Table of Contents

    Routed VPLS Specific ARP Cache Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308The allow-ip-int-binding VPLS Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308

    Routed VPLS SAPs only Supported on Standard Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . .308LAG Port Membership Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309VPLS Feature Support and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309

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

    Routed VPLS Caveats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313Epipe Emulation using Dot1q VLAN range SAP in VPLS with G8032 . . . . . . . . . . . . . . . . . . . . . . . . . . .314

    Configuration guidelines and restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315Configuring a VPLS Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319

    Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323Configuring VPLS Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324

    Creating a VPLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325Configuring a VPLS SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332Configuring SDP Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343

    Configuring VPLS Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345Creating a Management VPLS for SAP Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345Creating a Management VPLS for Spoke SDP Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347Configuring Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350Configuring Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352Configuring Selective MAC Flush. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358Configuring Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359

    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

    IEEE 802.1ah Provider Backbone BridgingIEEE 802.1ah Provider Backbone Bridging (PBB) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .458PBB Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459

    Integrated PBB-VPLS Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459PBB Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .461PBB Mapping to Existing VPLS Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .462SAP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .464

    PBB B-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .464PBB I-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .464

    PBB Packet Walkthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .466

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

  • Table of Contents

    PBB ELINE Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468PBB Resiliency for PBB epipe service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468PBB Resiliency for B-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468

    Access Multi-Homing for Native PBB (B-VPLS over SAP Infrastructure) . . . . . . . . . . . . . . . . . . . . . .469PBB QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .470PBB ACL Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .471Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .471Configuration Guidelines (for 7210 SAS-M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .472

    Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .474PBB ELAN and ELINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .474MC-LAG Multihoming for Native PBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .475

    PBB Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .477PBB Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .485

    Internet Enhanced ServiceIES Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .520IES Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .521

    IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .521. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .521

    SAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522

    Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522CPE Connectivity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522

    QoS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .523CPU QoS for IES interfaces in access-uplink mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .523CPU QoS for IES access interfaces in network mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .524

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

    Configuring an IES Service with CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .527Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .528Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .530Configuring IES Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .531

    Configuring an IES Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .531Configuring IES Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .532Configuring SAP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .533Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .533

    Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .534Modifying IES Service Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .534Deleting an IES Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .535Disabling an IES Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .536Re-Enabling an IES Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .536

    IES Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .537

    Virtual Private Routed Network ServiceVPRN Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .570

    Routing Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .571BGP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .572Route Distinguishers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .573

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

  • Table of Contents

    Route Reflector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .573CE to PE Route Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .574

    VPRN Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .577IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .578SAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .578

    Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .578QoS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .579Filter Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .579

    DSCP Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .580Default DSCP Mapping Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .581

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

    Service Label Mode of a VPRN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .584Configuring a VPRN Service with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585

    Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .586Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .587Configuring VPRN Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .588

    Creating a VPRN Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .588Configuring Global VPRN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .589

    Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .596Modifying VPRN Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .596Deleting a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .597Disabling a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .598Re-enabling a VPRN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .599

    VPRN Services Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .601

    Service Global CommandsShow Command Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .695Show, Clear, Debug, Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .697

    IES Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .721VPRN Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .741VPRN Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .814VPRN Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .818VLL Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .823VLL Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .878VLL Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .881VPLS Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .883VPLS Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .957VPLS Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .962

    Common CLI Command DescriptionsCommon Service Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .966

    Appendix: Split HorizonOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .968

    Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .968Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .969

    Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .971

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

  • Table of Contents

    Appendix: DHCP ManagementDHCP Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .974

    DHCP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .976Using Option 82 Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .976Trusted and Untrusted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .977DHCP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .977

    Common Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .979Configuration Guidelines for DHCP relay and snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .979Configuring Option 82 Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .979

    Page 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Table 3: SAP types in a service when QinQ SAP is in use (Network mode operation) . . . . . . . . . . . . . .37Table 4: SAP and Service Combinations for 7210 SAS-M and 7210 SAS-T in access-uplink mode . . . .38Table 5: Defect conditions and priority settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Table 6: ETH-CFM Support Matrix for 7210 SAS-M Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Table 7: ETH-CFM Support Matrix for 7210 SAS-T Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

    VLL ServicesTable 8: T1 Framing for CAS (RBS) Support in a T1 ESF Multi-frame. . . . . . . . . . . . . . . . . . . . . . . . . .123Table 9: Unstructured Payload Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Table 10: Default and Minimum Payload Size for CESoPSN without CAS. . . . . . . . . . . . . . . . . . . . . . . .129Table 11: Payload Size for T1 and E1 CESoPSN with CAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Table 12: Control Word Bit Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Table 13: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .235

    Virtual Private LAN ServiceTable 14: Routing behavior in RVPLS and interaction ARP Cache and MAC FIB . . . . . . . . . . . . . . . . . .308Table 15: ACL Lookup behavior with Ingress Override filter attached to an IES interface in a R-VPLS service.310Table 16: ACL Lookup behavior without Ingress Override filter attached to an IES interface in a R-VPLS service311Table 17: SAP BPDU Encapsulation States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340Table 18: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .442

    IEEE 802.1ah Provider Backbone Bridging

    Internet Enhanced Service

    Virtual Private Routed Network ServiceTable 19: DSCP/FC Marking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .580Table 20: Final Disposition of the packet based on per FC and per SAP policer or meter. . . . . . . . . . . .644

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

  • List of Tables

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

  • List of Figures

    Services OverviewFigure 1: Service Entities for SAS-M Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Figure 2: Service Access Point (SAP) for 7210 SAS-M in Network Mode . . . . . . . . . . . . . . . . . . . . . . . .29Figure 3: Multiple SAPs in a service using QinQ uplinks 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 . . . . . . . . . . . . . . . . .41Figure 6: G.8032 Ring in the Initial State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Figure 7: 0-1 G.8032 Ring in the Protecting State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Figure 8: 0-3 Ring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Figure 9: 0-4 G.8032 Sub-Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Figure 10: 0-6 Sub-Ring Homed to VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Figure 11: Service Creation and Implementation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Figure 12: Ethernet OAM Model for Broadband Access - Residential . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Figure 13: Ethernet OAM Model for Broadband Access - Wholesale . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

    VLL ServicesFigure 14: E1 Framing for CAS Support in an E1 Multi-frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122Figure 15: SAToP MPLS Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Figure 16: CESoPSN MPLS Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Figure 17: CESoPSN Packet Payload Format for Trunk-Specific n x 64 kb/s (with and without CAS transport) 125Figure 18: Control Word Bit Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Figure 19: Epipe/VLL Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Figure 20: Pseudowire Service Switching Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144Figure 21: VLL Resilience with Pseudowire Redundancy and Switching . . . . . . . . . . . . . . . . . . . . . . . . .145Figure 22: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148Figure 23: Master-Slave Pseudowire Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Figure 24: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153Figure 25: VLL Resilience with Pseudowire Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155Figure 26: VLL Resilience with Pseudowire Redundancy and Switching . . . . . . . . . . . . . . . . . . . . . . . . .157Figure 27: Redundant VLL Endpoint Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Figure 28: Access Node Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Figure 29: Access Node Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172Figure 30: Default QinQ SAP for Transit Traffic in a Ring Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Figure 31: SDPs Uni-Directional Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Figure 32: VLL Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196Figure 33: VLL Resilience with Pseudowire Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

    Virtual Private LAN ServiceFigure 34: VPLS Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255Figure 35: Access Port Ingress Packet Format and Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256Figure 36: Network Port Egress Packet Format and Flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256Figure 37: VPLS Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258Figure 38: Access Port Ingress Packet Format and Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259Figure 39: Network Port Egress Packet Format and Flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259

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

  • List of Figures

    Figure 40: MVR and MVR by Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268Figure 41: Access Resiliency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276Figure 42: HVPLS with Spoke Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283Figure 43: HVPLS Resiliency Based on AS Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285Figure 44: Dual Homed MTU-s in Two-Tier Hierarchy H-VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286Figure 45: HVPLS with SAP Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291Figure 46: Dual Homed CE Connection to VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293Figure 47: BGP AD NLRI versus IP VPN NLRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297Figure 48: Generalized Pseudowire-ID FEC Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298Figure 49: BGP-AD and T-LDP Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300Figure 50: Epipe Emulation in a ring using VPLS with G.8032 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314Figure 51: Example Configuration for Protected VPLS SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346Figure 52: Example Configuration for Protected VPLS Spoke SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . .348Figure 53: Example Configuration for Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . .350Figure 54: Example Configuration for Loadbalancing Across Two Protected VPLS Spoke SDPs . . . . .352Figure 55: Example Configuration for Load Balancing with Management VPLS . . . . . . . . . . . . . . . . . . .359Figure 56: BGP AD Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361Figure 57: BGP-AD CLI Command Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362Figure 58: Sample Topology-AS Pseudo-wire in VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363

    IEEE 802.1ah Provider Backbone BridgingFigure 59: Large HVPLS Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459Figure 60: Large PBB-VPLS Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .460Figure 61: QinQ Payload in Provider Header Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .461Figure 62: PBB Mapping to VPLS Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .462Figure 63: PBB Packet Walkthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .466Figure 64: Access Dual-Homing into PBB BEBs - Topology View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .469

    Internet Enhanced ServiceFigure 65: Internet Enhanced Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .520

    Virtual Private Routed Network ServiceFigure 66: Virtual Private Routed Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .570Figure 67: Route Distinguisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .573Figure 68: Directly Connected IP Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .575Figure 69: Multiple Hops to IP Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .575Figure 70: Split Horizon Group Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .968Figure 71: IP Address Assignment with DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .974

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

  • Preface

    About This Guide

    This guide describes subscriber services, mirroring support provided by the 7210 SAS-M. All the variants of 7210 SAS-M can be configured in two modes, that is, in network mode and in access-uplink mode. In network mode configuration, 7210 SAS-M 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 appropriate mode can be selected by configuring the BOF appropriately.

    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.

    Notes:

    This user guide is applicable to all 7210 SAS-M platforms, unless specified otherwise.

    In access-uplink and network mode, it is expected that the user will only configure the required CLI parameters appropriate for the mode. Unless otherwise noted, the configuration is similar in both the network mode and access uplink mode.

    This guide also contains 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, it is 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.

    Audience

    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

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

  • Preface

    Service mirroring

    Operation, Administration and Maintenance (OAM) operations

    Page 16 7210 SAS-M and 7210 SAS-T Ser-vices Guide

  • Preface

    List of Technical Publications

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

    7210 SAS M, T, and X OS Basic System Configuration Guide

    This guide describes basic system configurations and operations.

    7210 SAS M, T, and X OS System Management Guide

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

    7210 SAS M, T, and X OS Interface Configuration Guide

    This guide describes card, Media Dependent Adapter (MDA), and port provisioning.

    7210 SAS M, T, and X OS Router Configuration Guide

    This 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 Guide

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

    7210 SAS M, T, and X OS OAM and Diagnostic Guide

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

    7210 SAS-M and 7210 SAS-T OS Quality of Service Guide

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

    7210 SAS-M and 7210 SAS-T Services GuidePage 17

  • Preface

    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://www1.alcatel-lucent.com/comps/pages/carrier_support.jhtml

    Page 18 7210 SAS-M and 7210 SAS-T Ser-vices Guide

  • Getting Started

    In This Chapter

    This book provides process flow information to configure provision services.

    Alcatel-Lucent 7210 SAS Services Configuration Process

    Table 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 services

    Global entities Configuring Global Service Entities with CLI on page 63

    VLL services Ethernet Pipe (Epipe) Services on page 136

    VPLS service Virtual Private LAN Service on page 253

    IES service Internet Enhanced Service on page 465

    VPRN service Internet Enhanced Service on page 465

    Reference List of IEEE, IETF, and other proprietary entities.

    Standards and Protocol Support on page 981

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

  • Getting Started

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

  • Services Command Reference

    In This Chapter

    This 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 205 Epipe Service Configuration Commands on page 207 VPLS Service Configuration Commands on page 372 IES Service Configuration Commands on page 537 VPRN Service Configuration Commands on page 602

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

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

  • SERVICES OVERVIEW

    In This Section

    This 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 40

    Service Creation Process Overview on page 60

    Deploying and Provisioning Services on page 61

    Configuration Notes on page 62

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

  • Introduction

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

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

  • Services

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

    Virtual Private LAN Service (VPLS) A Layer 2 multipoint-to-multipoint VPN. See Virtual Private LAN Service on page 253.

    Internet Enhanced Service (IES) A routed connectivity service used to provide IP services in 7210 SAS-M (network mode) and 7210 SAS-X. A routed connectivity service used to transport in-band management traffic, this service is available for 7210 SAS-M and 7210 SAS-T devices configured 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 569.

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

  • Introduction

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

  • Services

    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 7210 SAS- M and 7210 SAS-T devices configured in access-uplink mode supports QinQ Layer 2 uplinks to transport the services to the provider edge in a hierarchical configuration.

    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 Entities

    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 40) (for distributed services only)

    Figure 1: Service Entities for SAS-M 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

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

  • Services

    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 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-M in Network Mode

    OSSG002

    Customer

    27

    IP/MPLS Network

    SAP

    3/1/6

    dot1q

    SAP

    2/2/3

    dot1q

    Service

    Cust-27

    SDP

    ALA-A

    Customer

    27

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

  • Service Entities

    Figure 3: Multiple SAPs in a service using QinQ uplinks 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

    27

    Page 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)

    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

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

  • Service Entities

    Default 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-M and 7210 SAS-T devices configured in access-uplink mode)

    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

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

  • Services

    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 use

    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:

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

  • Service Entities

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

    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)

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

  • Services

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

    Services and SAP Encapsulations

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

    Table 2: Service and Encapsulation

    Port Type Encapsulation

    Ethernet Null

    Ethernet Dot1q

    Ethernet QinQ

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

  • Service Entities

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

    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

    Note: Access-egress QoS policy is assigned per access port.

    SAPs using connection-profile (to specify dot1q VLAN ranges) can be configured in a service only when svc-sap-type is set to 'dot1q-range'.

    When a service is configured to use svc-sap-type 'dot1q-range', the outermost V-LAN tag of the packets are not stripped when the packet is received on access port ingress. For more information on processing behavior for this type of service, see Ethernet Pipe (Epipe) Services on page 136 section.

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

  • Services

    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.

    The guidelines listed below are not applicable when the 7210 SAS- M devices are configured in access uplink mode and access uplink SAPs are in use.

    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