CTR 8500

MPLS Configuration
Version 3.4.0

260-668256-014
 MPLS CONFIGURATION

Copyright & Terms of Use

October 2017
This documentation incorporates features and functions provided with CTR 8500
MPLS Configuration, version 3.4.0.
Copyright © 2017 by Aviat Networks, Inc.

All rights reserved.

No part of this publication may be reproduced, transmitted, transcribed, stored in
a retrieval system, or translated into any language or computer language, in any
form or by any means, electronic, magnetic, optical, chemical, manual or
otherwise, without the prior written permission of Aviat Networks Inc.
To request permission, contact techpubs@[Link].
Warranty

Aviat Networks makes no representation or warranties with respect to the

contents hereof and specifically disclaims any implied warranties or
merchantability or fitness for any particular purpose.
Further, Aviat Networks reserves the right to revise this publication and to make
changes from time to time in the content hereof without obligation of Aviat
Networks to notify any person of such revision or changes.
Safety Recommendations

The following safety recommendations must be considered to avoid injuries to

persons and/or damage to the equipment:
1. Installation and Service Personnel: Installation and service must be carried
out by authorized personnel who have the technical training and experience
necessary to be aware of any hazardous operations during installation and
service, and of measures to avoid any danger to themselves, to any other
personnel, and to the equipment.
2. Access to the Equipment: Access to the equipment in use must be restricted
to service personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and
Safety sections of the Eclipse User Manual.
4. Service Personnel Skill: Service personnel must have received adequate
technical training on telecommunications and in particular on the equipment
and capabilities this addendum refers to.
Trademarks

All trademarks are the property of their respective owners.

260-668256-014 OCTOBER 2017 III

 MPLS CONFIGURATION

IV AVIAT NETWORKS
 MPLS CONFIGURATION

Aviat NetworksTechnical Support

Service and Technical Support:
For customer service and technical support, contact one of the regional Technical
Help Desks listed below.
Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help Desk
Aviat Networks, Inc. Aviat Networks Aviat Networks
San Antonio, TX Blantyre, Glasgow, Scotland Clark Freeport Zone
U.S.A. G72 0FB Philippines 2023
United Kingdom
Phone:+1 210 526 6345 Phone: +1 210 526 6345 Phone: +1 210 526 6345
Toll Free (USA): Fax: Fax: +63 45 599 5196
+1 800 227 8332 +44 16 9871 7204 (English)
Fax:+1 210 526 6315 +33 1 5552 8012 (French)
Email: Email: Email:
[Link]@av [Link]@aviatnet [Link]@aviatne
[Link] .com [Link]

Global Support Hotline: +1 210 526 6345

Call this phone number for support from anywhere in the world. Aviat Networks'
Global Support Hotline is available 24 hours a day, 7 days a week, providing
uninterrupted support for all our customers.
When you call our Global Support Hotline:
l You will be greeted by an automated response that will ask you for your
PIN#. Request a PIN# here: [Link]
us/technical-assistance/pin-request-form/.
l As soon as you enter your PIN#, you will be transferred to our Global
Technical Helpdesk that will assist you with your technical issue.
l If you do not have a PIN# your call will be answered by our Support
Assurance Desk. Your call will be supported and prioritized accordingly.

Or you can contact your local Aviat Networks office. Contact information is
available on our website at: [Link]
support/technical-assistance/ 

Sales and Sales Support:

For sales information, contact one of the Aviat Networksheadquarters, or find
your regional sales office at: HTTP://[Link]/.

260-668256-014 OCTOBER 2017 V

 MPLS CONFIGURATION

Corporate Headquarters International Headquarters

California, USA Singapore
Aviat Networks, Inc. Aviat Networks (S) Pte. Ltd.
860 N. McCarthy Blvd., Suite 200 17, Changi Business Park Central 1
Milpitas, CA 95035 Honeywell Building, #04-01
U.S.A. Singapore 486073

Phone: + 1 408 941 7100 Phone: + 65 6496 0900

Fax: + 1 408 941 7110 Fax: + 65 6496 0999>
Toll Free for Sales Inquiries: Sales Inquiries:
+ 1 888 478 9669 +1-321-674-4252

VI AVIAT NETWORKS
 MPLS CONFIGURATION

Product Compliance Notes

CTR 8540, CTR 8312, CTR 8311, and CTR 8380 have been tested for and meet all
applicable EMC standards. The equipment was tested using screened cable; if any
other type of cable is used, it may violate EMC compliance.
CTR 8540, CTR 8312, CTR 8311, and CTR 8380 are Class A products. In a domestic
environment these products may cause radio interference in which case the user
may be required to take adequate measures. This equipment is intended to be
used exclusively in telecommunications centers.

Regulatory Information for 5.8 GHz Band

ODU 600

The following regulatory information applies to license-free operation on the 5.8

GHz band of ODU 600.

FCC Notices
l ODU 600, 5.8GHz, must be professionally installed and maintained.
l This equipment has been tested and found to comply with the limits for
a Class A digital device, pursuant to Part 15 of the FCC rules. These
limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial
environment. This equipment generates, uses and can radiate radio
frequency energy and, if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential
environment is likely to cause harmful interference in which case the
user will be required to correct the interference at their own expense.
l ODU 600, 5.8GHz, is compliant with the relevant parts of FCC CFR47,
Part 15.407.
l To ensure compliance with the FCC RF exposure requirements, a
minimum distance of 18 meters must be maintained between the
antenna and any persons whilst the unit is operational. This calculation
is based on the maximum conducted power and maximum antenna
gain.
l ODU 600, 5.8GHz, has been certified for use with a parabolic antenna
with a maximum gain of 45.9dBi or a flat panel antenna with a
maximum gain of 28dBi.
l The filters and software provided with this product allow for
transmission only in the frequency range 5725 – 5850 MHz to ensure
compliance with Part 15.407.
l According to the conducted power limit in FCC CFR 47, Part 15.407, the
power for this device has been limited to 1W (30dBm) at the antenna

260-668256-014 OCTOBER 2017 VII

 MPLS CONFIGURATION

port.
l FCC CFR47, Part 15.407 excludes the use of point-to-multipoint
systems, omnidirectional applications and multiple co-located
intentional radiators. This system is only for fixed, point-to-point
operation.

International Use of 5.8 GHz

ODU 600 with CTR 8540, CTR 8312, CTR 8311, or CTR 8380, 5.8 GHz, does not
employ DFS, and as such the equipment cannot be deployed within Europe or any
country where DFS is a regulatory requirement for protection of radars.

Networking Devices in Electric Power Substations

For IEEE 1613 compliant products, category 7 Ethernet cables must be used in
order to ensure compliance.

WEEE Directive
In accordance with the WEEE Directive (2012/19/EU), CTR 8540, CTR 8312, CTR
8311, and CTR 8380 is marked with the following symbol:

This symbol indicates that this equipment should be collected separately for the
purposes of recovery and/or recycling.
For information about collection and recycling of Aviat Networks equipment
please contact your local Aviat Networks sales office. If you purchased your
product via a distributor please contact the distributor for information regarding
collection and recovery/recycling.
More information on the WEEE Directive is available at our website:
[Link]
(WEEE is the acronym for Waste Electrical and Electronic Equipment)

RoHS Directive
CTR 8540, CTR 8312, CTR 8311, and CTR 8380 meets the requirements of ROHS
directive 2011/65/EU.

VIII AVIAT NETWORKS

 MPLS CONFIGURATION

Declaration of Conformity, Radio Equipment Directive

(RED), 2014/53/EU
Aviat Networks tímto prohlašuje, že tento ODU 600/ODU 600sp
with CTR 8311, CTR 8312, CTR 8380, CTR 8540 je ve shodě se
Czech Republic základními požadavky a dalšími příslušnými ustanoveními
směrnice 2014/53/EU.
Undertegnede , Aviat Networks erklærer herved, at følgende
udstyr ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR
Denmark 8380, CTR 8540 overholder de væsentlige krav og øvrige
relevante krav i direktiv 2014/53/EU.
Hiermit erklärt , Aviat Networks dass sich das Gerät ODU
600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
Germany     Austria     Switzerland    Belgium in Übereinstimmung mit den grundlegenden Anforderungen und
den übrigen einschlägigen Bestimmungen der Richtlinie
2014/53/EU befindet.
Luxembourg     Netherlands     Liechtenstein
Käesolevaga kinnitab , Aviat Networks seadme ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 vastavust
Estonia direktiivi 2014/53/EL põhinõuetele ja nimetatud direktiivist
tulenevatele teistele asjakohastele sätetele.
Hereby, Aviat Networks declares that ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 is in compliance with
United Kingdom Ireland          Malta the essential requirements and other relevant provisions of
Directive 2014/53/EU.
Por medio de la presente Aviat Networks declara que el ODU
600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
Spain cumple con los requisitos esenciales y cualesquiera otras
disposiciones aplicables o exigibles de la Directiva 2014/53/UE.
ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ, Aviat Networks ΔΗΛΩΝΕΙ ΟΤΙ ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
Greece      Cyprus ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩΔΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ
ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ ΔΙΑΤΑΞΕΙΣ ΤΗΣ ΟΔΗΓΙΑΣ 2014/53/ΕE.
Par la présente, Aviat Networks déclare que l'appareil ODU
600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
France  Luxembourg Switzerland Belgium est conforme aux exigences essentielles et aux autres
dispositions pertinentes de la directive 2014/53/UE.
Con la presente , Aviat Networks dichiara che questo ODU
600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
Italy            Switzerland è conforme ai requisiti essenziali ed alle altre disposizioni
pertinenti stabilite dalla direttiva 2014/53/UE.
Ar šo Aviat Networks deklarē, ka ODU 600/ODU 600sp with CTR
8311, CTR 8312, CTR 8380, CTR 8540 atbilst Direktīvas
Latvia 2014/53/ES būtiskajām prasībām un citiem ar to saistītajiem
noteikumiem,
Šiuo Aviat Networks deklaruoja, kad šis ODU 600/ODU 600sp
with CTR 8311, CTR 8312, CTR 8380, CTR 8540 atitinka
Lithuania esminius reikalavimus ir kitas 2014/53/ES Direktyvos nuostatas.
Hierbij verklaart , Aviat Networks dat het toestel ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 in
Netherlands      Belgium overeenstemming is met de essentiële eisen en de andere
relevante bepalingen van richtlijn 2014/53/EU.

260-668256-014 OCTOBER 2017 IX

 MPLS CONFIGURATION

Hawnhekk, Aviat Networks, jiddikjara li dan ODU 600/ODU 600sp

with CTR 8311, CTR 8312, CTR 8380, CTR 8540 ikkonforma mal-
Malta ħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm
fid-Dirrettiva 2014/53/UE.
Alulírott, Aviat Networks nyilatkozom, hogy a ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 megfelel
Hungary a vonatkozó alapvetõ követelményeknek és az 2014/53/EU
irányelv egyéb elõírásainak.
Niniejszym Aviat Networks oświadcza, że ODU 600/ODU 600sp
with CTR 8311, CTR 8312, CTR 8380, CTR 8540 jest zgodny z
Poland zasadniczymi wymogami oraz pozostałymi stosownymi
postanowieniami Dyrektywy 2014/53/UE.
Aviat Networks declara que este ODU 600/ODU 600sp with CTR
8311, CTR 8312, CTR 8380, CTR 8540 LL/STR 600 está
Portugal conforme com os requisitos essenciais e outras disposições da
Directiva 2014/53/UE.
Aviat Networks izjavlja, da je ta ODU 600/ODU 600sp with CTR
8311, CTR 8312, CTR 8380, CTR 8540 v skladu z bistvenimi
Slovenia zahtevami in ostalimi relevantnimi določili direktive 2014/53/EU.
Aviat Networks týmto vyhlasuje, že ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 spĺňa základné
Slovakia požiadavky a všetky príslušné ustanovenia Smernice
2014/53/EÚ.
Aviat Networks vakuuttaa täten että ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 tyyppinen laite on
Finland direktiivin 2014/53/EU oleellisten vaatimusten ja sitä koskevien
direktiivin muiden ehtojen mukainen.
Härmed intygar Aviat Networks att denna ODU 600/ODU 600sp
with CTR 8311, CTR 8312, CTR 8380, CTR 8540 tår I
Sweden överensstämmelse med de väsentliga egenskapskrav och övriga
relevanta bestämmelser som framgår av direktiv 2014/53/EU.
Hér með lýsir Aviat Networks yfir því að ODU 600/ODU 600sp
with CTR 8311, CTR 8312, CTR 8380, CTR 8540 er í samræmi
við grunnkröfur og aðrar kröfur, sem gerðar eru í tilskipun
Iceland
2014/53/EU.
Aviat Networks erklærer herved at utstyret ODU 600/ODU 600sp
with CTR 8311, CTR 8312, CTR 8380, CTR 8540 er i samsvar
med de grunnleggende krav og øvrige relevante krav i direktiv
Norway
2014/53/EU.
Noi, Aviat Networks, declarăm pe propria noastră răspundere că
produsul ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR
România 8380, CTR 8540 este în conformitate cu cerinţele esenţiale şi
celelalte prevederi aplicabile ale Directivei 2014/53/UE.

Full declarations of conformity are available at:

[Link]
[Link]
[Link]
[Link]
[Link]
[Link]

X AVIAT NETWORKS
 MPLS CONFIGURATION

Country Availability Matrix

Aviat’s radios are classified under the Radio Equipment Directive (2014/53/EU) as
Class 2 products. For details of where the equipment is intended to be used, see
the country matrix below. Aviat Networks intends to market this equipment
where a cross (X) is shown.
Band (GHz) L6 U6 07 08 10 11 13 15 18 23 26 28 32 38 42
Austria X X X X X X X X X X X X X X X
Belgium X X X X X X X X X X X X X
Bulgaria X X X X X X X X X X X X X
Cyprus X X X X X X X X X X X X X X
Czech Republic X X X X X X X X X X X
Denmark X X X X X X X X X X X X
Estonia X X X X X X X X X X X X X X X
Finland X X X X X X X X X X X X X X
France X X X X X X X X X X X X X X
Germany X X X X X X X X X X X X X X X
Greece X X X X X X X X
Hungary X X X X X X X X X X X
Iceland X X X X X X X X X X X X X
Ireland X X X X X X X X X X X
Italy X X X X X X X X X X X X X
Latvia X X X X X X X X X X X
Lithuania X X X X X X X X X X X X X X
Luxembourg X X X X X X X X X X X X X
Malta X X X X X X X X X X X X X
Netherlands X X X X X X X X X X X
Norway X X X X X X X X X X X X X
Poland X X X X X X X X X X X X X X
Portugal X X X X X X X X X X X X
Romania X X X X X X X X X X X X X X X
Slovak Republic X X X X X X X X X X X X X
Slovenia X X X X X X X X X X X X X X
Spain X X X X X X X X X X X X
Sweden X X X X X X X X X X X
Switzerland X X X X X X X X X X X X X X
United Kingdom X X X X X X X X X X X X X

IT SHOULD BE NOTED THAT A LICENSE TO OPERATE THIS EQUIPMENT

WILL BE REQUIRED AND THE RELEVANT REGULATOR MUST BE
CONTACTED PRIOR TO INSTALLATION AND COMMISSIONING.

260-668256-014 OCTOBER 2017 XI

 MPLS CONFIGURATION

Contents

Copyright & Terms of Use iii

Aviat NetworksTechnical Support v
Product Compliance Notes vii
Regulatory Information for 5.8 GHz Band vii
Networking Devices in Electric Power Substations viii
WEEE Directive viii
RoHS Directive viii
Declaration of Conformity, Radio Equipment Directive (RED), 2014/53/EU ix
Contents xii
Chapter 1. Introduction xv
Purpose and Scope xv
Acronyms xvi
References xx
Document Conventions xxi
How This Manual Is Organized xxi
Chapter 2. Example Topologies xxii
Topology Diagrams xxii
Pre-Requisite Global Configurations xxiv
Configuring Loopback Interfaces xxv
Configuring IP addresses for Physical Interfaces xxv
IS-IS Router Configuration xxvi
IS-IS Circuit Configuration xxvi
Useful Show Commands xxvi
Example Configuration Scripts: IPv4 and IS-IS xxvii
Topology A xxvii
Topology B xxxi
Topology C xxxix
Chapter 3. MPLS Traffic Engineering Fundamentals liv
TE-Link Configuration liv
Enabling TE Extensions for IS-IS lvi
Configuring RSVP-TE lvii
Useful Show Commands lviii
Example Configuration Scripts: TE links, IS-IS-TE and RSVP-TE lviii
Configuration for Topology A lix
Configuration for Topology B lxiv
Configuration for Topology C lxxii
Chapter 4. Configuring MPLS Traffic Engineered LSPs xc
Path Options for TE-Tunnels xc
Dynamic Path Option xci
Explicit Path Option xci

XII AVIAT NETWORKS

 MPLS CONFIGURATION

Bandwidth Attribute for TE-Tunnels xciv

Priority Attributes for TE-Tunnels xciv
Affinity Attribute for TE-Tunnels xciv
Record-route Option xcv
Useful Show Commands xcv
Example Configuration Scripts: Dynamic MPLS-TE Tunnels xcv
Dynamic Tunnels for Topology A xcvi
Dynamic Tunnels for Topology B xcvii
Dynamic Tunnels for Topology C xcviii
Chapter 5. Layer 2 Virtual Private Networks c
Reference Model For L2 Transport Over MPLS c
Service Types c
Attachment Circuit Types ci
Pseudo-wires ci
Pseudo-wire Establishment cii
Pseudo-wire Modes: Raw vs. Tagged cii
Targeted LDP Configuration ciii
VPWS Configuration civ
Configuration Example: VPWS with Port Based Attachment Circuit cv
Configuration Example: VPWS with Port+Vlan Based Attachment Circuit cvi
VPLS Configuration cvii
Configuration Example: VPLS with VLAN Based Attachment Circuit cviii
Useful Show Commands cxiii
Chapter 6. Layer 3 Virtual Private Networks cxiv
Overview cxiv
VRF Configuration cxv
L3VPN Route AND Label Distribution cxvi
Route Distinguisher (RD) cxvi
Route Target (RT) cxvii
MP-BGP Peering cxviii
Configure CE-PE Routing cxix
Static Routing cxix
eBGP Routing cxx
Useful Show Commands cxxi
Example Configuration Scripts cxxii
VRF & MP-BGP Configuration (Topology B) cxxii
CE-PE Static Routing (Topology B) cxxxi
CE-PE eBGP (Topology B) cxxxii
Chapter 7. MPLS Ping & Trace Route cxxxvi
Introduction cxxxvi
ping mpls IPv4 target (LDP signalled LSP) cxxxvi
ping mpls RSVP-TE tunnel cxxxvii
ping mpls L2VPN Pseudowire cxxxvii
trace mpls IPv4 target (LDP signalled LSP) cxxxix
Chapter 8. End To End LSP Protection cxl
Failure Detection cxl
BFD for failure detection on MPLS-TE Tunnels cxl

260-668256-014 OCTOBER 2017 XIII

 MPLS CONFIGURATION

Protection Mode 1:1 cxli

Configuration Example – 1:1 End To End Protection With BFD (Using explicit paths
for working and protecting LSPs) cxlii
Appendix A. MPLS Label Ranges In AOS cxlvi
Nomenclature cxlvi
Remote Label cxlvi
Local Label cxlvi
Local Label Ranges cxlvii
Remote Label Ranges cxlviii

XIV AVIAT NETWORKS

 MPLS CONFIGURATION

Chapter 1. Introduction
Aviat Networks MPLS provides a feature-rich, efficient and flexible label
switching capability as required by industry standards. It enables service
providers to implement VPN services, traffic engineering, redundancy and fast
failure detection in the networks. Key MPLS features supported on AOS include:
l LDP and RSVP-TE for MPLS LSP signalling
l Layer 2 and Layer 3 VPNs
l TDM transport over MPLS networks
l Rich set of traffic engineering capabilities
l Fast failure detection and LSP protection
l Quality of Service
l Diagnostics and OAM functions

Purpose and Scope

This document describes configuration of MPLS functionality on CTR 8500.  The
reader is expected to have a basic understanding of IP routing and MPLS
technologies, as well as basic familiarity with Aviat Networks CTR platform.
Some MPLS features are described in their dedicated configuration manuals.
Please refer to section References on page xx for a list of relevant Aviat
Networks user documents.

260-668256-014 OCTOBER 2017 XV

 MPLS CONFIGURATION

Acronyms

XVI AVIAT NETWORKS

 MPLS CONFIGURATION

Table 1. Acronyms

260-668256-014 OCTOBER 2017 XVII

 MPLS CONFIGURATION

Acronym Explanation
ABR Area Boundary Router (in OSPF)
ARP Address Resolution Protocol
AS Autonomous System
ASBR Autonomous System Boundary Router (in OSPF)
ATM Asynchronous Transfer Mode
BFD Bidirectional Forwarding Detection – A fast failure detection protocol
BGP Border Gateway Protocol
CE Customer Edge
CE Router Customer Edge Router
CLI Command Line Interface
CSPF Constrained SPF (Constrained Shortest Path First) – Algorithm for computing
path on traffic engineered LSP using the traffic engineering topology
information in the traffic engineering database.
FEC Forwarding Equivalence Class
FTN Tunnel Forwarding Equivalence Class (FTN) to Next Hop Label Forwarding Entry
(NHLFE) Tunnel - Maps a Forwarding Equivalence Class (e.g. IP traffic with
specific destination address, DSCP markings) to an MPLS LSP at the edge of
an MPLS network
GMPLS Generalized MPLS
IGP Interior Gateway Protocol
IP Internet Protocol
IPv4 Internet Protocol Version 4
IPv6 Internet Protocol Version 6
IS-IS Intermediate System to Intermediate System (An Interior Gateway Protocol)
L2VPN Layer 2 Virtual Private Network
L3 Layer 3 - Network Layer
L3VPN Layer 3 Virtual Private Network
LAN Local Area Network
LB Link Bundling
LDP Label Distribution Protocol – Used for signalling MPLS LSP labels
LER Label Edge Router
LSP Label Switched Path
LSR Label Switch Router
ME Maintenance Entity
MEG Maintenance Entity Group
MEP Maintenance Entity Group End Point
MIB Management Information Base
MP-BGP Multiprotocol Extensions for BGP
MPLS Multi-Protocol Label Switching

XVIII AVIAT NETWORKS

 MPLS CONFIGURATION

OAM Operations, Administration and Management

OSPF Open Shortest Path First (An Interior Gateway Protocol)
PE Provider Edge
PE Router Provider Edge Router
PHB Per Hop Behaviour
PSC Per Hop Behaviour Scheduling Class
PSC Interfaces Packet Switching Capable Interfaces
PST Path Segmented Tunnel
PW Pseudo-wire
PWE Pseudo-wire Emulation Edge to Edge
QoS Quality of Service
RD Route Distinguisher – Used in L3VPN. RD is appended to an IPv4 address in a
customer’s VRF to convert it to VPNv4 address which can be signalled to
remote PEs via MP-BGP
RSVP Resource Reservation Protocol
RSVPTE Resource Reservation Protocol with Traffic Engineering – Used for signalling
traffic engineered tunnels/LSPs
RT Route Target – Used in L3VPN to control dissemination of customer VRF routes
SAToP Structure-Agnostic Time Division Multiplexing (TDM) over Packet
SNMP Simple Network Management Protocol
TCP Transmission Control Protocol
TDM Time Division Multiplexing
TE Traffic Engineering
TE Link Traffic Engineering Link
T-LDP Targeted Label Distribution Protocol – Mainly used to signal L2VPN Pseudo-
wire labels across PE routers
TLM TE Link Manager – A software entity in AOS responsible for managing TE link
information
TLV Type Length Value Encoding
UDP User Datagram Protocol
VC Virtual Circuit
VCCV Virtual Circuit Connectivity Verification
VFI Virtual Forwarding Instance
VLAN Virtual Local Area Network
VLL Virtual Leased Line
VPLS Virtual Private LAN Service
VPN Virtual Private Network
VPWS Virtual Private Wire Service

260-668256-014 OCTOBER 2017 XIX

 MPLS CONFIGURATION

References
l CTR 8500/8300 Getting Started - Configuration
l CTR 8500/8300 Configuration – IP
l CTR 8500/8300 Configuration – IS-IS
l CTR 8500/8300 Configuration – MEF-8 CESoETH/MPLS SAToP
l CTR 8500/8300 Configuration – MPLS Packet Loss and Delay
Measurement
l CTR 8500/8300 CLI Reference Manual Vol 1
l CTR 8500/8300 CLI Reference Manual Vol 2
l E. Rosen, A. Viswanathan, R. Callon, “Multiprotocol Label Switching
Architecture”, RFC 3031, January 2001.
l R. Callon, P. Doolan, N. Feldman, A. Fredette, G. Swallow, A.
Viswanathan, “A Framework for Multiprotocol Label Switching”, draft-
[Link], September 1999.
l C. Boscher, P. Cheval, L. Wu, E. Gray, “LDP State Machine”, RFC 3215,
January 2002.
l E. Rosen, D. Tappan, G. Federkow, Y. Rekhter, D. Farinacci, T. Li, A.
Conta, “MPLS Label Stack Encoding”, RFC 3032, January 2001.
l L. Andersson, [Link], B. Thomas, “LDP Specification”, RFC 5036,
October 2007.
l D. Awduche, L. Berer, D. Gan, T. Li, G, Swallow, V. Srinivasan, “RSVP-
TE: Extensions to RSVP for LSP Tunnels”, RFC 3209, December 2001.
l S. Bryant, P. Pate, “Pseudo Wire Emulation Edge-to-Edge (PWE3)
Architecture”, RFC 3985, March 2005.
l L. Martini, N. El-Aawar, T. Smith, G. Heron, “Pseudowire Setup and
Maintenance Using the Label Distribution Protocol (LDP)”, RFC 4447,
April 2006.
l L. Martini, E. Rosen, N. El-Aawar, G. Heron, “Encapsulation Methods for
Transport of Ethernet over MPLS Networks”, RFC 4448, April 2006.
l F. Le Faucheur, L. Wu, B. Davie, S. Davari, P. Vaananen, R. Krishnan, P.
Cheval, J. Heinanen, “MPLS Support of Differentiated Services”, RFC
3270, May 2002.
l E. Rosen, Y. Rekhter, “BGP/MPLS IP Virtual Private Networks” , RFC
4364, Feb 2006.

XX AVIAT NETWORKS
 MPLS CONFIGURATION

Document Conventions
Table 2. Document Conventions

Convention Usage
Code Text CLI Commands
Code Italics User inputs to command
Blue code CLI Command Output
Red Code Output for configured value

How This Manual Is Organized

Communication networks can be viewed as being organized in multiple layers
(physical, link, network layers etc.) and planes (data, control, management).
Aviat Networks MPLS supports multiple protocols in each of the different layers
and planes. OSPF, IS-IS and BGP are supported for IPv4 routing. LSP signalling is
supported via static configuration, LDP and RSVP-TE. Layer 2 VPN pseudo-wires
can be configured statically or via targeted LDP. Layer 3 VPNs support a number
of options for routing between CE and PE devices. AOS implementation is flexible
and enables the service providers to choose any suitable protocol or mechanism
for each layer. This results in a large matrix of possible combinations of protocols
which cannot be covered individually. To address this problem, we have taken the
following approach in this manual:
l Interior gateway protocols are described in their own dedicated
manuals.
l IS-IS is chosen as underlying IGP for all examples in this manual.
l A set of basic network topologies and relevant IP layer configurations
are provided in chapter 2. Most MPLS feature configuration examples are
constructed over these baseline configurations.
l Configuration examples for L2VPN and L3VPN are described over RSVP-
TE based LSPs.
l Where possible, configuration examples for a feature in higher layer
builds upon the examples for lower layer configuration in previous
chapters.

260-668256-014 OCTOBER 2017 XXI

 EXAMPLE TOPOLOGIES CHAPTER 2

Chapter 2. Example Topologies

This section shows some basic network topologies and provides minimal IPv4
and IS-IS routing configuration for these topologies. This is a pre-requisite
configuration for various MPLS feature examples which follow in subsequent
chapters. The information in this section is concise. For details on IS-IS
configuration on AOS, please refer to CTR 8500/8300 Configuration – IS-IS.

Topology Diagrams
Topology A on page xxiii- is used for describing simple point to point services
such as VPWS
Topology B on page xxiii- is used for describing multipoint services such as VPLS
and L3VPN
Topology C on page xxiv- is used for describing traffic engineering and LSP
protection
Following conventions are used in this document:
l Rest of the document will refer to the topologies in this section by using
the topology labels -Topology A, Topology B etc.
l Labels CTR A, CTR B, etc. represent CTR devices within a topology.
These labels are used in the subsequent sections to refer to the
particular device.
l GI 0/2 to GI 0/7 represent the front panel Ethernet ports on the CTR
devices.
l ‘To CE’ represents a connection to a Customer Edge device. The
connection to CE device can be at layer 2 (Ethernet/VLAN) or layer 3
(IPv4), depending on the type of MPLS service being configured. Details
of CE-PE link configuration are specific to the type of service being
configured and are included in the service configuration examples.

AVIAT NETWORKS OCTOBER 2017 XXII

CHAPTER 2 EXAMPLE TOPOLOGIES

Figure 1. Topology A

Figure 2. Topology B

XXIII OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

Figure 3. Topology C

Pre-Requisite Global Configurations

For all examples in this manual, it is assumed that the CTR is in ‘customer
bridge’ mode and unwanted layer 2 protocols such as Spanning Tree Protocol
and Generic Attribute Registration Protocol (GARP) are turned off. The following
configuration achieves this:
aos# configure terminal
aos(config)# switch default
aos(config-switch)# shutdown spanning-tree
aos(config-switch)# set gmrp disable
aos(config-switch)# set gvrp disable
aos(config-switch)# shutdown garp
aos(config-switch)# bridge-mode customer
aos(config-switch)# end

AVIAT NETWORKS OCTOBER 2017 XXIV

 CHAPTER 2 EXAMPLE TOPOLOGIES

Configuring Loopback Interfaces

IPv4 loopback interfaces are used for multiple purposes including identifying the
device, addressing it for management, and directing control plane traffic to the
device. Many routing protocols (OSPF, BGP) and signalling protocols (LDP,
RSVP) use loopback addresses to identify the device. All examples in this
manual require at least one loopback interface to be configured on CTR.
Loopback interface can be configured through the following commands:
aos# configure terminal
aos(config)# interface loopback 0
aos(config-if)# ip address [Link].[Link]
aos(config-if)# no shutdown
aos(config-if)# end
In this example, loopback 0 is the identifier assigned to the interface – the
format for this is keyword loopback followed by a number. Apart from this, IP
address and subnet mask are required before the loopback interface is activated
with no shutdown command.

Configuring IP addresses for Physical Interfaces

By default, all physical ports on CTR operate as layer 2 ports, called switchport,
and are mapped to the default switch context. In order to use the port for
IP/MPLS functionality, it must be unmapped from the default switch context and
enabled for layer 3 operation with no switchport command. After this, an IP
address and subnet mask can be assigned. The following example shows how to
configure  IP address [Link]/24 on front panel Ethernet port gi 0/2:
aos# configure terminal
aos(config)# interface gigabitethernet 0/2
aos(config-if)# shutdown
aos(config-if)# no map switch default
aos(config-if)# no switchport
aos(config-if)# ip address [Link] [Link]
aos(config-if)# no shutdown
aos(config-if)# exit

XXV OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

IS-IS Router Configuration

For example, in this manual, all devices will be configured with an instance of
level-2 IS-IS router. A net address and level-2 configuration is the minimal
configuration required. In later sections, traffic-engineering extensions for IS-
IS will be enabled where required. Following commands are required for the
minimal configuration:
Enable IS-IS routing process.
aos# configure terminal
aos(config)# router IS-IS
Set Net ID
aos(config-router)# net [Link]
Assign a working area type
aos(config-router)# is-type level-2
aos(config-router)# exit

IS-IS Circuit Configuration

Minimal configuration for each IS-IS circuit includes specifying the circuit type
(level 1, level 2) and broadcast vs. point-to-point operating mode. All examples
in this manual use level-2 circuits in broadcast mode. The following example
shows how to configure this for front panel Ethernet port gi 0/2:
aos(config)# interface gigabitethernet 0/2
aos(config-if)# ip router IS-IS broadcast
aos(config-if)# IS-IS circuit-type level-2-only
aos(config-if)# exit

Useful Show Commands

l aos# sh ip interface – Displays all IP enabled interfaces with
address and status information.
l aos# sh ip route – Displays all IP global routing table. This includes
static routes and routes learnt via all routing protocols.
l aos# sh ip IS-IS route – Displays IS-IS specific routing table.

AVIAT NETWORKS OCTOBER 2017 XXVI

 CHAPTER 2 EXAMPLE TOPOLOGIES

Example Configuration Scripts: IPv4 and IS-IS

Topology A
Configuration Summary
This section includes complete configuration scripts for all devices in Topology A
on page xxiii. The scripts can be copied into a text file and applied to a CTR
device running with factory default configuration. The scripts will configure basic
IP interfaces in accordance with the following tables. All devices are in the same
IS-IS level-2 area and all circuits are broadcast type.
Table 3. Topology A - Device IP and IS-IS Configuration

Device Loopback Address IS-IS NET ID

CTR A [Link]/32 [Link]
CTR B [Link]/32 [Link]
CTR C [Link]/32 [Link]

Table 4. Topology A - Port Connections and IP Addresses

Device Interface IP Address Connects to

CTR A Gi 0/2 [Link]/24 CTR B Gi 0/2
CTR B Gi 0/2 [Link]/24 CTR A Gi 0/2
CTR B Gi 0/3 [Link]/24 CTR C gi 0/3
CTR C Gi 0/3 [Link]/24 CTR B gi 0/3

CTR A Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0

XXVII OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

ip address [Link] [Link]

no shutdown
end

configure terminal
interface gigabitethernet 0/2
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/2
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

CTR B Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp

AVIAT NETWORKS OCTOBER 2017 XXVIII

CHAPTER 2 EXAMPLE TOPOLOGIES

bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/2
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/3
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit

XXIX OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

interface gigabitethernet 0/2

ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/3
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

CTR C Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/3
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

AVIAT NETWORKS OCTOBER 2017 XXX

 CHAPTER 2 EXAMPLE TOPOLOGIES

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/3
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

Topology B
Configuration Summary
This section includes complete configuration scripts for all devices in Topology B
on page xxiii. The scripts can be copied into a text file and applied to a CTR
device running with factory default configuration. The scripts will configure basic
IP interfaces in accordance with the following tables. All devices are in the same
IS-IS level-2 area and all circuits are broadcast type.
Table 5. Topology B - Device IP and IS-IS Configuration

Device Loopback Address IS-IS NET ID

CTR A [Link] [Link]
CTR B [Link] [Link]
CTR C [Link] [Link]
CTR D [Link] [Link]

XXXI OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

Table 6. Topology B - Port Connections and IP Addresses

Device Interface IP Address Connects to

CTR A Gi 0/2 [Link]/24 CTR B Gi 0/2
CTR A Gi 0/4 [Link]/24 CTR D Gi 0/4
CTR B Gi 0/2 [Link]/24 CTR A Gi 0/2
CTR B Gi 0/3 [Link]/24 CTR C Gi 0/3
CTR B Gi 0/5 [Link]/24 CTR D Gi 0/5
CTR C Gi 0/3 [Link]/24 CTR B Gi 0/3
CTR C Gi 0/6 [Link]/24 CTR D Gi 0/6
CTR D Gi 0/4 [Link]/24 CTR A Gi 0/4
CTR D Gi 0/5 [Link]/24 CTR B Gi 0/5
CTR D Gi 0/6 [Link]/24 CTR C Gi 0/6

CTR A Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/2
shutdown
no map switch default
no switchport
ip address [Link] [Link]

AVIAT NETWORKS OCTOBER 2017 XXXII

 CHAPTER 2 EXAMPLE TOPOLOGIES

no shutdown
exit
interface gigabitethernet 0/4
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/2
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/4
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

CTR B Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable

XXXIII OCTOBER 2017 AVIAT NETWORKS

EXAMPLE TOPOLOGIES CHAPTER 2

shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/2
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/3
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/5
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal

AVIAT NETWORKS OCTOBER 2017 XXXIV

 CHAPTER 2 EXAMPLE TOPOLOGIES

router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/2
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/3
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/5
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

CTR C Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]

XXXV OCTOBER 2017 AVIAT NETWORKS

EXAMPLE TOPOLOGIES CHAPTER 2

no shutdown
end

configure terminal
interface gigabitethernet 0/3
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/6
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/3
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/6
ip router IS-IS broadcast

AVIAT NETWORKS OCTOBER 2017 XXXVI

 CHAPTER 2 EXAMPLE TOPOLOGIES

IS-IS circuit-type level-2-only

end

CTR D Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/4
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/5
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit

XXXVII OCTOBER 2017 AVIAT NETWORKS

EXAMPLE TOPOLOGIES CHAPTER 2

interface gigabitethernet 0/6

shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/4
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/5
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/6
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

AVIAT NETWORKS OCTOBER 2017 XXXVIII

 CHAPTER 2 EXAMPLE TOPOLOGIES

Topology C
Configuration Summary
This section includes complete configuration scripts for all devices in Topology C
on page xxiv. The scripts can be copied into a text file and applied to a CTR
device running with factory default configuration. The scripts will configure basic
IP interfaces in accordance with the following tables. All devices are in the same
IS-IS level-2 area and all circuits are broadcast type.
Table 7. Topology C - Device IP and IS-IS Configuration

Device Loopback Address IS-IS NET ID

CTR A [Link] [Link]
CTR B [Link] [Link]
CTR C [Link] [Link]
CTR D [Link] [Link]
CTR E [Link] [Link]
CTR F [Link] [Link]
CTR G [Link] [Link]

XXXIX OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

Table 8. Topology C - Port Connections and IP Addresses

Device Interface IP Address Connects to

CTR A Gi 0/2 [Link]/24 CTR B Gi 0/2
CTR A Gi 0/3 [Link]/24 CTR F Gi 0/3
CTR B Gi 0/2 [Link]/24 CTR A Gi 0/2
CTR B Gi 0/4 [Link]/24 CTR F Gi 0/4
CTR B Gi 0/6 [Link]/24 CTR C Gi 0/6
CTR B Gi 0/7 [Link]/24 CTR G Gi 0/7
CTR C Gi 0/4 [Link]/24 CTR G Gi 0/4
CTR C Gi 0/5 [Link]/24 CTR D Gi 0/5
CTR C Gi 0/6 [Link]/24 CTR B Gi 0/6
CTR D Gi 0/2 [Link]/24 CTR E Gi 0/2
CTR D Gi 0/5 [Link]/24 CTR 5 Gi 0/5
CTR D Gi 0/7 [Link]/24 CTR F Gi 0/7
CTR E Gi 0/2 [Link]/24 CTR D Gi 0/2
CTR E Gi 0/5 [Link]/24 CTR F Gi 0/5
CTR E Gi 0/6 [Link]/24 CTR G Gi 0/6
CTR F Gi 0/3 [Link]/24 CTR A Gi 0/3
CTR F Gi 0/4 [Link]/24 CTR B Gi 0/4
CTR F Gi 0/5 [Link]/24 CTR E Gi 0/5
CTR F Gi 0/7 [Link]/24 CTR D Gi 0/7
CTR G Gi 0/4 [Link]/24 CTR C Gi 0/4
CTR G Gi 0/6 [Link]/24 CTR E Gi 0/6
CTR G Gi 0/7 [Link]/24 CTR B Gi 0/7

CTR A Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0

AVIAT NETWORKS OCTOBER 2017 XL

CHAPTER 2 EXAMPLE TOPOLOGIES

ip address [Link] [Link]

no shutdown
end

configure terminal
interface gigabitethernet 0/2
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/3
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/2
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/3

XLI OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

ip router IS-IS broadcast

IS-IS circuit-type level-2-only
end

CTR B Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/2
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/4
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown

AVIAT NETWORKS OCTOBER 2017 XLII

CHAPTER 2 EXAMPLE TOPOLOGIES

exit
interface gigabitethernet 0/6
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/7
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/2
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/4
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/6

XLIII OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

ip router IS-IS broadcast

IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/7
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

CTR C Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/4
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/5
shutdown

AVIAT NETWORKS OCTOBER 2017 XLIV

CHAPTER 2 EXAMPLE TOPOLOGIES

no map switch default

no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/6
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/4
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/5
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/6
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

XLV OCTOBER 2017 AVIAT NETWORKS

 EXAMPLE TOPOLOGIES CHAPTER 2

CTR D Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/2
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/5
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/7
shutdown
no map switch default

AVIAT NETWORKS OCTOBER 2017 XLVI

 CHAPTER 2 EXAMPLE TOPOLOGIES

no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/2
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/5
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/7
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

CTR E Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp

XLVII OCTOBER 2017 AVIAT NETWORKS

EXAMPLE TOPOLOGIES CHAPTER 2

bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/2
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/5
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/6
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS

AVIAT NETWORKS OCTOBER 2017 XLVIII

 CHAPTER 2 EXAMPLE TOPOLOGIES

net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/2
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/5
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/6
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

CTR F Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown

XLIX OCTOBER 2017 AVIAT NETWORKS

EXAMPLE TOPOLOGIES CHAPTER 2

end

configure terminal
interface gigabitethernet 0/3
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/4
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/5
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/7
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS

AVIAT NETWORKS OCTOBER 2017 L

 CHAPTER 2 EXAMPLE TOPOLOGIES

net [Link]
is-type level-2
exit
interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/3
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/4
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/5
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/7
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

CTR G Configuration
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

LI OCTOBER 2017 AVIAT NETWORKS

EXAMPLE TOPOLOGIES CHAPTER 2

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/4
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/6
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
exit
interface gigabitethernet 0/7
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

configure terminal
router IS-IS
net [Link]
is-type level-2
exit

AVIAT NETWORKS OCTOBER 2017 LII

CHAPTER 2 EXAMPLE TOPOLOGIES

interface loopback 0
ip router IS-IS
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/4
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/6
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
exit
interface gigabitethernet 0/7
ip router IS-IS broadcast
IS-IS circuit-type level-2-only
end

LIII OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

Chapter 3. MPLS Traffic Engineering

Fundamentals
MPLS traffic engineering allows a high level of control over the path which traffic
takes through the network. The tunnel paths can be determined based on link
parameters such as available bandwidth, administrative colouring etc. allowing
the operators to balance the utilization of links. Before MPLS traffic engineered
tunnels can be set up, a number of underlying parameters and signalling
protocols have to be configured in the network. Configuration of these
underlying elements is the subject of this chapter. These elements include:
l Traffic engineering parameters for individual links. In AOS, this
information is encapsulated in Traffic Engineering Link (TE-Link).
l Network-wide dissemination of traffic engineering link parameters by
enabling TE extensions for the IGP
NOTE: In SW R eleas e 3.4, TE Ex tens ions are only supported for IS-IS.
TE-ex tens ion s upport for OSPF is ex perimental.
l Enabling and configuring RSVP-TE entities on all devices. RSVP-TE is
the protocol which signals the LSPs.

TE-Link Configuration
In CTR, a TE-Link is a logical interface that describes the traffic engineering
parameters of a link connected to the router. The link parameters are
configured for the egress direction. This means that for a link ‘A-B’ between
devices A and B, a TE-link has to be configured on device A describing
parameters for traffic in A→B direction, and another TE-link on device B for
traffic in B→A direction.
The supported Traffic Engineering parameters are as follows:
l Traffic Engineering Metric – By default this has the same value as IGP
metric for the link. However, service proviers are free to change the
value and use any meaning/ interpretation that suits their needs. For
example, metric can be configured based on the latency of the link.
l Resource-class or Administrative colour – Allows links to be
administratively grouped allowing the user to prefer or exclude certain
groups for an LSP. This value is a 32-bit bit field. Each bit can have a

AVIAT NETWORKS OCTOBER 2017 LIV

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

meaning assigned by a service provider. The bit-field for a particular

link is compared against configured ‘affinity’ attribute of MPLS tunnel
(See chapter 4), to determine if a tunnel is allowed to use this link.
l Maximum Link Bandwidth
l Maximum reservable Bandwidth – This parameter can be more or less
than the maximum link bandwidth allowing the operators to enable
over-subscription/ under-subscription of links
l Minimum reservable bandwidth
NOTE: The minimum res erv able bandw idth is adv ertised in R SVP-TE
signalling and is c ompared w ith us er c onfigured value for the tunnel.
H ow ev er, AOS does not s upport path c alc ulation using minimum
reserv able bandw idth as a c ons traint.
WARNING: TE-Links can only be created on IP interfaces which do not already
have MPLS enabled on them. If a TE-link is to be created over a physical interface,
mpls ip must NOT be enabled on that interface before TE-link creation. The
process of mapping the TE-Link to a physical interface will enable the mpls ip
automatically.
NOTE: In SW R eleas e 3.4, s upport for c reating TE-Links over IVR s
(VLAN IP Interfac es ) is not av ailable.
NOTE: Ens ure that the loc al TE-Link IP address matc hes the IP interface
it w ill be mapped to. IS-IS-TE w ill only flood the addres s specified in the
TE-Link , w hic h c an only be manually c onfigured in R elease 3.4.

The following example shows configuration of a TE-link on a link from CTR A to

CTR B (A→B direction), in Topology A on page xxiii.

Globally enable support for MPLS traffic engineering

aos(config)# mpls traffic-eng tunnels

Create a TE-LINK called te12 and specify IP addresses for local and remote
ends. Remote router ID is the router ID assigned to TE-router at the other end of
the link.
aos(config)# mpls traffic-eng
aos(config-mpls-te)# te-link te12
aos(config-mpls-te-link)# address-type ipv4
aos(config-mpls-te-link)# local te-link ipv4 [Link] remote te-link ipv4
[Link]
aos(config-mpls-te-link)# remote router-id [Link]
aos(config-mpls-te-link)# resource-class class-value 0x1
aos(config-mpls-te-link)# no shutdown

LV OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

Map the TE-Link to a physical interface, in this case front panel port 2, and
specify link parameters:
aos(config-mpls-te-link)# int gi 0/2
aos(config-mpls-comp-link)# min lsp bandwidth 1024
aos(config-mpls-comp-link)# max reservable bandwidth 20000
aos(config-mpls-comp-link)# switching-capability psc1 encoding packet
aos(config-mpls-comp-link)# no shutdown
aos(config-mpls-comp-link)# exit

Enable IGP advertisement for this TE-Link:

aos(config-mpls-te-link)# advertise
aos(config-mpls-te-link)# exit
aos(config-mpls-te)# exit

Enabling TE Extensions for IS-IS

Traffic Engineering extensions on IS-IS can be enabled to flood TE-Link
advertisements and calculate tunnel paths for RSVP-TE via the following steps in
the router IS-IS configuration mode:
Set the traffic engineering router ID using the command mpls traffic-eng
router id x.x.x.x. The router ID must correspond to the IP address of a
configured loopback address on the CTR.
Enable the TE-Database and begin TE-Link information flooding using the
command mpls traffic-eng [level-1 | level-2 | level-1-2]. TE extensions can
be enabled on level 1 only, level 2 only or both. Not selecting a level will
enable TE extensions all currently enabled IS-IS levels.

The following example shows configuring TE extensions for IS-IS on CTR A, in

Topology A on page xxiii:
Enable IS-IS routing process.
aos# configure terminal
aos(config)# router IS-IS

Set Traffic Engineering router ID.

aos(config-router)# mpls traffic-eng router-id [Link]

AVIAT NETWORKS OCTOBER 2017 LVI

 CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

Enable Traffic Engineering Database and flooding

aos(config-router)# mpls traffic-eng
aos(config-router)# end
NOTE: Enabling the TE Ex tens ions on an IS-IS level w ill automatic ally
set the IS-IS metric s ty le to w ide for that lev el. There is currently no
support for the trans itional metric s ty le.

Configuring RSVP-TE
RSVP-TE is the signalling protocol used for setting up traffic-engineered LSPs in
an MPLS network. When a TE-tunnel is configured, the path for the tunnel is
computed at the head end router by executing CSPF algorithm over the TE
database1. The tunnel is signalled over calculated path via RSVP-TE protocol
which communicates the path information to each router along the path, checks
the router at each hop for errors and signals the ingress and egress labels for
each hop along the signalled tunnel. All routers participating in traffic
engineering must have RSVP-TE configured.
RSVP-TE must first be configured globally by specifying a router ID which
corresponds to an already configured loopback address, the outgoing label
range, the hello packet refresh interval and the maximum number of interfaces
participating in RSVP.
NOTE: The c onfigured Label range only applies to outgoing labels being
dis tributed from the loc al node to the far end on label exc hange (ingress
pac kets w ill be tagged w ith this label). C TR is able to acc ept any unused
inc oming label from its neighbouring dev ic es .

Each interface participating in RSVP-TE signalling must also be specified in the

RSVP configuration, in order for the label exchange to take place on those
interfaces.
NOTE: For eac h interfac e partic ipating in R SVP-TE, a ‘s ignalling link
attributes ’ parameter c an be s et. This mus t matc h the R esource C lass set
for the TE-Link c onfigured for the interfac e in order for tunnels w ith
resourc e c las s bas ed c ons traints to be s ignalled suc cess fully.

The following example shows configuration of RSVP-TE entity on CTR A, in

Topology A on page xxiii:
Set global (per router) configuration for RSVP including router ID and label
range and enable the RSVP entity:
aos(config)# rsvp
aos(config-rsvp)# set rsvp disable

1 In certain cases, for example when using loose hops in LSP path specification,
only part of the CSPF computation happens at the head-end.

LVII OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

aos(config-rsvp)# router-id [Link]

aos(config-rsvp)# signalling label range min 100001 max 100100
aos(config-rsvp)# signalling hello supported
aos(config-rsvp)# signalling hello refresh interval 30000
aos(config-rsvp)# signalling max interfaces 8
aos(config-rsvp)# set rsvp enable

Enable RSVP on individual interfaces which are to be made available for MPLS
LSPs – in this case it is front panel port 2:
aos(config-rsvp)# interface gi 0/2
aos(config-rsvp-if)# signalling link attributes 0x1
aos(config-rsvp-if)# no shutdown
aos(config-rsvp-if)# exit
aos(config-rsvp-if)# exit

Useful Show Commands

l sh mpls traffic engineering te-link: Shows details and status of all TE-
links on the router.
l sh rsvp req: Shows requests sent via RSVP protocol. This will display
useful information when a tunnel has been configured on the device.

Example Configuration Scripts: TE links, IS-IS-TE

and RSVP-TE
This section provides scripts with all pre-requisite configurations for setting up
MPLS-TE tunnels.  Complete configuration scripts for all devices in topologies A,
B and C from section 2.1 are provided. These scripts perform the following
operations:
l Configure TE-Links for each IP link in the MPLS network (excluding links
to CE devices).
l Enable TE Extensions for IS-IS including wide metric support.
l Enable and configure RSVP-TE on all devices. RSVP-TE is enabled on all
MPLS interfaces.

AVIAT NETWORKS OCTOBER 2017 LVIII

 CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

The scripts can be copied into a text file and applied to a CTR device. It is
assumed that before applying the scripts in this section, the appropriate
baseline IP and IS-IS configuration from the section Example Configuration
Scripts: IPv4 and IS-IS on page 1 have been applied to the devices.
After the scripts in this section are applied, the network will be ready for setting
up MPLS-TE tunnels via user specified constraints.

Configuration for Topology A

CTR A Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te12
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/2
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit

configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
mpls traffic-eng
end

LIX OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

rsvp
set rsvp disable
router-id [Link]
signalling label range min 100101 max 100200
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/2
signalling link attributes 0x1
no shutdown
exit
exit

CTR B Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te21
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/2
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng

AVIAT NETWORKS OCTOBER 2017 LX

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

te-link te23
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/3
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100201 max 100300
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/2
signalling link attributes 0x1
no shutdown
exit
interface gi 0/3
signalling link attributes 0x1
no shutdown

LXI OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

exit
exit

CTR C Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te32
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/3
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100301 max 100400
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable

AVIAT NETWORKS OCTOBER 2017 LXII

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

interface gi 0/3
signalling link attributes 0x1
no shutdown
exit
exit

LXIII OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

Configuration for Topology B

CTR A Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te12
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/3
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te14
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/4
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown

AVIAT NETWORKS OCTOBER 2017 LXIV

 CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100101 max 100200
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/2
signalling link attributes 0x1
no shutdown
exit
interface gi 0/4
signalling link attributes 0x1
no shutdown
exit
exit

CTR B Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te21
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]

LXV OCTOBER 2017 AVIAT NETWORKS

MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

resource-class class-value 0x1

no shutdown
int gi 0/2
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te24
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/5
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te23
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown

AVIAT NETWORKS OCTOBER 2017 LXVI

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

int gi 0/3
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100201 max 100300
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/2
signalling link attributes 0x1
no shutdown
exit
interface gi 0/3
signalling link attributes 0x1
no shutdown
exit
interface gi 0/5
signalling link attributes 0x1
no shutdown
exit
exit

LXVII OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

CTR C Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te32
address-type ipv32
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/3
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te34
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/6
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit

AVIAT NETWORKS OCTOBER 2017 LXVIII

 CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100301 max 100400
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/3
signalling link attributes 0x1
no shutdown
exit
interface gi 0/6
signalling link attributes 0x1
no shutdown
exit
exit

CTR D Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te41
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/4

LXIX OCTOBER 2017 AVIAT NETWORKS

MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

min lsp bandwidth 1024

max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te42
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/5
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te43
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/6
min lsp bandwidth 1024
max reservable bandwidth 20000

AVIAT NETWORKS OCTOBER 2017 LXX

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

switching-capability psc1 encoding packet

no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100401 max 100500
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/4
signalling link attributes 0x1
no shutdown
exit
interface gi 0/5
signalling link attributes 0x1
no shutdown
exit
interface gi 0/6
signalling link attributes 0x1
no shutdown
exit
exit

LXXI OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

Configuration for Topology C

CTR A Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te12
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/2
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te16
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/3
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown

AVIAT NETWORKS OCTOBER 2017 LXXII

 CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100101 max 100200
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/2
signalling link attributes 0x1
no shutdown
exit
interface gi 0/3
signalling link attributes 0x1
no shutdown
exit
exit

CTR B Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te21
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]

LXXIII OCTOBER 2017 AVIAT NETWORKS

MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

resource-class class-value 0x1

no shutdown
int gi 0/2
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te26
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/4
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te27
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown

AVIAT NETWORKS OCTOBER 2017 LXXIV

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

int gi 0/7
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te23
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/6
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100201 max 100300
signalling hello supported

LXXV OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

signalling hello refresh interval 30000

signalling max interfaces 8
set rsvp enable
interface gi 0/2
signalling link attributes 0x1
no shutdown
exit
interface gi 0/4
signalling link attributes 0x1
no shutdown
exit
interface gi 0/6
signalling link attributes 0x1
no shutdown
exit
interface gi 0/7
signalling link attributes 0x1
no shutdown
exit
exit

CTR C Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te32
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/6
min lsp bandwidth 1024
max reservable bandwidth 20000

AVIAT NETWORKS OCTOBER 2017 LXXVI

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

switching-capability psc1 encoding packet

no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te37
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/4
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te34
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/5
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown

LXXVII OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100301 max 100400
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/4
signalling link attributes 0x1
no shutdown
exit
interface gi 0/5
signalling link attributes 0x1
no shutdown
exit
interface gi 0/6
signalling link attributes 0x1
no shutdown
exit
exit

CTR D Configuration
configure terminal
mpls traffic-eng tunnels

AVIAT NETWORKS OCTOBER 2017 LXXVIII

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

mpls traffic-eng
te-link te43
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/5
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te46
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link].6
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/7
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te45

LXXIX OCTOBER 2017 AVIAT NETWORKS

MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/2
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100401 max 100500
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/2
signalling link attributes 0x1
no shutdown
exit
interface gi 0/5
signalling link attributes 0x1
no shutdown
exit

AVIAT NETWORKS OCTOBER 2017 LXXX

 CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

interface gi 0/7
signalling link attributes 0x1
no shutdown
exit
exit

CTR E Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te56
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/1
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te57
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/6

LXXXI OCTOBER 2017 AVIAT NETWORKS

MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

min lsp bandwidth 1024

max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te54
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/2
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100501 max 100600
signalling hello supported
signalling hello refresh interval 30000

AVIAT NETWORKS OCTOBER 2017 LXXXII

 CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

signalling max interfaces 8

set rsvp enable
interface gi 0/1
signalling link attributes 0x1
no shutdown
exit
interface gi 0/2
signalling link attributes 0x1
no shutdown
exit
interface gi 0/6
signalling link attributes 0x1
no shutdown
exit
exit

CTR F Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te61
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/3
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit

LXXXIII OCTOBER 2017 AVIAT NETWORKS

MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

exit
mpls traffic-eng
te-link te62
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/4
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te64
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/7
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng

AVIAT NETWORKS OCTOBER 2017 LXXXIV

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

te-link te65
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/1
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable
router-id [Link]
signalling label range min 100601 max 100700
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/1
signalling link attributes 0x1
no shutdown
exit
interface gi 0/3
signalling link attributes 0x1
no shutdown

LXXXV OCTOBER 2017 AVIAT NETWORKS

 MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

exit
interface gi 0/4
signalling link attributes 0x1
no shutdown
exit
interface gi 0/7
signalling link attributes 0x1
no shutdown
exit
exit

CTR G Configuration
configure terminal
mpls traffic-eng tunnels
mpls traffic-eng
te-link te72
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/7
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te75
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]

AVIAT NETWORKS OCTOBER 2017 LXXXVI

CHAPTER 3 MPLS TRAFFIC ENGINEERING FUNDAMENTALS

remote router-id [Link]

resource-class class-value 0x1
no shutdown
int gi 0/6
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
mpls traffic-eng
te-link te73
address-type ipv4
local te-link ipv4 [Link] remote te-link ipv4 [Link]
remote router-id [Link]
resource-class class-value 0x1
no shutdown
int gi 0/4
min lsp bandwidth 1024
max reservable bandwidth 20000
switching-capability psc1 encoding packet
no shutdown
exit
advertise
exit
exit
configure terminal
router IS-IS
mpls traffic-eng router-id [Link]
end
rsvp
set rsvp disable

LXXXVII OCTOBER 2017 AVIAT NETWORKS

MPLS TRAFFIC ENGINEERING CHAPTER 3
FUNDAMENTALS

router-id [Link]
signalling label range min 100701 max 100800
signalling hello supported
signalling hello refresh interval 30000
signalling max interfaces 8
set rsvp enable
interface gi 0/4
signalling link attributes 0x1
no shutdown
exit
interface gi 0/6
signalling link attributes 0x1
no shutdown
exit
interface gi 0/7
signalling link attributes 0x1
no shutdown
exit
exit

AVIAT NETWORKS OCTOBER 2017 LXXXVIII

 CONFIGURING MPLS TRAFFIC ENGINEERED CHAPTER 4
LSPS

Chapter 4. Configuring MPLS Traffic

Engineered LSPs
AOS allows operators a great degree of control over routing of MPLS tunnels1.
This control is exercised mainly by specifying various attributes of the tunnels.
These attributes are described in the sections below.

Path Options for TE-Tunnels

Direct control over path taken by a tunnel can be exercised by configuring path
options, which can be dynamic or explicit.

1 RFC-3209 defines LSP tunnel as follows:

Once a label is assigned to a set of packets, the label effectively defines the
‘flow’ through the LSP. We refer to such an LSP as an ‘LSP tunnel’ because the
traffic through it is opaque to intermediate nodes along the label switched path.

The terms LSP Tunnel/MPLS Tunnel and LSP are often used interchangeably in
literature. The distinction is usually not important except in the cases of
protected tunnel where a single tunnel can have two LSPs: a working (main) LSP
and a protecting (backup) LSP.

From the perspective of user configuration in CTR, an MPLS Tunnel is an

interface on a device with an  identifier assigned to it. Once established, the
tunnel can be used as a next hop for an IP address, bound to an L2VPN pseudo-
wire or assigned an L3VPN binding. The LSP is the actual label switched path
which the tunnel takes through the network and is identified by an LSP ID as well
as state information within individual routers which includes incoming and
outgoing labels at each hop. The tunnel is configured by an operator, LSP is
calculated and signalled internally by AOS software in cooperation with other
routers along the path.

AVIAT NETWORKS OCTOBER 2017 XC

 CHAPTER 4 CONFIGURING MPLS TRAFFIC ENGINEERED LSPS

Dynamic Path Option

With dynamic path option, the tunnel path is calculated based on the lowest cost
path which satisfies all other constraints specified for the tunnel, such as
bandwidth, resource class. The path is calculated using the TE-metrics in the TE
Database.
Note that the default value of TE-metric is the IGP cost of the link. Unless some
TE-link metrics have been changed, the tunnel configured with dynamic path
option will follow the IGP’s lowest cost path if this path meets all the constraints.
The following example shows configuration of a TE- tunnel from CTR A to CTR B
in Topology A on page xxiii
aos(config)# int mplstunnel 13
aos(config-if)# tunnel mpls destination [Link] source [Link]
aos(config-if)# tunnel mode mpls traffic-eng
aos(config-if)# tunnel signalling protocol rsvp
aos(config-if)# tunnel mpls traffic-eng path-option number 1 dynamic
aos(config-if)# no shutdown

NOTE: Sourc e and D es tination IP addres s es are mandatory and are set to
R SVP router ID for s ourc e and des tination routers.
NOTE: In SW R eleas e 3.4, only mpls traffic -engineering is supported as
the tunnel mode. unidirec tional, c orouted-bidiretional and ass ociated-
bidirec tional modes are not s upported.
NOTE: In SW R eleas e 3.4, only rs v p is s upported as tunnel signalling
protoc ol. s tatic , c rldp, none and other options are not supported.

Explicit Path Option

AOS allows configuring explicit path as a list of IP addresses (RSVP router IDs),
and using it as path option for MPLS tunnels. The constraints specified in the
configured path will be applied. The tunnel will fail to come up if the configured
path is invalid or if the required resources such as bandwidth are not available
on the configured path.
Tunnel path can be specified using one of the following ways:

Strict Hop
When a hop is specified as strict in the path option, it is supposed to be directly
reachable from the hop before it in the path specification.
The following example demonstrates configuration of a tunnel from CTR A to
CTR D in Topology C on page xxiv via CTR B, CTRG, and CTR E

XCI OCTOBER 2017 AVIAT NETWORKS

 CONFIGURING MPLS TRAFFIC ENGINEERED CHAPTER 4
LSPS

Define an explicit path consisting of a set of strict hops and assign it identifier 1:
aos(config)# ip explicit-path identifier 1
aos(cfg-ip-expl-path)# index 1 next-address strict [Link]
aos(cfg-ip-expl-path)# index 2 next-address strict [Link]
aos(cfg-ip-expl-path)# index 3 next-address strict [Link]
aos(cfg-ip-expl-path)# index 4 next-address strict [Link]
aos(cfg-ip-expl-path)# exit

Use explicit path 1 as the path option for the tunnel:

aos(config)# int mplstunnel 41
aos(config-if)# tunnel mpls destination [Link] source [Link]
aos(config-if)# tunnel mode mpls traffic-eng
aos(config-if)# tunnel signalling protocol rsvp
aos(config-if)# tunnel mpls traffic-eng path-option number 1 explicit identifier 1
aos(config-if)# no shutdown

Loose Hop
When a hop in the path is specified as loose, the path from the previous hop to
the loose hop is calculated using TE-metric or other constraints provided. The
path beyond the loose hop is not calculated at the head end. The loose hop
router is expected to run a CSPF calculation to calculate the route from itself to
the tail end or to the next loose hop. This option is typically used when the
tunnel spans multiple IGP areas. The area boundary router (L1-2 router in case
of IS-IS) is specified as a loose hop in this case.
The following example demonstrates configuration of a tunnel from CTR A to
CTR D in Topology C on page xxiv, using CTR E as a loose hop. In this case, the
head end calculates path to CTR E using default TE-metric. CTR E calculates the
path to the tail end which is directly connected. As a result, the tunnel will take
the path CTR A→CTR F→CTR E→CTR D.
Define an explicit path consisting of a loose hop and assign it identifier 1:
aos(config)# ip explicit-path identifier 1
aos(cfg-ip-expl-path)# index 1 next-address loose [Link]
aos(cfg-ip-expl-path)# exit

Use explicit path 1 as the path option for the tunnel:

aos(config)# int mplstunnel 41
aos(config-if)# tunnel mpls destination [Link] source [Link]

AVIAT NETWORKS OCTOBER 2017 XCII

 CHAPTER 4 CONFIGURING MPLS TRAFFIC ENGINEERED LSPS

aos(config-if)# tunnel mode mpls traffic-eng

aos(config-if)# tunnel signalling protocol rsvp
aos(config-if)# tunnel mpls traffic-eng path-option number 1 explicit identifier 1
aos(config-if)# tunnel mpls traffic-eng record-route
aos(config-if)# no shutdown

Exclude Address
Exclude address is used to define a path option where the specified node should
not be used on the path of the tunnel.
As an example, consider Topology C on page xxiv. Based on IGP cost, the
shortest path from CTR A to CTR D is via CTR F (CTR A → CTR F → CTR D). If the
operator wishes to avoid routing the tunnel through CTR F, the address of CTR F
can be specified in the exclude list. In that case, the tunnel will be routed via
next best path (CTR A → CTR B → CTR C → CTR D). This is shown in the
following example:
Define an explicit path with CTR F ([Link]) as exclude address and assign it
identifier 1:
aos(config)# ip explicit-path identifier 1
aos(cfg-ip-expl-path)# index 1 exclude-address [Link]
aos(cfg-ip-expl-path)# exit

Use explicit path 1 as the path option for the tunnel:

aos(config)# int mplstunnel 41
aos(config-if)# tunnel mpls destination [Link] source [Link]
aos(config-if)# tunnel mode mpls traffic-eng
aos(config-if)# tunnel signalling protocol rsvp
aos(config-if)# tunnel mpls traffic-eng path-option number 1 explicit identifier 1
aos(config-if)# no shutdown

XCIII OCTOBER 2017 AVIAT NETWORKS

 CONFIGURING MPLS TRAFFIC ENGINEERED CHAPTER 4
LSPS

Bandwidth Attribute for TE-Tunnels

Tunnel routing can be managed by specifying bandwidth constraint for the
tunnel. When bandwidth constraint is specified, a link will be used on the tunnel
path only if the available bandwidth is more than the configured bandwidth for
the tunnel. If this constraint is not met, either  some of the existing tunnels will
be pre-empted based on the set-up and hold priorities (see Priority Attributes
for TE-Tunnels on page xciv) or the tunnel setup will fail. Bandwidth attribute is
specified under the mpls tunnel interface configuration with the following
command:
aos(config-if)# tunnel mpls traffic-eng bandwidth <value in kbps>

NOTE: Bandw idth mus t be higher than 1024 kpbs.

NOTE: Bandw idth res erv ation parameter is us ed only for tunnel signalling
. R es erv ing bandw idth for a tunnel does not nec essarily guarantee that
the tunnel w ill c arry traffic at this bandw idth, nor w ill it restrict a tunnel
from pas s ing traffic at a higher bandw idth than it has reserved. If traffic
policing is required, it mus t be c onfigured s eparately.

Priority Attributes for TE-Tunnels

MPLS tunnel priorities affect the behaviour when enough resources are not
available for a newly created tunnel. In this case the setup priority of the new
tunnel is compared against the hold priority of existing tunnels on the link. If an
existing tunnel with lower priority is found, it will be torn down to make room
for the new tunnel. Tunnel setup and hold priorities are configured with the
following command under mpls tunnel interface configuration:
aos(config-if)# tunnel mpls traffic-eng priority <setup priority 0-7> <hold
priority 0-7>

NOTE: 0 is the highes t priority , 7 is the low es t.

Affinity Attribute for TE-Tunnels

The affinity attribute of a tunnel is compared against the resource class value of
a TE-link to determine if the link is allowed to be used on the tunnel. Both
affinity and resource class are 32-bit bit-masks used to group the links based on
operator-determined parameters, e.g. latency, geographical constraints etc.
Three types of affinity attributes can be specified for a tunnel:

AVIAT NETWORKS OCTOBER 2017 XCIV

 CHAPTER 4 CONFIGURING MPLS TRAFFIC ENGINEERED LSPS

l Exclude-all attribute: A link will not be used for the tunnel if the link’s
resource class specification includes any attribute included in the
exclude-all affinity value for the tunnel.
l Include-any attribute: A link will be used for the tunnel if it carries any
of the attribute in include-any affinity parameter for the tunnel.
l Include-all: A link will be used for the tunnel if it carries all the
attributes in include-all affinity parameter for the tunnel.

Record-route Option
This option enables the inclusion of Record Route Object (RFC 3209) in the
RSVP-TE messages. This object records the path actually taken by the LSP.
NOTE: N ote: The us e of rec ord-route option is mandatory w hen loose
hops are us ed on the tunnel path.

This option can be enabled via following command under mpls tunnel interface
configuration:
aos(config-if)# tunnel mpls traffic-eng record-route

Useful Show Commands

l sh mpls traffic-eng tunnels brief: Shows status and brief
information about the configured tunnels.
l sh mpls traffic-eng tunnels: Shows detailed information about the
configured tunnels.

Example Configuration Scripts: Dynamic MPLS-TE

Tunnels
The scripts in this section are provided to support configuration examples in the
following chapters. These scripts can be copied into the configuration console.
The scripts will establish full mesh of MPLS-TE tunnels between provider edge
routers in example topologies in Topology Diagrams on page xxii.
Configurations from Example Configuration Scripts: IPv4 and IS-IS on page 1
and Example Configuration Scripts: TE links, IS-IS-TE and RSVP-TE on page 1
must be completed before applying the configurations in this section.

XCV OCTOBER 2017 AVIAT NETWORKS

 CONFIGURING MPLS TRAFFIC ENGINEERED CHAPTER 4
LSPS

Dynamic Tunnels for Topology A

CTR A Configuration
Tunnel from CTR A to CTR C
configure terminal
int mplstunnel 13
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp
tunnel mpls traffic-eng path-option number 1 dynamic
no shutdown
end

CTR C Configuration
Tunnel from CTR C to CTR A
configure terminal
int mplstunnel 31
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp
tunnel mpls traffic-eng path-option number 1 dynamic
no shutdown

AVIAT NETWORKS OCTOBER 2017 XCVI

 CHAPTER 4 CONFIGURING MPLS TRAFFIC ENGINEERED LSPS

Dynamic Tunnels for Topology B

CTR A Configuration
Tunnel from CTR A to CTR C
configure terminal
int mplstunnel 13
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp
tunnel mpls traffic-eng path-option number 1 dynamic
no shutdown
end

Tunnel from CTR A to CTR D

configure terminal
int mplstunnel 14
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp
tunnel mpls traffic-eng path-option number 1 dynamic
no shutdown
end

CTR C Configuration
Tunnel from CTR C to CTR A
configure terminal
int mplstunnel 31
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp
tunnel mpls traffic-eng path-option number 1 dynamic
no shutdown

XCVII OCTOBER 2017 AVIAT NETWORKS

 CONFIGURING MPLS TRAFFIC ENGINEERED CHAPTER 4
LSPS

Tunnel from CTR C to CTR D

configure terminal
int mplstunnel 34
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp
tunnel mpls traffic-eng path-option number 1 dynamic
no shutdown

CTR D Configuration
Tunnel from CTR D to CTR A
aos(config)# int mplstunnel 41
aos(config-if)# tunnel mpls destination [Link] source [Link]
aos(config-if)# tunnel mode mpls traffic-eng
aos(config-if)# tunnel signalling protocol rsvp
aos(config-if)# tunnel mpls traffic-eng path-option number 1 dynamic
aos(config-if)# no shutdown
aos(config-if)# end

Tunnel from CTR D to CTR C

aos(config)# int mplstunnel 43
aos(config-if)# tunnel mpls destination [Link] source [Link]
aos(config-if)# tunnel mode mpls traffic-eng
aos(config-if)# tunnel signalling protocol rsvp
aos(config-if)# tunnel mpls traffic-eng path-option number 1 dynamic
aos(config-if)# no shutdown

Dynamic Tunnels for Topology C

CTR A Configuration
Tunnel from CTR A to CTR C
configure terminal
int mplstunnel 14
tunnel mpls destination [Link] source [Link]

AVIAT NETWORKS OCTOBER 2017 XCVIII

 CHAPTER 4 CONFIGURING MPLS TRAFFIC ENGINEERED LSPS

tunnel mode mpls traffic-eng

tunnel signalling protocol rsvp
tunnel mpls traffic-eng path-option number 1 dynamic
no shutdown
end

CTR D Configuration
Tunnel from CTR D to CTR A
configure terminal
int mplstunnel 41
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp
tunnel mpls traffic-eng path-option number 1 dynamic
no shutdown

XCIX OCTOBER 2017 AVIAT NETWORKS

 LAYER 2 VIRTUAL PRIVATE NETWORKS CHAPTER 5

Chapter 5. Layer 2 Virtual Private

Networks

Reference Model For L2 Transport Over MPLS

Figure 4. PWE3 Network Reference Model for MPLS L2VPNs

L2VPN implementation in AOS is based on pseudo-wires and follows the

reference model described in RFC-3985. The model is shown in figure PWE3
Network Reference Model for MPLS L2VPNs on page c, above. All configurations
for L2VPNs reside on the provider edge routers. The core routers in the network
only have to provide MPLS transport via LDP or RSVP-TE signalled LSPs. Key
elements and supported features for L2VPNS are summarised below.

Service Types
l Virtual Private Wire Service (VPWS): VPWS provides a layer 2 point-to-
point connection, which is effectively equivalent to providing a leased
line supporting Ethernet transport.
l Virtual Private LAN Service (VPLS): VPLS provides a Layer 2 multipoint
service which extends a private LAN segment across the provider’s
MPLS network. This creates the appearance to the users that all sites
are interconnected though a single Ethernet switch. In addition to

AVIAT NETWORKS OCTOBER 2017 C

 CHAPTER 5 LAYER 2 VIRTUAL PRIVATE NETWORKS

providing layer 2 transport, VPLS also provides switch functions such as

MAC address learning and ageing.

Both VPWS and VPLS transport Layer 2 Ethernet frames across the network. This
in turn allows any type of Layer 3 payload, not just IP, being carried by those
Ethernet frames to be conveyed. 

Attachment Circuit Types

A customer edge device accesses the L2VPN service by connecting to the
provider edge device via an attachment circuit (AC). The following types of
attachment circuits are supported:
l Port – A physical interface such as an Ethernet port. Any traffic that
arrives on the port is passed on to the L2VPN PW.
l VLAN – Connecting to PE over a single VLAN (Only supported for VPLS).
The VLAN on the PE device may contain more than one port. This type
of attachment circuit is typically used when an L2VPN site has multiple
pieces of customer equipment which have to be connected to same
L2VPN service via a single PE router. The recommended configuration
is to create a VLAN based attachment circuit on PE router with a port
provided for each piece of external equipment.

NOTE: A phy s ic al port c annot be a member of more than one VLAN based
attachment c irc uits .

l Port + VLAN – This configuration provides the ability to create multiple

attachment circuits on a single physical port. The traffic for each
attachment circuit is identified by the VLAN tag configured for that
attachment circuit and is mapped to the appropriate L2VPN PW. This
scheme is useful for separating different types of traffic arriving on the
same physical interface, e.g. separating customer data traffic from
management traffic and mapping them to different L2VPN services.

Pseudo-wires
Pseudo-wires are the mechanism used to carry L2 frames over MPLS cloud.
Pseudo-wires are configured on the provider edge devices and are invisible to
the core routers (LSRs or P-routers).

CI OCTOBER 2017 AVIAT NETWORKS

 LAYER 2 VIRTUAL PRIVATE NETWORKS CHAPTER 5

In data plane, packets belonging to a PW are identified by a PW label plus

optional control word and associated channel headers. PW label is pushed on the
packet at the PE router before the MPLS LSP label i.e., PW label is the inner label
in MPLS label stack. MPLS routers in the network (P routers) switch the packets
based on the outermost label only (MPLS transport label). At the remote PE
router, after the MPLS transport label is popped, the PW label is used to map the
packet to the appropriate attachment circuit.

Pseudo-wire Establishment
Pseudowire establishment involves exchange of PW labels and other control
information across PE routers. In AOS, this can be accomplished in one of the
two possible ways:
l Manual/ static configuration of labels and PW parameters at both ends
l Using Targeted LDP to allocate labels and negotiate PW parameters

Pseudo-wire Modes: Raw vs. Tagged

RFC 4448 specifies two operating modes for L2VPN Pseudowire.

l Tagged mode- Service delimiting tag is carried over the PW. If a

service delimiting tag is not present on the traffic received at the
attachment circuit, a dummy tag is inserted.
l Raw mode- Service delimiting tag is stripped before a packet is sent on
the PW.

NOTE: It is rec ommended to us e R aw mode pseudo-w ires w hen

connec ting to port-bas ed attac hment c irc uits .
NOTE: It is rec ommended to us e tagged mode pseudo w ires w hen
connec ting to VLAN or Port+VLAN bas ed attachment circ uits.

Service Delimiting Tag Conventions In AOS

l On a port based attachment circuit, a service-delimiting tag is deemed
to be not present. All traffic arriving on the port is sent to the L2VPN PW
connected to the AC. Any VLAN tags present on the traffic are
considered to be customer tags and are preserved over the emulated
service.
NOTE: Max imum of 2 c us tomer VLAN tags can be preserved for raw
mode PW .

AVIAT NETWORKS OCTOBER 2017 CII

 CHAPTER 5 LAYER 2 VIRTUAL PRIVATE NETWORKS

NOTE: Max imum of 1 VLAN tag c an be preserved for tagged mode PW .

If cus tomer traffic has 2 VLAN tags , the outer cus tomer tag is
ov erw ritten by dummy s erv ic e-delimiting tag. For this reason, it is not
recommended to us e tagged mode ps euodow ire w ith Port bas ed
attac hment c irc uits .
l On VLAN and Port+VLAN ACs, the Attachment Circuit VLAN tag on the
PE node is considered to be the service delimiting tag. The outermost
tag on customer traffic is compared against the service delimiting tag
to identify the correct PW.
NOTE: It is pos s ible for Attac hment C irc uits at both ends of a
ps eudo-w ire to us e different VLAN ID s . For example, A PW can be
connec ted to AC Port Gi0/1:VLAN 100 at PE 1 and to Port Gi 0/2:
VLAN 200 at PE 2. In this c as e, traffic w hich arrives from the
cus tomer netw ork w ith VLAN 100 is mapped on the pseodow ire and at
the egres s s ide, the s erv ic e delimiting tag is overw ritten by the VLAN
ID of egres s attac hment c irc uit, i.e. the traffic is sent out to C E2
dev ic e w ith outermos t VLAN tag 200. This provides a w ay of doing
VLAN trans lation.

Targeted LDP Configuration

Pseudowires are the common building blocks for both VPWS and VPLS. It is
recommended to use T-LDP to signal pseudo-wires. In order to exchange
Pseudowire setup information, the PE routers at both ends require a T-LDP
session established between them. IPv4 connectivity and reachability must be
established between the two devices for T-LDP session to be set up. After that,
the following configuration is required:
l Enable the LDP process and assign router ID to local LDP router.
l Create an LDP ‘entity’ to manage the session with a particular remote
end PE. A separate entity has to be configured for T-LDP session with
each PE.
l Under each entity, specify IP address of the remote PE (LDP router ID).
l Under each entity, specify a label range to be used.
NOTE: In SW R eleas e 3.4, the trans port address used for a T-LD P
sess ion s hould be the loopbac k interfac e.
NOTE: AOS us es liberal label retention mode and uns olic ited label
dis tribution mode by default.

The following example shows configuration of T-LDP on CTR A in Topology A on

page xxiii. A targeted LDP session is configured towards CTR C. Similar
configuration on CTR C is required for the session to be established.

On CTR A:

CIII OCTOBER 2017 AVIAT NETWORKS

 LAYER 2 VIRTUAL PRIVATE NETWORKS CHAPTER 5

aos# configure terminal

aos(config)# mpls ldp
aos(config-mpls-ldp)# router-id loopback 0 force
aos(config-mpls-ldp)# entity 1
aos(config-mpls-ldp-entity-1)# neighbor [Link] targeted
aos(config-mpls-ldp-entity-1)# ldp label range min 160100 max 160199
aos(config-mpls-ldp-entity-1)# transport-address tlv loopback 0
aos(config-mpls-ldp-entity-1)# no shutdown
aos(config-mpls-ldp-entity-1)# end

On CTR C:

aos# configure terminal

aos(config)# mpls ldp
aos(config-mpls-ldp)# router-id loopback 0 force
aos(config-mpls-ldp)# entity 1
aos(config-mpls-ldp-entity-1)# neighbor [Link] targeted
aos(config-mpls-ldp-entity-1)# ldp label range min 160300 max 160399
aos(config-mpls-ldp-entity-1)# transport-address tlv loopback 0
aos(config-mpls-ldp-entity-1)# no shutdown
aos(config-mpls-ldp-entity-1)# end

VPWS Configuration

After IPv4 connectivity and MPLS transport have been provisioned in the
network, follow the steps below for configuration of VPWS:
Configure targeted LDP sessions across the edge devices. This step is not
required if manual configuration of PW labels will be used.
NOTE: It is rec ommended to us e T-LD P for signalling PW s bec ause
static c onfiguration of labels is hard to manage in large netw ork s.

1. Configure PW and connect it to the attachment circuit (AC) on each edge

router.

AVIAT NETWORKS OCTOBER 2017 CIV

 CHAPTER 5 LAYER 2 VIRTUAL PRIVATE NETWORKS

Configuration Example: VPWS with Port Based

Attachment Circuit
This example demonstrates creation of a VPWS service between CTR A and CTR
C on Topology A on page xxiii. It is assumed that IPv4 and LSP configuration is
completed on the topology according to scripts in the following sections:
l Topology A on page 1
l Configuration for Topology A on page 1
l Dynamic Tunnels for Topology A on page 1
l T-LDP is configured with script in section Targeted LDP Configuration on
page ciii.

VPWS is a point to point service and is configured directly under the attachment
circuit interface on each device. In this case port Gi0/4 is used as attachment
circuit on both devices.

On CTR A:

aos# configure terminal

aos(config)# interface gigabit ethernet 0/4

Connect the interface to pseuodowire. Target PE for PW is [Link], PW ID is set

to 1. The PW goes over MPLS-TE LSPs, forward tunnel 13 and reverse tunnel 31:
aos(config-if)#mpls l2transport pwidfec [Link] pwid 1 groupid 1 mplstype te 13
31 pwtype eth

On CTR C:

aos# configure terminal

aos(config)# interface gigabit ethernet 0/4

Connect the interface to pseuodowire. Target PE for PW is [Link], PW ID is set

to 1. The PW goes over MPLS-TE LSPs, forward tunnel 31 and reverse tunnel 13:
aos(config-if)#mpls l2transport pwidfec [Link] pwid 1 groupid 1 mplstype te 31
13 pwtype eth

CV OCTOBER 2017 AVIAT NETWORKS

 LAYER 2 VIRTUAL PRIVATE NETWORKS CHAPTER 5

Configuration Example: VPWS with Port+Vlan Based

Attachment Circuit
This example demonstrates creation of two VPWS services between CTR A and
CTR C on Topology A on page xxiii. It is assumed that IPv4 and LSP configuration
is completed on the topology according to scripts in the following sections:
l Topology A on page 1
l Configuration for Topology A on page 1
l Dynamic Tunnels for Topology A on page 1
l T-LDP is configured with script in section Targeted LDP Configuration on
page ciii.

Both VPWS services terminate on physical port Gi 0/4 but use different
Port+VLAN attachment circuits. PW 1 will use VLAN 101 as attachment circuit,
PW 2 will use VLAN 102. For Port + VLAN AC, the service is configured under
VLAN interface. The PW is configured in tagged mode.

On CTR A:

aos# configure terminal

aos(config)# switch default
aos(config-switch)# vlan 101
aos(config-switch-vlan)# ports add gig 0/4
aos(config-switch-vlan)# mpls l2transport pwidfec [Link] pwid 1 groupid 1
mplstype te 13 31 port-ifindex gigabitethernet 0/4 pwtype ethtag
aos(config-switch-vlan)# end

aos# configure terminal

aos(config)# switch default
aos(config-switch)# vlan 102
aos(config-switch-vlan)# ports add gig 0/4
aos(config-switch-vlan)# mpls l2transport pwidfec [Link] pwid 2 groupid 2
mplstype te 13 31 port-ifindex gigabitethernet 0/4 pwtype ethtag
aos(config-switch-vlan)# end

AVIAT NETWORKS OCTOBER 2017 CVI

 CHAPTER 5 LAYER 2 VIRTUAL PRIVATE NETWORKS

On CTR C:

aos# configure terminal

aos(config)# switch default
aos(config-switch)# vlan 101
aos(config-switch-vlan)# ports add gig 0/4
aos(config-switch-vlan)# mpls l2transport pwidfec [Link] pwid 1 groupid 1
mplstype te 31 13 port-ifindex gigabitethernet 0/4 pwtype ethtag
aos(config-switch-vlan)# end

aos# configure terminal

aos(config)# switch default
aos(config-switch)# vlan 102
aos(config-switch-vlan)# ports add gig 0/4
aos(config-switch-vlan)# mpls l2transport pwidfec [Link] pwid 2 groupid 2
mplstype te 31 13 port-ifindex gigabitethernet 0/4 pwtype ethtag
aos(config-switch-vlan)# end

VPLS Configuration
The key steps for configuration of a VPLS service after IPv4 connectivity and
LSPs have been established are:
Configure targeted LDP sessions across the edge devices. Each PE router
should have a T-LDP session with all other PE routers in the VPLS service.
Configure a VFI and VPN instance for the service.
Add PWs to the VPN instance. This is different from VPWS where PWs are
created directly under interface or VLAN configuration in CLI. In most
scenarios a PW to each PE router has to be configured, i.e. all PE devices
participating in the VPLS service are connected with a full mesh of PWs.
Connect the attachment circuits to the VFI instance.

CVII OCTOBER 2017 AVIAT NETWORKS

 LAYER 2 VIRTUAL PRIVATE NETWORKS CHAPTER 5

Configuration Example: VPLS with VLAN Based

Attachment Circuit
This example demonstrates creation of a VPLS service with CTR A, CTR B and
CTR C as PE routers on Topology B on page xxiii. It is assumed that IPv4 and LSP
configuration is completed on the topology according to scripts in the following
sections:
l Topology B on page 1
l Configuration for Topology B on page 1
l Dynamic Tunnels for Topology B on page 1

The attachment circuit is VLAN 101. In this case the VLAN has only one port Gi
0/4. However, multiple ports can be added to the VLAN and traffic arriving on
any of those ports with VLAN 101 as outer tag will be forwarded via VPLS.

CTR A Configuration
Enable LDP and configure targeted LDP entities towards CTR C and CTR D:
aos# configure terminal
aos(config)# mpls ldp
aos(config-mpls-ldp)# router-id loopback 0 force
aos(config-mpls-ldp)# entity 1
aos(config-mpls-ldp-entity-1)# neighbor [Link] targeted
aos(config-mpls-ldp-entity-1)# ldp label range min 160100 max 160149
aos(config-mpls-ldp-entity-1)# transport-address tlv loopback 0
aos(config-mpls-ldp-entity-1)# no shutdown
aos(config-mpls-ldp-entity-1)# exit
aos(config-mpls-ldp)# entity 2
aos(config-mpls-ldp-entity-1)# neighbor [Link] targeted
aos(config-mpls-ldp-entity-1)# ldp label range min 160150 max 160199
aos(config-mpls-ldp-entity-1)# transport-address tlv loopback 0
aos(config-mpls-ldp-entity-1)# no shutdown
aos(config-mpls-ldp-entity-1)# exit

Configure VLAN for attachment circuit:

aos# configure terminal
aos(config)# vlan 102
aos(config-vlan)# ports gi 0/4

AVIAT NETWORKS OCTOBER 2017 CVIII

 CHAPTER 5 LAYER 2 VIRTUAL PRIVATE NETWORKS

aos(config-vlan)# exit

Configure VFI and VPN. A user defined string is assigned to the VFI for
identification. In this case, the VFI is called VPLS_ACD. Configure two PWs
under the VPN instance, one towards CTR C and one towards CTR D:
aos# configure terminal
aos(config)# switch default
aos(config-switch)# l2 vfi VPLS_ACD manual
aos(config-switch-vfi)# vpn 1
aos(config-switch-vfi)# neighbor [Link] pwidfec pwid 13 groupid 1
encapsulation mpls mplstype te 13 31 pwtype ethtag
aos(config-switch-vfi)# neighbor [Link] pwidfec pwid 14 groupid 1
encapsulation mpls mplstype te 14 41 pwtype ethtag
aos(config-switch-vfi)# end

Connect the AC VLAN to the VFI:

aos# configure terminal
aos(config)# vlan 102
aos(config-vlan)# xconnect vfi VPLS_ACD
aos(config-vlan)# end

CTR C Configuration
Enable LDP and configure targeted LDP entities towards CTR A and CTR D:
aos# configure terminal
aos(config)# mpls ldp
aos(config-mpls-ldp)# router-id loopback 0 force
aos(config-mpls-ldp)# entity 1
aos(config-mpls-ldp-entity-1)# neighbor [Link] targeted
aos(config-mpls-ldp-entity-1)# ldp label range min 160200 max 160249
aos(config-mpls-ldp-entity-1)# transport-address tlv loopback 0
aos(config-mpls-ldp-entity-1)# no shutdown
aos(config-mpls-ldp-entity-1)# exit
aos(config-mpls-ldp)# entity 2
aos(config-mpls-ldp-entity-1)# neighbor [Link] targeted

CIX OCTOBER 2017 AVIAT NETWORKS

 LAYER 2 VIRTUAL PRIVATE NETWORKS CHAPTER 5

aos(config-mpls-ldp-entity-1)# ldp label range min 160250 max 160299

aos(config-mpls-ldp-entity-1)# transport-address tlv loopback 0
aos(config-mpls-ldp-entity-1)# no shutdown
aos(config-mpls-ldp-entity-1)# exit

Configure VLAN for attachment circuit:

aos# configure terminal
aos(config)# vlan 102
aos(config-vlan)# ports gi 0/4
aos(config-vlan)# exit

Configure VFI and VPN. A user defined string is assigned to the VFI for
identification. In this case, the VFI is called VPLS_ACD. Configure two PWs
under the VPN instance, one towards CTR A and one towards CTR D:
aos# configure terminal
aos(config)# switch default
aos(config-switch)# l2 vfi VPLS_ACD manual
aos(config-switch-vfi)# vpn 1
aos(config-switch-vfi)# neighbor [Link] pwidfec pwid 13 groupid 1
encapsulation mpls mplstype te 31 13 pwtype ethtag
aos(config-switch-vfi)# neighbor [Link] pwidfec pwid 34 groupid 1
encapsulation mpls mplstype te 34 43 pwtype ethtag
aos(config-switch-vfi)# end

Connect the AC VLAN to the VFI:

aos# configure terminal
aos(config)# vlan 102
aos(config-vlan)# xconnect vfi VPLS_ACD
aos(config-vlan)# end

CTR D Configuration
Enable LDP and configure targeted LDP entities towards CTR A and CTR C:
aos# configure terminal
aos(config)# mpls ldp

AVIAT NETWORKS OCTOBER 2017 CX

CHAPTER 5 LAYER 2 VIRTUAL PRIVATE NETWORKS

aos(config-mpls-ldp)# router-id loopback 0 force

aos(config-mpls-ldp)# entity 1
aos(config-mpls-ldp-entity-1)# neighbor [Link] targeted
aos(config-mpls-ldp-entity-1)# ldp label range min 160300 max 160349
aos(config-mpls-ldp-entity-1)# transport-address tlv loopback 0
aos(config-mpls-ldp-entity-1)# no shutdown
aos(config-mpls-ldp-entity-1)# exit
aos(config-mpls-ldp)# entity 2
aos(config-mpls-ldp-entity-1)# neighbor [Link] targeted
aos(config-mpls-ldp-entity-1)# ldp label range min 160350 max 160399
aos(config-mpls-ldp-entity-1)# transport-address tlv loopback 0
aos(config-mpls-ldp-entity-1)# no shutdown
aos(config-mpls-ldp-entity-1)# exit

Configure VLAN for attachment circuit:

aos# configure terminal
aos(config)# vlan 102
aos(config-vlan)# ports gi 0/4
aos(config-vlan)# exit

Configure VFI and VPN. A user defined string is assigned to the VFI for
identification. In this case, the VFI is called VPLS_ACD. Configure two PWs
under the VPN instance, one towards CTR A and one towards CTR C:
aos# configure terminal
aos(config)# switch default
aos(config-switch)# l2 vfi VPLS_ACD manual
aos(config-switch-vfi)# vpn 1
aos(config-switch-vfi)# neighbor [Link] pwidfec pwid 14 groupid 1
encapsulation mpls mplstype te 41 14 pwtype ethtag
aos(config-switch-vfi)# neighbor [Link] pwidfec pwid 34 groupid 1
encapsulation mpls mplstype te 43 34 pwtype ethtag
aos(config-switch-vfi)# end

Connect the AC VLAN to the VFI:

aos# configure terminal

CXI OCTOBER 2017 AVIAT NETWORKS

 LAYER 2 VIRTUAL PRIVATE NETWORKS CHAPTER 5

aos(config)# vlan 102

aos(config-vlan)# xconnect vfi VPLS_ACD
aos(config-vlan)# end

Variation 1: Port Based Attachment Circuit

In order to configure VPSL with port based attachment circuit, following
modifications are required to the above configuration:
1. Remove pwtype ethtag config from all Pseudowire configurations in order
to make PWs raw mode. CTR A configuration for VFI is modified as follows:
aos# configure terminal
aos(config)# switch default
aos(config-switch)# l2 vfi VPLS_ACD manual
aos(config-switch-vfi)# vpn 1
aos(config-switch-vfi)# neighbor [Link] pwidfec pwid 13 groupid 1
encapsulation mpls mplstype te 13 31
aos(config-switch-vfi)# neighbor [Link] pwidfec pwid 14 groupid 1
encapsulation mpls mplstype te 14 41
aos(config-switch-vfi)# end

2. Instead of connecting VLAN 102 to VFI, issue xconnect command under

interface configuration for the AC port. For example, use the following
commands on CTR A to connect physical port gi 0/5 to VPLS. Ensure Gi 0/5 is
not in any vlan.
aos# configure terminal
aos(config)# int gi 0/5
aos(config-if)# xconnect vfi VPLS_ACD
aos(config-if)# end

Variation 2: Port+VLAN Based Attachment Circuit

In order to configure VPLS with port+vlan based attachment circuit, the
following modifications are required to the above configuration:
Ensure the port is a member of attachment circuit vlan. Add vlan ID to the
xconnect command when connecting port to the VFI:
aos# configure terminal
aos(config)# int gi 0/5
aos(config-if)# xconnect vfi VPLS_ACD port-vlan 102
aos(config-if)# end

AVIAT NETWORKS OCTOBER 2017 CXII

 CHAPTER 5 LAYER 2 VIRTUAL PRIVATE NETWORKS

Useful Show Commands

l show mpls l2transport summary or sh mpls l2transport detail: Shows
status and information about the configured L2VPN PWs.
l show vfi: Displays information about all VFIs on the system.

l show mac-address-table: Lists MAC addresses. This

includes MAC addresses on VFIs for VPLS. VPLS addresses
are listed under VLAN 4097 onwards.

CXIII OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

Chapter 6. Layer 3 Virtual Private

Networks

Overview
MPLS Layer 3 VPNs (also known as BGP/MPLS VPNs) provide VPN service at the
IP layer. Typically, at each VPN site, a provider edge router peers with a
customer edge router which connects to the rest of the customer network.
Similar to L2VPN, most L3VPN configuration resides in edge routers only. The
core routers in the service provider’s network simply switch traffic based on
MPLS transport labels.
The following sections describe the individual elements of L3VPNs and their
configuration in AOS. Most examples in this chapter are based on slightly
modified version of Topology B on page xxiii. It is assumed that basic IP and IS-
IS configuration, MPLS traffic engineering and LSP configuration has been
completed according to scripts in the following sections:
l Topology B on page 1
l Configuration for Topology B on page 1
l Dynamic Tunnels for Topology B on page 1

The new element introduced here are the three CE routers which peer with their
corresponding PE routers at each VPN site.

AVIAT NETWORKS OCTOBER 2017 CXIV

 CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

Figure 5. Modified Topology B for L3VPN - CE Devices Added

VRF Configuration
A separate Virtual Routing and Forwarding (VRF) instance is created on the
provider edge routers for each L3VPN service. A VRF instance maintains
separate (private) routing and forwarding tables for a L3VPN service containg
routing information to get customer traffc across different VPN sites. Each PE-CE
link on a PE router is assigned to a particular VRF. The traffic arriving at the PE
router from a CE router is mapped to the correct  L3VPN service, based on the
local configuration on the PE router, which assigns the receiving interface to a
particular VRF. The traffic arriving from the provider core is demultiplexed
based on the VPN label described in the section L3VPN Route AND Label
Distribution on page cxvi and mapped to the correct VRF instance. Once the VRF
instance is identified, the forwarding decision is made in both directions based
on the routing table for that VRF.
Loopback interfaces can also be added to a VRF and are useful for diagnostic and
identification purposes. For example, to be used as router IDs for routing
protocols running on CE-PE interface.

NOTE: In SW R eleas e 3.4, IP ping from a loopbac k addres s in a VR F to a

loopbac k addres s in the s ame VR F on a remote PE router (als o know n as
VR F Ping), is not s upported in C TR .

The following example shows configuration of a VRF on CTR A. The VRF is given
customer1 as the identifier. It has two interfaces: physical port gi 0/7 and a
loopback interface:
Create VRF customer1 :
aos# configure terminal
aos(config)# ip vrf customer1
aos(config)# end

Add port gi 0/7 to VRF and assign it an IP address. ip vrf forwarding <vrf-
identifier> command assigns the interface to a specific VRF. Without this
command, the interface would belong to the default VRF which is used for
‘normal’ IPv4 forwarding as opposed to L3VPN forwarding.
aos# configure terminal
aos(config)# interface gi 0/7
aos(config-if)# shutdown
aos(config-if)# no map switch default
aos(config-if)# no shutdown

CXV OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

aos(config-if)# ip vrf forwarding customer1

aos(config-if)# ip address [Link] [Link]
aos(config-if)# no shutdown
aos(config-if)# end

Add a loopback interface to the VRF:

aos# configure terminal
aos(config)# interface loopback 1
aos(config-if)# ip vrf forwarding customer1
aos(config-if)# ip address [Link] [Link]
aos(config-if)# end

L3VPN Route AND Label Distribution

BGP with multiprotocol extensions (MP-BGP) is used to signal L3VPN labels
across the PE devices. The VPN label is pushed on the packets before the MPLS
transport label (VPN label is the inner label). This label is transparent to the core
routers and is used at the remote PE to map the arriving packets to the correct
VRF. L3VPN label distribution requires little to no configuration from the user
apart from the label allocation mode. This can be one label per VRF or one label
per route, which means separate label for each route in the VRF.
MP-BGP is also used to exchange VRF routing information among PE routers. All
PE routers participating in L3VPN service must have a full mesh of BGP sessions,
unless a route reflector is used. BGP provides a great degree of control over
how the routes are propagated and shared across VPN sites. Route
Distinguishers and Route Targets are two key constructs involved in MP-BGP
configuration for L3VPNS. These are described in the following sections.

Route Distinguisher (RD)

A PE router learns and maintains customer route information for the local site,
such as which customer prefixes are aavailable at the site and are reachable via
this PE router. The PE router might learn this information via a routing protocol
running on CE-PE interface or this information might be statically configured in
the PE router. The PE router uses MP-BGP to send this information to other PE
routers in the network. With MP-BGP exchange, it also learns about other
customer prefixes and the correct PE devices which should be used to reach
those prefixes.

AVIAT NETWORKS OCTOBER 2017 CXVI

 CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

When IP prefixes belonging to customer VRFs (L3VPNs) are carried across the
provider network using BGP, they need to be distinguished from IP prefixes
belonging to the provider’s own network and from IP prefixes belonging to other
customer’s networks. This enables customers to use overlapping IP address
space. BGP’s multiprotocol extensions provide this capability by introducing
VPNv4 address family.
When a PE router uses BGP to exchange L3VPN prefixes, it converts them from
IPv4 to VPNv4 family addresses. To achieve this, the PE router adds a Route
Distinguisher (RD) to the customer’s IP prefix. Route Distinguisher is usually
statically configured in the PE routers. Its only role is to make the VPN
addresses uniquely identifiable. Any convenient allocation scheme can be used
to configure RDs, for example, one RD per VPN or one RD per site in a VPN. In
AOS, RD can be configured as the AS number followed by a number or an IP
addresss followed by a number.
The following example shows configuring a route distinguisher 65001:11 for on a
PE router for VRF customer1. It is assumed that 65001 is the AS number used in
provider’s network:
aos# configure terminal
aos(config)# ip vrf customer1 mpls
aos(ip-vrf-mpls)# rd 65001:11
aos(ip-vrf-mpls)# end

Route Target (RT)

Route target is a BGP Extended Community attribute which is used to apply
constraints to distribution and sharing of customer route information.
A PE router will attach RTs to all customer prefixes it advertises via MP-BGP.
The RT applied to advertised routes is controlled via export route target
configuration in the PE for a particular VRF.
When VPNv4 routes are received at a PE, the attached RTs are compared with
the settings for all defined VRFs. If a particular VRF has an import route target
configured with an RT value that is attached to the incoming route, then the
incoming route is accepted into VRF and installed in the VRF routing table. Using
this mechanism a number of VPN connectivity policies can be implemented. For
example, routes can be exchanged across all sites in a single VPN or
restirictions on connectivity can be imposed by configuring certain PEs to accept
routes with only a subset of RTs.
The format of route target in AOS is similar to route distinguisher, i.e. AS
number followed by a number or IP address followed by an number.

CXVII OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

The following example demonstrates RT configuration on CTR A for Topology B

(Figure- Modified Topology B for L3VPN - CE Devices Added). AS:nn format is
used here. It is assumed that AS number for provider’s network is 65001. It is
assumed that CTR C and CTR D export routes with RTs 65001:13 and 65001:14
respectively. CTR A is being configured to accept all routes with these two RTs.
CTR A exports its routes with RT 65001:11.
aos# configure terminal
aos(config)# ip vrf customer1 mpls
aos(ip-vrf-mpls)# route-target import 100:13
aos(ip-vrf-mpls)# route-target import 100:14
aos(ip-vrf-mpls)# route-target export 100:11
aos(ip-vrf-mpls)# end

MP-BGP Peering
Once RDs and RTs are configured, the full mesh of MP-BGP peerings among all
PE routers has to be configured. Under each BGP neighbour which is a PE,
address family VPNv4 has to be enabled. Redistribution of internal routes for
VRF has to be enabled for BGP. If TE tunnels are being used, L3VPN binding to
the tunnels has to be configured. The following example shows this configuration
for CTR A with MP-BGP sessions to CTR C and CTR D (Figure- Modified Topology
B for L3VPN - CE Devices Added):
Enable BGP routing in the device and apply global BGP configuration. The local
BGP entity should be configured with the AS number for the provider’s network.
In this example, the number is assumed to be 65001:
aos# configure terminal
aos(config)# router bgp 65001
aos(config-router)# redistribute all
aos(config-router)# bgp router-id [Link]
aos(config-router)# label-allocation-mode per-vrf 

Configure sessions with other BGP peers. Redistribution of VPNv4 address

family has to be enabled with each peer. In this example, the two BGP peers are
the PE routers (CTR-C [Link] and CTR-D [Link]):
aos(config-router)# neighbor [Link] remote-as 65001
aos(config-router)# neighbor [Link] update-source [Link]
aos(config-router)# address-family vpnv4
aos(config-router-afvpnv4)# neighbor [Link] activate

AVIAT NETWORKS OCTOBER 2017 CXVIII

 CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

aos(config-router-afvpnv4)# ex
aos(config-router)# neighbor [Link] remote-as 65001
aos(config-router)# neighbor [Link] update-source [Link]
aos(config-router)# address-family vpnv4
aos(config-router-afvpnv4)# neighbor [Link] activate
aos(config-router-afvpnv4)# end
Configure redistribution of VRF customer1 routes to BGP:
aos# configure terminal
aos(config)# router bgp 65001
aos(config-router)# address-family ipv4 vrf customer1
aos(config-router-af4)# bgp redistribute-internal
aos(config-router-af4)# redistribute all
aos(config-router-af4)# end

Configure MPLS-TE tunnel bindings:

aos# configure terminal
aos(config)# mpls l3vpn binding  ipv4 [Link] [Link] rsvp-te 13
aos(config)# mpls l3vpn binding  ipv4 [Link] [Link] rsvp-te 14
aos(config)# end

Configure CE-PE Routing

So far, most of the configuration has been on PE devices. At this stage, provider
network has been configured to propagate customer routes across different VPN
sites and also to forward traffic to these routes. The last step is to enable
configuration of routing information between PE and CE devices to enable the PE
routers to learn customer routes.

Static Routing
Simplest solution is to use static routing. A CE device has a static route, or
multiple static routes if needed, configured on it which uses the PE device as the
next hop to all VPN addresses on remote sites. The PE router has a static route
towards CE configured for all the prefixes present on the VPN site to which the
PE router is connected. PE router will redistribute this information to other PEs
via MP-BGP.
This requires prior knowledge of prefixes present at each site which have to be
statically configured on PE and CE devices.

CXIX OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

The following example shows static configuration at Site A (CTR A and CTR CE-
A) in Topology B (Figure- Modified Topology B for L3VPN - CE Devices Added). It
is assumed that a CTR CE-A has a loopback address [Link]/32 which is
being configured to be reachable from other VPN sites. Also assume that
customer site has a local subnet [Link]/16 which is being configured to be
reachable from other sites.
Configuration on CTR-A is to add static routes in VRF customer1. These static
routes use directly connected link [Link] (assuming the other side has
address [Link]) as the next hop:
aos# c t
aos(config)# ip route vrf customer1 [Link] [Link] [Link]
aos(config)# ip route vrf customer1 [Link] [Link] [Link]
aos(config)# end 

Configuration on CTR CE-A is to use CTR A as next hop for all remote sites.
Assume CTR C and CTR D have similar loopback addresses ([Link] &
[Link]) and network segments connected ([Link]/16 and [Link]/16).
CTR CE-A will use CTR-A as the next hop for all of these addresses. Note that
VRF is only applicable to PE router. At the CE router, the connection appears to
be a ‘normal’ IPv4 connection and all addresses are in the default VRF:
aos# c t
aos(config)# ip route [Link] [Link] [Link]
aos(config)# ip route [Link] [Link] [Link]
aos(config)# ip route [Link] [Link] [Link]
aos(config)# ip route [Link] [Link] [Link]
aos(config)# end 

eBGP Routing
eBGP is a popular dynamic routing protocol used on CE-PE interface. When eBGP
is used, the AS-nubmer on CE router will be the AS number for customer’s
network (which is different from provider’s AS). The PE device is configured to
redistribute IP addresses from VRF customer1 to eBGP. Note that a single
instance of BGP is running on the PE device and it handles both MP-BGP peerings
for L3VPN signalling within the provider’s network and CE-PE signalling with
customer router. The peers for each address family and VRF are configured
separately.

AVIAT NETWORKS OCTOBER 2017 CXX

 CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

For Topology B (Figure- Modified Topology B for L3VPN - CE Devices Added),

after all configurations till section L3VPN Route AND Label Distribution on page
cxvi are complete, the following configuration will enable eBGP as CE-PE routing
protocol on VRF customer1. Note that remote-as override option must be set to
prevent BGP’s loop prevention mechanism to kick in when a route from a
remote customer site is advertised, if all customer sites use same AS number:
aos# configure terminal
aos(config)# router bgp 65001
aos(config-router)# address-family ipv4 vrf customer1
aos(config-router-af4)# neighbor [Link] remote-as 65002
aos(config-router-af4)# neighbor [Link] activate
aos(config-router-af4)# neighbor [Link] next-hop-self
aos(config-router-af4)# neighbor [Link] as-override
aos(config-router-af4)# end

At CTR CE-A an eBGP instance with neighbourship to local PE has to be

configured. Note that the CE device sees all addresses as ‘normal’ IPv4
addresses in its default VRF:
aos# c t
aos(config)# router bgp 65002
aos(config-router)# bgp router-id [Link]
aos(config-router)# neighbor [Link] remote-as 65001
aos(config-router)# redistribute all
aos(config-router)# end

Useful Show Commands

l show ip bgp summary: BGP summary status.
l show ip bgp neighbor: List of BGP peers and status of sessions.
l show ip bgp rib: BGP routing information base.
l show ip interface vrf <vrf-name>: List of IP interfaces in a VRF.
l show ip route vrf <vrf-name>: routing table entires specific to the
VRF.

CXXI OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

Example Configuration Scripts

This example demonstrates creation of an L3VPN service with three sites on
Topology B (Figure- Modified Topology B for L3VPN - CE Devices Added). It is
assumed that IPv4 and MPLS-TE LSP configuration has been completed on the
topology according to scripts in the following sections:
l Topology B on page 1
l Configuration for Topology B on page 1
l Dynamic Tunnels for Topology B on page 1

VRF & MP-BGP Configuration (Topology B)

In this section interface, VRF and MP-BGP configuration is performed on PE
routers. IP interfaces are configured on CE devices.
For details on individual steps in this configuration on CTR A, refer to:
l VRF Configuration on page cxv
l L3VPN Route AND Label Distribution on page cxvi

CTR A Configuration
Create VRF customer1 :
configure terminal
ip vrf customer1
end

Add port gi 0/7 to VRF and give it an IP address:

configure terminal
interface gi 0/7
shutdown
no map switch default
no shutdown
ip vrf forwarding customer1
ip address [Link] [Link]
no shutdown
end

Add a loopback interface to the VRF:

AVIAT NETWORKS OCTOBER 2017 CXXII

CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

configure terminal
interface loopback 1
ip vrf forwarding customer1
ip address [Link] [Link]
end

Configure RD and RTs:

configure terminal
ip vrf customer1 mpls
rd 65001:11
end
configure terminal
ip vrf customer1 mpls
route-target import 100:13
route-target import 100:14
route-target export 100:11
end

Configure MP-BGP peers and enable for address family vpnv4:

configure terminal
router bgp 65001
redistribute all
bgp router-id [Link]
label-allocation-mode per-vrf 
neighbor [Link] remote-as 65001
neighbor [Link] update-source [Link]
address-family vpnv4
neighbor [Link] activate
ex
neighbor [Link] remote-as 65001
neighbor [Link] update-source [Link]
address-family vpnv4
neighbor [Link] activate
end

CXXIII OCTOBER 2017 AVIAT NETWORKS

LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

Configure redistribution of VRF customer1 routes to MP-BGP (internal):

configure terminal
router bgp 65001
address-family ipv4 vrf customer1
bgp redistribute-internal
redistribute all
end

Configure MPLS-TE tunnel bindings:

configure terminal
mpls l3vpn binding  ipv4 [Link] [Link] rsvp-te 13
mpls l3vpn binding  ipv4 [Link] [Link] rsvp-te 14
end

AVIAT NETWORKS OCTOBER 2017 CXXIV

 CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

CTR C Configuration
Create VRF customer1 :
configure terminal
ip vrf customer1
end

Add port gi 0/7 to VRF and give it an IP address:

configure terminal
interface gi 0/7
shutdown
no map switch default
no shutdown
ip vrf forwarding customer1
ip address [Link] [Link]
no shutdown
end

Add a loopback interface to the VRF:

configure terminal
interface loopback 1
ip vrf forwarding customer1
ip address [Link] [Link]
end

Configure RD and RTs:

configure terminal
ip vrf customer1 mpls
rd 65001:13
end
configure terminal
ip vrf customer1 mpls
route-target import 100:11
route-target import 100:14
route-target export 100:13

CXXV OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

end

Configure MP-BGP peers and enable for address family vpnv4:

configure terminal
router bgp 65001
redistribute all
bgp router-id [Link]
label-allocation-mode per-vrf 
neighbor [Link] remote-as 65001
neighbor [Link] update-source [Link]
address-family vpnv4
neighbor [Link] activate
ex
neighbor [Link] remote-as 65001
neighbor [Link] update-source [Link]
address-family vpnv4
neighbor [Link] activate
end
Configure redistribution of VRF customer1 routes to MP-BGP (internal):
configure terminal
router bgp 65001
address-family ipv4 vrf customer1
bgp redistribute-internal
redistribute all
end

Configure MPLS-TE tunnel bindings:

configure terminal
mpls l3vpn binding  ipv4 [Link] [Link] rsvp-te 31
mpls l3vpn binding  ipv4 [Link] [Link] rsvp-te 34
end

CTR D Configuration
Create VRF customer1 :

AVIAT NETWORKS OCTOBER 2017 CXXVI

CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

configure terminal
ip vrf customer1
end

Add port gi 0/7 to VRF and give it an IP address:

configure terminal
interface gi 0/7
shutdown
no map switch default
no shutdown
ip vrf forwarding customer1
ip address [Link] [Link]
no shutdown
end

Add a loopback interface to the VRF:

configure terminal
interface loopback 1
ip vrf forwarding customer1
ip address [Link] [Link]
end

Configure RD and RTs:

configure terminal
ip vrf customer1 mpls
rd 65001:14
end
configure terminal
ip vrf customer1 mpls
route-target import 100:11
route-target import 100:13
route-target export 100:14
end

CXXVII OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

Configure MP-BGP peers and enable for address family vpnv4:

configure terminal
router bgp 65001
redistribute all
bgp router-id [Link]
label-allocation-mode per-vrf 
neighbor [Link] remote-as 65001
neighbor [Link] update-source [Link]
address-family vpnv4
neighbor [Link] activate
ex
neighbor [Link] remote-as 65001
neighbor [Link] update-source [Link]
address-family vpnv4
neighbor [Link] activate
end
Configure redistribution of VRF customer1 routes to MP-BGP (internal):
configure terminal
router bgp 65001
address-family ipv4 vrf customer1
bgp redistribute-internal
redistribute all
end

Configure MPLS-TE tunnel bindings:

configure terminal
mpls l3vpn binding  ipv4 [Link] [Link] rsvp-te 41
mpls l3vpn binding  ipv4 [Link] [Link] rsvp-te 43
end

CTR CE-A Configuration

Global L3 configurations, create IP link to PE and a loopback address:

configure terminal

AVIAT NETWORKS OCTOBER 2017 CXXVIII

 CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/7
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

CTR CE-C Configuration

Global L3 configurations, create IP link to PE and a loopback address:
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

CXXIX OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal
interface gigabitethernet 0/7
shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

CTR CE-D Configuration

Global L3 configurations, create IP link to PE and a loopback address:
configure terminal
switch default
shutdown spanning-tree
set gmrp disable
set gvrp disable
shutdown garp
bridge-mode customer
end

configure terminal
interface loopback 0
ip address [Link] [Link]
no shutdown
end

configure terminal

AVIAT NETWORKS OCTOBER 2017 CXXX

 CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

interface gigabitethernet 0/7

shutdown
no map switch default
no switchport
ip address [Link] [Link]
no shutdown
end

CE-PE Static Routing (Topology B)

This section demonstrates configuration of static CE-PE routing for VRF
customer1 on Topology B (Figure- Modified Topology B for L3VPN - CE Devices
Added). It is assumed that all configuration till sectionVRF & MP-BGP
Configuration (Topology B) has been completed.
It is assumed that CTR CE-A has a network segment [Link]/16 connected to it
which shall be made reachable via L3VPN. Similarly, it is assumed that CTR-C
has a segment [Link]/16 and CTR-D has a segment [Link]/16.
For details on individual steps in this configuration on CTR A and CTR CE-A, refer
to Static Routing on page cxix.

CTR A Configuration
ct
ip route vrf customer1 [Link] [Link] [Link]
ip route vrf customer1 [Link] [Link] [Link]
end 

CTR C Configuration
ct
ip route vrf customer1 [Link] [Link] [Link]
ip route vrf customer1 [Link] [Link] [Link]
end 

CTR D Configuration
ct
ip route vrf customer1 [Link] [Link] [Link]
ip route vrf customer1 [Link] [Link] [Link]

CXXXI OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

end 

CTR CE-A Configuration

ct
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
end 

CTR CE-C Configuration

ct
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
end 

CTR CE-D Configuration

ct
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
end 

CE-PE eBGP (Topology B)

This section demonstrates configuration of eBGP routing on CE-PE interface for
VRF customer1 onTopology B (Figure- Modified Topology B for L3VPN - CE
Devices Added). It is assumed that all configuration till section VRF & MP-BGP
Configuration (Topology B) has been completed. For details on individual steps
in this configuration on CTR A, refer to eBGP Routing on page cxx.

AVIAT NETWORKS OCTOBER 2017 CXXXII

 CHAPTER 6 LAYER 3 VIRTUAL PRIVATE NETWORKS

CTR A Configuration
configure terminal
router bgp 65001
address-family ipv4 vrf customer1
neighbor [Link] remote-as 65002
neighbor [Link] activate
neighbor [Link] next-hop-self
neighbor [Link] as-override
end

CTR C Configuration
configure terminal
router bgp 65001
address-family ipv4 vrf customer1
neighbor [Link] remote-as 65002
neighbor [Link] activate
neighbor [Link] next-hop-self
neighbor [Link] as-override
end

CTR D Configuration
configure terminal
router bgp 65001
address-family ipv4 vrf customer1
neighbor [Link] remote-as 65002
neighbor [Link] activate
neighbor [Link] next-hop-self
neighbor [Link] as-override
end

CTR CE-A Configuration

ct
router bgp 65002

CXXXIII OCTOBER 2017 AVIAT NETWORKS

 LAYER 3 VIRTUAL PRIVATE NETWORKS CHAPTER 6

bgp router-id [Link]

neighbor [Link] remote-as 65001
redistribute all
end

CTR CE-C Configuration

ct
router bgp 65002
bgp router-id [Link]
neighbor [Link] remote-as 65001
redistribute all
end

CTR CE-D Configuration

ct
router bgp 65002
bgp router-id [Link]
neighbor [Link] remote-as 65001
redistribute all
end

AVIAT NETWORKS OCTOBER 2017 CXXXIV

 MPLS PING & TRACE ROUTE CHAPTER 7

Chapter 7. MPLS Ping & Trace Route

Introduction
To verify the connectivity of LSP connections an MPLS ping can be sent by using
the ping mpls command. An MPLS echo reply is sent in response to an MPLS ping
request.
To test the path, the trace mpls command can be used. The trace mpls
command is similar to the ping mpls command except that the trace command
will send several echo request packets with increasing TTL (similar to IP
Traceroute).
There are four fundamental variations of the command;
l ipv4 – Verification of an LSP bound to a specified ipv4 address.
l pseudowire – Verification of Virtual Circuit Connections (VCCV).
l traffic-eng – Verification of a Traffic-Engineered (TE) Tunnel.
l meg-name – Verification of a Maintenance Entity Group (MEG).
NOTE: In SW R eleas e 3.4, LSP Ping w ith MEG option is not supported.

ping mpls IPv4 target (LDP signalled LSP)

This command can be used to send an echo request for an LSP which is bound to
the designated IPv4 address. The CTR will place a label on the packet according
to the FEC designated by the IPv4 address. 
An example to verify ipv4 LDP signalled LSP of specified address and mask
length:
aos#ping mpls ipv4 [Link]/32
Sending 5, 100-byte MPLS Echos to [Link]/32,
timeout is 2 seconds
Codes :
'!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, m - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no rx label,
'P' - no rx intf label prot, 'p' - premature termination of LSP,

AVIAT NETWORKS OCTOBER 2017 CXXXVI

 CHAPTER 7 MPLS PING & TRACE ROUTE

'R' - transit router, 'X' - unknown return code, 'x' - return code 0,
'I' - Unknown upstream interface index, 'U' - Reserved
!!!!!
Success Rate is 100 percent (5/5), round-trip min/avg/max = 62/70/94 ms

ping mpls RSVP-TE tunnel

This command can be used to verify a Traffic-Engineered (TE) Tunnel.
An example to verify Traffic-Engineered Tunnel number 1 with verbose output:
aos#ping mpls traffic-eng Tunnel 1 verbose
Sending 5, 100-byte MPLS Echos to Tunnel 1,
timeout is 2 seconds
Codes :
'!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, m - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no rx label,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'X' - unknown return code, 'x' - return code 0,
'I' - Unknown upstream interface index, 'U' - Reserved

Type escape sequence to abort.

!size 100, reply addr [Link], return code 3
!size 100, reply addr [Link], return code 3
!size 100, reply addr [Link], return code 3
!size 100, reply addr [Link], return code 3
!size 100, reply addr [Link], return code 3

Success Rate is 100 percent (5/5), round-trip min/avg/max = 61/71/87 ms

ping mpls L2VPN Pseudowire

This command can be used to verify a Virtual Circuit Connection (VCCV) enabled
pseudowire. Before this command can be used, pseudo-wire OAM capabilities
must be globally enabled and VCCV must be configured on the PW.

CXXXVII OCTOBER 2017 AVIAT NETWORKS

MPLS PING & TRACE ROUTE CHAPTER 7

PW OAM capabilities can be globally enabled via following set of commands. For
more information, refer to CTR 8500/8300 CLI Reference Manual Vol 2 for
details):
aos(config)# configure terminal
aos(config)# mpls oam enable
aos(config)# pseudowire-notification pw-status
aos(config)# pw-cc-capability router-alert-label
aos(config)# pw-cv-capability lsp-ping
aos(config)# end

In addition, OAM capability and relevant parameters need to be configured over

the L2VPN PW under the individual PW configuration via pseudowire-oam
command. For example, configuration in Configuration Example: VPWS with
Port Based Attachment Circuit on page cv for VPWS PW will be modified as
follows to enable OAM capability:
aos# configure terminal
aos(config)# interface gigabit ethernet 0/4
aos(config-if)# mpls l2transport pwidfec [Link] pwid 1 groupid 1 mplstype te
13 31
aos(config-if)# mpls pseudowire-oam pwid 1 local-cc-type router-alert-label
local-cv-type lsp-ping remote-cc-type router-alert-label remote-cv-type lsp-
ping
aos(config-if)# end

An example to verify pseudowire at the specified ipv4 address and virtual circuit
id:

aos#ping mpls pseudowire [Link] vc-id 1

Sending 5, 100-byte MPLS Echos to [Link],
timeout is 2 seconds, send interval is 0 msec:

Codes :
'!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, m - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no rx label,
'P' - no rx intf label psrot, 'p' - premature termination of LSP,

AVIAT NETWORKS OCTOBER 2017 CXXXVIII

 CHAPTER 7 MPLS PING & TRACE ROUTE

'R' - transit router, 'X' - unknown return code, 'x' - return code 0,
'I' - Unknown upstream interface index, 'U' - Reserved

Type escape sequence to abort.

!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/32/40 ms PE-
802#

trace mpls IPv4 target (LDP signalled LSP)

This command can be used to send a traceroute request for an LSP which is
bound to the designated IPv4 address.
An example to verify ipv4 LDP signalled LSP of specified address and mask
length:
aos#trace mpls ipv4 [Link]/32
Tracing MPLS Label Switched Path to to [Link]/32,
timeout is 2 seconds
Codes :
'!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, m - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no rx label,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'X' - unknown return code, 'x' - return code 0,
'I' - Unknown upstream interface index, 'U' - Reserved

Type escape sequence to abort.

0 [Link] [Link] MRU 1500 [Labels: 40 Exp: 0]
L 1 [Link] [Link] MRU 1500 [Labels: implicit-null 25 Exp: 0] 63 ms ret code 8
! 2 [Link] 65 ms, ret code 3

CXXXIX OCTOBER 2017 AVIAT NETWORKS

 END TO END LSP PROTECTION CHAPTER 8

Chapter 8. End To End LSP Protection

RFC 4872 describes a number of possible mechanisms for end to end recovery
of MPLS LSPs. In general terms, the recovery process consists of:
l detecting a failure; and
l B- switching the traffic to an alternative path

The alternative path is determined by the head-end router for the LSP.
Depending on the protection mechanism in use, this path may or may not be
calculated and signalled in advance. The following sections describe
configuration of different elements of LSP protection in AOS.

Failure Detection
The simplest failure detection configuration is to rely on the mechanisms built-in
to RSVP-TE. An RSVP-TE node is expected to send a PATH ERROR message to the
head end LSR of an LSP when a failure on the LSP is detected. For example, a
physical link being used by an LSP goes down. RSVP-TE also maintains Hello
timers to aid detection of adjacency failures. If protection for a tunnel is
converted, the head end LSR can react to this message and switch the traffc to
alternative path. No additional configuration on a tunnel is needed for this kind
of detection.
RSVP-TE based failure detection mechanisms tend to be slow in detecting
failures. The recommended method of failure detection for protected LSPs is
using BFD with hardware offloading.

BFD for failure detection on MPLS-TE Tunnels

CTR supports BFD with hardware offloading. BFD interval can be set to as low as
1 millisecond. Lower BFD intervals offer faster detection times.
The following example shows configuration of BFD to monitor a pair of MPLS
tunnels between two routers [Link] and [Link]. A BFD session has to be
configured at both devices.
Globally enable BFD module on the router:
aos(config)# no shutdown bfd
aos(config)# bfd enable

AVIAT NETWORKS OCTOBER 2017 CXL

 CHAPTER 8 END TO END LSP PROTECTION

Configure a BFD session number 10 on the router [Link] . A similar session

needs to be configured at the router [Link]. The session ID of the session on
remote device should be used as BFD discriminator in router [Link]. The
following configuration is for router [Link]. It enables hardware offloading for
BFD and sets BFD interval to 3 msec.
aos(config)# bfd session 10
aos(config-bfdsess)#  bfd mpls traffic-eng tunnel 1  source [Link] destina
[Link]
aos(config-bfdsess)#  bfd set offload
aos(config-bfdsess)#  bfd interval 3 min_rx 3 multiplier 3
aos(config-bfdsess)#  bfd params sess-type single-hop
aos(config-bfdsess)#  bfd params remote-discr 20
aos(config-bfdsess)#  bfd params role active
aos(config-bfdsess)#  bfd params mode cc
aos(config-bfdsess)#  bfd enable
aos(config-bfdsess)# end

NOTE: In SW R eleas e 3.4, the BFD s es s ion is ass ociated w ith an MPLS
–Tunnel and not w ith indiv idual LSPs . The s es sion ass ociated w ith the
tunnel c an monitor only the w ork ing LSP for the tunnel. Failures on the
protec ting LSPs c annot be detec ted w ith BFD .

Protection Mode 1:1

AOS supports 1:1 protection mode for MPLS-TE tunnels. In this mode, both
working and protecting LSPs are calculated and signalled in advance. Under
normal conditions, the traffic flows through the working LSP. As soon as a
failure is detected on working LSP, the head-end router switches the traffic to
protecting LSP.
NOTE: By default, 1:1 protec tion in AOS operates in ‘revertiv e’ mode w ith
a fixed w ait to res tore timer of 120s . The ex pec ted behaviour in this mode
is : upon firs t failure, traffic s w itc hes to protecting path. As soon as
w ork ing path is operational, the head end node starts the w ait to restore
timer. After 120 s ec of w ork ing path bec oming functional, traffic is
sw itched to w ork ing path again.

The path options for working and protecting path are configured individually
using the commands described in Path Options for TE-Tunnels on page xc.

CXLI OCTOBER 2017 AVIAT NETWORKS

 END TO END LSP PROTECTION CHAPTER 8

NOTE: In SW R eleas e 3.4, the w ork ing LSP can use all path options
des cribed in s ec tion 4.1. H ow ev er, the protecting LSP must alw ays be
defined as an ex plic it path w ith a s equenc e of strict hops.
NOTE: R FC 4872 as s umes w ork ing and protecting LSPs to be resource-
dis joint. AOS does not enforc e this res tric tion. This allow s some
protec tion to be c onfigured on netw ork topologies w here more than one
fully res ourc e-dis joint path is not av ailable. The obv ious dow n-side of
us ing non-dis joint paths is that no protec tion w ill be available against
failure on a link /node us ed by both w ork ing and protecting LSPs.
Therefore, to max imiz e the benefits of LSP protection, operators should
av oid s haring link s /nodes betw een w ork ing and protecting LSPs w herever
it is pos s ible to do s o.

The steps for configuration of an MPLS-TE tunnel with 1:1 protection are:
l Define paths for working and protecting LSPs using ip explicit-path
command. This is not needed if dynamic path option is to be used.
l Under MPLS tunnel configuration specify:
o End to end protection type as one-to-one.
o Specify the explicit path identifier configured above as path option 1
for working LSP or specify dynamic path under option 1.
o Specify the explicit path identifier configured above for protecting
LSP as backup-path.
These steps are demonstrated in the sections below.

Configuration Example – 1:1 End To End Protection

With BFD (Using explicit paths for working and
protecting LSPs)
This example provides configuration scripts which can be used to establish
protected tunnels between CTR A and CTR D in Topology C on page xxiv. BFD is
enabled with hardware offloading to support fast recovery.
It is assumed that IS-IS with TE extensions, TE-Links, and RSVP-TE
configurations have been completed on all nodes in the network using scripts
provided in sections Topology C on page 1 and Configuration for Topology C on
page 1. Note that tunnels, BFD and protection configuration are needed only at
the tunnel endpoint nodes. Intermediate nodes in the network only need to be
running IS-IS-TE, TE-links and RSVP-TE (Configured in sections 2.8.3 and
3.5.3).
Details of tunnels are:
Tunnel from CTR-A to CTRD:
Working path: CTR-A → CTR-F → CTR-D
Protecting path: CTR-A → CTR-B → CTR-C → CTR-D

AVIAT NETWORKS OCTOBER 2017 CXLII

 CHAPTER 8 END TO END LSP PROTECTION

Tunnel from CTR-D to CTRA:

Working path: CTR-D → CTR-F → CTR-A
Protecting path: CTR-D → CTR-C → CTR-B → CTR-A

CTR-A Configuration
Define explicit paths for LSPs:
configure terminal
ip explicit-path identifier 1
index 1 next-address strict [Link]
index 2 next-address strict [Link]
exit
ip explicit-path identifier 2
index 1 next-address strict [Link]
index 2 next-address strict [Link]
index 3 next-address strict [Link]
end

Configure protected tunnel use path 1 for working path and path 2 for backup
path:
configure terminal
interface mplstunnel 1
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp
tunnel mpls traffic-eng record-route
tunnel endpoint capability encoding lsp-packet switching psc1
tunnel mpls traffic-eng path-option number 1 explicit identifier 1
tunnel mpls traffic-eng backup path-option number 1 explicit identifier 2
tunnel mpls end-to-end-protection-type one-to-one
no shut
end

CXLIII OCTOBER 2017 AVIAT NETWORKS

 END TO END LSP PROTECTION CHAPTER 8

Enable BFD, and configure BFD with hardware offloading to monitor the working
LSP:
configure terminal
no shutdown bfd
bfd enable
bfd session 10
bfd mpls traffic-eng tunnel 1  source [Link] dest [Link]
bfd set offload
bfd interval 3 min_rx 3 multiplier 3
bfd params sess-type single-hop
bfd params remote-discr 20
bfd enable
end

CTR-D Configuration
Define explicit paths for LSPs:
configure terminal
ip explicit-path identifier 1
index 1 next-address strict [Link]
index 1 next-address strict [Link]
exit
ip explicit-path identifier 2
index 1 next-address strict [Link]
index 2 next-address strict [Link]
index 2 next-address strict [Link]
end

Configure protected tunnel use path 1 for working path and path 2 for backup
path:
configure terminal
interface mplstunnel 2
tunnel mpls destination [Link] source [Link]
tunnel mode mpls traffic-eng
tunnel signalling protocol rsvp

AVIAT NETWORKS OCTOBER 2017 CXLIV

CHAPTER 8 END TO END LSP PROTECTION

tunnel mpls traffic-eng record-route

tunnel endpoint capability encoding lsp-packet switching psc1
tunnel mpls traffic-eng path-option number 1 explicit identifier 1
tunnel mpls traffic-eng backup path-option number 1 explicit identifier 2
tunnel mpls end-to-end-protection-type one-to-one
no shut
end

Enable BFD, and configure BFD with hardware offloading to monitor the working
LSP:
configure terminal
no shutdown bfd
bfd enable
bfd session 20
bfd mpls traffic-eng tunnel 2  source [Link] dest [Link]
bfd set offload
bfd interval 3 min_rx 3 multiplier 3
bfd params sess-type single-hop
bfd params remote-discr 10
bfd enable
end

CXLV OCTOBER 2017 AVIAT NETWORKS

 MPLS CONFIGURATION

Appendix A. MPLS Label Ranges In AOS

Nomenclature

Remote Label
This is also called out label or push label. This label is advertised to the device
under configuration from its partner device. This label will be ‘pushed’ on all
packets before they are sent out towards the partner. Partner could be the next
hop for an LSP or the remote PE router for AToM, L2VPN and L3VPN service.

Local Label
This is also called in label or pop label. This is the label which the device being
configured advertises to its partners. The device unvder configuration expects
the partner to send the traffic with this label pushed on it. The device will use
this label to map the packet to an LSP or service and will perform a pop or swap
operation on this label.

260-668256-014 OCTOBER 2017 CXLVI

APPENDIX A, MPLS LABEL RANGES IN AOS

Local Label Ranges

Table 9. Local Label Ranges

Label Range Application Configuration Information

0-15 Standard reserved labels
16-99 Reserved/Unused in AOS
100-100,000 MPLS LSPs signalled with Configured under non-targeted ldp entity
LDP with command:
ldp label range min <value> max <value>
If not configured, the entity will use entire
label range.
100,001-160,000 MPLS LSPs signalled with Configured under rsvp entity with
RSVP-TE command:
signalling label range min <value> max
<value>
If not configured, the entity will use entire
available range 160,001-200,000
160,001-200,000 AToM services signalled with Configured under targeted ldp entity with
T-LDP (e.g VPWS, VPLS, command :
SAToP) ldp label range min <value> max <value>
If multiple targeted LDP entities are
configured on a single device, they must
have nonoverlapping label ranges.
200,001-300,000 Space available for static label Availale for configuration as ”local label” in
assignment. Usable for static the following commands:
LSPs and AToM. Static LSP:
mpls static binding
mpls static
crossconnect
VPWS/AToM:
mpls l2transport
manual <ip-addr>
pwid <id> locallabel
<label>
VPLS:
neighbour <ip-addr>
manual pwid <id>
locallabel <label>
300,001-400,000 L3VPN Labels The range is internally resered for L3VPN
labels.
400,001- Reserved/Unused in AOS
1,048,575

CXLVII AVIAT NETWORKS

 MPLS CONFIGURATION

Remote Label Ranges

To allow maximum inter-operability against other vendors, AOS allows the
entire MPLS label space (16-1,048,575) to be used as remote label range for all
applications. In cases where remote label is received via a dynamic signalling
protocol, AOS will honour any label in the range (16-1,048,575) as out label and
will push the label to the traffic at the appropriate position in the MPLS label
stack. For static configuration, AOS allows the entire range (16-1,048,575) to be
configured as out label or remote label.

260-668256-014 OCTOBER 2017 CXLVIII

APPENDIX A, MPLS LABEL RANGES IN AOS

CXLIX AVIAT NETWORKS

 260-668256-014
[Link]