7705 SAR

R6.0 Strategic Industries

Student Guide
TER36055_V3.0-SG Edition 1

COPYRIGHT © ALCATEL-LUCENT @@YEAR. ALL RIGHTS RESERVED.

Passing on and copying of this document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

 Terms of use and legal notices

Switch to notes view!

TERMS OF USE AND LEGAL NOTICE
Alcatel-Lucent provides this training course to you subject to these Terms of Use and Legal Notice. Your use of this training course
and/or this site constitutes your acceptance of and agreement to these Terms of Use and Legal Notice. These Terms of Use and Legal
Notice, as well as the contents of this training course, may be updated or amended by Alcatel-Lucent from time to time without prior
notice to you. Your use of the Alcatel-Lucent training materials after such update or amendment constitutes your acceptance of and
agreement to said updated or amended Terms of Use and Legal Notice.

SAFETY WARNING
Alcatel-Lucent training materials can be for products or refer to products that have both lethal and dangerous voltages present. Always
observe all safety precautions and do not work on the equipment alone. The user is strongly advised not to wear conductive jewelry
while working on the products. Equipment referred to or used during this course may be electrostatic sensitive. Please observe correct
anti-static precautions.

PERMISSION TO USE CONTENT

The information, communications, scripts, photos, text, video, graphics, music, sounds, images and other materials provided in this
training course (collectively the "Content"), is intended for the lawful use of employees of Alcatel-Lucent and other authorized
participants in this Alcatel-Lucent training course. You are hereby granted a non-exclusive, non-transferable permission to access and
use the Content solely for your personal training and non-commercial use. This permission may be terminated by Alcatel-Lucent at
any time for any reason or no reason, with or without notice. You must immediately cease use of the Content upon such termination.

COPYRIGHTS AND TRADEMARKS

The unauthorized copying, displaying or other use of any Content from this training course is a violation of the law and Alcatel-Lucent’s
corporate policies. The Content is protected in France, the U.S. and other countries by a variety of laws, including but not limited to,
copyright laws and treaty provisions, trademark laws, patent laws and other proprietary rights laws (collectively, "IP Rights"). In
addition to Alcatel-Lucent’s IP Rights in the Content, in part and in whole, Alcatel-Lucent, and any of the third parties who have
licensed and/or contributed to the Content, owns a copyright in the formatting and presentation of the Content.
Alcatel-Lucent does not grant you any permission to use the Content other than the permission expressly stated in these Terms of Use
and Legal Notice. All other use of Content from this training course, including, but not limited to, modification, publication, transmission,
participation in the transfer or sale of, copying, reproduction, republishing, creation of derivative works from, distribution, performance,
display, incorporation into another training course or presentation, or in any other way exploiting any of the Content, in whole or in
part,2for uses other than those expressly permitted COPYRIGHT
herein©isALCATEL-LUCENT
strictly prohibited and shall not be made without Alcatel-Lucent’s prior
2014. ALL RIGHTS RESERVED.
written consent. All characters appearing in this training course are fictitious. Any resemblance to real persons, living or dead, is purely
@@PRODUCT
@@COURSENAME
coincidental.
There may be a number of proprietary logos, marks, trademarks, slogans and product designations found in the Content. Alcatel,
Lucent, Alcatel-Lucent and the Alcatel-Lucent logos are trademarks of Alcatel-Lucent. All other trademarks are the property of their
respective owners. Alcatel-Lucent does not grant you a license to use any of the foregoing logos, marks, trademarks, slogans and
product designations in any fashion. Granting of the right to access and use the Content for training purposes does not confer upon
you any license under any of Alcatel-Lucent’s or any third party's IP Rights.

DISCLAIMER
ALCATEL-LUCENT DISCLAIMS ALL WARRANTIES REGARDING THE TRAINING COURSES OR THE CONTENT, EXPRESS OR IMPLIED,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
THE ALCATEL-LUCENT WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY INJURY, LOSS, CLAIM, DAMAGE, OR ANY SPECIAL,
EXEMPLARY, PUNITIVE, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING WITHOUT LIMITATION
LOSS PROFITS OR LOSS SAVINGS), WHETHER BASED IN CONTRACT, TORT, STRICT LIABILITY OR OTHERWISE, THAT ARISES OUT
OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THE CONTENT OR THE TRAINING COURSES BY YOU, OR (B)
ANY FAILURE OR DELAY BY ALCATEL-LUCENT, ITS OFFICERS, DIRECTORS, AGENTS OR EMPLOYEES IN CONNECTION WITH THE
CONTENT OR THE TRAINING COURSES (INCLUDING, WITHOUT LIMITATION, THE USE OF OR INABILITY TO USE ANY COMPONENT
OF THE CONTENT OR TRAINING BY YOU). SOME JURISDICTIONS LIMIT OR PROHIBIT SUCH EXCLUSION OF WARRANTIES OR
LIMITATION OF LIABILITIES AND SO THE FOREGOING EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITY MAY NOT APPLY
TO YOU.

GOVERNING LAW
These Terms of Use and Legal Notice are governed by the laws of France. The operation and use of the training course is governed by
the laws of the country that governs your employment contract, if applicable. If any provision of these Terms of Use and Legal Notice,
or the application thereto to a person or circumstance, is held invalid or unenforceable by law, statute or a court of competent
jurisdiction, for any reason, then such provision shall be modified and/or superseded by a provision that reflects the intent of the
original provision as closely as possible. All other provisions of these Terms of Use and Legal Notice shall remain in full force and
effect. You may not assign these Terms of Use or any permission granted hereunder without Alcatel-Lucent’s prior written
consent. Nothing herein shall be deemed an employment agreement or an offer of employment or an alteration in any way of a user’s
terms of employment with or within Alcatel-Lucent.
Copyright © 2013 Alcatel-Lucent. All Rights Reserved

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

 Course outline

1. Strategic
Welcome Industries
to 7705 SAR Overview
R6.01.Strategic
StrategicIndustries
Industries Solution Overview
2. Internal Routing Protocol
1. Link
1. Strategic State Protocols
Industries Overview Overview
1. Strategic Industries Solution Overview
2. OSPF
2. Internal Routing Protocol
3. IS-IS
1. Link State Protocols Overview
3. IP/MPLS
2. OSPF
1. MPLS Overview
3. IS-IS
2. LDP
3. IP/MPLS
3. RSVP-TE
1. MPLS Overview
4. Services
2. LDP
1. Services
3. RSVP-TEOverview
2. Services Components
4. Services
1. Services Overview
3. C-Pipe
2. Services Components
4. E-Pipe
3. C-Pipe
3 5. A-Pipe COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
4. E-Pipe
@@PRODUCT

6. I-Pipe
@@COURSENAME

5. A-Pipe
6. I-Pipe
7. VPLS
8. VPRN
9. IES
5. Synchronization
1. Synchronization Overview
6. Quality of Service
1. Quality of Service
7. HA and Resiliency
1. Resiliency and High Availibility
8. OAM
1. ETH-OAM
9. Typical Applications
1. Typical Applications
10. Service Aware Manager
1. 5620 SAM

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

 Course objectives

7705 SAR

Upon completion of this course, you should be able to:
R6.0 Strategic
 • Identify Industries
the various Alcatel-Lucent Strategic Industries Solutions
 • Understand the synchronization method and high availability capabilities of the 7705 SAR
 • Describe the services supported for the Strategic Industry market
Upon completion of this course, you should be able to:
 • Explain how legacy services are supported and how the 7705 SAR incorporates the Alcatel-
Lucent packet microwave solution

 • Understand
• Identify the varioushow Service Level
Alcatel-Lucent Agreements
Strategic (SLAs)
Industries are enforced and how performance
Solutions
measurements are performed.

• Understand
 • Configurethe and
synchronization
troubleshootmethod andSAR
the 7705 highand
availability
servicescapabilities of the 7705 SAR

 • Identify
• Describe the 7705supported
the services SAR network resilience
for the Strategicand high-availability
Industry market features

 • Describe the Ethernet OAM tools supported by the 7705 SAR
• Explain how legacy services are supported and how the 7705 SAR incorporates the Alcatel-Lucent packet
 • Define
microwave the role of the 5620 SAM in the Strategic Industries market
solution

• Understand how Service Level Agreements (SLAs) are enforced and how performance measurements are
performed.

• Configure and troubleshoot the 7705 SAR and services

• Identify the 7705 SAR network resilience and high-availability features

• Describe the Ethernet OAM tools supported by the 7705 SAR

• Define the role of the 5620 SAM in the Strategic Industries market

4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

@@PRODUCT
@@COURSENAME

Your feedback is appreciated!

Please feel free to Email your comments to:

[email protected]

Please include the following training reference in your email:

TER36055_V3.0-SG Edition 1

Thank you!

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

Learning experience powered by
Alcatel-Lucent University

Section 1
Strategic Industries Overview
Module 1
Strategic Industries Solution Overview
TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

1—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 1
 Blank page

1—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 2
Module objectives

Upon completion of this module, you should be able to:

List the different domains of the Strategic Industries

Outline typical applications in the strategic industry market

Describe the Alcatel-Lucent solution

Identify key requirements

Determine the positioning of the 7705 SAR

1—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 3
Module objectives [cont.]

1—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 4
 Table of Contents

1 Strategic Industries Market 8

Page
2 Alcatel-Lucent’s Solution and Key Features 17
1 Strategic
3 The 7705 Industries
SARMarket 8 23
1.1 Strategic Industries Market 9
4 Strategic
1.2 End-to-End Service
Industries Market:Management
Energy 10 30
1.3 The Strategic Industries Market: Transportation 11
5 The
1.4 Rapid CellIndustries
Strategic DeploymentMarket: Public sector 13 35
6 Summary
1.5 The Strategic Industries Market: Enterprise market 14 39
1.6 The Strategic Industries Market: Defense and security 15
1.7 Knowledge check 16
2 Alcatel-Lucent’s Solution and Key Features 17
2.1 Legacy versus a new IP/MPLS network 18
2.2 Typical legacy applications 19
2.3 Strategic Industry Example: Utilities Network 20
2.4 SR-OS on the Service Routing Platforms 21
2.5 Knowledge check 22
3 The 7705 SAR 23
3.1 The 7705 SAR—an award-winning product line 24
3.2 The 7705 SAR—an award-winning product line (continued) 25
3.3 Extension of Service Routing Values 26
3.4 Continued Investment in the 7705 SAR Family 27
3.5 Infrastructure and Networking Flexibility 28
3.6 Knowledge check 29
4 End-to-End
1—1—5
Service Management 30
4.1Strategic
Alcatel-Lucent 5620
Industries Overview — Strategic
7705 SAR — R6.0 Strategic Industries
Service Aware Manager
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Industries Solution Overview 31
4.2 Streamlined Service Provisioning with 5620 SAM 32
4.3 5650 CPAM Auto-OA&M and Conditional Testing 33
4.4 Knowledge check 34
5 Rapid Cell Deployment 35
5.1 Importance of Rapid Cell Site Deployment 36
5.2 Rapid Cell Site Deployment: Auto-Discovery & Provisioning (ADP) 37
5.3 Knowledge check 38
6 Summary 39
6.1 Continuing Success of the 7705 SAR 40

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 5
Table of Contents [cont.]

1—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 6
 This page is left blank intentionally

1—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Oil and Gas companies typically have many facilities. A reliable communications infrastructure interconncects
these facilities to support core operations such as distribution and pipeline management. Increasingly, the
communications requierment is IP centric with services including critical voice, video and data. Implementing a
next generation IP/MPLS-based network with hierarchical QoS can ensure that critical traffic is guaranteed while
enabling other corporate services that improve efficiency and lower operating costs.

Utilities are very effective in managing their own communications infrastructures. In a deregulated telecom
market, utilities can leverage their experience in managing communications infrastrutures and in providing
critical services to increase revenues. One opportunity being embraced by a growing number of utilites is to
become a UTelco - Utility Telco. While an IP/MPLS network delivers the need for a robust mission critical
network, its capability to deliver multiple services makes it also perfectly suited as a network infrastructure to
offer business and residential services, as well as carriers’ carrier bandwidth wholesale. For smaller communities,
a UTelco can also be an enabler to ensure economic growth, attract and retain business, and provide high-quality
services to citizens.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 7
 1 Strategic Industries Market

1—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 8
 1 Strategic Industries Market
1.1 Strategic Industries Market

Energy Transportation Public sector Enterprises Defense & Security

The IPD portfolio of products, services and

solutions have been providing highly reliable,
flexible, mission critical infrastructures to these
customers for many years.

1—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Alcatel-Lucent realizes the enormous potential of the strategic industries and enterprises. The IP portfolio of
products, services and solutions have been providing highly reliable, flexible, mission critical infrastructures to
their customers for many years.

The Strategic Industry market is typically subdivided into sub domains like energy, transportation, the public
sector, enterprises and defense and security.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 9
 1 Strategic Industries Market
1.2 Strategic Industries Market: Energy

Energy market comprises utility, oil and gas and the new utility-Telco’s

Rely on their own integrated communications network

Need to support legacy or non-packet based technologies over a packet

based network

IP/MPLS is ideally suited to support these mission critical applications

Utility Telco can become U-Telco in deregulated market

U-Telco offering business and residential services

Or offer bandwidth wholesale to carriers

1 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Energy companies rely on their integrated communications networks to support core business such as electricity
distribution and pipeline operations. The Alcatel-Lucent IP/MPLS network infrastructure can enable an energy
company to extend and enhance its network with new technologies like IP, Ethernet and MPLS. These new
technologies will enable the company to optimize its network to reduce both CAPEX and OPEX without
jeopardizing reliability. Advanced technologies also enable the introduction of new applications that can improve
operational and workflow efficiency. A highly available IP/MPLS infrastructure is ideally suited to support both
mission critical operations and enterprise communications requirements. This infrastructure can also enable an
energy company to operate as a service provider - offering business and residential services, as well as carriers’
carrier bandwidth wholesale.

Utility companies rely heavily on their communications infrastructures to ensure the flawless delivery of critical
services. Information management technologies are now being integrated with grid operations, to deploy new
types of services, including automation systems, metering infrastructures, and control applications to improve
customer service and power reliability. Increasingly, the utility network infrastructure must deliver integrated
voice, data and video communications. While traditional communications systems have been effective, these
newer services such as Ethernet SCADA, VoIP, IP surveillance, video conferencing, wireless data can be more
effectively delivered in a converged IP/MPLS next-generation network.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 10
 1 Strategic Industries Market
1.3 The Strategic Industries Market: Transportation

Transportation market comprises railway, airport highway and seaport

Need to support internal operations and customer-oriented services

Both mission-critical and non-mission critical

IP/MPLS perfectly suited with configurable QoS levels

1 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Transportation companies’ communications infrastructures support a broad range of applications, including those
related to the internal operations and those that support customer-oriented services. Alcatel-Lucent has a compelling
IP/MPLS based communications infrastructure that enables these companies to meet the performance requirements
of all their applications, from non-critical business applications to mission-critical services. A service-aware IP/MPLS
network provides the benefit of supporting consolidated voice, data and video applications that can be managed
through configurable QoS levels.

Many rail operators are undertaking an information and communications technology (ICT) transformation to increase
the efficiency of their IT infrastructures and capitalize on technological innovations. Traditionally, rail operators have
managed multiple networks supporting different applications. Now, a growing number of applications are IP-based.
Many of these IP applications are much more demanding in terms of bandwidth, availability and responsiveness.
Rather than continue to manage separate networks, adding IP into the mix, rail operators can improve the efficiency
of their operations by adopting an IP/MPLS converged network. This approach provides rail operators with an
effective network for IP video, voice and data traffic.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 11
 1 Strategic Industries Market
1.3 The Strategic Industries Market: Transportation [cont.]

This page is left blank intentionally

1 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Airports have many communications requirements interconnecting facilities such as main terminal buildings,
control tower, cargo building, fire station etc. A communications infrastructure is required to provide support for
all data, voice and video communications for IT, security and control systems in an airport for both operational
needs as well as service resale. A highly available IP/MPLS network can meet the demanding expectations for
service convergence of mixed voice, data and video traffic associated with the diversity of subsystems and
applications. Airport Authorities worldwide have also used IP networks in air traffic control networks supporting
mission critical voice and data communications.

Highway agencies are responsible for operating, maintaining and improving road infrastructures. A
communications network supporting voice, video and data is very critical in the operations to improve travel. To
support customer needs to safe road and improved journey time, many agencies are deploying new roadside
devices to support their operations. This requires a communications network that can support various types of IP-
based information between the operational center and the tens of thousand devices alongside the highways
Deploying a converged, high-speed, IP/MPLS communications network alongside the highways can improve
operational efficiency, improve traffic flow, enhance safety and security, and improve driver information.

A communications infrastructure in a seaport provides communications services to the Port Authorities, Customs,
Police, and Shipping Companies, etc. An IP/MPLS network offers a seaport the flexibility, scalability and feature
sets required for mission-critical operations supporting signals for Radar, SCADA, Port & Vessel Information
Systems, as well as all associated Enterprise voice, data and video communicaitons requirements.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 12
 1 Strategic Industries Market
1.4 The Strategic Industries Market: Public sector

The Public Sector market comprises Municipalities, State- Regional- and

Federal governments, Public Safety Agencies, Healthcare and Education

Advanced applications and services becoming increasingly crucial

IP/MPLS network applications were developed to provide an effective

infrastructure to carry the voice, data and video traffic

1 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Alcatel-Lucent has being providing networking infrastructure for the Municipal, State and Federal
Public Sectors as well as public and private Hospitals and Education institutions for many years. The
IP Division has products and services where mission critical infrastructure and converged networks are
required. Our carrier grade products ensure even the most stringent reliability and maintainability
requirements are met.
The IP Division has categorized the various government markets into several sectors to help align
solution material with real opportunities. These sectors include Municipal, State, Federal, Healthcare
and Education.
Cities and municipalities have recognized the social and economic benefits of ensuring access to
global information for their government employees, businesses and residences. However, many
communities have poor access to information infrastructure and with advanced applications and
services becoming increasingly crucial, some municipalities and their utilities are taking a proactive
approach to broadband-access-network creation by building and managing their own networks.
The Alcatel-Lucent IP/MPLS network applications were developed to provide an effective infrastructure
to carry the voice, data and video traffic offered to businesses and residences by carriers around the
world and those same capabilities are extremely effective for municipal and city networks. These
networks may initially converge all the government voice and data traffic then expand to offer access
to businesses and ultimately provide the triple play services, including video on demand (VoD) to their
residences.

The demands on State and Regional governments to provide ubiquitous services for policing and
security including land mobile radio access, the transfer of data from government supported hospitals,
universities, government offices and other research organizations, often in underserved areas is
forcing them to look at either a combined service provider and state owned network or a completely
state owned network where appropriate services are not offered.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 13
 1 Strategic Industries Market
1.5 The Strategic Industries Market: Enterprise market

The enterprise market comprises financial institutions, hotels digital

broadcast services

looking for cost effective feature rich network infrastructure

Typical services are transfer of data, front office applications, CCTV, VoD,
VoIP,…

Need simple and easy network management capabilities

1 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Large Enterprise customers are looking for cost effective, feature rich network infrastructure and
options to reduce their costs and gain the competitive edge. The Large Enterprise categories include
Financial Institutions, Hospitality, Enterprise (manufacturing, pharmaceuticals, SAN, etc.) and Digital
Video Broadcast. The enterprises that the IP Division's IP/MPLS products address are the multi-site
and campus type networks where high capacity, business critical voice, video and data traffic needs to
be cost effectively delivered. These networks often include the Enterprise Business Group's portfolio of
LAN switching products.
There are several key benefits for large enterprises when they own and operate their
telecommunications requirements. These include; a wider range of service options, direct control for
introducing beneficial services, reduction in monthly costs, and in some cases the opportunity to
generate revenue through resale of unused bandwidth.

Financial institutions usually have many geographically dispersed locations with requirements for
secure data transfer, administration activities, voice traffic, ABM machines, corporate video, etc.
Separate networks or services from the provider can add up to considerable costs. An IP/MPLS
network for some or all of the locations can be deployed to reduce those monthly costs by combining
the various types of traffic over a common infrastructure or set of leased services and support the
tremendous increase in high capacity applications. With guaranteed QoS assigned to each traffic type
(application, user, etc.) the concern of congestion affecting voice calls or critical data transfers is
alleviated.
Large enterprises such manufacturing, pharmaceuticals, and retail have an inherent need for cost
effectively managing their mission critical and business critical voice, data and video traffic. Whether in
a network of several locations or a campus environment, the need to ensure secure, reliable transfer of
data to/from the data centre, CCTV monitoring of the premises or production lines from a central point
and high quality voice for customer interactions, all point to the need for an IP/MPLS based solution.

Large hotels can often be viewed as a private company and service provider in one. They have
Copyright
considerable administrative activities © 2014 requiring
including Alcatel-Lucent. All Rightstransfer
the secure Reserved.
of data, front office
applications, CCTV, managementTER36055_V3.0-SG-R6.0-Ed1
of attached attractions Module
such 1.1casinos
as
Section 1 — Module 1 — Page 14
Edition N/A
but they also have the
requirement to provide voice, data and increasingly video services (triple play, VoD) to their customers
 1 Strategic Industries Market
1.6 The Strategic Industries Market: Defense and security

Need for a fully networked force is greater than ever

Effective command and control is essential

Built-in application awareness, traffic optimization and end-to-end

management boost overall mission effectiveness and flexibility.

1 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

The scope and nomenclature of the original Network Centric Warfare concept has evolved and been renamed by defense
departments around the globe. The need for a fully networked force is now greater than ever. Precise and current intelligence at
headquarters is essential for effective command and control, and the need for shared
situational awareness is arguably even more critical in a stabilization operation of a failed state than it is in a traditional combat
operation.
The Alcatel-Lucent Mission-critical WAN Infrastructure helps defense departments address these challenges with a
communications foundation that allows always-on communications to be securely shared among entities. The Alcatel-Lucent
Mission critical WAN Infrastructure cost-effectively expands into new areas, scaling bandwidth to
accommodate new applications that enhance mission effectiveness. Built-in application awareness, traffic optimization and end-
to-end management boost overall mission effectiveness and flexibility.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 15
 1 Strategic Industries Market
1.7 Knowledge check

What are typical requirements needed in the Strategic Industry market

(choose all that apply)?

a) High availability
b) Configurable QoS levels
c) Support for both mission-critical and non mission critical services
d) Support for legacy services

1 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Correct answer: a, b, c, d

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 16
 2 Alcatel-Lucent’s Solution and Key Features

1 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 17
 2 Alcatel-Lucent’s Solution and Key Features
2.1 Legacy versus a new IP/MPLS network

Legacy applications are still of great importance

Huge installed base

Ideal for mission-critical applications

BUT a legacy network is lacking

A cost effective common network infrastructure

Easy management network capabilities

Highly resilient network

Solution -> IP/MPLS in combination with legacy network!

Legacy and TDM analogue/digital applications will continue to exist and

need to be supported on new IP/MPLS networks

Examples of typical legacy network applications :

Router interconnect/backhaul

Land Mobile Radio (LMR)/Air Traffic Control air-ground radio interconnect/backhaul

Surveillance, Control and Data Acquisition (SCADA)

Teleprotection

Craft/maintenance voice communications

1 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Legacy and TDM networks have proven their usages in the strategic industry market. Both for mission-critical and
non mission-critical applications. Even today, they are of high importance. Legacy and TDM networks are
characterized by there own way of sending information between each other. TDM networks are typical connection
oriented services over a synchronized network. This is achieved by allocating dedicated time-slots to each user. But,
a legacy network is lacking a cost effective common network that is highly resilient and manageable.
The solution is the combination of the well know IP/MPLS infrastructure with a legacy network.

Examples of typical legacy network applications :

Router interconnect/backhaul

Land Mobile Radio (LMR)/Air Traffic Control air-ground radio interconnect/backhaul

Surveillance, Control and Data Acquisition (SCADA)

Teleprotection

Craft/maintenance voice communications

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 18
 2 Alcatel-Lucent’s Solution and Key Features
2.2 Typical legacy applications
Interface Description/Features Typical Applications
RS-232 •“Original” data interface •SCADA
•300bps  56kb/s speed •Radar data backhaul (ATC)
Data Interfaces

•Sync or async operation •Railway hot box detectors

•Full or half duplex operation •Teleprotection
•Railway signaling/control
V.35 •“High speed” serial interface •Router interconnect over TDM networks
•N x 64kb/s (typical max speed 2Mb/s)
•Synchronous, full duplex operation
X.21 •N x 64kb/s serial interface (max 2Mb/s) •Paging networks
•Synchronous, full duplex operation •Router interconnect
•Teleprotection
E&M •“Ear & Mouth” or “Earth & Magneto” •PBX interconnect
•2 wire or 4 wire options •Mobile radio base station interconnect
Voice Interfaces

•North American (µ-Law) and international •Teleprotection

(A-Law) voice encoding
FXS •Foreign Exchange – Station •Analog voice communications (telephone set –
•Analog interface to telephone set network)
•µ-Law & A-Law voice encoding
FXO •Foreign Exchange – Office •Analog voice communications (network –
•Analog interface to central office telephone set)
•µ-Law & A-Law voice encoding

1 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

This slide shows some typical legacy voice and data interfaces and their applications. These applications need
further support when renewing the network!

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 19
 2 Alcatel-Lucent’s Solution and Key Features
2.3 Strategic Industry Example: Utilities Network
Corporate HQ / NOC
Internet

Omni PCX SCADA

7705 SAR
7750 SR
5620 SAM

RTU
Power E&M
Generation ERP
TPR
LMR
IP/MPLS NOC

7705 SAR
Network

Substation
IED WiFi TDM Camera

Issues & Opportunities Value Proposition Differentiators & Credentials

• Need to reliable and support • Reliable and resilient support of • Deep corporate understanding of
crucial legacy services e.g. legacy and advanced services major strategic industry segments
SCADA, Teleprotection • All networking infrastructure • Compact and ‘green’ platforms
• Opportunity to modernize the models supported – point to point, • Non-stop services and resilient,
infrastructure for capacity and Layer 2 and 3 VPNs flexible topologies
more efficient operations
• Two-time winner of UTC: “Best
Telecom Equipment “ Award

1 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Crucial services like SCADA and Tele-protection need to be supported in a reliably way as
they are enormously crucial. Human life depends on these applications! At the same time,
the current infrastructure which has a long and proven life need to modernized. This is an
opportunity to install a modern, cost effective, easy manageable network infrastructure. This
network does need to support the current installed base of services and applications, but will
create an opportunity to deliver advanced new services an interfaces. Typical new advanced
services are point-to-point and point-to-multi-point L2 and L3 VPN type of services.
Alcatel-Lucent has a long and deep understanding of the major strategic industry markets
and knows the importance of a green, compact and cost-effective network.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 20
 2 Alcatel-Lucent’s Solution and Key Features
2.4 SR-OS on the Service Routing Platforms

7950 XRS
Terabit service routing
SR-OS

Service scaling and performance

High availability

Queuing
7750 SR 7450 ESS
Flexible forwarding

Services orientation

OA&M

Network management
7750 SR-c4 7705 SAR 7210 SAS
Timing/Synchronization
7750 SR-c12

Unified management
functional platforms

5620 5650 5670 5750

SAM CPA RAM SSC
1 — 1 — 21
M
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

The major SR-OS product families are the 7750 service router, the 7950 core router, the 7450 Ethernet
service switch, the 7705 service access router and the 7210 service access switch.
Each of the families are designed to deliver flexible and scalable networking solutions. Utilizing customized
interface options , field replaceable components and operational software. The portfolio includes service
routers and Ethernet service switches with a broad range of capacities. From 9 Gigabits per second for the
7750 SR-c4 up to 400 Gigabits per second for the 7750 SR-12.The complete portfolio is managed by the
5620 Service Aware Manager or SAM.

The superior functions and capabilities that differentiate our service routing platforms from a typical edge
and Internet router are the enormous service scale and performance, the high availability features like non-
stop routing and non-stop service, the huge queue buffer space available and the deep packet inspection
that allows a flexible way of forwarding.
The SR-OS products have a standard set of operation and maintenance tools allowing to troubleshoot on
MPLS, IP and service level.
Sync-E and 1588v2 are included as the standard for packet synchronization.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 21
 2 Alcatel-Lucent’s Solution and Key Features
2.5 Knowledge check

Choose the correct statement from the following options:

a) RS232, E&M and FXS/FXO are old interfaces and do not need to be
supported in a new modern network
b) An IP/MPLS platform is perfectly suite to support both legacy and new
ethernet/IP based services
c) The SR-OS product line has dedicated management platforms, each
product has his own management platform
d) The 7705 SAR is a brand new product line and has not been installed
in a customer premises today

1 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Correct answer: b

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 22
 3 The 7705 SAR

1 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 23
 3 The 7705 SAR
3.1 The 7705 SAR—an award-winning product line

• Optimally scaled platforms for efficient

aggregation and routing over any media to
reduce backhaul transport costs
• Built on the Service Router-OS for an extensive,
highly resilient and evolvable feature set
• Interface flexibility enables a seamless transition
from 2G/3G to 4G RAN and/or for legacy to
IP/Ethernet migration
• Strong QoS capabilities ensuring service-level
awareness and control
• Efficient creation & management of services via
the 5620 SAM management suite
• Multiple award-winning product portfolio

7705 SAR: First place winner of the

2009 ALU Corporate Quality Excellence Award

1 — 1 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

The Alcatel-Lucent 7705 Service Aggregation Router (SAR) is optimized for multiservice adaptation, aggregation
and routing, especially onto a modern, economical Ethernet and IP/MPLS infrastructure.
It is the platform mostly used in the strategic industry market.
It is part of the SR-OS IP/MPLS products which results in a highly resilient and evolvable feature set. It comes in
different sizes according to the need and scalability of the network. It has huge options to install different
interface cards. Because of the inheritance of features and software of other SR-OS products, it has strong QoS
capabilities ensuring service-level awareness and control.
It is no coincidence this is a multiple award-winning product.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 24
 3 The 7705 SAR
3.3 Extension of Service Routing Values

Continuing SR-OS Software

Technology Transfer

7750 Service Router 5620 SAM 7705 Service Aggregation Router

Extending best-of-breed IP/MPLS

The 7750 SR family: 3rd wave technology to the smaller sites and hubs
IP/MPLS services platform
Consistent, common features and

Huge industry traction in IP/MPLS operational practices end-to-end
network transformations
Rapidly evolvable and flexible

Extensive large scale experience with capabilities as needs change e.g. for
pseudowires as well as state-of-the- LTE
art routing, forwarding and switching
Consistent management/operations

Alcatel-Lucent continues to drive  Simple, powerful GUI-based OAM
standards and innovation  Recognized as benchmark in industry
 Powerful, Flexible Traffic Management
 Service assurance for SLA enforcement

1 — 1 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

It is of no doubt that the SR-OS IP/MPLS products have a long proven installed base by all the major telecom
operators worldwide. Alcatel-Lucent continues to drive the standards and innovations.
Based on what is learned and developed in the 7750 SR, there is a continuous software technology transfer from the
7x50 SR-OS service router towards the 7705 Service Aggregation Router or SAR.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 25
 3 The 7705 SAR
3.4 Continued Investment in the 7705 SAR Family
Enhancing options for Layer 3 aggregation and routing out to the smallest sites
MPLS LDP Prefix Aggregation,

Policy-Based Routing Epipe: Spoke-SDP Label

OSPF on VPRN PE-CE Interfaces R 6.0 Withdrawal Option, VPLS:

BGP Next-Hop-Self on Route Reflectors Spoke-SDP Label Withdrawal

BGP in Base Routing Option, LSR LDP ECMP, LDP

RIP Tree-Trace

IPv6 Support Enhancements R 5.0
•eBGP PE-CE
Further Utility & Resiliency •OSPF GR helper

R 4.0 •IPv6
Further Flexibility & Scale
•VPLS
•VPRN
•IES Fully LTE-ready with
•IP Tunnels R 3.0 any-to-any connectivity

Support for Hub sites and •OSPF

resilient architectures R 2.0 & 2.1 •FRR, RSVP-TE
•Full MPLS LSR
•IS-IS
•IP Filters
IP GRE tunneling R 1.1 •SRLG

•Static IP Forwarding
•BFD, R 1.0 Basic Forwarding Management and
•ECMP Signaling Support
•Basic LER
Enabling evolution of Aggregation and Routing Networks
1 — 1 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

The 7705 SAR has proven itself in customer networks all over the world. Each release adds features on top of the
previous one. The initial release supported the basic forwarding and management support. The latest release (6.0)
includes a rich set of features, as shown on the slide.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 26
 3 The 7705 SAR
3.5 Infrastructure and Networking Flexibility
Any G Backhaul

Aggregation & 1000s of protected

Ethernet, VPLS site connections
Backhaul
Synchronization
IP and IP VPN Flexibility

TDM
DS1/E1 End-to-End OAM

GE
ATM End-to-End Reliability
Any DSL
IP & MPLS
Serial data, E&M Microwave Networking Flexibility
7705 SAR
GPON Services Flexibility
Frame Relay Fixed/Mobile
OADM
CWDM IP & Optical
HDLC Networking
ANY ACCESS
Voice & CAPEX Optimized
Teleprotection Portfolio

ANY SCALE

1 — 1 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Any access and scale are two of the key important aspects of the 7705 SAR. It does not only provide Ethernet
connectivity as layer 2 access method, but also TDM, ATM, serial data, E&M, Frame Relay, HDLC and voice and
Tele-protection connectivity options.
On the aggregation side it has a variety of connection options like E1/DS1, any DSL flavor, Microwave, GPON,
CWDM and of course Gigabit Ethernet.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 27
 3 The 7705 SAR
3.6 Knowledge check

Choose the correct statement from the following options:

a) The 7705 SAR software has been designed with the intent to be
deployed only on 7705 SAR devices.
b) The 7705 SAR software is inherited from the 7x50 line of products.

1 — 1 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Correct answer: b.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 28
 4 End-to-End Service Management

1 — 1 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 29
4 End-to-End Service Management
4.1 Alcatel-Lucent 5620 Service Aware Manager
FEATURE BREADTH MANAGEMENT

Service-oriented management
 Service provisioning
Service management  Service alarms and state cause
 Service topology map
 Service assurance

Network-oriented management
 Physical topology maps
Network management  Network topology maps: tunnels,
LSPs (label switched path)
SAM-O
 Network commissioning: tunnels,
SAM-P SAM-A LSPs
SAM-E
Nodal-oriented management
Element management  Equipment inventory and configuration
 Alarm surveillance and policies

Integrated element + network + service management. Common across SR portfolio.

1 — 1 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

The SAM-E and SAM-P modules are standard, while SAM-O and SAM-A are optional
software modules.

SAM-A Alcatel-Lucent 5620 Service Aware Manager - Assurance

SAM-E Alcatel-Lucent 5620 Service Aware Manager - Element Management

SAM-O Alcatel-Lucent 5620 Service Aware Manager - OSS Interface

SAM-P Alcatel-Lucent 5620 Service Aware Manager - Provisioning

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 30
 4 End-to-End Service Management
4.2 Streamlined Service Provisioning with 5620 SAM

Policy-Based Provisioning

Policy-based configuration

Ingress/egress security rules

Ingress/egress QoS policy

Multicast policies

Accounting policy

L2 & L3 Service Activation

Point-and-click service activation

Traffic engineering

MPLS fast reroute for resiliency

SLA Simple service provisioning using wizards and

Comprehensive OAM toolkit
service templates to reduce complexity across

Service assurance across network SR/7705 nodes
elements

1 — 1 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

The 5620 SAM provides simple service provisioning using wizards and service templates to reduce
the complexity across SR-OS network elements (such as 7705 SAR, 7750 SR, and 7455 ESS).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 31
4 End-to-End Service Management
4.3 5650 CPAM Auto-OA&M and Conditional Testing

1 — 1 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 32
 4 End-to-End Service Management
4.4 Knowledge check

The 5620 SAM supports some of the following features—select all that
apply:

a) Service management
b) Network management
c) Element management
d) Policy based provisioning
e) L2/L3 service activation
f) SLA enforcement
g) Detect path changes and automatically triggers OAM tests

1 — 1 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Correct answer: a, b, c, d, e, f.

Note that all answers are correct except “g” because this feature is supported on the 5650 CPAM. The 5650 CPAM
is an optional but integrated part of the management platform.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 33
 5 Rapid Cell Deployment

1 — 1 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 34
 5 Rapid Cell Deployment
5.1 Importance of Rapid Cell Site Deployment

Cell sites often number in the thousands.

Typically — even for macro cells — footprints are being reduced, and cell
site density is increasing.

Installing a device in a cell site needs to be as simple as possible.

While deployment and commissioning efficiency is important anywhere in

the network, a simplification focus here can really save OPEX costs.

Focused OAM Innovation can Reduce OPEX

1 — 1 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Customers can have often a huge number of sites where 7705 SAR’s need to be installed. Doing on-site installation
should be done as quickly and easy as possible.
The rapid cell deployment feature offers a plug and play type of system which highly reduces operational expenditure
costs or OPEX.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 35
 5 Rapid Cell Deployment
5.2 Auto-Discovery & Provisioning (ADP)

Installing a device in a site needs to be as simple as possible:

During initialization, the 7705 SAR runs ADP

Discovery phase of the 7705 SAR is automatic

Pre-defined templates are applied to the 7705 SAR

Gig Metro Ethernet Gig

E E
7705 SAR
7750SR

1 7705 ADP Advertisement Protocol 7750

2 7705 Initial Configuration 7750 + 5620

3 7705 Discovery of the node by 5620 5620

1 — 1 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Hardware
ADP support on any a8-ethv1 & v2 port
ADP support on any a8-ethv3 port

Self Discovery
Bring up primary CSM
Bring up standby CSM and synch their ADP state
Bring up line card or cards
Bring up ports on which ADP can operate

NW Discovery
Send dhcp-discovery packets from all ADP supported & up ports
Ability to understand and make use of following fields under option-67 of dhcp_offer
-> System-address, System-name, System-location, Configuration to use (ftp url), BOF command(s)

ADP Modes
ADP to kick-in with uninterrupted first boot (on both SAR-8 & SAR-F nodes) - Default
ADP to turn itself off automatically upon successful completion (i.e. system-ip assignment)
Option to enable/disable ADP via cli/snmp
Option to enable/disable ADP via interrupting boot-up (i.e. bootloader interactive session)
Co-existence of CLI Sessions once NW ip address is assigned (ssh in default config)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 36
 5 Rapid Cell Deployment
5.3 Knowledge check

The rapid cell deployment of a device in a site is as simple as possible,

and includes the following steps, except one (select all that apply):

a) During initialization, the 7705 SAR runs ADP.

b) The 5620 SAM discovers the 7705 SAR network elements
automatically.
c) The 7705 SAR sends Connectivity Fault Management messages to its
peers.
d) Pre-defined templates are applied to the 7705 SAR.

1 — 1 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Correct answer: a, b, d.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 37
 6 Summary

1 — 1 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 38
 6 Summary
6.1 Continuing Success of the 7705 SAR

• Ethernet and IP/MPLS infrastructure over any media

Technology • Non-stop services and resilient, flexible topologies
Leadership • Flexible, accurate synchronization
• Compact and ‘green’ platforms

Extensive • Over 165 customers

Customer • Installations in 40+ countries worldwide
• Transformation and Leverage
Base • From legacy services: 2G, 3G to fully routed and LTE

Service • Wireless mobile aggregation and backhaul

• Strategic Industries e.g., transport, utilities, government
Breadth • Business services, legacy to packet evolution

Market • Over 100,000 units shipped since launch in May 2008

• Multi-award winning product line
Impact • Leading role in LTE trials worldwide

1 — 1 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

The continuing success of the 7705 SAR stems from the following factors:

Technology Leadership

Extensive Customer Base

Service Breadth

Market Impact

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 39
End of module
Strategic Industries Solution Overview

1 — 1 — 40 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Strategic Industries Overview — Strategic Industries Solution Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 1.1 Edition N/A
Section 1 — Module 1 — Page 40
Learning experience powered by
Alcatel-Lucent University

Section 2
Internal Routing Protocol
Module 1
Link State Protocols Overview
TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

2—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 1
 Blank page

2—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 2013-06-14 Gallardo, Jose R. First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 2
Module objectives

• Upon completion of this module, you should be able to:

Identify the information exchanged by routers running a link-state routing

protocol and the messages utilized with that purpose

Explain how routers utilize that information to find the best routes to
forward packets to their destinations

Describe the optimizations introduced to reduce the complexity of the
algorithm used to calculate shortest paths

List the databases maintained by routers running a link-state routing
protocol

2—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 3
Module objectives [cont.]

2—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 4
 Table of Contents

1 Overview of Link-State Routing Protocols 7

Page

1 Overview of Link-State Routing Protocols 7

1.1 Overview of Link-State Routing Protocols 8
1.2 Overview of Link-State Routing Protocols (continued) 9
1.3 Overview of Link-State Routing Protocols (continued) 10
1.4 Overview of Link-State Routing Protocols – Example 11
1.5 Optimizations 12
1.6 Optimizations - Areas 13
1.7 Optimizations - Designated Routers 14
1.8 Optimizations - Designated Routers (continued) 15
1.9 Protocol messages 16
1.10 Databases 17
1.11 Module summary 18

2—1—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 5
Table of Contents [cont.]

2—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 6
 1 Overview of Link-State Routing Protocols

2—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 7
1 Overview of Link-State Routing Protocols
1.1 Overview of Link-State Routing Protocols

• Routers running a link-state protocol share detailed topology and IPv4

reachability information with each other
• Each router is responsible for describing the topology and IP
reachability in its own neighborhood, including:

Other routers to which it is connected

The characteristics of the links that connect it to other routers: point-to-
point or broadcast, the cost of using the link (metric)

IPv4 sub-networks directly attached to it, and the cost (link metric) to send
packets to them

IPv4 sub-networks that are external to the routing domain (which have
been discovered because the router is running an additional routing
protocol), and the cost to send packets to them

2—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 8
 1 Overview of Link-State Routing Protocols
1.2 Overview of Link-State Routing Protocols (continued)

Example of topology and IP reachability information being advertised:

Advertising router: Router A

Topology

Neighboring routers:
• Router B via a ptp link with cost 100
• Router C via a ptp link with cost 100
Internal reachable IP sub-networks:
IP Reachability

• 10.10.10.1/32 cost 0
• 10.1.25.0/24 cost 100
• 10.1.24.0/28 cost 100
• 10.1.23.0/28 cost 100
External reachable IP sub-networks: 10.1.25.0/24
• 20.20.20.0/24 cost 300
A B
Point-to-point
System IP Address
10.10.10.1/32 10.1.23.0/28

Point-to-point
External Routing 10.1.24.0/28
Domain
20.20.20.0/24 C

2—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Router IDs A, B, and C are not IP addresses. They are part of the topology information, not of the IP
reachability information.

A Router ID is 32-bit identifier. IS-IS uses an additional identifier known as system ID, which is a 48-bit
identifier.

Interfaces interconnecting routers usually do not need global unicast addresses assigned to them; they are
shown in this figure only to enrich the example.

Information about link-local IP addresses is not flooded throughout the routing domain.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 9
 1 Overview of Link-State Routing Protocols
1.3 Overview of Link-State Routing Protocols (continued)

• A message is generated by each router to advertise the local

information, and it is flooded so that all routers can get a copy of it
• When every router has generated such an advertisement and copies
have been flooded, each router has visibility of detailed topology and IP
reachability information of the entire routing domain
• Such information is then used by each router to independently calculate
the shortest path to any subnetwork identified by an IPv4 prefix
• The algorithm used to calculate shortest paths is known as:

Shortest Path First - SPF

Also known as the Dijkstra’s algorithm
• Flooding of topology information is done reliably, using numbered
advertisements and acknowledgments, to make sure databases are
identical and routing decisions are consistent among routers

2 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

The topology information may be flooded throughout the entire routing domain or, if the routing domain is
sub-divided into smaller areas (as will be explained shortly), the topology information will only be flooded
within the area where the advertising router is located.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 10
 1 Overview of Link-State Routing Protocols
1.4 Overview of Link-State Routing Protocols – Example

1. Initially, router A only knows about A B

its directly attached IP sub-networks

2. By establishing adjacencies, it
discovers its immediate neighbors
C D

3. After exchanging Link-State

Advertisements, it gets the entire Hello Message
Link-State Advertisement
topology and IP reachability
information

4. Using that information, it runs the 5. It stores calculated next hops for
SPF algorithm to calculate the known prefixes in the route table
shortest path tree with itself as the Dest Address Next Hop Type Metric
root 10.10.10.1/32 System Local 0
10.10.10.2/32 Interface toB ProtX 100
10.10.10.3/32 Interface toC ProtX 100
10.10.10.4/32 Interface toC ProtX 200

2 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

To establish adjacencies, as mentioned in step 2 above, Hello messages are enough for IS-IS. For OSPF,
routers additionally need to synchronize their link-state databases.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 11
1 Overview of Link-State Routing Protocols
1.5 Optimizations

• The complexity of the SPF algorithm increases with the number of links
present in the network
• Two optimizations were introduced to reduce this complexity and to
decrease the convergence time:

Breaking the entire routing domain into smaller areas

Electing a designated router on broadcast interfaces

2 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 12
1 Overview of Link-State Routing Protocols
1.6 Optimizations - Areas

• When the routing domain is sub-divided into areas:

Detailed topology and IP reachability information is only shared among
routers within the same area

Some routers will act as gateways between areas so that packets can still
be routed throughout the routing domain, but only IP reachability
information will be shared between areas, not topology information

The hierarchy that is needed (area-internal routers with limited knowledge
and gateway routers with additional knowledge) is handled differently in
OSPFv2 and IS-IS, both of which are link-state routing protocols

2 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 13
1 Overview of Link-State Routing Protocols
1.7 Optimizations - Designated Routers

• On a broadcast link, which can have more than two routers connected
to it, there may be a large number of logical connections
• Each of these logical connections needs to be considered separately by
the SPF algorithm during the process to find shortest paths

Physical connection
Logical connections

2 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 14
 1 Overview of Link-State Routing Protocols
1.8 Optimizations - Designated Routers (continued)

• To reduce the number of logical connections that need to be advertised

and evaluated by SPF, a designated router will be elected
• The designated router will then act as if it were two separate routers:
the actual one and a pseudo-node that is added to the topology
• The number of routers grows by one, but the number of logical
connections is reduced

Routers only form adjacencies with

the designated router, which also
reduces the protocol complexity

Designated router

Logical connections

2 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

The designated router is called designated intermediate system in IS-IS, but the concept is identical.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 15
1 Overview of Link-State Routing Protocols
1.9 Protocol messages

• Link-state protocols use different types of messages:

Hello messages, used to discover neighboring routers and to assess if they
are compatible to establish an adjacency (e.g. sitting in the same area,
matching authentication, etc.)

Link-state advertisements

Messages to exchange advertisements reliably (database description,
advertisement requests and advertisement acknowledgments), so that
link-state databases can be effectively synchronized

2 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 16
1 Overview of Link-State Routing Protocols
1.10 Databases

• Routers running a link-state protocol maintain three databases:

Adjacency database: includes the neighboring routers

Link-state database: includes topology and IP reachability information

Forwarding database: includes the next hop for each known IP prefix,
corresponding to the calculated shortest path

2 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 17
1 Overview of Link-State Routing Protocols
1.11 Module summary

• Routers running a link-state routing protocol exchange detailed

topology and IP reachability information
• They utilize that information to calculate the shortest path to any
subnetwork identified by an IPv4 prefix
• The algorithm used to calculate shortest paths is known as Shortest
Path First (SPF) or Dijkstra’s algorithm
• Two optimizations are introduced to reduce the complexity of the SPF
algorithm: sub-dividing the network into areas, and electing designated
routers on broadcast links
• Several message types are used by these protocols: Hello, link-state
advertisements, and messages to exchange advertisements reliably
• Any router running a link-state routing protocol will maintain three
databases: Adjacency, Link-state, and Forwarding databases

2 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 18
References

2 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 19
End of module
Link State Protocols Overview

2 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — Link State Protocols Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.1 Edition N/A
Section 2 — Module 1 — Page 20
Learning experience powered by
Alcatel-Lucent University

Section 2
Internal Routing Protocol
Module 2
OSPF
TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

2—2—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 1
 Blank page

2—2—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries This page is left blank intentionally

Document History

Edition Date Author Remarks

01 2013-06-14 Gallardo, Jose R. First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 2
Module objectives

• Upon completion of this module, you should be able to:

List the different message types used by OSPF

Explain the different OSPF states in an adjacency and the transition
conditions between states

Describe the different Link-State Advertisement (LSA) types used by OSPF
and the information carried by them

Explain how OSPF handles the hierarchy that is needed when the routing
domain is sub-divided into areas (area-internal routers with limited
knowledge and gateway routers with additional knowledge)

Identify the different area types that can be configured in OSPF and the
constraints imposed by them

Identify the commands that can be used to configure and verify OSPF

2—2—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 3
Module objectives [cont.]

2—2—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 4
 Table of Contents

1 OSPFv2 Overview 7
Page
2 LSA Types 23
1 OSPFv2 Overview 7
3 OSPF
1.1 CaseOverview Study – Single Area 8 27
1.2 Hello Messages 9
4 Database
1.3 Adjacency Descriptionon Point-to-Point
Message link 11 33
1.4 Link-State Request Message 12
5 Link-State
1.5 Adjacency Update on Messages
Broadcast link 13 41
1.6
6 Link-State
Link-State Acknowledgment
Database Messages 14 47
1.7 OSPF Adjacency States 15
1.8
7 OSPFCaseAdjacency Study – States – Common
Multiple AreasProblems 16 56
1.9 Link Metric 17
8 Link-State
1.10 Multicast Addresses Databases
Reserved for OSPF 18 62
1.11 Area Border Routers 19
9 AAutonomous
1.12 Slightly Different Scenario
System Border Routers 20 71
1.13 OSPF Area Types 21
10OSPF
1.14 OSPFArea Multi-Area Adjacency on a Single
Types (continued) Link 22 77
2 LSA Types 23
11LSA
2.1 OSPF Types Authentication 24 84
2.2 LSA Types and Their Flooding Scopes 25
3 Case Study – Single Area 27
3.1 Topology of Reference 28
3.2 Router configuration – R1 29
3.32 —Router
2—5
configuration – R2 30
3.4Internal
Router configuration
Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries
– R3COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
31
3.5 Router configuration – R4 32
4 Adjacency on Point-to-Point link 33
4.1 Adjacency on Point-to-Point link 34
4.2 Adjacency verification 40
5 Adjacency on Broadcast link 41
5.1 Adjacency on Broadcast link 42
5.2 Adjacency verification 46
6 Link-State Database 47
6.1 Link-State Database 48
6.2 LSAs advertised by R1 49
6.3 LSAs advertised by R2 50
6.4 LSAs advertised by R3 52
6.5 LSAs advertised by R4 53
6.6 Route table 55
7 Case Study – Multiple Areas 56
7.1 Topology of Reference 1 57
7.2 Router configuration – R1 58
7.3 Router configuration – R2 59
7.4 Router configuration – R3 60
7.5 Router configuration – R4 61
8 Link-State Databases 62
8.1 Link-State Database for Area 1 63
8.2 LSAs advertised by R2 64
8.3 Link-State Database for Area 3 66
8.4 LSAs advertised by R2 67
8.5 Link-State Database for Area 4 68
8.6 LSAs advertised by R2 69
9 A Slightly Different Scenario 71
9.1 Topology of Reference 2 72
9.2 OSPFv2 configuration on R2 73
9.3 OSPFv2 configuration on R4 74
9.4 Link-State Database for Area 4 75

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 5
 Table of Contents [cont.]

Page

9.5 LSAs advertised by R2 76

10 OSPF Multi-Area Adjacency on a Single Link 77
10.1 OSPF Multi-Area Adjacency on a Single Link 78
10.2 OSPF Multi-Area Adjacency on a Single Link – Motivation 79
10.3 OSPF Multi-Area Adjacency on a Single Link – Application 80
10.4 Verification 81
10.5 End result 83
11 OSPF Authentication 84
11.1 OSPF Authentication 85
11.2 OSPF Configuration 86
11.3 OSPF Authentication – Messages 87
11.4 Lab 5 – OSPF 88
11.5 Module summary 89

2—2—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 6
 1 OSPFv2 Overview

2—2—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 7
1 OSPF Overview
1.1 OSPF Overview

• OSPF is a link-state routing protocol that enables routers to exchange

detailed topology and IPv4 reachability information

Topology and IPv4 reachability information is packaged inside Link-State
Advertisements (LSAs)
• Such information can be used to calculate the shortest path to any
subnetwork identified by an IPv4 prefix
• OSPF uses five different packet types

Hello

Database Description

Link-State Request

Link-State Update

Link-State Acknowledgment

2—2—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 8
 1 OSPF Overview
1.2 Hello Messages

• Sent periodically on physical interfaces where OSPF is enabled

• Used to discover neighboring routers, to assess if they are compatible
to establish an adjacency, to elect the designated router on broadcast
links, and as keep-alive after an adjacency has been formed
• To establish an adjacency, the following parameters in the Hello
message need to be compatible:

The interfaces on both routers need to belong to the same area

The area type must be the same (normal, stub or not-so-stubby)

Authentication information must match (if any, at the interface/global level)

Hello and dead intervals (how often Hello messages are expected and
maximum time allowed without receiving one, respectively) must be the
same

OSPF supports multiple protocol instances per link, thus the instance ID must
also match

2—2—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Area types (normal, stub or not-so-stubby) will be explained shortly.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 9
 1 OSPF Overview
1.2 Hello Messages [cont.]

• Hello messages also carry a priority value that helps determine which
router in a broadcast link will be elected as the designated router (DR)

If there is a tie in the DR election based on priority, it is broken by the
highest router ID
• As neighbors are discovered, their router IDs will be added to the list of
neighbors advertised in the Hello messages
• Once the DR/BDR have been elected, their corresponding router IDs will
be advertised as well

A new router that becomes active on the link after the DR/BDR election has
passed will not try to run another election, but will honor the existing
DR/BDR (non-preemptive)

2 — 2 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

The router ID is a 32-bit unique identifier.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 10
 1 OSPF Overview
1.3 Database Description Message

• After compatibility has been established, Database Description (DBD)

messages are used to describe the contents of the local link-state
database in a condensed manner
• Useful for routers to realize what information is missing for databases
to be synchronized
• DBD messages also carry the maximum packet size allowed on the
interface (maximum transfer unit – MTU)

The initial DBD messages are used to establish whether MTU sizes are
compatible – last compatibility test
• DBD messages are exchanged reliably using a master-slave approach

Messages sent by the master serve to carry data and to poll the slave

Messages sent by the slave serve to carry data and to acknowledge receipt
of data received from the master

The initial DBD messages are also used to identify master and slave

2 — 2 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

The master-slave relationship that is established between the two routers is a clever way of accomplishing a
reliable transfer of DBD messages without the need to introduce additional acknowledgment messages.

It works as a polling mechanism in the sense that when the master sends a DBD message with a certain sequence
number, the slave must send back a DBD message with the same sequence number. The master increases the
sequence number after each exchange.

For the slave, receiving a DBD message means useful information coming from the master and, at the same time,
it is an opportunity to send a DBD message to describe its own database. If the database description does not fit
within a single packet due to MTU limitations, the slave will indicate it with a flag known as the MORE bit, which
will tell the master that additional polls are required to allow the slave to finish describing its database. Even
when the slave does not have any more information to send, it will respond to a DBD message received from the
master with an empty DBD message.

For the master, receiving a DBD message means useful information coming from the slave and, at the same time,
an acknowledgment that its own information previously sent was successfully received by the slave. If a response
is not received within a certain time, the master will resend the DBD message.

The router with the highest router ID becomes the master.

DBD messages are transmitted using unicast addressing, meaning that the link-local unicast address of the
neighbor is used as the destination IP address within the IPv4 header.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 11
1 OSPF Overview
1.4 Link-State Request Message

• After each router has described the contents of its own link-state
database, Link-State Request messages are used to ask for the
information that is missing for the databases to become synchronized
• As mentioned before, the topology and IPv4 reachability information
that is to be shared among routers is packaged inside Link-State
Advertisements (LSAs)
• A single Link-State Request message can be used to request multiple
LSAs that the other router has but this router is missing

2 — 2 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 12
1 OSPF Overview
1.5 Link-State Update Messages

• A Link-State Update message is used to transfer one or more LSAs from

one router to another
• A Link-State Update message can be transmitted in two cases:

As a result of a request received during database synchronization, or

Whenever the topology changes and the new information is being flooded
throughout the network

2 — 2 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 13
1 OSPF Overview
1.6 Link-State Acknowledgment Messages

• Whenever a router receives an LSA (inside an LSU message), it needs to

send back an Link-State Acknowledgment message as part of the
reliable transfer of information
• Each LSA received must be explicitly acknowledged
• Multiple LSAs can be acknowledged within the same Link-State
Acknowledgment message

2 — 2 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 14
 1 OSPF Overview
1.7 OSPF Adjacency States

• The 7 states to establish an adjacency between two routers are:

Down – neighbor has not been discovered

Initializing – one-way communication has been verified via Hello messages

2-way – two-way communication has been verified via Hello messages

Exstart – MTU compatibility is being verified via DBD messages

Exchange – database description (LSA list) being exchanged via DBD messages

Loading – exchanging LSAs

Full – link-state databases fully synchronized

• On a broadcast link, routers will only establish a full adjacency with the
DR and the BDR: routers other than DR/BDR will remain in the 2-way
state with each other

2 — 2 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

The 7 states to fulfill adjacency between two routers are:

• Down – neighbor has not been discovered: no Hello messages have been received from neighbor yet

• Initializing – one-way communication has been verified: Hello messages have been received from neighbor,
but the neighbor list in the Hello messages does not include the local router ID (I can see him, but I do not
know if he can see me)
To exchange Hello messages successfully, routers must be compatible in the sense that they have to be
located in the same area, the area type has to be the same, the Hello and Dead intervals have to be the
same, and they have to be properly authenticated
• 2-way – two-way communication has been verified: Hello messages have been received from neighbor, and
the local router ID is included in the neighbor list contained in Hello messages (I can see him and he can see
me); on a broadcast link, routers remain in the 2-way state for 40 seconds to allow for more routers to be
discovered and, at the end, run the DR/BDR election including all of the routers that have been discovered
• Exstart – MTU compatibility being verified: empty DBD messages are exchanged, MTU sizes are checked for
compatibility
• Exchange – database description (LSA list) being exchanged: DBD messages with useful information are being
exchanged to describe the contents of the link-state databases (equivalent to a library catalog)
• Loading – exchanging LSAs: not only a list of LSAs, but the LSAs themselves are being exchanged to make sure
that both routers end up having the same information
• Full – link-state databases are fully synchronized

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 15
 1 OSPF Overview
1.8 OSPF Adjacency States – Common Problems

• OSPF Adjacency States:

Down If adjacency is stuck here, some parameters are not compatible
(area, area type, authentication, Hello and dead interval, etc)

Initializing
If adjacency is stuck here, interface types are

2-way not compatible (point-to-point vs broadcast)

Exstart If adjacency is stuck here,
there is an MTU mismatch

Exchange

Loading

Full

2 — 2 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

If routers cannot see each other (remain in the Down state) even if they are physically connected, the most likely
cause is that some parameters exchanged in the Hello message are not compatible (area, area type,
authentication, Hello and dead interval, etc).

If one router gets stuck in the Init state, while the other is in the Down state, the most likely problem is that
interface types are not compatible (point-to-point vs broadcast). The router on the broadcast side expects for a
DR/BDR election to be run, but the router on the point-to-point side will not participate (it will never include the
DR/BDR router IDs in its Hello messages). Eventually, the router on the broadcast side gives up after realizing
that the adjacency will not work and goes back to the Down state. The router on the point-to-point side, on the
other side, will continue to receive Hello messages from the other router, so it will remain in the Init state.

If routers get stuck in the Exstart or Exchange state, the most likely cause is an MTU mismatch.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 16
1 OSPF Overview
1.9 Link Metric

• In link-state protocols, the shortest path is defined as the one for which
the sum of link costs is minimum
• The default metric in OSPF assigns a cost to all links according to the
following equation:
link cost = reference bandwidth ÷ link bandwidth

• The default reference bandwidth is 100 Gbps, or 100,000,000 Kbps

• Link cost is configurable in two ways:

By directly setting a value
Example: config router ospf area 0 interface "toR2" metric 500

By specifying a different reference bandwidth

Example: configure router ospf reference-bandwidth 200000000

2 — 2 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 17
 1 OSPF Overview
1.10 Multicast Addresses Reserved for OSPF

• OSPFv2 routers use IPv4 multicast addresses to communicate with each

other
• The following are multicast addresses reserved for OSPF:

224.0.0.5 - All OSPF routers on the segment

224.0.0.6 - All OSPF DR/BDR routers on the segment
• Respective multicast MAC addresses:

224.0.0.5 – 01:00:5E:00:00:05

224.0.0.6 – 01:00:5E:00:00:06

2 — 2 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

In addition to a designated router (DR) elected on each broadcast interface, OSPF also elects a backup designated
router (BDR), which collects the same information and establishes the same adjacencies as the DR, and is thus
ready to take over if the DR fails.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 18
1 OSPF Overview
1.11 Area Border Routers

• An OSPF routing domain can be sub-divided into two or more areas

• An Area Border Router (ABR) is a router that participates in two or more
areas

An ABR has some interfaces that belong to an OSPF area and some other
interfaces that belong to a different area
• ABRs have the additional responsibility of sharing their knowledge of
IPv4 sub-networks that exist in one area into the other
• In every OSPF routing domain, there must be a backbone area with
area-ID equal to 0.0.0.0
• All other areas must be adjacent to the backbone area in the sense that
there has to be an ABR that participates both in the backbone and in
the non-backbone area

2 — 2 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 19
1 OSPF Overview
1.12 Autonomous System Border Routers

• In addition to advertising IPv4 sub-networks directly attached to it, a

router may want to advertise sub-networks that are external to the
OSPF routing domain
• A sub-networks is considered external if the router knows about it
because it is running an additional routing protocol besides OSPF or two
separate instances of OSPF
• A router that advertises external IP sub-networks is known as
Autonomous System Border Router (ASBR)

2 — 2 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 20
 1 OSPF Overview
1.13 OSPF Area Types

• There are different area types:

Normal area: routers inside want to know explicitly about every IP sub-
network, either within the OSPF domain or external (the backbone area is
always normal)

Stub area: routers inside want to know about IP sub-networks within the
OSPF domain, but not about external IP sub-networks

Stub area with no summaries (totally stubby): routers inside want to know
only about OSPF sub-networks within the same area, but not about OSPF sub-
networks in other areas or about external sub-networks

Not-so-stubby area (NSSA): routers inside want to know explicitly about
every sub-network within the OSPF domain and about external sub-networks
as long as they are advertised by a router within the same OSPF area

NSSA area with no summaries (totally NSSA): similar to a totally stubby
area, but additionally routers inside want to know explicitly about external
sub-networks as long as they are advertised by a router within the same
OSPF area

2 — 2 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

There are different area types:

Normal area: area in which routers want to have explicit entries in their routing table for every network, either
within the OSPF domain or external (the backbone area is always normal)

Stub area: area in which routers want to know explicitly about every network within the OSPF domain, but not
about external networks; they rely on area-border routers (ABRs) to reach external networks by means of a
default route installed in the routing table pointing to an ABR

Stub area with no summaries (totally stubby): area in which routers want to know explicitly only about
networks directly attached to routers within the same OSPF area, but not about OSPF networks in other areas or
about external networks; they rely on ABRs to reach unknown networks by means of a default route installed in
the routing table pointing to an ABR

Not-so-stubby area (NSSA): area in which routers want to know explicitly about every network within the OSPF
domain and about external networks as long as they are advertised by a router in the same OSPF area; they can
rely on an ABR or on the ASBR (AS-border router – the router advertising external networks) to reach unknown
networks by means of a default route installed in the routing table; default route injection needs to be manually
configured either at the ABR or the ASBR (originate-default-route command)

NSSA area with no summaries (totally NSSA): similar to a totally stubby area, but additionally routers want to
know explicitly about external networks as long as they are advertised by an ASBR in the same OSPF area; they
can rely on an ABR or on the ASBR to reach unknown networks by means of a default route installed in the routing
table; default route injection needs to be manually configured either at the ABR or the ASBR (originate-default-
route command)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 21
1 OSPF Overview
1.14 OSPF Area Types (continued)

• Routers within an area other than Normal rely on ABRs or ASBRs to

reach unknown IP sub-networks by means of a default route installed in
their routing table
• The default route is injected by ABRs automatically in stub and totally
stubby areas, but needs manual configuration in NSSA and totally NSSA
areas
• In an NSSA and in a totally NSSA area one can choose if the default
route will be injected by the ABRs or by the ASBRs

2 — 2 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 22
 2 LSA Types

2 — 2 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 23
2 LSA Types
2.1 LSA Types
LSA LSA
Description
Type Name
Flooded by every router, describing directly attached links with IP Prefix
1 Router
and Mask. This LSA type does not leave the area it was originated.
Sent by the DR of a broadcast link, describing neighboring routers as seen
2 Network
by the pseudo node; link metric is always zero.
Network Sent by ABRs, to advertise networks in one area to another. One LSA is
3
Summary generated for every known network, and it is sent to all areas in the AS.
ASBR Flooded by ABRs, throughout the AS and is used to advertise the location
4
Summary of the ASBR.
AS- Sent by ASBRs throughout the AS in order to advertise networks from
5
External other Autonomous Systems.
NSSA Sent by ASBRs in an NSSA area, describing sub-networks that exist in
7
External another AS and the cost to reach them.

2 — 2 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 24
2 LSA Types
2.2 LSA Types and Their Flooding Scopes

• Different LSA types have different flooding scopes

Area scope: to be flooded to all routers participating in a given area; not to
be propagated by ABRs into other areas

Routing domain scope: to be flooded to all routers participating in the
same OSPF Autonomous System; it is to be propagated by ABRs into other
areas

2 — 2 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 25
 2 LSA Types
2.2 LSA Types and Their Flooding Scopes [cont.]

• Area scope:

Router LSA

Network LSA

Network Summary LSA

ASBR Summary

NSSA LSA
• Routing domain scope: The information included in these LSAs can cross area
borders, but new LSAs need to be generated by ABRs to

AS External LSA share the information with routers in other areas

2 — 2 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

The information included in these LSAs can cross area borders, but new LSAs need to be generated by ABRs to
share the information with routers in other areas.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 26
 3 Case Study – Single Area

2 — 2 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 27
3 Case Study – Single Area
3.1 Topology of Reference

Router System IP
Name Address
R1 10.10.10.1/32
R2 10.10.10.2/32
R3 10.10.10.3/32
R4 10.10.10.4/32
External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

Broadcast
R4 10.1.24.0/28

2 — 2 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 28
 3 Case Study – Single Area
3.2 Router configuration – R1
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system“
address 10.10.10.1/32
no shutdown
exit
interface "toR2"
port 1/1/2
address 10.1.12.1/28
no shutdown
exit
router-id 10.10.10.1
#------------------------------------------
echo "OSPF Configuration"
#------------------------------------------
ospf
area 0.0.0.0
interface "system"
interface-type point-to-point
no shutdown
External Routing
exit Domain
interface "toR2" 20.20.20.0/24
interface-type point-to-point
no shutdown
exit
exit
exit
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

Broadcast
R4 10.1.24.0/28

2 — 2 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Note that interface toR2 is assigned a link-local addresses to talk to each other. It is included here to enrich the
example and to show how they are advertised inside LSAs.

Note also that interface toR2 is configured inside OSPF as point-to-point.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 29
 3 Case Study – Single Area
3.3 Router configuration – R2
#------------------------------------------ #------------------------------------------
echo "IP Configuration" echo "OSPF Configuration"
#------------------------------------------ #------------------------------------------
interface "loop1" ospf
loopback asbr
address 20.20.20.1/32 export "from-direct-to-ospf"
no shutdown area 0.0.0.0
exit interface "system"
interface "system" interface-type point-to-point
address 10.10.10.2/32 no shutdown
no shutdown exit
exit interface "toR1"
interface "toR1" interface-type point-to-point
port 1/1/2 no shutdown
address 10.1.12.2/28 exit
no shutdown interface "toR3"
exit interface-type point-to-point
interface "toR3" no shutdown
port 1/1/3 exit
address 10.1.23.2/28
no shutdown
interface "toR4"
no shutdown
External Routing
exit exit Domain
interface "toR4" exit 20.20.20.0/24
port 1/1/1 exit
address 10.1.24.2/28
no shutdown
exit
router-id 10.10.10.2
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

Broadcast
R4 10.1.24.0/28

2 — 2 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

In the configuration excerpts above, we can see R2’s interfaces to all its directly connected neighbors. They are
included here to enrich the example and to show how they are advertised inside LSAs.

Also, you may note that interfaces “toR1” and “toR3” are configured inside OSPF as point-to-point interface
types, while interface toR4 is configured inside OSPF as broadcast (default, if no type is specified).
Lastly, interface loop1 plays the role of an external network that is advertised into OSPF by R2 (which becomes
an ASBR) via an export policy. The export policy is shown below:
#--------------------------------------------------
echo "Policy Configuration"
#--------------------------------------------------
policy-options
begin
prefix-list "only-loop1"
prefix 20.20.20.0/24 longer
exit
policy-statement "from-direct-to-ospf"
entry 10
from
protocol direct
prefix-list "only-loop1"
exit
to
protocol ospf
exit
action accept
exit
exit
exit
commit
exit

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 30
3 Case Study – Single Area
3.4 Router configuration – R3
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.3/32
no shutdown
exit
interface "toR2"
port 1/1/3
address 10.1.23.3/28
no shutdown
exit
router-id 10.10.10.3
#------------------------------------------
echo "OSPF Configuration"
#------------------------------------------
ospf
area 0.0.0.0
interface "system"
interface-type point-to-point
no shutdown
External Routing
exit Domain
interface "toR2" 20.20.20.0/24
interface-type point-to-point
no shutdown
exit
exit
exit
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

Broadcast
R4 10.1.24.0/28

2 — 2 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 31
 3 Case Study – Single Area
3.5 Router configuration – R4
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.4/32
no shutdown
exit
interface "toR2"
port 1/1/1
address 10.1.24.4/28
no shutdown
exit
router-id 10.10.10.4
#------------------------------------------
echo "OSPF Configuration"
#------------------------------------------
ospf
area 0.0.0.0
interface "system"
interface-type point-to-point
no shutdown
External Routing
exit Domain
interface "toR2" 20.20.20.0/24
no shutdown
exit
exit
exit
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

Broadcast
R4 10.1.24.0/28

2 — 2 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Note that interface “toR2” is configured inside OSPF as broadcast (default).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 32
 4 Adjacency on Point-to-Point link

2 — 2 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 33
4 Adjacency on Point-to-Point link
4.1 Adjacency on Point-to-Point link

• After these Hello messages, routers R1 and R2 move to the Init state

119 2014/05/06 17:41:14.58 CEST MINOR: DEBUG 118 2014/05/06 17:41:05.18 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT

>> Outgoing OSPF packet on I/F to-R2 >> Outgoing OSPF packet on I/F to-R1
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.1 Router Id : 10.10.10.2
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : e7a3 Checksum : e7a2
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : HELLO Packet Type : HELLO
Packet Length : 44 Packet Length : 44

Network Mask : 255.255.255.240 Network Mask : 255.255.255.240

Hello Interval : 10 Hello Interval : 10
Options : 02 -------E-- Options : 02 -------E--
Rtr Priority : 1 Rtr Priority : 1
Dead Interval : 40 Dead Interval : 40
Designated Router : 0.0.0.0 Designated Router : 0.0.0.0
Backup Router : 0.0.0.0 Backup Router : 0.0.0.0
" "

Empty list of neighbors Empty list of neighbors

R1 R2
Point-to-point
10.1.12.0/28

2 — 2 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 34
4 Adjacency on Point-to-Point link
4.1 Adjacency on Point-to-Point link [cont.]

• After these Hello messages, routers R1 and R2 move to the 2-Way state

121 2014/05/06 17:41:14.58 CEST MINOR: DEBUG 120 2014/05/06 17:41:14.82 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT

>> Outgoing OSPF packet on I/F to-R2 >> Outgoing OSPF packet on I/F to-R1
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.1 Router Id : 10.10.10.2
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : d393 Checksum : d393
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : HELLO Packet Type : HELLO
Packet Length : 48 Packet Length : 48

Network Mask : 255.255.255.240 Network Mask : 255.255.255.240

Hello Interval : 10 Hello Interval : 10
Options : 02 -------E-- Options : 02 -------E--
Rtr Priority : 1 Rtr Priority : 1
Dead Interval : 40 Dead Interval : 40
Designated Router : 0.0.0.0 Designated Router : 0.0.0.0
Backup Router : 0.0.0.0 Backup Router : 0.0.0.0
Neighbor-1 : 10.10.10.2 Neighbor-1 : 10.10.10.1
" "

Non-empty list of neighbors Non-empty list of neighbors

R1 R2
Point-to-point
10.1.12.0/28

2 — 2 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 35
4 Adjacency on Point-to-Point link
4.1 Adjacency on Point-to-Point link [cont.]

• These DBD messages are transmitted by routers R1 and R2 right after

entering the 2-way state, and they move to the Exstart state
• The list of LSAs is empty because the main goal is to compare MTU sizes
and to prepare the LSA list exchange by identifying master and slave
122 2014/05/06 17:41:14.59 CEST MINOR: DEBUG 122 2014/05/06 17:41:14.83 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT

>> Outgoing OSPF packet on I/F to-R2 >> Outgoing OSPF packet on I/F to-R1
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.1 Router Id : 10.10.10.2
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : fe51 Checksum : fe58
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : DB_DESC Packet Type : DB_DESC
Packet Length : 32 Packet Length : 32

Interface MTU : 1564 Interface MTU : 1564

Options : 000042 Options : 000042
Flags : 7 INIT MORE MAST Flags : 7 INIT MORE MAST
Sequence Num : 697171 Sequence Num : 697163
" "

Empty list of LSAs Empty list of LSAs

R1 R2
Point-to-point
10.1.12.0/28

2 — 2 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 36
 4 Adjacency on Point-to-Point link
4.1 Adjacency on Point-to-Point link [cont.]
• If MTUs match, after identifying master and slave, routers R1 and R2
transmit new DBD messages actually describing their link-state
database contents, and they move to the Exchange state
126 2014/05/06 17:41:14.59 CEST MINOR: DEBUG 125 2014/05/06 17:41:14.83 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT

>> Outgoing OSPF packet on I/F to-R2 >> Outgoing OSPF packet on I/F to-R1
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.1 Router Id : 10.10.10.2
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : fe5f Checksum : fe5d
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : DB_DESC Packet Type : DB_DESC
Packet Length : 32 Packet Length : 32

Interface MTU : 1564 Interface MTU : 1564

Options : 000042 Options : 000042
Flags : 0 Slave Flags : 1 MAST Master
Sequence Num : 697164 Sequence Num : 697164
" "

Empty Empty
list of LSAs list of LSAs

R1 R2
Point-to-point
10.1.12.0/28

2 — 2 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

The master-slave relationship that is established between the two routers is a clever way of accomplishing a
reliable transfer of DBD messages without the need to introduce additional acknowledgment messages.

It works as a polling mechanism in the sense that when the master sends a DBD message with a certain sequence
number, the slave must send back a DBD message with the same sequence number. The master increases the
sequence number after each exchange.

For the slave, receiving a DBD message means useful information coming from the master and, at the same time,
it is an opportunity to send a DBD message to describe its own database. If the database description does not fit
within a single packet due to MTU limitations, the slave will indicate it with a flag known as the MORE bit, which
will tell the master that additional polls are required to allow the slave to finish describing its database. Even
when the slave does not have any more information to send, it will respond to a DBD message received from the
master with an empty DBD message.

For the master, receiving a DBD message means useful information coming from the slave and, at the same time,
an acknowledgment that its own information previously sent was successfully received by the slave. If a response
is not received within a certain time, the master will resend the DBD message.

The router with the highest router ID becomes the master.

DBD messages are transmitted using unicast addressing, meaning that the link-local unicast address of the
neighbor is used as the destination IP address within the IPv6 header.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 37
 4 Adjacency on Point-to-Point link
4.1 Adjacency on Point-to-Point link [cont.]

• When routers R1 and R2 finish describing their link-state database

contents, they will send Link-State Request messages and move to the
Loading state
• Afterward, LSU messages will be exchanged to send the requested LSAs
191 2014/05/06 18:05:20.52 CEST MINOR: DEBUG 191 2014/05/06 18:05:20.73 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT
>> Outgoing OSPF packet on I/F to-R2 >> Outgoing OSPF packet on I/F to-R1
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.1 Router Id : 10.10.10.2
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : ac91 Checksum : ac93
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : LS_REQ Packet Type : LS_REQ
Packet Length : 48 Packet Length : 48
LS Type : RTR LS Type : RTR
Link State Id : 10.10.10.2 Link State Id : 10.10.10.1
Advt Router : 10.10.10.2 Advt Router : 10.10.10.1
LS Type : AROP LS Type : AROP
Link State Id : 1.0.0.1 Link State Id : 1.0.0.1
Advt Router : 10.10.10.2 Advt Router : 10.10.10.1
" "
R1 R2
Point-to-point
10.1.12.0/28

2 — 2 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

LS Type: AROP (Area Opaque LSA)

This LSA is TLV based and used to carry Traffic-Engineering router info. For example, the router-id of a router
with traffic engineering enabled router.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 38
4 Adjacency on Point-to-Point link
4.1 Adjacency on Point-to-Point link [cont.]

• When all the LSAs have been transmitted (not shown) and the last
acknowledgment has been received, meaning that the databases are
synchronized, routers R1 and R2 move to the Full state

202 2014/05/06 18:05:20.64 CEST MINOR: DEBUG 198 2014/05/06 18:05:20.76 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT
>> Outgoing OSPF packet on I/F to-R2 >> Outgoing OSPF packet on I/F to-R1
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.1 Router Id : 10.10.10.2
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : a994 Checksum : 39a4
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : LS_ACK Packet Type : LS_ACK
Packet Length : 204 Packet Length : 64
" "

R1 R2
Point-to-point
10.1.12.0/28

2 — 2 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 39
4 Adjacency on Point-to-Point link
4.2 Adjacency verification

• The following command can be used to verify that the adjacency was
successfully established
R1# show router ospf neighbor

===============================================================================
OSPFv2 (0) all neighbors
===============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------
to-R2 10.10.10.2 Full 1 0 35
0.0.0.0
-------------------------------------------------------------------------------
No. of Neighbors: 1
===============================================================================

2 — 2 — 40 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 40
 5 Adjacency on Broadcast link

2 — 2 — 41 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 41
5 Adjacency on Broadcast link
5.1 Adjacency on Broadcast link

• After these Hello messages, routers R2 and R4 move to the Init state

221 2014/05/06 19:23:27.18 CEST MINOR: DEBUG 5 2014/05/06 19:23:26.82 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT

>> Outgoing OSPF packet on I/F to-R4 >> Outgoing OSPF packet on I/F to-R2
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.2 Router Id : 10.10.10.4
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : e7a2 Checksum : e7a0
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : HELLO Packet Type : HELLO
Packet Length : 44 Packet Length : 44

Network Mask : 255.255.255.240 Network Mask : 255.255.255.240

Hello Interval : 10 Hello Interval : 10
Options : 02 -------E-- Options : 02 -------E--
Rtr Priority : 1 Rtr Priority : 1
Dead Interval : 40 Dead Interval : 40
Designated Router : 0.0.0.0 Designated Router : 0.0.0.0
Backup Router : 0.0.0.0 Backup Router : 0.0.0.0
"Router : 0.0.0.0 "
"

Empty list of neighbors

Empty list of neighbors

R2 R4
Broadcast
10.1.24.0/28

2 — 2 — 42 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 42
5 Adjacency on Broadcast link
5.1 Adjacency on Broadcast link [cont.]

• After these Hello messages, routers R2 and R4 move to the 2-Way state

223 2014/05/06 19:23:27.20 CEST MINOR: DEBUG 7 2014/05/06 19:23:26.82 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT

>> Outgoing OSPF packet on I/F to-R4 >> Outgoing OSPF packet on I/F to-R2
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.2 Router Id : 10.10.10.4
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : d390 Checksum : d390
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : HELLO Packet Type : HELLO
Packet Length : 48 Packet Length : 48

Network Mask : 255.255.255.240 Network Mask : 255.255.255.240

Hello Interval : 10 Hello Interval : 10
Options : 02 -------E-- Options : 02 -------E--
Rtr Priority : 1 Rtr Priority : 1
Dead Interval : 40 Dead Interval : 40
Designated Router : 0.0.0.0 Designated Router : 0.0.0.0
Backup Router : 0.0.0.0 Backup Router : 0.0.0.0
Neighbor-1 : 10.10.10.4 Neighbor-1 : 10.10.10.2
" "

Non-empty list of neighbors Non-empty list of neighbors

R2 R4
Broadcast
10.1.24.0/28

2 — 2 — 43 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 43
5 Adjacency on Broadcast link
5.1 Adjacency on Broadcast link [cont.]

• R2 and R4 wait for 40 seconds before running a DR/BDR election

• Afterward, they send new Hello messages to finalize election

231 2014/05/06 19:24:04.34 CEST MINOR: DEBUG 16 2014/05/06 19:24:07.32 CEST MINOR: DEBUG
#2001 Base OSPFv2 #2001 Base OSPFv2
"OSPFv2: PKT "OSPFv2: PKT

>> Outgoing OSPF packet on I/F to-R4 >> Outgoing OSPF packet on I/F to-R2
OSPF Version : 2 OSPF Version : 2
Router Id : 10.10.10.2 Router Id : 10.10.10.4
Area Id : 0.0.0.0 Area Id : 0.0.0.0
Checksum : 8f86 Checksum : 8f88
Auth Type : Null Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00 Auth Key : 00 00 00 00 00 00 00 00
Packet Type : HELLO Packet Type : HELLO
Packet Length : 48 Packet Length : 48

Network Mask : 255.255.255.240 Network Mask : 255.255.255.240

Hello Interval : 10 Hello Interval : 10
Options : 02 -------E-- Options : 02 -------E--
Rtr Priority : 1 Rtr Priority : 1
Dead Interval : 40 Dead Interval : 40
Designated Router : 10.1.24.4 Designated Router : 10.1.24.4
Backup Router : 10.1.24.4 Backup Router : 10.1.24.2
Neighbor-1 : 10.10.10.4 Neighbor-1 : 10.10.10.2
" "

Elected DR/BDR R2 R4 Elected DR/BDR

are advertised Broadcast are advertised
10.1.24.0/28

2 — 2 — 44 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 44
 5 Adjacency on Broadcast link
5.1 Adjacency on Broadcast link [cont.]

• When DR/BDR election has been finalized, routers R2 and R4 send

empty DBD messages to compare MTU sizes and identify master and
slave, and they move to the Exstart state
• After this point the process is the same as that on a point-to-point link
235 2014/05/06 19:24:07.69 CEST MINOR: DEBUG
#2001 Base OSPFv2 17 2014/05/06 19:24:07.32 CEST MINOR: DEBUG
"OSPFv2: PKT #2001 Base OSPFv2
"OSPFv2: PKT
>> Outgoing OSPF packet on I/F to-R4
OSPF Version : 2 >> Outgoing OSPF packet on I/F to-R2
Router Id : 10.10.10.2 OSPF Version : 2
Area Id : 0.0.0.0 Router Id : 10.10.10.4
Checksum : e663 Area Id : 0.0.0.0
Auth Type : Null Checksum : e65d
Auth Key : 00 00 00 00 00 00 00 00 Auth Type : Null
Packet Type : DB_DESC Auth Key : 00 00 00 00 00 00 00 00
Packet Length : 32 Packet Type : DB_DESC
Packet Length : 32
Interface MTU : 1564
Options : 000042 Interface MTU : 1564
Flags : 7 INIT MORE MAST Options : 000042
Sequence Num : 703296 Flags : 7 INIT MORE MAST
" Sequence Num : 703300
"

Empty list of LSAs

Empty list of LSAs
R2 R4
Broadcast
10.1.24.0/28

2 — 2 — 45 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

What comes next is the exchange of DBD messages describing their respective databases, the transmission of LS
Request messages as needed, the exchange of LSUs carrying the requested LSAs, and the transmission of LS
Acknowledgments after successfully receiving the LSAs.

After all this process, databases are synchronized and the routers move to the Full state.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 45
5 Adjacency on Broadcast link
5.2 Adjacency verification

• The following command can be used to verify that the adjacency was
successfully established
R4# show router ospf neighbor

===============================================================================
OSPFv2 (0) all neighbors
===============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------
to-R2 10.10.10.2 Full 1 0 33
0.0.0.0
-------------------------------------------------------------------------------
No. of Neighbors: 1
===============================================================================

2 — 2 — 46 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 46
 6 Link-State Database

2 — 2 — 47 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 47
6 Link-State Database
6.1 Link-State Database

• Routers will generate and share the following LSAs, that will be stored
in the link-state database (details follow)
R2# show router ospf database

===============================================================================
OSPFv2 (0) Link State Database (Type : All)
===============================================================================
Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
-------------------------------------------------------------------------------
Router 0.0.0.0 10.10.10.1 10.10.10.1 302 0x80000005 0x6862
Router 0.0.0.0 10.10.10.2 10.10.10.2 74 0x80000008 0x7251
Router 0.0.0.0 10.10.10.3 10.10.10.3 442 0x80000002 0x802f
Router 0.0.0.0 10.10.10.4 10.10.10.4 400 0x80000004 0x42e5
Network 0.0.0.0 10.1.24.4 10.10.10.4 402 0x80000001 0xfce0
AS Ext n/a 20.20.20.1 10.10.10.2 72 0x80000001 0x1361
-------------------------------------------------------------------------------
No. of LSAs: 6

External Routing
Domain
20.20.20.0/24
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28
R4 Broadcast
10.1.24.0/28

2 — 2 — 48 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 48
 6 Link-State Database
6.2 LSAs advertised by R1

• Router R1 will generate and share the following LSAs

Num of LSAs : 1
LS ID : 10.10.10.1 LS Type : RTR
Area ID : 0.0.0.0 Router ID : 10.10.10.1
Seq. Num : 80000002 Age : 1
Length : 60 Checksum : 6e5f
Options Bits Set: E 02
Topology: R2 is its neighbor
# Links : 3 Flags:
1 Link Type : P2P Link Nbr Rtr ID : 10.10.10.2
I/F Addr : 10.1.12.1 metric-0 : 100
2 Link Type : Stub Net Network : 10.1.12.0
Mask : 255.255.255.240 metric-0 : 100 IP reachability: IP
3 Link Type : Stub Net Network : 10.10.10.1 addresses of system and
Mask : 255.255.255.255 metric-0 : 0 toR2 interfaces

External Routing
Domain
20.20.20.0/24
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

R4 Broadcast
10.1.24.0/28

2 — 2 — 49 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

The Link LSA generated by R1 is shown here as an example. Link LSAs for other routers will not be shown. This
one is taken from a capture of the messages exchanged between R1 and R2 during adjacency establishment.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 49
6 Link-State Database
6.3 LSAs advertised by R2

• Router R2 will generate and share the following LSAs

Num of LSAs : 1
LS ID : 10.10.10.2 LS Type : RTR
Area ID : 0.0.0.0 Router ID : 10.10.10.2
Seq. Num : 80000007 Age : 1
Length : 96 Checksum : 6e58
Options Bits Set: E 02 Topology: R1, R3 (the DR)
# Links : 6 Flags: are its neighbors
1 Link Type : P2P Link Nbr Rtr ID : 10.10.10.1
I/F Addr : 10.1.12.2 metric-0 : 100
2 Link Type : Stub Net Network : 10.1.12.0
Mask : 255.255.255.240 metric-0 : 100
3 Link Type : Stub Net Network : 10.10.10.2
Mask : 255.255.255.255 metric-0 : 0
4 Link Type : Transit DR IP Addr : 10.1.24.4
I/F Addr : 10.1.24.2 metric-0 : 100
5 Link Type : P2P Link Nbr Rtr ID : 10.10.10.3
I/F Addr : 10.1.23.2 metric-0 : 100
6 Link Type : Stub Net Network : 10.1.23.0
Mask : 255.255.255.240 metric-0 : 100

External Routing
Domain
20.20.20.0/24
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

R4 Broadcast
Advertising IP address of interface toR4 10.1.24.0/28
is the responsibility of the DR (R4)

2 — 2 — 50 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 50
6 Link-State Database
6.3 LSAs advertised by R2 [cont.]

• As an ASBR, R2 will generate an additional LSA

Num of LSAs : 1
LS ID : 20.20.20.1 LS Type : EXT IP reach: external IP prefix
Area ID : --------- Router ID : 10.10.10.2 and the cost to reach it
Seq. Num : 80000001 Age : 1
Length : 36 Checksum : 1361
Options Bits Set: E 02

Dest Addr : 20.20.20.1 Netmask : 255.255.255.255

Fwd Addr : 0.0.0.0 E2-Metric 0: 1
Route Tag : 0

External Routing
Domain
20.20.20.0/24
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

R4 Broadcast
10.1.24.0/28

2 — 2 — 51 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 51
6 Link-State Database
6.4 LSAs advertised by R3

• Router R3 will generate and share the following LSAs

Num of LSAs : 1
LS ID : 10.10.10.3 LS Type : RTR
Area ID : 0.0.0.0 Router ID : 10.10.10.3
Seq. Num : 80000002 Age : 1
Length : 60 Checksum : 802f IP reach: IP address of
Options Bits Set: E 02
system interface
# Links : 3 Flags:
1 Link Type : Stub Net Network : 10.10.10.3
Mask : 255.255.255.255 metric-0 : 0
2 Link Type : P2P Link Nbr Rtr ID : 10.10.10.2 Topology: R2 is its neighbor
I/F Addr : 10.1.23.3 metric-0 : 100
3 Link Type : Stub Net Network : 10.1.23.0
Mask : 255.255.255.240 metric-0 : 100

External Routing
Domain
20.20.20.0/24
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

R4 Broadcast
10.1.24.0/28

2 — 2 — 52 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 52
6 Link-State Database
6.5 LSAs advertised by R4

• Router R4 will generate and share the following LSAs

LS ID : 10.10.10.4 LS Type : RTR
Area ID : 0.0.0.0 Router ID : 10.10.10.4
Seq. Num : 80000003 Age : 1
Length : 48 Checksum : bda4
Options Bits Set: E 02 IP reach: IP address of
system interface
# Links : 2 Flags:
1 Link Type : Stub Net Network : 10.10.10.4
Mask : 255.255.255.255 metric-0 : 0
2 Link Type : Stub Net Network : 10.1.24.0
Mask : 255.255.255.240 metric-0 : 100

External Routing
Domain
20.20.20.0/24
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28

R4 Broadcast
10.1.24.0/28

2 — 2 — 53 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 53
6 Link-State Database
6.5 LSAs advertised by R4 [cont.]

• As the DR, router R4 will generate additional LSAs acting as the

pseudo-node
Num of LSAs : 1 Topology: R2 and R4 are its
LS ID : 10.1.24.4 LS Type : NET
Area ID : 0.0.0.0 Router ID : 10.10.10.4 neighbors
Seq. Num : 80000001 Age : 1
Length : 32 Checksum : fce0
Options Bits Set: E 02

Netmask : 255.255.255.240
Adj Rtr 1 : 10.10.10.4 Adj Rtr 2 : 10.10.10.2

External Routing
Domain
20.20.20.0/24
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28 10.1.23.0/28
Pseudo-node Broadcast
R4 10.1.24.0/28

2 — 2 — 54 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 54
6 Link-State Database
6.6 Route table

• Note that the next hop to reach all IPv4 prefixes learned through OSPF
is identified by the interface address of a neighboring router.
R2# show router route-table

===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.1.12.0/28 Local Local 02h57m04s 0
to-P1 0
10.1.23.0/28 Local Local 05d05h01m 0
to-P3 0
10.1.24.0/28 Local Local 05d05h01m 0
to-P4 0
10.10.10.1/32 Remote OSPF 00h13m39s 10
10.1.12.1 100
10.10.10.2/32 Local Local 05d05h07m 0
system 0
10.10.10.3/32 Remote OSPF 00h13m39s 10
10.1.23.3 100
10.10.10.4/32 Remote OSPF 00h12m59s 10
10.1.24.4 100
20.20.20.1/32 Local Local 01h12m18s 0
loop1 0
-------------------------------------------------------------------------------
No. of Routes: 8

2 — 2 — 55 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 55
 7 Case Study – Multiple Areas

2 — 2 — 56 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 56
7 Case Study – Multiple Areas
7.1 Topology of Reference 1

Router System IP
Name Address
R1 10.10.10.1/32
R2 10.10.10.2/32
R3 10.10.10.3/32
R4 10.10.10.4/32
External Routing
Domain
Area Interfaces Area Type 20.20.20.0/24
0.0.0.0 System R2 Backbone
System R1 R1 R2 R3
0.0.0.1 Normal Point-to-point Point-to-point
R1-R2
System R3 Totally
0.0.0.3 Point-to-point
R2-R3 stubby
External Routing R4
System R4 Domain
0.0.0.4 Normal 30.30.30.0/24
R2-R4
2 — 2 — 57 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 57
 7 Case Study – Multiple Areas
7.2 Router configuration – R1
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "loop2"
loopback
address 30.30.30.1/32
no shutdown
exit
interface "system”
address 10.10.10.1/32
no shutdown
exit
interface "toR2“
address 10.1.12.1/28
port 1/1/2
no shutdown
exit
router-id 10.10.10.1
#------------------------------------------
echo "OSPFv2 Configuration"
#------------------------------------------
External Routing
ospf Domain
asbr 20.20.20.0/24
export "from-direct-to-ospf"
area 0.0.0.1
interface "system"
interface-type point-to-point
no shutdown
exit R1 R2 R3
interface "toR2"
interface-type point-to-point Point-to-point Point-to-point
no shutdown
exit
exit
exit Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 58 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Note that interface toR2 is configured inside OSPF, area 1, as point-to-point.

In this example, R1 will also advertise an external network into OSPF (i.e. will become an ASBR). Interface loop1
plays the role of an external network that is advertised into OSPF by R1 via an export policy. The export policy is
shown below:
#--------------------------------------------------
echo "Policy Configuration"
#--------------------------------------------------
policy-options
begin
prefix-list "only-loop1"
prefix 30.30.30.0/24 longer
exit
policy-statement "from-direct-to-ospf"
entry 10
from
protocol direct
prefix-list "only-loop1"
exit
to
protocol ospf
exit
action accept
exit
exit
exit
commit
exit

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 58
 7 Case Study – Multiple Areas
7.3 Router configuration – R2
#------------------------------------ #--------------------------------------
echo "IP Configuration" echo "OSPFv2 Configuration"
#------------------------------------ #--------------------------------------
interface "loop1" ospf
loopback asbr
address 20.20.20.1/32 export "from-direct-to-ospf"
no shutdown area 0.0.0.0
exit interface "system"
interface "system" interface-type point-to-point
address 10.10.10.2/32 no shutdown
no shutdown exit
exit exit
interface "toR1" area 0.0.0.1
port 1/1/2 interface "toR1"
address 10.1.12.2/28 interface-type point-to-point
no shutdown no shutdown
exit exit
interface "toR3" exit
port 1/1/3 area 0.0.0.3
address 10.1.23.2/28 stub no summaries
no shutdown exit
exit interface "toR3"
interface "toR4" interface-type point-to-point
port 1/1/1 no shutdown
address 10.1.24.2/28 exit External Routing
no shutdown exit Domain
exit area 0.0.0.4 20.20.20.0/24
router-id 10.10.10.2 interface "toR4"
interface-type point-to-point
no shutdown
exit
exit R1 R2 R3
exit Point-to-point Point-to-point

Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 59 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Note also that all interfaces, toR1, toR3 and toR4, are now configured inside OSPF as point-to-point. Each is
added to a different area. Area 3 is configured as a STUB network with no summaries (totally stubby).
Similar to the single-area case, interface loop1 plays the role of an external network that is advertised into OSPF
by R2 (which becomes an ASBR) via an export policy. The export policy is shown below:
#--------------------------------------------------
echo "Policy Configuration"
#--------------------------------------------------
policy-options
begin
prefix-list "only-loop1"
prefix 20.20.20.0/24 longer
exit
policy-statement "from-direct-to-ospf"
entry 10
from
protocol direct
prefix-list "only-loop1"
exit
to
protocol ospf
exit
action accept
exit
exit
exit
commit
exit

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 59
 7 Case Study – Multiple Areas
7.4 Router configuration – R3
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.3/32
no shutdown
exit
interface "toR2"
port 1/1/3
address 10.1.23.3/28
no shutdown
exit
router-id 10.10.10.3
#------------------------------------------
echo "OSPFv2 Configuration"
#------------------------------------------
ospf
area 0.0.0.3
stub
exit
interface "system"
External Routing
interface-type point-to-point Domain
no shutdown 20.20.20.0/24
exit
interface "toR2"
interface-type point-to-point
no shutdown
exit
exit R1 R2 R3
exit
Point-to-point Point-to-point

Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 60 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Note that interface toR2 is configured inside OSPF, area 3, as point-to-point.

Area 3 is configured as a STUB network. There is no need to add the "no summaries" part, since that command
only has a effect on an ABR, indicating it that prefixes external to the area should not be advertised.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 60
 7 Case Study – Multiple Areas
7.5 Router configuration – R4
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.4/32
no shutdown
exit
interface "toR2"
port 1/1/1
address 10.1.24.4/28
no shutdown
exit
router-id 10.10.10.4
#------------------------------------------
echo "OSPFv2 Configuration"
#------------------------------------------
ospf
area 0.0.0.4
interface "system"
interface-type point-to-point
no shutdown
External Routing
exit Domain
interface "toR2" 20.20.20.0/24
interface-type point-to-point
no shutdown
exit
exit
exit
R1 R2 R3
Point-to-point Point-to-point

Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 61 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Note that interface toR2 is configured inside OSPF, area 4, as point-to-point.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 61
 8 Link-State Databases

2 — 2 — 62 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 62
8 Link-State Databases
8.1 Link-State Database for Area 1

• The LSAs that will be visible to routers in area 1, which is a normal

area, are shown below (details follow)
R1# show router ospf database

===============================================================================
OSPFv2 (0) Link State Database (Type : All)
===============================================================================
Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
-------------------------------------------------------------------------------
Router 0.0.0.1 10.10.10.1 10.10.10.1 244 0x80000004 0x7059
Router 0.0.0.1 10.10.10.2 10.10.10.2 240 0x80000002 0xf106 NEW Type 3 LSA
Summary 0.0.0.1 10.1.23.0 10.10.10.2 229 0x80000001 0x7352
Summary 0.0.0.1 10.1.24.0 10.10.10.2 220 0x80000001 0x685c
Summary 0.0.0.1 10.10.10.2 10.10.10.2 239 0x80000002 0xee2d
Summary 0.0.0.1 10.10.10.3 10.10.10.2 50 0x80000001 0xd2e4
Summary 0.0.0.1 10.10.10.4 10.10.10.2 29 0x80000001 0xc8ed
AS Ext n/a 30.30.30.1 10.10.10.1 331 0x80000001 0xafa7 NEW Type 5 LSA
AS Ext n/a 20.20.20.1 10.10.10.2 246 0x80000027 0xc687
-------------------------------------------------------------------------------
No. of LSAs: 9
External Routing
Domain
• There are no Network LSAs because all links are 20.20.20.0/24

point-to-point R1 R2 R3
Point-to-point Point-to-point
• Summary LSAs are now visible in the database.
• Next slides will show more info on Type 5 LSAs,
Point-to-point
AS Ext. External Routing R4
Domain
30.30.30.0/24

2 — 2 — 63 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 63
 8 Link-State Databases
8.2 LSAs advertised by R2

• Router R2, being an ABR, will generate the following Type 3 LSAs.

LS ID : 10.10.10.2 LS Type : SUMM IP reach: R1 is in area 1

Area ID : 0.0.0.1 Router ID : 10.10.10.2 and R2 is in area 0. System
Seq. Num : 80000001 Age : 1
Length : 28 Checksum : f02c address of R2 advertised.
Options Bits Set: E 02

Dest Addr : 10.10.10.2 Netmask : 255.255.255.255

Metric-0 : 0

LS ID : 10.1.23.0 LS Type : SUMM

Area ID : 0.0.0.1 Router ID : 10.10.10.2 IP reach: R1 is in area 1
Seq. Num : 80000001 Age : 1 and R2 is in area 0.
Length : 28 Checksum : 7352 Interface address of R2-R3
Options Bits Set: E 02
advertised.
Dest Addr : 10.1.23.0 Netmask : 255.255.255.240
Metric-0 : 100

•Remember that type 3, Summary LSAs, are

generated by ABRs to advertise networks in
one area to another.

2 — 2 — 64 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 64
8 Link-State Databases
8.3 Link-State Database for Area 3

• The LSAs that will be visible to routers in area 3, which is a totally

stubby area, are shown below (details follow)
R3# show router ospf database

===============================================================================
OSPFv2 (0) Link State Database (Type : All)
===============================================================================
Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
-------------------------------------------------------------------------------
Router 0.0.0.3 10.10.10.2 10.10.10.2 562 0x80000002 0x954e
Router 0.0.0.3 10.10.10.3 10.10.10.3 561 0x80000002 0x9e13
-------------------------------------------------------------------------------
No. of LSAs: 2

• R3 is a totally stubby area or stubby area with

no summaries, meaning that there are no type
3,4 or 5 LSAs. This is why there are no summary
LSAs in database above, as was observed in R1. External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 65 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 65
8 Link-State Databases
8.4 LSAs advertised by R2

• Router R2, being an ABR, will generate and share the following LSA.

Remember that R3 is a stubby area with no summaries.
Num of LSAs : 1
LS ID : 10.10.10.2 LS Type : RTR
Area ID : 0.0.0.3 Router ID : 10.10.10.2
Seq. Num : 80000004 Age : 1
Length : 48 Checksum : 9150
Options Bits Set: None (00)
IP reach: Point to point link
# Links : 2 Flags: ABR for the system address.
1 Link Type : P2P Link Nbr Rtr ID : 10.10.10.3
I/F Addr : 10.1.23.2 metric-0 : 100
2 Link Type : Stub Net Network : 10.1.23.0
Mask : 255.255.255.240 metric-0 : 100 IP reach: Interface address
with the stub net as link
type.

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 66 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 66
8 Link-State Databases
8.5 Link-State Database for Area 4

• The LSAs that will be visible to routers in area 4, which is a normal

area, are shown below (details follow)
R4# show router ospf database

===============================================================================
OSPFv2 (0) Link State Database (Type : All)
===============================================================================
Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
-------------------------------------------------------------------------------
Router 0.0.0.4 10.10.10.2 10.10.10.2 75 0x80000009 0x9b3a
Router 0.0.0.4 10.10.10.4 10.10.10.4 80 0x8000000a 0xbee2
Summary 0.0.0.4 10.1.12.0 10.10.10.2 547 0x80000001 0xece3
Summary 0.0.0.4 10.1.23.0 10.10.10.2 547 0x80000001 0x7352
Summary 0.0.0.4 10.10.10.1 10.10.10.2 65 0x80000001 0xe6d2
Summary 0.0.0.4 10.10.10.2 10.10.10.2 547 0x80000001 0xf02c
Summary 0.0.0.4 10.10.10.3 10.10.10.2 65 0x80000001 0xd2e4 NEW Type 4 LSA
AS Summ 0.0.0.4 10.10.10.1 10.10.10.2 65 0x80000001 0xd8df
AS Ext n/a 30.30.30.1 10.10.10.1 546 0x80000001 0xafa7
AS Ext n/a 20.20.20.1 10.10.10.2 80 0x8000002b 0xbe8b
-------------------------------------------------------------------------------
No. of LSAs: 10 External Routing
Domain
20.20.20.0/24
• The new LSA type here is AS summary, which
will be discussed in next slide. R1 R2 R3
Point-to-point Point-to-point
• External prefixes advertised by both ASBRs (R1
and R2) are visible and highlighted in red. Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 67 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 67
8 Link-State Databases
8.6 LSAs advertised by R2

• Router R2, will advertise to R4 the location of the R1, as it is an ASBR

to all other areas.

LS ID : 10.10.10.1 LS Type : ASBR

Area ID : 0.0.0.4 Router ID : 10.10.10.2
Seq. Num : 80000001 Age : 1
Length : 28 Checksum : d8df
Options Bits Set: E 02

ASB Rtr Id : 10.10.10.1 Netmask : 0.0.0.0

Metric-0 : 100

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 68 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 68
8 Link-State Databases
8.6 LSAs advertised by R2 [cont.]

• Router R2, being an ABR, will share the following LSAs

Num of LSAs : 1
LS ID : 20.20.20.1 LS Type : EXT
Area ID : --------- Router ID : 10.10.10.2 IP reach: external IP prefix
Seq. Num : 80000001 Age : 1 connected to R2
Length : 36 Checksum : 1361
Options Bits Set: E 02

Dest Addr : 20.20.20.1 Netmask : 255.255.255.255

Fwd Addr : 0.0.0.0 E2-Metric 0: 1
Route Tag : 0

IP reach: external IP prefix

Num of LSAs : 1 connected to R1
LS ID : 30.30.30.1 LS Type : EXT
Area ID : --------- Router ID : 10.10.10.1
Seq. Num : 80000001 Age : 2
Length : 36 Checksum : afa7
Options Bits Set: E 02

Dest Addr : 30.30.30.1 Netmask : 255.255.255.255

Fwd Addr : 0.0.0.0 E2-Metric 0: 1
Route Tag : 0
External Routing
Domain
20.20.20.0/24
• AS External LSA is the reason that the router in area
4 knows about external prefixes and how to reach the R1 R2 R3
Point-to-point Point-to-point
router who originally brought the prefix into OSPF
(through the ABR). Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 69 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 69
 9 A Slightly Different Scenario

2 — 2 — 70 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 70
9 A Slightly Different Scenario
9.1 Topology of Reference 2

Router System IP
Name Address
R1 10.10.10.1/32
R2 10.10.10.2/32
R3 10.10.10.3/32
R4 10.10.10.4/32
External Routing
Domain
Area Interfaces Area Type 20.20.20.0/24
0.0.0.0 System R2 Backbone
System R1 R1 R2 R3
0.0.0.1 Normal Point-to-point Point-to-point
R1-R2
System R3 Totally
0.0.0.3 Point-to-point
R2-R3 stubby
External Routing R4
System R4 Domain
0.0.0.4 NSSA 30.30.30.0/24
R2-R4
2 — 2 — 71 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 71
 9 A Slightly Different Scenario
9.2 OSPFv2 configuration on R2
#--------------------------------------
echo "OSPFv2 Configuration"
#--------------------------------------
ospf
asbr
export "from-direct-to-ospf"
area 0.0.0.0
interface "system"
interface-type point-to-point
no shutdown
exit
exit
area 0.0.0.1
interface "toR1"
interface-type point-to-point
no shutdown
exit
exit
area 0.0.0.3 External Routing
stub no summaries
exit Domain
interface "toR3" 20.20.20.0/24
interface-type point-to-point
no shutdown
exit
exit
area 0.0.0.4
nssa R1 R2 R3
originate-default-route
exit Point-to-point Point-to-point
interface "toR4"
interface-type point-to-point
no shutdown
exit
exit Point-to-point
exit External Routing R4
Domain
30.30.30.0/24

2 — 2 — 72 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Area 4 is configured as NSSA. The "originate-default-route" command is added since the default route is not
injected by default by the ABR.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 72
 9 A Slightly Different Scenario
9.3 OSPFv2 configuration on R4
#------------------------------------------
echo "OSPFv2 Configuration"
#------------------------------------------
ospf
area 0.0.0.4
nssa
exit
interface "system"
interface-type point-to-point
no shutdown
exit
interface "toR2"
interface-type point-to-point
no shutdown
exit
exit
exit

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point
External Routing R4
Domain
30.30.30.0/24

2 — 2 — 73 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Area 4 is configured as NSSA. There is no need to add the "originate-default-route" part, since that command only
has a effect on an ABR, indicating it that the default route needs to be injected.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 73
9 A Slightly Different Scenario
9.4 Link-State Database for Area 4

• The LSAs that will be visible to routers in area 4, which is now an NSSA
area, are shown below. Generated by R2, as it is the advertising ASBR.
R4# show router ospf database

===============================================================================
OSPFv2 (0) Link State Database (Type : All)
===============================================================================
Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
-------------------------------------------------------------------------------
Router 0.0.0.4 10.10.10.2 10.10.10.2 13 0x80000002 0xf7d6
Router 0.0.0.4 10.10.10.4 10.10.10.4 12 0x80000002 0xecbe
Summary 0.0.0.4 10.1.12.0 10.10.10.2 18 0x80000001 0xbc7
Summary 0.0.0.4 10.1.23.0 10.10.10.2 18 0x80000001 0x9136
Summary 0.0.0.4 10.10.10.1 10.10.10.2 13 0x80000001 0x5b6 NEW Type 7 LSA
Summary 0.0.0.4 10.10.10.2 10.10.10.2 18 0x80000001 0xf10
Summary 0.0.0.4 10.10.10.3 10.10.10.2 13 0x80000001 0xf0c8
NSSA 0.0.0.4 20.20.20.1 10.10.10.2 16 0x80000001 0x155f
-------------------------------------------------------------------------------
No. of LSAs: 8 External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point
• Type 7, NSSA, LSAs are only advertised within External Routing R4
Domain
the NSSA area. 30.30.30.0/24

2 — 2 — 74 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 74
9 A Slightly Different Scenario
9.5 LSAs advertised by R2

• Router R2, being an ABR, will generate and share the following LSA

LS ID : 20.20.20.1 LS Type : NSSA NSSA LS Type for

Area ID : 0.0.0.4 Router ID : 10.10.10.2
Seq. Num : 80000001 Age : 1 20.20.20.0/24 network
Length : 36 Checksum : 155f
Options Bits Set: None (00)

Dest Addr : 20.20.20.1 Netmask : 255.255.255.255

Fwd Addr : 0.0.0.0 N2-Metric 0: 1
Route Tag : 0

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point
• Very similar to the way the external prefix is
advertised in a normal area, but this time an Point-to-point
NSSA LSA is being used instead of an AS External Routing
Domain
R4
External LSA 30.30.30.0/24

2 — 2 — 75 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 75
 10 OSPF Multi-Area Adjacency on a Single Link

2 — 2 — 76 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 76
 10 OSPF Multi-Area Adjacency on a Single Link
10.1 OSPF Multi-Area Adjacency on a Single Link

Definition
 Modification to OSPF's specification to allow a single IP interface to be part of
multiple OSPF areas at the same time

Supported
 For all OSPF instances

 Within a VPRN context the same way as within the base routing

 For multi-area adjacency with or without area 0

2 — 2 — 77 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

OSPF Multi-Area Adjacency is described in detail in RFC 5185.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 77
 10 OSPF Multi-Area Adjacency on a Single Link
10.2 OSPF Multi-Area Adjacency on a Single Link - Motivation

 Intra-area paths are preferred over inter-area paths. Because of this, intra area traffic
may have to use suboptimal paths to forward its traffic.
 Allowing a single IP interface to be associated with more than one area would make the
link visible as part of the topology of both areas, which would enable the discovery of
optimum paths

PE1 Shorter path, PE2

=============================================================================== not used 10.10.10.2/32
10.10.10.1/32
Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref ABR Area 0 ABR
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.1.23.0/28 Remote OSPF 00h03m34s 10 10GE (10)
10.1.14.4 300

Intf: 10.1.23.2/28
1GE 1GE
(100) (100)
*A:PE1# traceroute 10.1.23.2
traceroute to 10.1.23.2, 30 hops max, 40 byte packets
Area 1
1 10.1.14.4 (10.1.14.4) 3.79 ms 3.00 ms 4.06 ms
2 10.1.34.3 (10.1.34.3) 4.22 ms 16.4 ms 4.19 ms
3 10.1.23.2 (10.1.23.2) 3.77 ms 3.54 ms 3.83 ms
1GE(100)

PE4 PE3
10.10.10.4/32 10.10.10.3/32

2 — 2 — 78 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 78
 10.3 OSPF Multi-Area Adjacency on a Single Link –
Application
 Solves the issue by allowing a single IP interface to belong to multiple areas
 Allows the corresponding link to be considered as intra-area link in multiple areas
PE1 PE2
10.10.10.1/32 10.10.10.2/32
A:PE1>config>router>ospf# info
----------------------------------------------
area 0.0.0.0
interface "system" See Notes ABR Area 0 ABR
exit
interface "to_PE3"
interface-type point-to-point 10GE (10)
metric 10
exit
exit
area 0.0.0.1
interface "to_PE2"
interface-type point-to-point High-speed interface
exit 1GE 1GE
interface "to_PE3" secondary configured in both (100) (100)
metric 10
exit Area 0 and Area 1 Area 1
exit

A:PE3>config>router>ospf# info
---------------------------------------------- 1GE(100)
area 0.0.0.0
interface "system"
exit PE4 PE3
interface "to_PE1" 10.10.10.1/32 10.10.10.3/32
interface-type point-to-point
metric 10
exit
Each multi-area adjacency is announced as
exit
area 0.0.0.1
a point-to-point link in the configured area
interface "to_PE4"
interface-type point-to-point by the routers connected to that link
exit
interface "to_PE1" secondary Multi-area interfaces cannot be of interface-
metric 10
exit type ‘broadcast’
exit

2 — 2 — 79 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

 ABRs will establish multiple adjacencies belonging to different areas

 Each multi-area adjacency is announced as a point-to-point link in the configured area by the routers
connected to that link

 Unlike numbered point-to-point links, no type 3 link is advertised for multi-area adjacencies (in the
Router LSA)

 Point-to-point link provides a topological path for that area

 BFD not supported on multi-area interfaces. Inherits the BFD characteristics from its primary interface

 Multi-area interface cannot be configured as passive.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 79
10 OSPF Multi-Area Adjacency on a Single Link
10.4 Verification

A:PE1# show router ospf interface

==========================================================
OSPFv2 (0) all interfaces
==========================================================
If Name Area Id Designated Rtr Bkup Desig Rtr Adm Oper
-------------------------------------------------------------------------------
system 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
to-P2 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
to-P2 0.0.0.1 0.0.0.0 0.0.0.0 Up PToP
to-P4 0.0.0.1 0.0.0.0 0.0.0.0 Up PToP
-------------------------------------------------------------------------------
No. of OSPF Interfaces: 4

A:PE2# show router ospf interface

===========================================================
OSPFv2 (0) all interfaces
===========================================================
If Name Area Id Designated Rtr Bkup Desig Rtr Adm Oper
-------------------------------------------------------------------------------
system 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
to-P1 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
to-P1 0.0.0.1 0.0.0.0 0.0.0.0 Up PToP
to-P3 0.0.0.1 0.0.0.0 0.0.0.0 Up PToP
-------------------------------------------------------------------------------
No. of OSPF Interfaces: 4

2 — 2 — 80 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 80
10 OSPF Multi-Area Adjacency on a Single Link
10.4 Verification [cont.]

A:PE1# show router ospf neighbor

===========================================================
OSPFv2 (0) all neighbors
===========================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------
to-P2 10.10.10.2 Full 1 0 34
0.0.0.0
to-P2 10.10.10.2 Full 1 0 36
0.0.0.1
to-P4 10.10.10.4 Full 1 0 34
0.0.0.1
-------------------------------------------------------------------------------
No. of Neighbors: 3

A:PE2# show router ospf neighbor

===========================================================
OSPFv2 (0) all neighbors
===========================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------
to-P1 10.10.10.1 Full 1 0 32
0.0.0.0
to-P1 10.10.10.1 Full 1 0 39
0.0.0.1
to-P3 10.10.10.3 Full 1 0 30
0.0.0.1
-------------------------------------------------------------------------------
No. of Neighbors: 3

2 — 2 — 81 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 81
 10 OSPF Multi-Area Adjacency on a Single Link
10.5 End result

 After the change, PE1 is able to consider the fastest link as one of its options to reach the
desired prefix
 The best path is selected and sub-optimal routing is avoided

PE1 PE2
10.10.10.1/32 10.10.10.2/32
===========================================================================
Route Table (Router: Base)
=========================================================================== ABR Area 0 ABR
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric 10GE (10)
-----------------------------------------------------------------
10.1.23.0/28 Remote OSPF 00h04m08s 10
10.1.12.2

Intf: 10.1.23.2/28
1GE 1GE
(100) (100)
Area 1
*A:PE1# traceroute 10.1.23.2
traceroute to 10.1.23.2, 30 hops max, 40 byte packets
1 10.1.23.2 (10.1.23.2) 2.54 ms 2.08 ms 2.96 ms
1GE(100)

PE4 PE3
10.10.10.1/32 10.10.10.3/32

2 — 2 — 82 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 82
 11 OSPF Authentication

2 — 2 — 83 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 83
11 OSPF Authentication
11.1 OSPF Authentication

• Authentication is configured on OSPF interfaces for added security

• There are three types of authentication

None (default)

Password

MD5
• If there is a mismatch in authentication, the neighborship will be in non
existent.
284 2014/05/08 16:04:14.30 CEST MINOR: DEBUG #2001 Base OSPFv2

Debug "OSPFv2: PKT DROPPED
authentication failure"

Log 99 *A:P1# show log log-id 99

============================================================
===================
Event Log 99
============================================================
===================
Description : Default System Log
Memory Log contents [size=500 next event=742 (wrapped)]
741 2014/05/08 16:04:52.04 CEST WARNING: OSPF #2044 Base VR: 1 OSPFv2 (0)
"LCL_RTR_ID 10.10.10.1: Packet failed authFailure authentication on interface to-P2 from
10.1.12.2 in hello"

2 — 2 — 84 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 84
11 OSPF Authentication
11.2 OSPF Configuration

• Authentication is configured at the interface level in OSPF

• Password Type
*A:R1>config>router>ospf# info
----------------------------------------------
interface "to-R2"
interface-type point-to-point
authentication-type password
authentication-key “Alcatel”
no shutdown
exit
exit
----------------------------------------------

• MD5 Type
*A:R1>config>router>ospf# info
----------------------------------------------
interface "to-R2"
interface-type point-to-point
authentication-type message-digest
message-digest-key 1 md5 Alcatel
no shutdown
exit
exit
----------------------------------------------

2 — 2 — 85 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 85
11 OSPF Authentication
11.3 OSPF Authentication – Messages

• Authentication information is carried in different OSPF messages.

Hello 265 2014/05/08 15:27:54.22 CEST MINOR: DEBUG #2001
Base OSPFv2

DB Desc "OSPFv2: PKT

>> Incoming OSPF packet on I/F to-P2

LS Request OSPF Version
Router Id
:2
: 10.10.10.2
Area Id : 0.0.0.0

LS Update Checksum
Auth Type
: e3e9
: SimplePasswrd
Auth Key : 41 6c 63 61 74 65 6c 00

LS Ack Packet Type
Packet Length
: LS_ACK
: 44
• If MD5 is used the message is slightly LS ID : 10.10.10.1
Area ID : 0.0.0.0
LS Type : RTR
Router ID : 10.10.10.1
different, as auth type is different. Seq. Num : 80000001
Length : 36
Age :1
Checksum : 5b9a
Options Bits Set: E 02
315 2014/05/08 16:07:29.35 CEST MINOR: DEBUG #2001
Base OSPFv2 "
"OSPFv2: PKT

>> Outgoing OSPF packet on I/F to-P2

OSPF Version :2
Router Id : 10.10.10.1
Area Id : 0.0.0.0
Checksum : 0000
Auth Type : CRYPT
MD5 key ID :1
MD5 Digest Len : 16
Sequence Number : 1007
Packet Type : LS_ACK
Packet Length : 44

2 — 2 — 86 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 86
11 OSPF Authentication
11.4 Lab 5 – OSPF

2 — 2 — 87 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 87
11 OSPF Authentication
11.5 Module summary

• OSPF uses five message types: Hello, Database Description (DBD), LS

Request, LS Update, LS Acknowledgment
• An OSPF speaker may be in any of seven adjacency states at a given
time: Down, Initializing, 2-way, Exstart, Exchange, Loading, Full
• Routers become fully adjacent only after synchronizing their respective
link-state databases
• OSPF uses eight different LSA types: Router, Network, Network
Summary, ASBR Summary, AS-External, AS External, Group Membership,
NSSA External
• There are five different area types in OSPF: Normal, Stub, Totally
Stubby, NSSA, Totally NSSA
• There is always a backbone area (area 0) and all other areas need to be
adjacent to it by means of at least one ABR

2 — 2 — 88 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 88
References

2 — 2 — 89 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 89
End of module
OSPF

2 — 2 — 90 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — OSPF
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.2 Edition N/A
Section 2 — Module 2 — Page 90
Learning experience powered by
Alcatel-Lucent University

Section 2
Internal Routing Protocol
Module 3
IS-IS
TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

2—3—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 1
 Blank page

2—3—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 2013-06-14 Gallardo, Jose R. First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 2
Module objectives

• Upon completion of this module, you should be able to:

List the different message types used by IS-IS

Explain the states in which an IS-IS speaker may be and the transition
conditions between states

Describe the information carried within an IS-IS Link-state PDU (LSP)

Explain how IS-IS handles the hierarchy that is needed when the routing
domain is sub-divided into areas (area-internal routers with limited
knowledge and gateway routers with additional knowledge)

Identify the commands that can be used to configure and verify IS-IS

2—3—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 3
Module objectives [cont.]

2—3—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 4
 Table of Contents

1 IS-IS Overview 7
Page
2 Case Study – Single Area 36
1 IS-IS Overview 7
3 Adjacency
1.1 IS-IS Overview on Broadcast link 8 54
1.2 Native
4 Link-State Databasevs Multi-topology 9 58
1.3 Native vs Multi-topology (continued) 10
5 Case
1.4 Example Study of Native – Multiple
Usage inAreas
the Wrong Environment 11 72
1.5 IS-IS Hierarchical Model 12
6 Link-State
1.6 IS-IS Hierarchical Databases
Model – Example 16 79
1.7 Link Metric 22
1.8 IS-IS Packet Types 24
1.9 Hello Messages 25
1.10 PSNP and CSNP Messages 27
1.11 Link-State PDU Messages 30
1.12 Link-State PDU Messages – Level 1 31
1.13 Link-State PDU Messages – Level 2 32
1.14 IS-IS Adjacency States 33
1.15 IS-IS Adjacency States – common problems 34
1.16 Multicast addresses reserved for IS-IS 35
2 Case Study – Single Area 36
2.1 Topology of Reference 37
2.2 Router configuration – R1 38
2.3
2—3—5
Router configuration – R2 39
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
2.4 Router
Internal configuration
Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries
– R3 40
2.5 Router configuration – R4 41
2.6 IS-IS Message Types 43
2.7 Adjacency on Point-to-Point link 45
2.8 Adjacency verification 53
3 Adjacency on Broadcast link 54
3.1 Adjacency on Broadcast link 55
4 Link-State Database 58
4.1 Link-State Database 59
4.2 LSP advertised by R1 60
4.3 LSP advertised by R2 – Level 1 61
4.4 LSP advertised by R2 – Level 2 64
4.5 LSP advertised by R3 66
4.6 LSP advertised by R4 68
4.7 Route table 71
5 Case Study – Multiple Areas 72
5.1 Topology of Reference 73
5.2 Router configuration – R1 74
5.3 Router configuration – R5 75
5.4 Router configuration – R2 76
5.5 Router configuration – R3 77
5.6 Router configuration – R4 78
6 Link-State Databases 79
6.1 Link-State Database for Area 49.0051 80
6.2 LSP advertised by R1 – Level 1 81
6.3 LSP advertised by R5 82
6.4 Link-State Database for Area 49.0052 83
6.5 LSP advertised by R2 – Level 1 84
6.6 LSP advertised by R2 – Level 1 (continued) 85
6.7 LSP advertised by R3 86
6.8 LSP advertised by R4 87
6.9 Link-State Database for the Level-2 Backbone 89
6.10 LSP advertised by R1 – Level 2 90
6.11 LSP advertised by R2 – Level 2 91
Copyright © 2014 Alcatel-Lucent. All Rights Reserved.
TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 5
 Table of Contents [cont.]

Page

6.12 Route table 93

6.13 Lab 6 – IS-IS 96

2—3—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 6
 1 IS-IS Overview

2—3—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 7
 1 IS-IS Overview
1.1 IS-IS Overview

• IS-IS was created by the International Organization for Standardization

(ISO) and complies with the Open Systems Interconnection (OSI)
communication model
• IS-IS is a link-state routing protocol that enables routers (Intermediate
Systems) to exchange detailed topology and IP reachability information

Topology and IPv4 reachability information is packaged inside Link-State
PDUs (LSPs)

• Such information can be used to calculate the shortest path to any

subnetwork identified by an IP prefix
• The same IS-IS protocol is used in IPv4 and IPv6 environments

The same protocol instance can even be used by a dual-stack router to build
both its IPv4 and its IPv6 route tables

2—3—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

IS-IS was created by the International Organization for Standardization (ISO) and complies with the Open
Systems Interconnection (OSI) communication model. In OSI terminology, a router is known as an
Intermediate System (IS). Hence, IS-IS is a protocol that enables ISs to talk to each other and collaborate to
make routing decisions.

PDU stands for Protocol Data Unit and it describes a unit of information that is exchanged between peers
corresponding to the same protocol layer in the Open System Interconnection (OSI) model.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 8
1 IS-IS Overview
1.5 IS-IS Hierarchical Model

• An IS-IS routing domain can be sub-divided into several areas to reduce

the complexity of the SPF algorithm (used to calculate shortest paths)
and to decrease the convergence time
• Detailed topology and IP reachability information is only shared among
routers within the same area
• Some routers will act as gateways between areas so that packets can
still be routed throughout the entire routing domain
• IS-IS has two hierarchical levels:

Level 1 (L1)

Level 2 (L2)

2—3—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 9
1 IS-IS Overview
1.5 IS-IS Hierarchical Model [cont.]

• L1-capable routers that belong to the same area can form a level-1
adjacency

They will share detailed topology information describing all the L1-capable
routers sitting inside the relevant area and the links that interconnect them

They will also share with each other IP reachability information describing
IP sub-networks directly attached to L1-capable routers sitting inside the
relevant area
• L2-capable routers, whether they belong to the same area or not, can
form a level-2 adjacency

They will share detailed topology information describing all the L2-capable
routers they know of, regardless of the area where they are located, and
the links that interconnect them

They will also share IP reachability information describing all IP sub-
networks they know of, regardless of the area where they are located, and
the cost to reach them
• A router can be both L1- and L2-capable

2 — 3 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 10
1 IS-IS Overview
1.5 IS-IS Hierarchical Model [cont.]

• L2-capable routers must form an undivided backbone and there must be

at least one router that is both L1- and L2-capable per area
• Routers that are both L1- and L2-capable serve as gateways to
interconnect areas, so that packets can be routed throughout the entire
IS-IS domain

Each will generate an LSP to advertise all prefixes sitting in its own area;
the LSPs are flooded to all L2-capable routers and, that way, the prefixes
become visible in other areas

With their extended knowledge, they help L1-only routers within their own
area to forward packets toward sub-networks in other areas

2 — 3 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 11
1 IS-IS Overview
1.5 IS-IS Hierarchical Model [cont.]

• When a router is both L1- and L2-capable and knows that there is at
least one more area, it will advertise in its level-1 LSP that it is
attached to the backbone setting the ATT bit

It means that it is level-2 capable, and that it knows about more prefixes
than the L1-only routers in the area
• Each L1-only router will select the closest router with the attached flag
set and will install in its route table a default route pointing to it

2 — 3 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 12
1 IS-IS Overview
1.6 IS-IS Hierarchical Model – Example

• In the example, R2 (level-1) will only know:

L1 Topology: that R1 exists and the link between them

L1 IP Reachability: sub-networks directly attached to either R1 or R2

R1 R3 R5

L1/L2 L1/L2 L1/L2

Area Area
49.0051 49.0052

L1 only L1 only L1 only

Level-1 adjacency
Level-2 adjacency
R2 R4 R6
2 — 3 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 13
1 IS-IS Overview
1.6 IS-IS Hierarchical Model – Example [cont.]

• R1 (level-1 and level-2) will know everything that R2 knows, plus:

L2 Topology: that R3 and R5 exist and the links interconnecting them

L2 IP Reachability: all sub-networks directly attached to any router

R1 R3 R5

L1/L2 L1/L2 L1/L2

Area Area
49.0051 49.0052

L1 only L1 only L1 only

Level-1 adjacency
Level-2 adjacency
R2 R4 R6
2 — 3 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 14
1 IS-IS Overview
1.6 IS-IS Hierarchical Model – Example [cont.]

• Similarly, R6 (level-1) will only know:

L1 Topology: that R3, R4 and R5 exist and the links interconnecting them

L1 IP Reachability: sub-networks directly attached to either R3, R4, R5 or R6

R1 R3 R5

L1/L2 L1/L2 L1/L2

Area Area
49.0051 49.0052

L1 only L1 only L1 only

Level-1 adjacency
Level-2 adjacency
R2 R4 R6
2 — 3 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 15
1 IS-IS Overview
1.6 IS-IS Hierarchical Model – Example [cont.]

• R5 (level-1 and level-2) will know everything that R6 knows, plus:

L2 Topology: that R1 and R3 exist and the links interconnecting them

L2 IP Reachability: all sub-networks directly attached to any router

R1 R3 R5

L1/L2 L1/L2 L1/L2

Area Area
49.0051 49.0052

L1 only L1 only L1 only

Level-1 adjacency
Level-2 adjacency
R2 R4 R6
2 — 3 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 16
 1 IS-IS Overview
1.6 IS-IS Hierarchical Model – Example [cont.]

• As soon as R3 and R5 know that there is another area (by their

participation in level 2), they will advertise in their level-1 LSPs:

That they are level-2 capable, and

That they know about more prefixes than the level-1-only routers in the area
• At that point, level-1-only routers in the area will know that they could
give to R3 or R5 packets going to unknown subnetworks, and they might
be able to help deliver them
There are no guarantees;
level-1-only routers rely
blindly on L1/L2 routers

In this example, R4 and R6 can

choose between R3 and R5;
each will select the closest one

2 — 3 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Something similar applies to the other area. Namely, that as soon as R1 knows that there is another area (by
its participation in level 2), it will advertise in its level-1 LSP:

• That it is level-2 capable, and

• That it knows about more prefixes than the level-1-only routers in the area by setting their ATT bit

At that point, level-1-only routers in the area (i.e. R2) will know that they could give to R1 packets going to
unknown subnetworks, and it might be able to help deliver them.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 17
 1 IS-IS Overview
1.6 IS-IS Hierarchical Model – Example [cont.]

• If R2 receives a packet destined to a sub-network directly attached to

R4 (not visible), it will forward it to R1, its closest L1/L2 router
• R1 will forward the packet towards R3, one of the L2-capable routers
that advertised the relevant prefix (shortest end-to-end path)
• R3 will use the shortest path within its area to reach the destination

Source Destination

2 — 3 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

In this example there are two L2-capable routers in the same area as the destination sub-network; namely
R3 and R5. Both of them will advertise the relevant destination prefix.

R1 needs to make a decision as to whether to forward the packet toward R3 or R5. To do that, it will select
the one that represents the shortest end-to-end path after adding the cost to reach the L2-capable router
(known because of R1's participation in level 2) to the cost advertised by the router to reach the
destination.

In the example, going through R3 is shorter than going through R5.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 18
 1 IS-IS Overview
1.7 Link Metric

• In link-state protocols, the shortest path is defined as the one for which
the sum of link costs is minimum
• The default metric in IS-IS assigns a fixed cost of 10 to all links
Applicable to both
• Link cost is configurable in two ways: IPv4 and IPv6

1.By directly setting a different value; examples: Overrides the

metric for IPv6
config router isis interface "toR2" level 1 metric 50

2.By specifying a reference bandwidth in Kbps; the link cost is then given by:
link cost = reference bandwidth ÷ link bandwidth; example:
config router isis reference-bandwidth 100000000

• If a cost greater that 63 is to be assigned to a link, the following

command is also needed
config router isis level 1 wide-metrics-only

2 — 3 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

In the original IS-IS standard, the link cost value was carried inside a 6-bit field within an LSP. That allowed
for a maximum value of 63.

This limit was not considered granular enough for the variety of link speeds in modern networks, so an
addendum to the standard allowed the possibility to carry larger values within a new 24-bit field called
"wide metric". The wide metric can carry a maximum link cost of 16,777,215.

By default both the original ("narrow") metric and the wide metric are carried within an LSP and both need
to have the same value. So, if a cost larger than 63 is assigned to a link, the LSP will actually carry a value
of 63. In order for the larger cost assignment to take effect, the wide-metrics-only command needs to
be issued so that the narrow metric is not carried within the LSP, which eliminates the restriction of the
wide metric having to be the same as the narrow metric.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 19
1 IS-IS Overview
1.7 Link Metric [cont.]

• Several metric options are included in the IS-IS standard to make the
protocol more versatile

Default Metric: typically a constant value assigned to all links, but it can be
changed to be inversely proportional to the link bandwidth (as seen in the
previous slide)

Delay Metric: value that could reflect the delay experienced by the packets
utilizing the link

Expense Metric: value that could reflect the monetary cost incurred by the
packets utilizing the link

Error Metric: value that could reflect the loss rate experienced by the
packets utilizing the link

• In practice, however, only the default metric is used

The other metric parameters, although not used, are still advertised with a
value of zero

2 — 3 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 20
 1 IS-IS Overview
1.8 IS-IS Packet Types

• IS-IS uses four different packet types

Hello

Partial Sequence Number PDU – PSNP

Complete Sequence Number PDU – CSNP

Link-State PDU – LSP

2 — 3 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

PDU stands for Protocol Data Unit and it describes a unit of information that is exchanged between peers
corresponding to the same protocol layer in the Open System Interconnection (OSI) model.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 21
1 IS-IS Overview
1.9 Hello Messages

• Sent periodically on physical interfaces where IS-IS is enabled

• Hello messages are used:

To discover neighboring routers

To assess if they are compatible to establish an adjacency

To elect the designated intermediate system (DIS) on broadcast links

As keep-alive after an adjacency has been formed

2 — 3 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 22
 1 IS-IS Overview
1.9 Hello Messages [cont.]

• Hello messages carry a priority value that helps determine which router
in a broadcast link will be elected as the designated IS (DIS)

If there is a tie in the DIS election based on priority, it is broken by the
largest MAC address
• As neighbors are discovered, their IDs will be added to the list of
neighbors advertised in the Hello messages

Neighbors are identified by their MAC addresses on broadcast interfaces
(where DIS election is needed) and by their system IDs on point-to-point
interfaces
• Every time a new Hello message is received, a new election is run

As a consequence, if a new router with a higher priority than the current
DIS becomes active on the link, it will immediately become the new DIS
(preemptive election)

2 — 3 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

The system ID is a 48-bit unique identifier. In an Alcatel-Lucent node, its value is inherited from the router
ID, which is a 32-bit identifier.

The way the system ID is obtained in an Alcatel-Lucent node is the following:

• Each byte of the router ID is written as a 3-digit decimal number,

• Each of these digits is represented in the system ID using four bits.

Example: Router ID = 172.19.254.1

• Each byte of the router ID is written as a 3-digit decimal number: 172.019.254.001
• Each of these digits is represented in the system ID using four bits: 17 20 19 25 40 01 (In hex)
0001 0111 0010 0000 0001 1001 0010 0101 0100 0000 0000 0001 (In binary)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 23
1 IS-IS Overview
1.10 PSNP and CSNP Messages

• PSNP (Partial Sequence Number PDU) and CSNP (Complete Sequence

Number PDU) messages are used to describe the contents of the local
link-state database in a condensed manner

PSNP is a partial list of the LSPs included in the link-state database

CSNP is a complete list of the LSPs included in the link-state database

2 — 3 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 24
 1 IS-IS Overview
1.10 PSNP and CSNP Messages [cont.]

• Each entry in a PSNP or CSNP message can be interpreted as a simple

advertisement, as a request or as an acknowledgment, depending on
its sequence number

If an LSP described in the message is newer (larger sequence number) than
the LSP contained in the link-state database of the receiver, or if the receiver
does not have such an LSP
 Interpreted as advertisement; the receiver needs to send back a PSNP to
request the newer LSP version

If an LSP described in the message is older (smaller sequence number) than

the LSP contained in the link-state database of the receiver
 Interpreted as a request for the newer LSP version

If an LSP described in the message is the same as the LSP contained in the
link-state database of the receiver (same sequence number)
 Interpreted as an acknowledgment of an LSP previously transmitted by the
receiver

2 — 3 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

To request an LSP that is not in its link-state database, a router needs to create a dummy entry first with a
sequence number equal to zero (not valid for a real LSP). It can then send a PSNP describing what it has.
The router on the other end will realize that it is a dummy entry and that it needs to send back a copy of
the real LSP version that it has.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 25
1 IS-IS Overview
1.10 PSNP and CSNP Messages [cont.]

• On a point-to-point link, LSPs are explicitly acknowledged by sending

back a PSNP message after an LSP is received

PSNP message transmission is triggered by a timer (every 5 seconds)

The same PSNP message is used to acknowledge receipt of all LSPs received
during that period

• On a broadcast link, LSPs are not explicitly acknowledged

The DIS sends CSNP messages periodically (every 10 seconds), which allows
other routers to verify if their databases are synchronized with that of the DIS

If, after receiving a CSNP, a router realizes that the DIS has one or more LSPs
that are not in its own database or that are newer, it will send a PSNP
message to request a copy

Conversely, if a router realizes that it itself has one or more LSPs that are not
in the DIS’s database or that are newer, it will send out copies of the LSPs

2 — 3 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 26
1 IS-IS Overview
1.11 Link-State PDU Messages

• In link-state protocols, routers share topology and IPv4 reachability

information
• It enables them to calculate the shortest path to any sub-network
• In IS-IS, such information is carried inside Link-State PDUs (LSPs)
• A Link-State PDU message can be transmitted in two cases:

As a result of a request received during database synchronization, or

Whenever the topology changes and the new information is being flooded
throughout the network

2 — 3 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 27
 1 IS-IS Overview
1.12 Link-State PDU Messages – Level 1

• Every L1-capable router is responsible to generate and share a level-1

Link-State PDU (LSP) message that includes local topology and IP
reachability information
• The same LSP message is used to carry all types of information:

Topology: describing neighboring L1-capable routers (intermediate systems)
and the metric of the corresponding links

Internal IP reachability: describing directly attached sub-networks and the
metric of the corresponding links

External IP reachability: describing sub-networks that exist in another AS
and the cost to reach them
• An additional LSP message is generated by the DIS of each broadcast
link acting as the pseudo node

2 — 3 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

In addition to advertising IPv4 sub-networks directly attached to it, a router may want to advertise sub-
networks that are external to the IS-IS routing domain. A sub-networks is considered external if the router
knows about it because it is running an additional routing protocol besides IS-IS or two separate instances of
IS-IS.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 28
 1 IS-IS Overview
1.13 Link-State PDU Messages – Level 2

• Every L2-capable router is responsible to generate and share a level-2

Link-State PDU (LSP) message that includes topology and IP reachability
information
• The same LSP message will carry the following information:

Topology: describing neighboring L2-capable routers (intermediate systems)
and the metric of the corresponding links

Internal IP reachability (if also L1-capable): describing all sub-networks
that are directly attached to any router within its area, and the cost to
reach them

External IP reachability: describing sub-networks that exist in another AS
and the cost to reach them
• An additional LSP message is generated by the DIS of each broadcast
link acting as the pseudo node

2 — 3 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

The internal IP reachability information will be included by a L2-capable router only if it is also L1-capable.

Advertising external prefixes can be configured independently for level 1 and level 2. By default, an L2-
capable router will not share with other L2-capable routers external prefixes advertised in level-1 LSPs. A
policy must be configured for that.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 29
 1 IS-IS Overview
1.14 IS-IS Adjacency States

• The 3 states to establish an adjacency between two routers are:

Down – neighbor has not been discovered

Initializing – one-way communication has been verified via Hello messages

Up – two-way communication has been verified via Hello messages

• Being in the Up state means that routers are adjacent

• At this point routers start synchronizing their databases
• A router on a broadcast link will only actively synchronize its database
with the DIS

2 — 3 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

The 3 states to fulfill adjacency between two routers are:

• Down – neighbor has not been discovered: no Hello messages have been received from neighbor yet

• Initializing – one-way communication has been verified: Hello messages have been received from
neighbor, but the neighbor list in the Hello messages does not include the local MAC address (I can see
him, but I do not know if he can see me)

To exchange Hello messages successfully, routers must be compatible in the sense that the interface
type has to be the same (point-to-point or broadcast) and they have to be properly authenticated. If
they are located in different areas they can only establish a L2 adjacency (if capable), and if they are
located in the same area they can establish both L1 and L2 adjacencies (if capable).

• Up – two-way communication has been verified: Hello messages have been received from neighbor, and
the local MAC address is included in the neighbor list contained in Hello messages (I can see him and he
can see me)

Being in the Up state means that routers are adjacent.

After the adjacency has been formed, routers start synchronizing their link-state databases. This is in
contrast to OSPF, in which routers become adjacent only after having synchronized the databases.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 30
 1 IS-IS Overview
1.15 IS-IS Adjacency States – common problems

• IS-IS Adjacency States:

Down If adjacency is stuck here, some parameters are not compatible
(area for L1, authentication, interface types - point-to-point vs broadcast)

Initializing
If adjacency is UP, but routing information is not shared, authentication

Up for Hello messages is properly configured, but authentication for other
types of messages is misconfigured

2 — 3 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

If routers cannot see each other (remain in the Down state) even if they are physically connected, the most
likely cause is that some parameters are not compatible. For instance, routers need to be in the same area
to form a L1 adjacency; authentication information must be the same; the interface type on both sides must
be the same (point-to-point vs broadcast).

If, on the other hand, routers are adjacent but are not sharing any more information (not exchanging LSPs),
the reason may be that authentication has been misconfigured. In IS-IS, authentication for Hello messages
and for other message types can be configured independently. If authentication is configured globally at the
isis context using the authentication-type and authentication-key commands, it applies to
all interfaces and for all types of messages.

If authentication is configured per level (level 1 or level 2), on the other hand, it applies to all messages
different from Hello. Authentication for Hello messages per level can be enabled using the hello-
authentication command, but it is disabled by default; if enabled, it will use the same type and key as
those used for other messages corresponding to the same level.

Lastly, if authentication is configured using the hello-authentication-type and hello-

authentication-key commands for a specific interface, it only applies to Hello messages, and not to
other message types.

It is important to be careful when configuring authentication for IS-IS.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 31
1 IS-IS Overview
1.16 Multicast addresses reserved for IS-IS

• IS-IS messages are not carried within IPv4 packets, but directly inside
layer-2 frames
• The following are Ethernet multicast addresses reserved for IS-IS:

0180:C200:0014 – All L1-capable routers on a broadcast interface

0180:C200:0015 – All L2-capable routers on a broadcast interface

0900:2b00:0005 – All routers on a point-to-point interface

• If needed, the Ethernet multicast address to be used by a router can be

changed:

configure router isis all-l1isis <MAC-address>
specifies the MAC address to be used for L1 messages

configure router isis all-l2isis <MAC-address>

specifies the MAC address to be used for L2 messages

2 — 3 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 32
 2 Case Study – Single Area

2 — 3 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 33
2 Case Study – Single Area
2.1 Topology of Reference

Router System IP Level

Name Address capability
R1 10.10.10.1 L1
R2 10.10.10.2 L1/L2
R3 10.10.10.3 L1
R4 10.10.10.4 L1
External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Broadcast
10.1.12.0/28
R4

2 — 3 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 34
 2 Case Study – Single Area
2.2 Router configuration – R1
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.1/32
no shutdown
exit
interface “toR2”
port 1/1/2
address 10.1.12.1/28
no shutdown
exit
router-id 10.10.10.1
#------------------------------------------
Echo “ISIS Configuration”
#------------------------------------------
isis
level-capability level-1
area-id 49.0051
interface "system" External Routing
interface-type point-to-point
no shutdown Domain
exit 20.20.20.0/24
interface "toR2"
interface-type point-to-point
no shutdown
exit
no shutdown
exit R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Broadcast
10.1.12.0/28
R4

2 — 3 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Note that interface toR2 is configured inside IS-IS as point-to-point.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 35
 2 Case Study – Single Area
2.3 Router configuration – R2
#--------------------------------------- #-------------------------------------
echo "IP Configuration" echo "ISIS Configuration"
#--------------------------------------- #-------------------------------------
interface "loop1" isis
loopback area-id 49.0051
address 20.20.20.1/32 export "from-direct-to-isis"
no shutdown interface "system"
exit interface-type point-to-point
interface "system" no shutdown
address 10.10.10.2 exit
no shutdown interface "toR1"
exit interface-type point-to-point
interface "toR1" no shutdown
port 1/1/2 exit
address 10.1.12.2/28 interface "toR3"
no shutdown interface-type point-to-point
exit no shutdown
interface "toR3" exit
port 1/1/3 interface "toR4"
address 10.1.23.2/28 interface-type broadcast
no shutdown no shutdown External Routing
exit exit
interface "toR4" no shutdown Domain
port 1/1/1 exit 20.20.20.0/24
address 10.1.24.2/28
no shutdown
exit
router-id 10.10.10.2
R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Broadcast
10.1.12.0/28
R4

2 — 3 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Note that interfaces toR1 and toR3 are configured inside IS-IS as point-to-point, while interface toR4 is
configured inside IS-IS as broadcast (default).
Lastly, interface loop1 plays the role of an external network that is advertised into IS-IS by R2 via an export
policy. The export policy is shown below:
#--------------------------------------------------
echo "Policy Configuration"
#--------------------------------------------------
policy-options
begin
prefix-list "only-loop1"
prefix 20.20.20.0/24 longer
exit
policy-statement "from-direct-to-isis"
entry 10
from
protocol direct
prefix-list "only-loop1"
exit
to
protocol isis
level 1
exit
action accept
exit
exit
exit
commit
exit

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 36
 2 Case Study – Single Area
2.4 Router configuration – R3
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.3/32
no shutdown
exit
interface "toR2"
port 1/1/3
address 10.1.23.3/28
no shutdown
exit
router-id 10.10.10.3
#------------------------------------------
echo "ISIS Configuration"
#------------------------------------------
isis
level-capability level-1
area-id 49.0051
interface "system" External Routing
interface-type point-to-point
no shutdown Domain
exit 20.20.20.0/24
interface "toR2"
interface-type point-to-point
no shutdown
exit
no shutdown
exit R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Broadcast
10.1.12.0/28
R4

2 — 3 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Note that interface toR2 is configured inside IS-IS as point-to-point.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 37
 2 Case Study – Single Area
2.5 Router configuration – R4
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.4/32
no shutdown
exit
interface "toR2"
port 1/1/1
address 10.1.24.2/28
no shutdown
exit
router-id 10.10.10.4
#------------------------------------------
echo "ISIS Configuration"
#------------------------------------------
isis
level-capability level-1
area-id 49.0051
interface "system" External Routing
interface-type point-to-point
no shutdown Domain
exit 20.20.20.0/24
interface "toR2"
interface-type broadcast
no shutdown
exit
no shutdown
exit R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Broadcast
10.1.12.0/28
R4

2 — 3 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Note that interface toR2 is configured inside IS-IS as broadcast (default).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 38
 3 Adjacency Establishment
and Database Synchronization

2 — 3 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 39
2 Case Study – Single Area
2.6 IS-IS Message Types

• The table below will show the different ISIS messages

Message Name Short Name Definition
Hello Hello Transmitted to monitor the
adjacency state.
Complete CSNP Contains list of all LSPs from
Sequence Number the current database. Triggers
PDU the transmission of LSPs and
sent periodically to ensure
synchronization
Link State PDU LSP Used to construct the link-
state database. Contain the
local interfaces that are used
in IS-IS and prefixes learned
from other adjacent routers.
Partial Sequence PSNP Used to request an LSP (or
Number PDU LSPs) and to acknowledge
when they are received.
2 — 3 — 40 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 40
 2 Case Study – Single Area
2.6 IS-IS Message Types [cont.]

• Example of ISIS messages being exchanged

R1 R5

HELLO Exchange

DIS* sends CSNP to trigger LSP exchange

R5 initiates LSP exchange

PSNP sent to acknowledge LSPs received

PSNP sent to request LSP

LSP that was requested is sent

PSNP sent to acknowledge requested LSP

Periodic CSNP sent for synchronization

DIS*- notes

2 — 3 — 41 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

DIS stands for the designated IS. One of the routers will elect itself as the DIS. This election process is based
on the interface priority, and if there is a tie it is broken by the highest MAC address.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 41
 2 Case Study – Single Area
2.7 Adjacency on Point-to-Point link

• After these Hello messages, routers R1 and R2 move to the Init state
341 2014/05/12 16:28:33.82 CEST MINOR: DEBUG #2001 834 2014/05/12 16:28:33.74 CEST MINOR: DEBUG #2001
Base ISIS PKT Base ISIS PKT
"ISIS PKT: "ISIS PKT:
TX ISIS PDU ifId 2 len 59: TX ISIS PDU ifId 2 len 59:
DMAC : 09:00:2b:00:00:05 DMAC : 09:00:2b:00:00:05

... Output omitted ... ... Output omitted ...

PDU Type : (11) Point-2-Point IS-IS Hello Pdu PDU Type : (11) Point-2-Point IS-IS Hello Pdu
Circuit Type : L1 Circuit Type : L1L2
Source Id : 01 00 10 01 00 01 Source Id : 01 00 10 01 00 02
Hold Time : 27 Hold Time : 27
Packet length : 42 Packet length : 42
Circuit Id : 0 Circuit Id : 0
Area Addresses: Area Addresses:
Area Address : (3) 49.0051 Area Address : (3) 49.0051
Supp Protocols: Supp Protocols:
Protocols : IPv4 Protocols : IPv4
I/F Addresses : I/F Addresses :
I/F Address : 10.1.12.1 I/F Address : 10.1.12.2
3Way Adjacency : 3Way Adjacency :
State : DOWN State : DOWN
Ext ckt ID : 2 Ext ckt ID : 2

Empty list of neighbors Empty list of neighbors

Note that point-to-point

R1 R2
Hello messages carry the Point-to-point
adjacency state 10.1.12.0/28

2 — 3 — 42 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 42
2 Case Study – Single Area
2.7 Adjacency on Point-to-Point link [cont.]

• After these Hello messages, routers R1 and R2 move to the Up state

342 2014/05/12 16:28:33.83 CEST MINOR: DEBUG #2001 835 2014/05/12 16:28:33.75 CEST MINOR: DEBUG #2001
Base ISIS PKT Base ISIS PKT
"ISIS PKT: "ISIS PKT:
TX ISIS PDU ifId 2 len 69: TX ISIS PDU ifId 2 len 69:
DMAC : 09:00:2b:00:00:05 DMAC : 09:00:2b:00:00:05

... Output omitted ... ... Output omitted ...

PDU Type : (11) Point-2-Point IS-IS Hello Pdu PDU Type : (11) Point-2-Point IS-IS Hello Pdu
Circuit Type : L1 Circuit Type : L1L2
Source Id : 01 00 10 01 00 01 Source Id : 01 00 10 01 00 02
Hold Time : 27 Hold Time : 27
Packet length : 52 Packet length : 52
Circuit Id : 0 Circuit Id : 0
Area Addresses: Area Addresses:
Area Address : (3) 49.0051 Area Address : (3) 49.0051
Supp Protocols: Supp Protocols:
Protocols : IPv4 Protocols : IPv4
I/F Addresses : I/F Addresses :
I/F Address : 10.1.12.1 I/F Address : 10.1.12.2
3Way Adjacency : 3Way Adjacency :
State : INIT State : INIT
Ext ckt ID : 2 Ext ckt ID : 2
NbrSysID : 01 00 10 01 00 02 NbrSysID : 01 00 10 01 00 01
Nbr ext ckt ID : 2 Nbr ext ckt ID : 2

Non-empty list of neighbors Non-empty list of neighbors

R1 R2
Point-to-point
10.1.12.0/28

2 — 3 — 43 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 43
2 Case Study – Single Area
2.7 Adjacency on Point-to-Point link [cont.]

• Subsequent Hello messages will indicate that they are in the Up state
• At this point they will proceed to synchronize their link-state databases
344 2014/05/12 16:28:33.82 CEST MINOR: DEBUG #2001 837 2014/05/12 16:28:33.74 CEST MINOR: DEBUG #2001
Base ISIS PKT Base ISIS PKT
"ISIS PKT: "ISIS PKT:
TX ISIS PDU ifId 2 len 69: TX ISIS PDU ifId 2 len 69:
DMAC : 09:00:2b:00:00:05 DMAC : 09:00:2b:00:00:05

... Output omitted ... ... Output omitted ...

PDU Type : (11) Point-2-Point IS-IS Hello Pdu PDU Type : (11) Point-2-Point IS-IS Hello Pdu
Circuit Type : L1 Circuit Type : L1L2
Source Id : 01 00 10 01 00 01 Source Id : 01 00 10 01 00 02
Hold Time : 27 Hold Time : 27
Packet length : 52 Packet length : 52
Circuit Id : 0 Circuit Id : 0
Area Addresses: Area Addresses:
Area Address : (3) 49.0051 Area Address : (3) 49.0051
Supp Protocols: Supp Protocols:
Protocols : IPv4 Protocols : IPv4
I/F Addresses : I/F Addresses :
I/F Address : 10.1.12.1 I/F Address : 10.1.12.2
3Way Adjacency : 3Way Adjacency :
State : UP State : UP
Ext ckt ID : 2 Ext ckt ID : 2
NbrSysID : 01 00 10 01 00 02 NbrSysID : 01 00 10 01 00 01
Nbr ext ckt ID : 2 Nbr ext ckt ID : 2

R1 R2
Point-to-point
10.1.12.0/28

2 — 3 — 44 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 44
2 Case Study – Single Area
2.7 Adjacency on Point-to-Point link [cont.]

• CSNP messages will be transmitted after the adjacency is established.

This message contains a description of the known LSPs and sequence
numbers being used. Also, it is the trigger for the transmission of LSPs.

347 2014/05/12 16:28:33.83 CEST MINOR: DEBUG #2001

Base ISIS PKT
"ISIS PKT:
RX ISIS PDU ifId 2 len 51:
DMAC : 09:00:2b:00:00:05

... Output omitted ...

PDU Type : (18) Level 1 CSNP PDU

Packet length : 51
Source Id : 01 00 10 01 00 02 00
Start LSP Id : 00 00 00 00 00 00 00 00
End LSP Id : FF FF FF FF FF FF FF FF
LSP Entries :
Remaining Life: 1200
LSP ID : 01 00 10 01 00 02 00 00
Sequence Num : 00000001
Checksum : 1281

R1 R2
Point-to-point
10.1.12.0/28

2 — 3 — 45 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 45
2 Case Study – Single Area
2.7 Adjacency on Point-to-Point link [cont.]

• Since initially each router only has one LSP in its link-state database
(its own), it will send it immediately. Received by R2. Topology,
narrow
Internal Reach: metric
7 2013/05/22 12:51:00.19 Default Metric: (I) 10
"ISIS PKT: Delay Metric : (I) 0
RX ISIS PDU ifId 2 len 197: Expense Metric: (I) 0
DMAC : 09:00:2b:00:00:05 Error Metric : (I) 0
Internal
IP Address : 10.1.12.0 IP reach
... Output omitted ... IP Mask : 255.255.255.240
Default Metric: (I) 0
PDU Type : (12) Level 1 Link State Pdu Delay Metric : (I) 0
Packet length : 197 Expense Metric: (I) 0
Rem Lifetime : 1200 Error Metric : (I) 0
LSP Id : 01 00 10 01 00 02 00 00 IP Address : 10.10.10.1
Sequence Num : 1 IP Mask : 255.255.255.255 I/F I/F
LSP Checksum : 3d71 Addresses :
LSP Flags : (00000003) L2 I/F Address : 10.10.10.1
Area Addresses: I/F Address : 10.1.12.1
Area Address : (3) 49.0051 TE IS Nbrs :
Supp Protocols: Nbr : P2.00
Protocols : IPv4 Default Metric : 10
IS-Hostname : R2 Sub TLV Len : 12
Router ID : IF Addr : 10.1.12.1
Router ID : 10.10.10.2 Nbr IP : 10.1.12.2
Topology,
IS Neighbors : TE IP Reach : wide
Virtual Flag : 0
Default Metric: (I) 10
Default Metric : 10 metric
Control Info: , prefLen 28
Delay Metric : (I) 0 Prefix : 10.1.12.0
Expense Metric: (I) 0 Default Metric : 0
Error Metric : (I) 0 Control Info: , prefLen 32
Neighbor : P2.00 Prefix : 10.10.10.1
R1 R2
Point-to-point
10.1.12.0/28

2 — 3 — 46 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 46
2 Case Study – Single Area
2.7 Adjacency on Point-to-Point link [cont.]

• Since initially each router only has one LSP in its link-state database
(its own), it will send it immediately. Received by R1. Topology,
narrow
349 2014/05/12 16:28:33.88 CEST MINOR: DEBUG Internal Reach: metric
#2001 Base ISIS PKT Default Metric: (I) 10
"ISIS PKT: Delay Metric : (I) 0
RX ISIS PDU ifId 2 len 141: Expense Metric: (I) 0
DMAC : 09:00:2b:00:00:05 Error Metric : (I) 0
IP Address : 10.1.23.0
... Output omitted ... IP Mask : 255.255.255.240
Default Metric: (I) 0 Internal
PDU Type : (12) Level 1 Link State Pdu Delay Metric : (I) 0 IP reach
Packet length : 141 Expense Metric: (I) 0
Rem Lifetime : 1200 Error Metric : (I) 0
LSP Id : 01 00 10 01 00 03 00 00 IP Address : 10.10.10.3
Sequence Num : 1 IP Mask : 255.255.255.255
LSP Checksum : f611 I/F Addresses :
LSP Flags : (00000001) L1 I/F Address : 10.10.10.3
Area Addresses: I/F Address : 10.1.23.3
Area Address : (3) 49.0051 TE IS Nbrs :
Supp Protocols: Nbr : 0100.1001.0002.00
Protocols : IPv4 Default Metric : 10
IS-Hostname : P3 Sub TLV Len : 12
Router ID : IF Addr : 10.1.23.3 Topology,
Router ID : 10.10.10.3 Nbr IP : 10.1.23.2 wide
IS Neighbors : TE IP Reach :
Virtual Flag : 0 Default Metric : 10 metric
Default Metric: (I) 10 Control Info: , prefLen 28
Delay Metric : (I) 0 Prefix : 10.1.23.0
Expense Metric: (I) 0 Default Metric : 0
Error Metric : (I) 0 Control Info: , prefLen 32
Neighbor : 0100.1001.0002.00 Prefix : 10.10.10.3
R1 R2
Point-to-point
10.1.12.0/28

2 — 3 — 47 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 47
2 Case Study – Single Area
2.7 Adjacency on Point-to-Point link [cont.]

• PSNP messages will be transmitted to acknowledge receipt of the LSPs

353 2014/05/12 16:28:35.77 CEST MINOR: DEBUG #2001 847 2014/05/12 16:28:35.74 CEST MINOR: DEBUG #2001
Base ISIS PKT Base ISIS PKT
"ISIS PKT: "ISIS PKT:
TX ISIS PDU ifId 2 len 100: TX ISIS PDU ifId 2 len 52:
DMAC : 09:00:2b:00:00:05 DMAC : 09:00:2b:00:00:05

... Output omitted ... ... Output omitted ...

PDU Type : (1a) Level 1 PSNP Pdu PDU Type : (1a) Level 1 PSNP Pdu
Packet length : 83 Packet length : 35
Source Id : 01 00 10 01 00 01 00 Source Id : 01 00 10 01 00 02 00
LSP Entries : LSP Entries :
Remaining Life: 1199 Remaining Life: 1198
LSP ID : 01 00 10 01 00 02 00 00 LSP ID : 01 00 10 01 00 01 00 00
Sequence Num : 00000002 Sequence Num : 00000001
Checksum : 0fa4 Checksum : 71dd
Remaining Life: 1198
LSP ID : 01 00 10 01 00 03 00 00
Sequence Num : 00000001
Checksum : f611
Remaining Life: 1198
LSP ID : 01 00 10 01 00 04 00 00
Sequence Num : 00000001
Checksum : 2a08
Remaining Life: 1198
LSP ID : 01 00 10 01 00 04 01 00
Sequence Num : 00000001
Checksum : 7fb1 R1 R2
Point-to-point
10.1.12.0/28

2 — 3 — 48 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 48
 2 Case Study – Single Area
2.7 Adjacency on Point-to-Point link [cont.]

• At this point routers will proceed to synchronize their databases

• Periodic CSNP messages are used to ensure database synchronization

425 2014/05/13 18:10:10.96 CEST MINOR: DEBUG

#2001 Base ISIS PKT
"ISIS PKT:
RX ISIS PDU ifId 5 len 67:
DMAC : 09:00:2b:00:00:05

... Output omitted ...

PDU Type : (18) Level 1 CSNP PDU

Packet length : 67
Source Id : 01 00 10 01 00 05 00
Start LSP Id : 00 00 00 00 00 00 00 00 LSPs generated by the real
End LSP Id : FF FF FF FF FF FF FF FF nodes (pseudo-node ID = 0)
LSP Entries :
Remaining Life: 1156
LSP ID : 01 00 10 01 00 01 00 00
Sequence Num : 00000003
Checksum : 3dfc
Remaining Life: 1150
LSP ID : 01 00 10 01 00 02 00 00
Sequence Num : 00000001
Checksum : c2e9
R1 R2
Point-to-point
10.1.12.0/28

2 — 3 — 49 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

The LSP ID consists of three fields which together identify a particular LSP:

• Source ID: system ID of the originating router,

• Pseudo-node ID: field that is non-zero only when the LSP is originated by a DIS to represent a pseudo-
node; this 1-byte field has the same value as the Local Circuit ID assigned to the broadcast link by the
DIS originating the LSP,

• LSP Number: when a router must break its LSP into multiple parts due to MTU limitations, this field
assigns consecutive numbers to the different parts; the first (or only) part is assigned a value of zero.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 49
2 Case Study – Single Area
2.8 Adjacency verification

• The following command can be used to verify that the adjacency was
successfully established
R1# show router isis adjacency

===============================================================================
ISIS Adjacency
===============================================================================
System ID Usage State Hold Interface MT-ID
-------------------------------------------------------------------------------
R2 L1 Up 22 to-R2 0
-------------------------------------------------------------------------------
Adjacencies : 1
===============================================================================

2 — 3 — 50 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 50
 3 Adjacency on Broadcast link

2 — 3 — 51 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 51
 3 Adjacency on Broadcast link
3.1 Adjacency on Broadcast link

• After these Hello messages, routers R2 and R4 move to the Init state
214 2014/05/12 21:03:53.55 CEST MINOR: DEBUG #2001 856 2014/05/12 21:03:53.48 CEST MINOR: DEBUG #2001
Base ISIS PKT Base ISIS PKT
"ISIS PKT: "ISIS PKT:
TX ISIS PDU ifId 3 len 59: TX ISIS PDU ifId 4 len 59:
DMAC : 01:80:c2:00:00:14 DMAC : 01:80:c2:00:00:14

... Output omitted ... ... Output omitted ...

PDU Type : (0f) Level 1 LAN IS-IS Hello Pdu PDU Type : (0f) Level 1 LAN IS-IS Hello Pdu
Circuit Type : L1 Circuit Type : L1L2
Source Id : 01 00 10 01 00 04 Source Id : 01 00 10 01 00 02
Hold Time : 27 Hold Time : 27
Packet length : 42 Packet length : 42
Priority : 64 Priority : 64
LAN Id : 01 00 10 01 00 04 01 LAN Id : 01 00 10 01 00 02 03
Area Addresses: Area Addresses:
Area Address : (3) 49.0051 Area Address : (3) 49.0051
Supp Protocols: Supp Protocols:
Protocols : IPv4 Protocols : IPv4
I/F Addresses : I/F Addresses :
I/F Address : 10.1.24.4 I/F Address : 10.1.24.2

Empty list of neighbors Empty list of neighbors

R2
Note that LAN Hello Broadcast
messages do NOT carry the
adjacency state 10.1.24.0/28
R4
2 — 3 — 52 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 52
3 Adjacency on Broadcast link
3.1 Adjacency on Broadcast link [cont.]

• After these Hello messages, routers R2 and R4 move to the Up state

• DIS is elected but not advertised in Hello messages
215 2014/05/12 21:03:53.57 CEST MINOR: DEBUG #2001 858 2014/05/12 21:03:53.51 CEST MINOR: DEBUG #2001
Base ISIS PKT Base ISIS PKT
"ISIS PKT: "ISIS PKT:
TX ISIS PDU ifId 3 len 67: TX ISIS PDU ifId 4 len 67:
DMAC : 01:80:c2:00:00:14 DMAC : 01:80:c2:00:00:14

... Output omitted ... ... Output omitted ...

PDU Type : (0f) Level 1 LAN IS-IS Hello Pdu PDU Type : (0f) Level 1 LAN IS-IS Hello Pdu
Circuit Type : L1 Circuit Type : L1L2
Source Id : 01 00 10 01 00 04 Source Id : 01 00 10 01 00 02
Hold Time : 27 Hold Time : 27
Packet length : 50 Packet length : 50
Priority : 64 Priority : 64
LAN Id : 01 00 10 01 00 04 01 LAN Id : 01 00 10 01 00 02 03
Area Addresses: Area Addresses:
Area Address : (3) 49.0051 Area Address : (3) 49.0051
Neighbors MACs: Neighbors MACs:
R4 becomes DIS
Neighbor : 9a7501010003 Neighbor : 9a7701010003 (Higher MAC)
Supp Protocols: Supp Protocols:
Protocols : IPv4 Protocols : IPv4
I/F Addresses : I/F Addresses :
I/F Address : 10.1.24.4 I/F Address : 10.1.24.2

Non-empty list of neighbors

Non-empty list of neighbors
R2
Broadcast
10.1.24.0/28
R4
2 — 3 — 53 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 53
 3 Adjacency on Broadcast link
3.1 Adjacency on Broadcast link [cont.]

• At this point routers will proceed to synchronize their databases

• The process is similar to what happens on a point-to-point link, except
that PSNP messages are not sent as acknowledgments, but the DIS will
send periodic CSNP messages to ensure database synchronization
876 2014/05/12 21:04:03.52 CEST MINOR: DEBUG
#2001 Base ISIS PKT
"ISIS PKT:
RX ISIS PDU ifId 4 len 115:
DMAC : 01:80:c2:00:00:14

... Output omitted ...

PDU Type : (18) Level 1 CSNP PDU

Packet length : 115
Source Id : 01 00 10 01 00 04 00 LSPs generated by the real
Start LSP Id : 00 00 00 00 00 00 00 00 nodes (pseudo-node ID = 0)
End LSP Id : FF FF FF FF FF FF FF FF
LSP Entries :
Remaining Life: 1191
LSP ID : 01 00 10 01 00 01 00 00 LSP generated by R4 acting as the
Sequence Num : 00000002
Checksum : 6fde
pseudo-node (pseudo-node ID ≠ 0)
Remaining Life: 1190
LSP ID : 01 00 10 01 00 02 00 00
Sequence Num : 00000001
Checksum : 11a3 R2
Remaining Life: 1191
LSP ID : 01 00 10 01 00 04 01 00
Sequence Num : 00000001 Broadcast
Checksum : 7fb1
... Output omitted ... 10.1.24.0/28
R4

2 — 3 — 54 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

The LSP ID consists of three fields which together identify a particular LSP:

• Source ID: system ID of the originating router,

• Pseudo-node ID: field that is non-zero only when the LSP is originated by a DIS to represent a pseudo-
node; this 1-byte field has the same value as the Local Circuit ID assigned to the broadcast link by the
DIS originating the LSP,

• LSP Number: when a router must break its LSP into multiple parts due to MTU limitations, this field
assigns consecutive numbers to the different parts; the first (or only) part is assigned a value of zero.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 54
 4 Link-State Database

2 — 3 — 55 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 55
4 Link-State Database
4.1 Link-State Database

• Routers will generate and share the following LSPs, that will be stored
in the link-state database (details follow)
show router isis database

========================================================================
ISIS Database
========================================================================
LSP ID Sequence Checksum Lifetime
Attributes
------------------------------------------------------------------------
R2 does NOT advertise
Displaying Level 1 database itself as attached
------------------------------------------------------------------------
R1.00-00 0x3 0x6ddf 914 L1
R2.00-00 0x2 0xfa4 909 L1L2
R3.00-00 0x3 0xf213 955 L1
R4.00-00 0x3 0x260a 1006 L1
R4.01-00 0x2 0x7db2 915 L1
Level (1) LSP Count : 5

Displaying Level 2 database

------------------------------------------------------------------------ External Routing
R2.00-00 0x4 0xc955 1008 L1L2 Domain
Level (2) LSP Count : 1 20.20.20.0/24
========================================================================
R1 R2 R3
Note that the router name is Point-to-point Point-to-point
displayed instead of the system ID 10.1.12.0/28
Broadcast
R4 10.1.12.0/28

2 — 3 — 56 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 56
4 Link-State Database
4.2 LSP advertised by R1

• Router R1 will generate and share the following LSP

LSP ID : R1.00-00 Level : L1
Sequence : 0x1 Checksum : 0x71dd Lifetime : 1101
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1 Max Area : 3
SysID Len : 6 Used Len : 141 Alloc Len : 1492
TLVs :
Area Addresses:
Area Address : (3) 49.0051
Supp Protocols:
Protocols : IPv4
IS-Hostname : R1
Router ID :
Router ID : 10.10.10.1
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10 Topology (narrow metric):
Delay Metric : (I) 0 R2 is its neighbor
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : R2.00
Internal Reach:
Default Metric: (I) 10 Internal IP reach: IP
Delay Metric : (I) 0
Expense Metric: (I) 0 addresses of system and
Error Metric : (I) 0
IP Address : 10.1.12.0
toR2 interfaces
IP Mask : 255.255.255.240
Default Metric: (I) 0
Delay Metric : (I) 0 External Routing
Expense Metric: (I) 0 Domain
Error Metric : (I) 0
IP Address : 10.10.10.1 20.20.20.0/24
IP Mask : 255.255.255.255
I/F Addresses : R1 R2 R3
I/F Address : 10.10.10.1 Point-to-point Point-to-point
I/F Address : 10.1.12.1
TE IS Nbrs : 10.1.12.0/28
Nbr : R2.00
Default Metric : 10
Topology (wide metric): Broadcast
Sub TLV Len : 12 R2 is its neighbor R4 10.1.12.0/28
IF Addr : 10.1.12.1
Nbr IP : 10.1.12.2

2 — 3 — 57 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 57
4 Link-State Database
4.3 LSP advertised by R2 – Level 1

• Router R2 will generate and share the following LSP

LSP ID : R2.00-00 Level : L1
Sequence : 0x1 Checksum : 0x11a3 Lifetime : 848
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1L2 Max Area : 3
SysID Len : 6 Used Len : 286 Alloc Len : 1492
TLVs :
Area Addresses:
Area Address : (3) 49.0051
Supp Protocols:
Protocols : IPv4
IS-Hostname : R2
Router ID :
Router ID : 10.10.10.2
IS Neighbors : Topology (narrow metric):
Virtual Flag : 0 R1, R3 and R4 (the DIS) are
Default Metric: (I) 10 its neighbors
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : R1.00
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0 External Routing
Neighbor : R3.00 Domain
IS Neighbors : 20.20.20.0/24
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
R1 R2 R3
Point-to-point Point-to-point
Expense Metric: (I) 0
Error Metric : (I) 0 10.1.12.0/28
Neighbor : R4.01 Broadcast
R4 10.1.12.0/28

2 — 3 — 58 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 58
4 Link-State Database
4.3 LSP advertised by R2 – Level 1 [cont.]

• Router R2 will generate and share the following LSP

Internal Reach:
Default Metric: (I) 10 Internal IP reach: IP
Delay Metric : (I) 0 addresses of system, toR1
Expense Metric: (I) 0 and toR4 interfaces
Error Metric : (I) 0
IP Address : 10.1.12.0
IP Mask : 255.255.255.240
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.23.0
IP Mask : 255.255.255.240
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.24.0
IP Mask : 255.255.255.240
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.10.10.2
IP Mask : 255.255.255.255
External Reach: External Routing
Default Metric: (I) 0 Domain
Delay Metric : (I) 0 External IP reach 20.20.20.0/24
Expense Metric: (I) 0
Error Metric : (I) 0 R1 R2 R3
IP Address : 20.20.20.1 Point-to-point Point-to-point
IP Mask : 255.255.255.255
I/F Addresses : 10.1.12.0/28
I/F Address : 10.10.10.2 Broadcast
I/F Address : 10.1.12.2 R4 10.1.12.0/28
I/F Address : 10.1.23.2
I/F Address : 10.1.24.2

2 — 3 — 59 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 59
4 Link-State Database
4.3 LSP advertised by R2 – Level 1 [cont.]

• Router R2 will generate and share the following LSP

TE IS Nbrs :
Nbr : R1.00 Topology (wide metric):
Default Metric : 10 R1, R3 and R4 (the DIS)
Sub TLV Len : 12
IF Addr : 10.1.12.2 are its neighbors
Nbr IP : 10.1.12.1
TE IS Nbrs :
Nbr : R3.00
Default Metric : 10
Sub TLV Len : 12
IF Addr : 10.1.23.2
Nbr IP : 10.1.23.3
TE IS Nbrs :
Nbr : R4.01
Default Metric : 10
Sub TLV Len : 6
IF Addr : 10.1.24.2
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 28
Prefix : 10.1.12.0
Default Metric : 10
Control Info: , prefLen 28
Prefix : 10.1.23.0
Default Metric : 10 External Routing
Control Info: , prefLen 28 Domain
Prefix : 10.1.24.0 20.20.20.0/24
Default Metric : 0
Control Info: , prefLen 32 R1 R2 R3
Prefix : 20.20.20.1 Point-to-point Point-to-point
Default Metric : 0
Control Info: , prefLen 32 10.1.12.0/28
Prefix : 10.10.10.2 Broadcast
R4 10.1.12.0/28

2 — 3 — 60 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 60
4 Link-State Database
4.4 LSP advertised by R2 – Level 2

• Router R2 will generate the following LSP, but it will not share it
because there are no other L2-capable routers
LSP ID : R2.00-00 Level : L2
Sequence : 0x4 Checksum : 0x8797 Lifetime : 888
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3
SysID Len : 6 Used Len : 215 Alloc Len : 1492
TLVs :
Area Addresses:
Area Address : (3) 49.0051
Supp Protocols: No topology information because
Protocols
IS-Hostname
: IPv4
: R2
it has no L2 neighbors
Router ID :
Router ID : 10.10.10.2 Internal IP reach: IP External prefixes not
Internal Reach:
Default Metric: (I) 10 addresses of all known advertised into L2 by default
Delay Metric : (I) 0 subnets in its area (an export policy is needed)
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.12.0
IP Mask : 255.255.255.240
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0 External Routing
Error Metric : (I) 0 Domain
IP Address : 10.1.23.0 20.20.20.0/24
IP Mask : 255.255.255.240
Default Metric: (I) 10
Delay Metric : (I) 0 R1 R2 R3
Point-to-point Point-to-point
Expense Metric: (I) 0
Error Metric : (I) 0 10.1.12.0/28
IP Address : 10.1.24.0 Broadcast
IP Mask : 255.255.255.240 R4 10.1.12.0/28

2 — 3 — 61 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 61
4 Link-State Database
4.4 LSP advertised by R2 – Level 2 [cont.]
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0 Internal IP reach: IP
Error Metric : (I) 0 addresses of all known
IP Address : 10.10.10.1
IP Mask : 255.255.255.255 subnets in its area
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.10.10.3
IP Mask : 255.255.255.255
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.10.10.4
IP Mask : 255.255.255.255
I/F Addresses : External prefixes not
I/F Address : 10.10.10.2 advertised into L2 by default
I/F Address : 10.1.12.2
I/F Address : 10.1.23.2 (an export policy is needed)
I/F Address : 10.1.24.2

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Broadcast
R4 10.1.12.0/28

2 — 3 — 62 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 62
4 Link-State Database
4.5 LSP advertised by R3

• Router R3 will generate and share the following LSP

LSP ID : R3.00-00 Level : L1
Sequence : 0x2 Checksum : 0xf412 Lifetime : 741
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1 Max Area : 3
SysID Len : 6 Used Len : 141 Alloc Len : 1492
TLVs :
Area Addresses:
Area Address : (3) 49.0051
Supp Protocols:
Protocols : IPv4
IS-Hostname : R3
Router ID :
Router ID : 10.10.10.3
IS Neighbors : Topology (narrow metric):
Virtual Flag : 0 R2 is its neighbor
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : R2.00
Internal Reach: Internal IP reach: IP
Default Metric: (I) 10 address of system interface
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0 External Routing
IP Address : 10.1.23.0 Domain
IP Mask : 255.255.255.240 20.20.20.0/24
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0 R1 R2 R3
Point-to-point Point-to-point
Error Metric : (I) 0
IP Address : 10.10.10.3 10.1.12.0/28
IP Mask : 255.255.255.255 Broadcast
R4 10.1.12.0/28
Continued…

2 — 3 — 63 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 63
4 Link-State Database
4.5 LSP advertised by R3 [cont.]

• Router R3 will generate and share the following LSP

I/F Addresses :
I/F Address : 10.10.10.3
I/F Address : 10.1.23.3
TE IS Nbrs :
Nbr : R2.00
Default Metric : 10 Topology (wide metric):
Sub TLV Len : 12
IF Addr : 10.1.23.3 R2 is its neighbor
Nbr IP : 10.1.23.2
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 28
Prefix : 10.1.23.0
Default Metric : 0 Topology (narrow metric):
Control Info: , prefLen 32 R2 is its neighbor
Prefix : 10.10.10.3

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Broadcast
R4 10.1.12.0/28

2 — 3 — 64 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 64
4 Link-State Database
4.6 LSP advertised by R4

• Router R4 will generate and share the following LSP

LSP ID : R4.00-00 Level : L1
Sequence : 0x4 Checksum : 0x240b Lifetime : 932
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1 Max Area : 3
SysID Len : 6 Used Len : 135 Alloc Len : 1492
TLVs :
Area Addresses:
Area Address : (3) 49.0051
Supp Protocols:
Protocols : IPv4
IS-Hostname : R4
Router ID :
Router ID : 10.10.10.4 Topology (narrow metric):
IS Neighbors :
Virtual Flag : 0 the DIS (the pseudo-node)
Default Metric: (I) 10 is its neighbor
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0 Internal IP reach: IP
Neighbor : R4.01
Internal Reach: addresses of system and
Default Metric: (I) 10 toR2 interfaces
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0 External Routing
IP Address : 10.1.24.0 Domain
IP Mask : 255.255.255.240 20.20.20.0/24
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0 R1 R2 R3
Point-to-point Point-to-point
Error Metric : (I) 0
IP Address : 10.10.10.4 10.1.12.0/28
IP Mask : 255.255.255.255 Pseudo-node Broadcast
R4 10.1.12.0/28

2 — 3 — 65 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 65
4 Link-State Database
4.6 LSP advertised by R4 [cont.]

• Router R4 will generate and share the following LSP

I/F Addresses :
I/F Address : 10.10.10.4
I/F Address : 10.1.24.4
TE IS Nbrs :
Nbr : P4.01
Default Metric : 10
Sub TLV Len : 6
Topology (wide metric):
IF Addr : 10.1.24.4 the DIS (the pseudo-node)
TE IP Reach : is its neighbor
Default Metric : 10
Control Info: , prefLen 28
Prefix : 10.1.24.0
Default Metric : 0
Control Info: , prefLen 32
Prefix : 10.10.10.4

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Pseudo-node Broadcast
R4 10.1.12.0/28

2 — 3 — 66 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 66
4 Link-State Database
4.6 LSP advertised by R4 [cont.]

• As the DIS, R4 will generate another LSP acting as the pseudo-node

LSP ID : R4.01-00 Level : L1
Sequence : 0x3 Checksum : 0x7bb3 Lifetime : 917
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1 Max Area : 3
SysID Len : 6 Used Len : 81 Alloc Len : 1492

TLVs :
IS Neighbors : Topology (narrow metric):
Virtual Flag : 0 R2 and R4 are its neighbors
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : R4.00
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : R2.00 Topology (wide metric):
TE IS Nbrs : R2 and R4 are its neighbors
Nbr : R4.00
Default Metric : 0
Sub TLV Len : 0 External Routing
TE IS Nbrs : Domain
Nbr : R2.00 20.20.20.0/24
Default Metric : 0
Sub TLV Len : 0 R1 R2 R3
Point-to-point Point-to-point
10.1.12.0/28
Pseudo-node Broadcast
R4 10.1.12.0/28

2 — 3 — 67 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 67
4 Link-State Database
4.7 Route table

• Each router will be aware of all prefixes that exist within the area
• Note that the next hop to reach all IPv4 prefixes learned through IS-IS
is identified by the configured interface address (to-Px)of a
neighboring router.
R2# show router route-table

===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.1.12.0/28 Local Local 06d04h03m 0
to-R1 0
10.1.23.0/28 Local Local 11d06h08m 0
to-R3 0
10.1.24.0/28 Local Local 11d06h08m 0
to-R4 0
10.10.10.1/32 Remote ISIS 00h32m38s 15
10.1.12.1 10
10.10.10.2/32 Local Local 11d06h14m 0
system 0
10.10.10.3/32 Remote ISIS 00h32m38s 15
10.1.23.3 10
10.10.10.4/32 Remote ISIS 00h32m37s 15
10.1.24.4 10
20.20.20.1/32 Local Local 06d02h18m 0
loop1 0
-------------------------------------------------------------------------------
No. of Routes: 8

2 — 3 — 68 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 68
 5 Case Study – Multiple Areas

2 — 3 — 69 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 69
5 Case Study – Multiple Areas
5.1 Topology of Reference

Router System IP Level

Name Address capability
R1 10.10.10.1 L1/L2
R2 10.10.10.2 L1/L2
R3 10.10.10.3 L1
R4 10.10.10.4 L1
R5 10.10.10.5 L1
External Routing
Domain
Area Routers 20.20.20.0/24

49.0051 R1 and R5
R1 R2 R3
49.0052 R2, R3 and R4 Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 70 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 70
5 Case Study – Multiple Areas
5.2 Router configuration – R1
#---------------------------------- #--------------------------------------
echo "IP Configuration" echo "ISIS Configuration"
#---------------------------------- #--------------------------------------
interface "system"
address 10.10.10.1/32
isis
area-id 49.0051
Link metric changed to
no shutdown reference-bandwidth 100000000 using reference bandwidth
exit level 1 wide-metrics-only
interface "toR2" level 2 wide-metrics-only
port 1/1/2 level-capability level-1/2
address 10.1.12.1/28 interface "system"
no shutdown interface-type point-to-point
exit no shutdown
interface "toR5" exit
port 1/1/1 interface "toR2"
address 10.1.15.1/28 interface-type point-to-point
no shutdown no shutdown
exit exit
router-id 10.10.10.1 interface "toR5"
interface-type point-to-point
no shutdown
exit
no shutdown
exit External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 71 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 71
 5 Case Study – Multiple Areas
5.3 Router configuration – R5
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.5/32
no shutdown
exit
interface "toR1"
port 1/1/1
address 10.1.15.5/28
no shutdown
exit
router-id 10.10.10.5
#------------------------------------------
echo "ISIS Configuration"
#------------------------------------------
isis
level-capability level-1
area-id 49.0051
reference-bandwidth 100000000
level 1 wide-metrics-only Link metric changed to
interface "system"
interface-type point-to-point using reference bandwidth External Routing
no shutdown Domain
exit 20.20.20.0/24
interface "toR1"
interface-type point-to-point
no shutdown
exit
no shutdown R1 R2 R3
exit
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 72 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Note that interface toR1 is not assigned a global unicast IPv4 address.

Note also that interface toR1 is configured inside IS-IS as point-to-point.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 72
 5 Case Study – Multiple Areas
5.4 Router configuration – R2
#----------------------------------- #------------------------------------- The external prefix will be
echo "IP Configuration" echo "ISIS Configuration" advertised in its level-2 LSP
#----------------------------------- #-------------------------------------
interface "loop1" isis (policy changed)
loopback area-id 49.0052
address 20.20.20.1/32 export "from-direct-to-isis" Link metric changed to
exit reference-bandwidth 100000000
interface "system" level 1 wide-metrics-only using reference bandwidth
address 10.10.10.2/32 level 2 wide-metrics-only
no shutdown level-capability level-1/2
exit interface "system"
interface "toR1" interface-type point-to-point
port 1/1/2 no shutdown
address 10.1.12.2/28 exit
no shutdown interface "toR1"
exit interface-type point-to-point
interface "toR3" no shutdown
port 1/1/3 exit
address 10.1.23.2/28 interface "toR3"
no shutdown interface-type point-to-point
exit no shutdown
interface "toR4" exit
port 1/1/1 interface "toR4" External Routing
address 10.1.24.2/28 interface-type point-to-point Domain
no shutdown no shutdown 20.20.20.0/24
exit exit
router-id 10.10.10.2 no shutdown
exit

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 73 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Note also that all interfaces, toR1, toR3 and toR4, are now configured inside IS-IS as point-to-point.
Lastly, interface loop1 plays the role of an external network that is advertised into IS-IS by R2 via an export
policy. The export policy has been changed to advertise the prefix in its level-2 LSP. The export policy is
shown below:
#--------------------------------------------------
echo "Policy Configuration"
#--------------------------------------------------
policy-options
begin
prefix-list "only-loop1"
prefix 20.20.20.0/24 longer
exit
policy-statement "from-direct-to-isis"
entry 10
from
protocol direct
prefix-list "only-loop1"
exit
to
protocol isis
level 2
exit
action accept
exit
exit
exit
commit
exit

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 73
5 Case Study – Multiple Areas
5.5 Router configuration – R3
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.3/32
no shutdown
exit
interface "toR2"
port 1/1/3
address 10.1.23.3/28
no shutdown
exit
router-id 10.10.10.3
#------------------------------------------
echo "ISIS Configuration"
#------------------------------------------
isis
level-capability level-1 Link metric changed to
area-id 49.0052
reference-bandwidth 100000000 using reference bandwidth
level 1 wide-metrics-only
interface "system"
interface-type point-to-point External Routing
no shutdown Domain
exit 20.20.20.0/24
interface "toR2"
interface-type point-to-point
no shutdown
exit
no shutdown R1 R2 R3
exit
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 74 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 74
5 Case Study – Multiple Areas
5.6 Router configuration – R4
#------------------------------------------
echo "IP Configuration"
#------------------------------------------
interface "system"
address 10.10.10.4/32
no shutdown
exit
interface "toR2"
port 1/1/1
address 10.1.24.4/28
no shutdown
exit
router-id 10.10.10.4
#------------------------------------------
echo "ISIS Configuration"
#------------------------------------------
isis
level-capability level-1
area-id 49.0052 Link metric changed to
reference-bandwidth 100000000 using reference bandwidth
level 1 wide-metrics-only
exit
interface "system" External Routing
interface-type point-to-point Domain
no shutdown 20.20.20.0/24
exit
interface "toR2"
interface-type point-to-point
no shutdown
exit R1 R2 R3
no shutdown
exit Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 75 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 75
 6 Link-State Databases

2 — 3 — 76 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 76
 6 Link-State Databases
6.1 Link-State Database for Area 49.0051

• The LSPs that will be visible to routers in area 49.0051 are shown below
(details follow)
• ATT indicates that other L1 routers within the same area that it is also
L2-capable.
R1# show router isis database level 1

==============================================================================
ISIS Database
==============================================================================
LSP ID Sequence Checksum Lifetime Attributes
------------------------------------------------------------------------

Displaying Level 1 database R1 advertises itself

------------------------------------------------------------------------ as attached
R1.00-00 0x76 0x5670 1143 L1L2 ATT
R5.00-00 0xa 0xb0f2 1139 L1
Level (1) LSP Count : 2
============================================================================== External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 77 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

The fact that R1 advertises itself as attached indicates other L1 routers within the same area that it is also
L2-capable and that there are other areas in the IS-IS domain.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 77
6 Link-State Databases
6.2 LSP advertised by R1 – Level 1

• Router R1 will generate and share the following LSP

LSP ID : R1.00-00 Level : L1
Sequence : 0x77 Checksum : 0x5471 Lifetime : 1121
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1L2 ATT Max Area : 3
SysID Len : 6 Used Len : 114 Alloc Len : 1492
TLVs :
Area Addresses:
Area Address : (3) 49.0051
Supp Protocols:
Protocols : IPv4
IS-Hostname : R1
Router ID :
Router ID : 10.10.10.1
I/F Addresses :
I/F Address : 10.10.10.1
I/F Address : 10.1.12.1
I/F Address : 10.1.15.1 Topology (wide metric only):
TE IS Nbrs : R5 is its neighbor
Nbr : R5.00
Default Metric : 100
Sub TLV Len : 12
IF Addr : 10.1.15.1
Nbr IP : 10.1.15.5
TE IP Reach : External Routing
Default Metric : 100 Domain
Control Info: , prefLen 28 20.20.20.0/24
Prefix : 10.1.12.0
Default Metric : 100
Control Info: , prefLen 28 R1 R2 R3
Prefix : 10.1.15.0 Internal IP reach: IP Point-to-point Point-to-point
Default Metric : 0
Control Info: , prefLen 32 address of system interface
Prefix : 10.10.10.1 Point-to-point Point-to-point
R5 R4

2 — 3 — 78 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 78
6 Link-State Databases
6.3 LSP advertised by R5

• Router R5 will generate and share the following LSP

LSP ID : R5.00-00 Level : L1
Sequence : 0xb Checksum : 0xaef3 Lifetime : 801
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1 Max Area : 3
SysID Len : 6 Used Len : 102 Alloc Len : 1492
TLVs :
Area Addresses:
Area Address : (3) 49.0051
Supp Protocols:
Protocols : IPv4
IS-Hostname : R5
Router ID :
Router ID : 10.10.10.5
I/F Addresses :
I/F Address : 10.10.10.5
I/F Address : 10.1.15.5 Topology (wide metric only):
TE IS Nbrs :
Nbr : R1.00 R1 is its neighbor
Default Metric : 100
Sub TLV Len : 12
IF Addr : 10.1.15.5
Nbr IP : 10.1.15.1
TE IP Reach :
Default Metric : 100 Internal IP reach: IP External Routing
Control Info: , prefLen 28 Domain
Prefix : 10.1.15.0
address of system interface 20.20.20.0/24
Default Metric : 0
Control Info: , prefLen 32
Prefix : 10.10.10.5 R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 79 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 79
 6 Link-State Databases
6.4 Link-State Database for Area 49.0052

• The LSPs that will be visible to routers in area 49.0052 are shown below
(details follow)
R3# show router isis database level 1

========================================================================
ISIS Database
========================================================================
LSP ID Sequence Checksum Lifetime
Attributes
------------------------------------------------------------------------

Displaying Level 1 database

------------------------------------------------------------------------ R2 advertises itself
R2.00-00 0x7e 0x6e3f 674 L1L2 ATT as attached
R3.00-00 0x78 0xfc65 900 L1
R4.00-00 0x7a 0xf9b1 559 L1
Level (1) LSP Count : 3
======================================================================

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 80 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

The fact that R2 advertises itself as attached indicates other L1 routers within the same area that it is also
L2-capable and that there are other areas in the IS-IS domain.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 80
6 Link-State Databases
6.5 LSP advertised by R2 – Level 1

• Router R2 will generate and share the following LSP

LSP ID : R2.00-00 Level : L1
Sequence : 0x7e Checksum : 0x6e3f Lifetime : 618
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1L2 ATT Max Area : 3
SysID Len : 6 Used Len : 152 Alloc Len : 1492 Internal IP reach: IP
TLVs : address of system interface
Area Addresses:
Area Address : (3) 49.0052
Supp Protocols:
Protocols : IPv4
IS-Hostname : R2
Router ID :
Router ID : 10.10.10.2
I/F Addresses :
I/F Address : 10.10.10.2
I/F Address : 10.1.12.2
I/F Address : 10.1.23.2
I/F Address : 10.1.24.2
TE IS Nbrs :
Nbr : R3.00
Default Metric : 100
Sub TLV Len : 12
IF Addr : 10.1.23.2 Topology (wide metric only): External Routing
Nbr IP
TE IS Nbrs
: 10.1.23.3
:
R3 and R4 are its neighbors Domain
Nbr : R4.00 20.20.20.0/24
Default Metric : 100
Sub TLV Len : 12 R1 R2 R3
IF Addr : 10.1.24.2
Nbr IP : 10.1.24.4 Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 81 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 81
6 Link-State Databases
6.6 LSP advertised by R2 – Level 1 (continued)

• Router R2 will generate and share the following LSP

TE IP Reach :
Default Metric : 100 Internal IP reach: IP
Control Info: , prefLen 28 address of system interface
Prefix : 10.1.12.0
Default Metric : 100
Control Info: , prefLen 28
Prefix : 10.1.23.0
Default Metric : 100
Control Info: , prefLen 28
Prefix : 10.1.24.0
Default Metric : 0
Control Info: , prefLen 32
Prefix : 10.10.10.2

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 82 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 82
6 Link-State Databases
6.7 LSP advertised by R3

• Router R3 will generate and share the following LSP

LSP ID : R3.00-00 Level : L1
Sequence : 0x7a Checksum : 0xf867 Lifetime : 904
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1 Max Area : 3
SysID Len : 6 Used Len : 101 Alloc Len : 1492

TLVs :
Area Addresses:
Area Address : (3) 49.0052
Supp Protocols:
Protocols : IPv4
IS-Hostname : R3
Router ID :
Router ID : 10.10.10.3
I/F Addresses :
I/F Address : 10.10.10.3
I/F Address : 10.1.23.3
TE IS Nbrs :
Nbr : R2.00 Topology (wide metric only):
Default Metric : 100
Sub TLV Len : 12 R2 is its neighbor
IF Addr : 10.1.23.3
Nbr IP : 10.1.23.2
TE IP Reach : External Routing
Default Metric : 100 Domain
Control Info: , prefLen 28 20.20.20.0/24
Prefix : 10.1.23.0 Internal IP reach: IP
Default Metric : 0
Control Info: , prefLen 32 address of system interface R1 R2 R3
Prefix : 10.10.10.3 Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 83 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 83
6 Link-State Databases
6.8 LSP advertised by R4

• Router R4 will generate and share the following LSP

LSP ID : R4.00-00 Level : L1
Sequence : 0x7d Checksum : 0xf3b4 Lifetime : 979
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1 Max Area : 3
SysID Len : 6 Used Len : 141 Alloc Len : 1492

TLVs :
Area Addresses:
Area Address : (3) 49.0052
Supp Protocols:
Protocols : IPv4
IS-Hostname : R4
Router ID :
Router ID : 10.10.10.4
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 63
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P2.00
Internal Reach:
Default Metric: (I) 63
Delay Metric : (I) 0 External Routing
Expense Metric: (I) 0 Domain
Error Metric : (I) 0 20.20.20.0/24
IP Address : 10.1.24.0 Internal IP reach: IP
IP Mask : 255.255.255.240 address of system interface
Default Metric: (I) 0 R1 R2 R3
Delay Metric : (I) 0
Expense Metric: (I) 0 Point-to-point Point-to-point
Error Metric : (I) 0
IP Address : 10.10.10.4
IP Mask : 255.255.255.255 Point-to-point Point-to-point
R5 R4

2 — 3 — 84 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 84
6 Link-State Databases
6.8 LSP advertised by R4 [cont.]

• Router R4 will generate and share the following LSP

I/F Addresses :
I/F Address : 10.10.10.4
I/F Address : 10.1.24.4
TE IS Nbrs :
Nbr : R2.00
Default Metric : 63 Topology (wide metric only):
Sub TLV Len : 12
IF Addr : 10.1.24.4 R2 is its neighbor
Nbr IP : 10.1.24.2
TE IP Reach :
Default Metric : 63
Control Info: , prefLen 28
Prefix : 10.1.24.0
Default Metric : 0
Control Info: , prefLen 32
Prefix : 10.10.10.4

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 85 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 85
6 Link-State Databases
6.9 Link-State Database for the Level-2 Backbone

• The LSPs that will be visible to L2-capable routers are shown below
(details follow)
R1# show router isis database level 2

========================================================================
ISIS Database
========================================================================
LSP ID Sequence Checksum Lifetime
Attributes
------------------------------------------------------------------------

Displaying Level 2 database

------------------------------------------------------------------------
R1.00-00 0x7 0xacec 589 L1L2
R2.00-00 0x8a 0x6ea6 1163 L1L2
Level (2) LSP Count : 2
======================================================================

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 86 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 86
6 Link-State Databases
6.10 LSP advertised by R1 – Level 2

• Router R1 will generate and share the following LSP

LSP ID : R1.00-00 Level : L2
Sequence : 0x8 Checksum : 0xaaed Lifetime : 1095
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3
SysID Len : 6 Used Len : 123 Alloc Len : 1492

TLVs :
Area Addresses:
Area Address : (3) 49.0051
Supp Protocols:
Protocols : IPv4
IS-Hostname : R1
Router ID :
Router ID : 10.10.10.1
I/F Addresses :
I/F Address : 10.10.10.1
I/F Address : 10.1.12.1
I/F Address : 10.1.15.1
TE IS Nbrs :
Nbr : R2.00 Topology (wide metric only):
Default Metric : 100 R2 is its neighbor
Sub TLV Len : 12
IF Addr : 10.1.12.1
Nbr IP : 10.1.12.2
TE IP Reach : External Routing
Default Metric : 100 Domain
Control Info: , prefLen 28 20.20.20.0/24
Prefix : 10.1.12.0
Default Metric : 100
Control Info: , prefLen 28 R1 R2 R3
Prefix : 10.1.15.0 Internal IP reach: IP Point-to-point Point-to-point
Default Metric : 0 addresses of all known
Control Info: , prefLen 32
Prefix : 10.10.10.1 subnets in its area Point-to-point Point-to-point
Default Metric : 100 R5 R4
Control Info: , prefLen 32
Prefix : 10.10.10.5

2 — 3 — 87 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 87
6 Link-State Databases
6.11 LSP advertised by R2 – Level 2

• Router R2 will generate and share the following LSP

LSP ID : R2.00-00 Level : L2
Sequence : 0x8a Checksum : 0x6ea6 Lifetime : 938
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3
SysID Len : 6 Used Len : 154 Alloc Len : 1492

TLVs :
Area Addresses:
Area Address : (3) 49.0052
Supp Protocols:
Protocols : IPv4
IS-Hostname : R2
Router ID :
Router ID : 10.10.10.2
I/F Addresses :
I/F Address : 10.10.10.2
I/F Address : 10.1.12.2
I/F Address : 10.1.23.2
I/F Address : 10.1.24.2
TE IS Nbrs : Topology (wide metric only):
Nbr : P1.00 R1 is its neighbor
Default Metric : 100
Sub TLV Len : 12
IF Addr : 10.1.12.2
Nbr IP : 10.1.12.1 External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 88 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 88
6 Link-State Databases
6.11 LSP advertised by R2 – Level 2 [cont.]

• Router R2 will generate and share the following LSP

TE IP Reach : Internal IP reach: IP
Default Metric : 100
Control Info: , prefLen 28 addresses of all known
Prefix : 10.1.12.0 subnets in its area
Default Metric : 100
Control Info: , prefLen 28
Prefix : 10.1.23.0
Default Metric : 100
Control Info: , prefLen 28
Prefix : 10.1.24.0
Default Metric : 0
Control Info: , prefLen 32 External IP reach: IP address
Prefix
Default
: 20.20.20.1
Metric : 0
of external subnetwork
Control Info: , prefLen 32 (advertised into L2 by policy)
Prefix : 10.10.10.2
Default Metric : 100
Control Info: , prefLen 32
Prefix : 10.10.10.3
Default Metric : 100
Control Info: , prefLen 32
Prefix : 10.10.10.4

External Routing
Domain
20.20.20.0/24

R1 R2 R3
Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 89 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 89
6 Link-State Databases
6.12 Route table

• L1-only routers, such as R5, will only be aware of prefixes directly

attached to routers within its own area
• For all unknown prefixes, it will install a default route that points to an
attached router within its area (R1)
R5# show router route-table

===============================================================================
IPv4 Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
0.0.0.0/0 Remote ISIS 01h07m35s 15
10.1.15.1 100
10.1.12.0/28 Remote ISIS 01h49m41s 15
10.1.15.1 200
10.1.15.0/28 Local Local 01h49m47s 0
to-R1 0
10.10.10.1/32 Remote ISIS 01h49m41s 15 External Routing
10.1.15.1 100 Domain
10.10.10.5/32 Local Local 12d01h39m 0 20.20.20.0/24
system 0
R1
------------------------------------------------------------------------------- R2 R3
No. of Routes: 5 Point-to-point Point-to-point

Point-to-point Point-to-point
R5 R4

2 — 3 — 90 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 90
6 Link-State Databases
6.12 Route table [cont.]

• The same applies to R3 and R4

• For all unknown prefixes, they will install a default route that points to
an attached router within its area (R2)
R3# show router route-table

===============================================================================
IPv4 Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
0.0.0.0/0 Remote ISIS 01h11m19s 15
10.1.23.2 100
10.1.12.0/28 Remote ISIS 01h46m15s 15
10.1.23.2 200
10.1.23.0/28 Local Local 12d01h38m 0
to-R2 0
10.1.24.0/28 Remote ISIS 01h46m15s 15
10.1.23.2 200
10.10.10.2/32 Remote ISIS 01h46m15s 15
10.1.23.2 100 External Routing
10.10.10.3/32 Local Local 12d01h43m 0 Domain
system 0 20.20.20.0/24
10.10.10.4/32 Remote ISIS 01h43m49s 15
10.1.23.2 R1 R2 R3
-------------------------------------------------------------------------------
Point-to-point Point-to-point
No. of Routes: 7

Point-to-point Point-to-point
R5 R4

2 — 3 — 91 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 91
6 Link-State Databases
6.12 Route table [cont.]

• L2-capable routers, such as R1 and R2, will be aware of all prefixes

regardless of the area where they reside
R1# show router route-table

===============================================================================
IPv4 Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.1.12.0/28 Local Local 06d21h03m 0
to-R2 0
10.1.15.0/28 Local Local 02h08m13s 0
to-R5 0
10.1.23.0/28 Remote ISIS 01h17m44s 18
10.1.12.2 200
10.1.24.0/28 Remote ISIS 01h17m44s 18
10.1.12.2 200
10.10.10.1/32 Local Local 12d01h50m 0
system 0
10.10.10.2/32 Remote ISIS 01h17m44s 18
10.1.12.2 100
10.10.10.3/32 Remote ISIS 01h17m44s 18
10.1.12.2 200
10.10.10.4/32 Remote ISIS 01h17m44s 18
10.1.12.2 200
10.10.10.5/32 Remote ISIS 01h17m44s 15
10.1.15.5 100
20.20.20.1/32 Remote ISIS 01h17m44s 18
10.1.12.2 100
-------------------------------------------------------------------------------
No. of Routes: 10

2 — 3 — 92 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 92
6 Link-State Databases
6.13 Lab 6 – IS-IS

2 — 3 — 93 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 93
Module summary

• IS-IS uses four message types: Hello, Partial Sequence Number PDU
(PSNP), Complete Sequence Number PDU (CSNP), Link-State PDU (LSP)
• An IS-IS speaker may be in any of three adjacency states at a given
time: Down, Initializing, Up
• Routers become fully adjacent after verifying two-way connectivity;
only then do they proceed to synchronize their respective link-state
databases
• There is only one type of LSP and it carries both topology and IP
connectivity information
• IS-IS has two hierarchical levels: Level 1 and Level 2
• L1 neighbors exchange area-specific information
• L2 neighbors exchange information that spans the entire routing domain

2 — 3 — 94 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 94
Module summary (continued)

2 — 3 — 95 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 95
References

2 — 3 — 96 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 96
End of module
IS-IS

2 — 3 — 97 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Internal Routing Protocol — IS-IS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 2.3 Edition N/A
Section 2 — Module 3 — Page 97
Learning experience powered by
Alcatel-Lucent University

Section 3
IP/MPLS
Module 1
MPLS Overview
TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

3—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 1
Blank page

3—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 2
Module objectives

Upon completion of this module, you should be able to describe:

Limitations of traditional IP routing and benefits of MPLS

MPLS terminology and concepts

MPLS data and control plane

Label signaling protocols: static, LDP, RSVP-TE

3—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 3
Module objectives [cont.]

3—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 4
 Table of Contents

1 — Limitations of Traditional IP Routing and benefits of MPLS 7

Page
2 — MPLS terminology and concepts 10
1—3— Limitations
MPLS controlof Traditional
planeIP Routing and benefits of MPLS 7 16
1.1 Limitations of Traditional IP Routing: Hyper-Aggregation 8
4 Benefits
1.2 — MPLS types
of MPLS 9 20
2 — MPLS terminology and concepts 10
2.1 MPLS: Terminology 11
2.2 MPLS: Basic operation 12
2.3 MPLS Label 13
2.4 MPLS Encapsulation: The Shim Header 14
2.5 Forwarding Equivalence Classes 15
3 — MPLS control plane 16
3.1 Static Label distribution 17
3.2 Dynamic Label distribution: Traffic/Control flow 19
4 — MPLS types 20
4.1 LDP Overview 21
4.2 RSVP-TE Overview 22
4.2 RSVP-TE Overview 23

3—1—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 5
Table of Contents [cont.]

3—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 6
 1 — Limitations of Traditional IP Routing and
benefits of MPLS

3—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 7
 1 — Limitations of Traditional IP Routing and benefits of MPLS
1.1 Limitations of Traditional IP Routing: Hyper-Aggregation

IP has a limited ability to alleviate hyper aggregation which leads to

network and link congestion

All network traffic will flow via the primary path

No traffic will use the Alternate Link  Inefficient use of resources

A Congestion -> packet loss ! B

Primary
Link

Alternate
Link

IGP
3—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

One of the major limitations in a classical IP routing network is that packets entering the network will
follow the IGP shortest path based on the metric calculations.

This implies that packets from different routers at side A that need to send traffic to side B over the IP
network, will follow the same path defined by the IGP topology. This can lead to congestion and under-
usage of other available resources. MPLS provides a whole array of tools to allow a network architect to
direct traffic over other paths depending on criteria such as bandwidth, link colors, hop limit and
manual configuration of the path preference.

The IP protocol alone is also unable to provide guaranteed service levels across a network end to end.
Certain applications may require a guaranteed amount of bandwidth and Service Providers want to be
able to offer service level agreements to their customers guaranteeing bandwidth and resource
availability.

Traditional IP routing protocols do not consider the available bandwidth in the network across the
primary or alternate links. This means that routers in the network are not aware if what bandwidth
resources are available over primary or alternate paths.

As shown in the example above, if all packets take the primary path the link may soon become
congested, resulting in packet loss.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 8
 1 — Limitations of Traditional IP Routing and benefits of MPLS
1.2 Benefits of MPLS
Exclude this link for
time-constrained
traffic

Congestion

IGP PATH

Use CSPF to avoid low

bandwidth links

MPLS PATH
Explicitly define the path

3—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Greater flexibility:
 Labeltagging allows forwarding along an explicitly defined path, which may be different from the
IGP path
 MPLS can find paths based on different criteria, e.g. bandwidth constraints, coloring constraints

Increased performance:
 MPLS offers improved network resiliency and recovery options compared to traditional IP networks
 Using
traffic engineering and techniques such as fast reroute, congestion and interruptions can be
reduced
 Paths can be set up manually or automatically in accordance to the set constraints

MPLS is independent of any IP routing protocol:

 The underlying routed infrastructure may be provided by any IGP

After path setup, data forwarding is done independently of the destination address.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 9
 2 — MPLS terminology and concepts

3 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 10
 2 — MPLS terminology and concepts
2.1 MPLS: Terminology

Multi Protocol Label Switching, MPLS:

• Allows the network operator to create end-to-end label-switched paths
(LSPs) for data forwarding, instead of using hop-by-hop IP routing
• Alleviates the limitations of traditional IP routing

LER: Label Edge Router LSP 1

LSR: Label Switch Router LSP 2

LSR
LSR

LSR
LER LSR
LER

3 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

MPLS provides the network administrator to create “tunnels” from the ingress to the egress of the MPLS
domain, usually a Provider’s network. These end-to-end tunnels alleviate the limitations of traditional
IP hop-by-hop routing, since the tunnel does not have to follow the path chosen by the IGP and it can be
created with certain characteristics such as bandwidth requirements, allowing SLAs to be defined.

Label Edge Router (LER)

An LER sits at the edge of an MPLS domain, either at the beginning (ingress) or end (egress) of a
Label Switched Path.

Label Switch Router (LSR)

A device that typically resides somewhere in the middle of an MPLS network and is capable of
forwarding datagrams based upon a label. An LSR will develop a Label Information Base (LIB) and a
Label Forwarding Information Base (LFIB) to switch packets according to the label value assigned to
the packet.

Label Switch Path (LSP)

A specific, unidirectional tunnel set up across the MPLS network between two LERs. Label Switch
Paths are established by network operators for a variety of purposes, such as to guarantee a certain
level of performance, to route around network congestion, or to create IP tunnels for network-based
virtual private networks.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 11
 2 — MPLS terminology and concepts
2.2 MPLS: Basic operation

Push Swap Swap Pop

LER LSR LSR LER

Label Switched Path

data label data label data label data data

IP Forwarding LABEL SWITCHING IP Forwarding

3 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

The MPLS LSPs are virtual “tunnels” created through the use of labels signalled between MPLS speaking
routers. Once a label is chosen at the ingress, the label header is put at the front of the packet header
so that the label value can be carried across the network with the packet. At each subsequent hop, the
Label Switch Router (LSR) simply looks up the label value in a table to make the forwarding decision,
there is no need to parse the IP header. Since the label is a fixed length, label look-up is fast and simple

MPLS performs three basic operations:

 Push - Puts a label onto the packet.
 Swap - Swaps or changes a label received at an ingress interface with a label at an egress interface
of the node. The label swapping is done in accordance to the Label Forwarding Information Base
(LFIB).
 Pop - Removes the label from the packet.
An LSR router can perform pop, push and swap operations. An LER can perform pop and push
operations.

Penultimate Hop Popping (PHP) pops a label one hop before the last node. This was initially done to
take some of the processing load off of the last router. This is not an issue anymore since most routers
can handle label popping at wire speed and the operation does not cause additional delays. Alcatel-
Lucent supports PHP but not if a node is the last hop. This means that the node does not initiate PHP
but will pop labels if requested to do so by the last router. This ensures interoperability of Alcatel-
Lucent systems with other vendor’s products.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 12
 2 — MPLS terminology and concepts
2.3 MPLS Label

Frame header Single Label

DA SA Type = MPLS IP IP Packet FCS

88 47 Header Header

Label Stack

Data Link MPLS MPLS IP Header IP Data FCS

Header Header 1 Header 2

4 Octets
Label Stack TTL
Label Exp. S
Entry Format
Label: Label Value, 20 bits
Exp.: Experimental, 3 bits (Class of Service)
S: Bottom of Stack, 1 bit (1 = last entry in label stack)
TTL: Time to Live, 8 bits

3 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Field Descriptions:

 Label: 20-bit field that carries the actual value of the label.
 Exp: This 3-bit field is reserved for experimental use. It is currently used for Class of Service(CoS).
 S: This bit is set to 1 for the last entry (bottom) in the label stack, and 0 for all other label stack
entries.
 TTL: This 8-bit field is used to encode a TTL value.

In MPLS, packets can carry not just one label, but a set of labels in a stack. An LSR can swap the label at
the top of the stack, pop the stack, or swap the label and push one or more labels into the stack. The
processing is always based on the top label, without regard for the possibility that some number of
other labels may have been above it in the past, or that some number of other labels may be below it at
present.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 13
 2 — MPLS terminology and concepts
2.4 MPLS Encapsulation: The Shim Header

Type = IP Type = IP
DA SA Payload FCS DA SA Payload
0800 0800 FCS

LSR LER Type = MPLS IP

DA SA 88 47 Header Payload FCS

LSR LSR Type = MPLS IP

DA SA 88 47 Header Payload FCS

LER LSR Type = MPLS IP

DA SA 88 47 Header Payload FCS

3 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

The MPLS label values are carried in an MPLS Shim header.

As defined by the Internet Assigned Numbers Authority (IANA) the Ethertype field of an Ethernet frame
must carry the following type codes to identify the payload of the frame.

Ethernet Description References

0x0800 Internet IP (IPv4) [IANA]

0x8847 MPLS Unicast [Rosen]
0x8848 MPLS Multicast [Rosen]

The MPLS encoding technique implementing the MPLS shim header.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 14
 2 — MPLS terminology and concepts
2.5 Forwarding Equivalence Classes

Forwarding Equivalence Class (FEC)

A group of IP packets forwarded in the same manner, over
the same path, with the same forwarding treatment B
A

Label Switched Path

MPLS packets are assigned to a FEC at the network ingress

FEC packets are transported by the LSP which has a label to identify it

Label switching is used to forward the labelled packet
3 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

The FEC is an important concept in MPLS. A FEC is any subset of packets that are forwarded in the same
way by a router. When a packet enters the MPLS network at the ingress node, the packet is mapped to a
particular FEC and forwarded in the same way across the network. Packets belonging to the same FEC
will get the same label.

When a packet enters the MPLS network at an iLER, the packet is mapped into a FEC. FEC assignment is
performed only once at the ingress, and the packet follows the LSP assigned to the FEC until network
egress.

Using MPLS, the aggregation of packet flows into FECs provides scalability that meets the demands of
the public Internet as well as enterprise applications.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 15
 3 — MPLS control plane

3 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 16
 3 — MPLS control plane
3.1 Static Label distribution

Static LSPs are manually configured on each LER/LSR

Labels are assigned on each router individually

Allows the creator to have full control on the path

Disadvantages:

Labour intensive operation

Changes need a reconfiguration on every node

No back-up or fast re-route

No support of label stacking

3 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

A static LSP specifies a static path and all routers that the LSP traverse must be configured manually
with labels. No signalling such as RSVP or LDP is required.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 17
 3 — MPLS control plane
3.1 Static Label distribution [cont.]

PE1# configure router mpls static-lsp

"PE-1 to PE-3"
to 3.3.3.3 PE2>config>router# mpls
push 999 nexthop 10.12.1.2 interface "tope1"
label-map 999
swap 998 nexthop 10.23.1.3
10.12.1.2

1.1.1.1/32 2.2.2.2/32
PE-1 (iLER) PE-2 (LSR)
10.23.1.3

Static LSP

Static LSP
PE-3 (eLER)
3.3.3.3/32

PE-4
4.4.4.4/32

PE3>config>router# mpls interface "tope2"

label-map 998
pop

3 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

The configuration above shows the static LSP configuration of PE-1. The static LSP transport tunnel is configured
to forward traffic across the provider core from PE1 to PE3.

The Static LSP is configured between these devices, from system address 1.1.1.1 to the device with system
address 3.3.3.3.

PE1 performs a PUSH operation and forwards the incoming packets to the next-hop address of 10.12.1.2, LSR2,
with a label of 999.

The transit LSRs perform SWAP operations and forward the packet to the manually defined next-hop.

PE3 performs a POP operation and forwards unlabeled packets external to the MPLS domain.

Note: An LSP is always unidirectional, therefore after the configurations shown above, only traffic from PE1 has
an LSP available to reach PE3, not the other way around.

These configuration steps demand the operator to log in and manually enter all the necessary commands in every
node, an extremely heavy task that can be accomplished by dynamic signalling protocols instead.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 18
 3 — MPLS control plane
3.2 Dynamic Label distribution: Traffic/Control flow

DATA LABEL DATA DATA

Data flow Data Plane

Data flow

Data traffic flows Downstream

LER1 LSR1 LER2

Control Plane

Label allocation flows Upstream

LABEL
(System Address)

Data packets flow in the downstream direction

Label bindings are distributed from the downstream to the upstream direction

3 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Terminology

Data packets flow in the downstream direction (data plane).

Control packets follow the upstream direction (control plane).

Label distribution
In the initial phase, LER2 is initiating the label distribution by sending a label advertisement message to
LER1 of its system address (FEC = system address). Label distribution is initiated at LER2 and follows the
upstream direction.

Data flow
After label distribution, data flows in the opposite direction of the label distribution path.
Packets flow from the ingress Label Edge Router (iLER) LER1 to the egress Label Edge Router (eLER), in
this case LER2.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 19
 4 — MPLS types

3 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 20
 4 MPLS types
4.1 LDP Overview

Label Distribution Protocol (LDP): This protocol is used to distribute labels

in an MPLS environment. LDP uses the underlying routing information
provided by IGP when building its Label Forward Information Base (LFIB).
The LFIB is used to make forwarding decisions of MPLS packets.
R1 R2
1.1.1.1/32 2.2.2.2/32
R1 --> R3: 10.1.12.0/28
Path chosen by IGP is
Metric: 10
R1->R2-> R3 due to the cost
being 20 (10+10).

10.1.14.0/28

10.1.23.0/28
Metric: 100

Metric: 10
MPLS packets will be forwarded
via the same path (R1->R2->R3).
10.1.34.0/28

Metric: 10
4.4.4.4/32 3.3.3.3/32
R4 R3

3 — 1 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

LDP will use the underlying routing information provided by IGP. In the example above, any packets destined to
R3 that are received by R1, will be forwarded via R2 (10.1.12.2 next-hop). Recall that IGP will use the most
optimal path to route a packet taking into account the metrics. In the example above, there are two paths for R1
to reach R3:

R1->R2->R3: Metric 20

R1->R4->R3: Metric 110

Now that the forwarding decision has been made by IGP, the LFIB will contain a label for R3’s prefix, 3.3.3.3/32,
with the next-hop being R2. R1 will also have another label for R4, but it will not be active (no next-hop
specified) since this is not the most optimal path. Once the MPLS packet is received by R2, it will again check its
LFIB and act as an LSR. It will check its LFIB for prefix 3.3.3.3/32, perform a swap action (remove label and add
new label), and forward packet via next-hop associated with label. R3 will now receive this packet, and pop the
label (remove MPLS header) and process the IP packet.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 21
 4 MPLS types
4.2 RSVP-TE Overview

Resource Reservation Protocol –Traffic Engineering (RSVP-TE) – This

protocol is also used to distribute labels in an MPLS environment. RSVP-TE
will use constraint parameters such as bandwidth, explicit hops, link
colouring and other user defined criteria instead of only the IGP routing
R2
information. R1
1.1.1.1/32 2.2.2.2/32

10.1.12.0/28
R1 --> R3:
Metric: 10
Path chosen by IGP is
R1->R2-> R3 due to the cost

10.1.14.0/28

10.1.23.0/28
Metric: 100

Metric: 10
being 20 (10+10).

MPLS packets will be forwarded

via a different path (R1->R4->R3)
10.1.34.0/28
due to configured explicit hop.
Metric: 10
4.4.4.4/32 3.3.3.3/32
R4 R3

3 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

RSVP-TE allows the establishment of Label Switched Paths (LSPs). When configuring a LSP, a path needs to be
specified. Now this path may be loose, meaning that there are no hops specified, in which it will use IGP routing
information (if no other constraints are specified) or the path may have strict hops configured. In the example
above, the path has a strict hop to R4, forcing the LSP to take a suboptimal path to R3. There are many reasons
to do this, one obvious example is if path R1->R2->R3 is heavily used for other purposes and R1->R4->R3 is not
used at all. Therefore setting a strict hop to R4 or traffic-engineering your network, can aid the network in using
all of its resources efficiently.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 22
End of module
MPLS Overview

3 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — MPLS Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.1 Edition N/A
Section 3 — Module 1 — Page 23
Learning experience powered by
Alcatel-Lucent University

Section 3
IP/MPLS
Module 2
LDP
TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

3—2—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 1
 Blank page

3—2—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 2
Module objectives

Upon completion of this module, you should be able to:

Describe the different label distribution mechanisms.

Understand the benefits of LDP.

Configuration of LDP.

3—2—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 3
Module objectives [cont.]

3—2—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 4
 Table of Contents

1 Label Distribution Protocol 7

Page

1 Label Distribution Protocol 7

1.1 LIB and LFIB 8
1.2 Label creation 9
1.3 Label binding to a FEC 10
1.4 Label binding to a FEC 11
1.5 Downstream Unsolicited Distribution Mode 12
1.6 Liberal Retention & Ordered Control Mode 13
1.7 IGP convergence 14
1.8 Minimum Configuration 15

3—2—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 5
Table of Contents [cont.]

3—2—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 6
 1 Label Distribution Protocol Overview

3—2—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 7
 1 Label Distribution Protocol Overview
1.1 Label binding to a FEC

LDP characteristics

Each LSR originates a label for its system address by default.

LDP relies on the underlying routing information provided by an IGP in order to
communicate label bindings to peers.

The router forwarding information base, or FIB, is responsible for determining the
hop-by-hop path through the network.

LER 1 LSR 2 LSR 3 LER 4

1/1/2 1/1/2 1/1/2 1/1/1

1/1/3 1/1/1 1/1/1 1/1/3
10.1.1.0/24 10.2.1.0/24
1.1.1.1/32 2.2.2.2/32 3.3.3.3/32 4.4.4.4/32

3—2—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

The industry defined two ways to bind a label to a FEC:

Advertise a label for each prefix in the routing table of the advertising router. This implies a large number of
labels in the MPLS network and may cause scalability issues.

Advertise a label per system address.

Alcatel-Lucent products advertise a label per system address as the default, resulting in fewer labels being used.

Once LDP neighbors have been established, each LDP enabled router originates a label for its system address, and
may originate a label for each FEC for which it has a next-hop that is external to the MPLS domain. To do this, an
export policy is required since by default Alcatel-Lucent generates a label for /32 addresses.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 8
 1 Label Distribution Protocol
1.2 Label creation

Labels are created based on the forwarding equivalence classes (FECs) created
through the layer 3 routing protocol. In order for label swapping to be
possible, common understanding of which FECs map to which labels must be
achieved between adjacent routers. The communication of label binding
information (such as the binding of an FEC to a specific label value) between
LSRs is accomplished by label distribution.

LER 1 LSR 2 LSR 3 LER 4

1/1/2 1/1/2 1/1/2 1/1/1

1/1/3 1/1/1 1/1/1 1/1/3
10.1.1.0/24 10.2.1.0/24
1.1.1.1/32 2.2.2.2/32 3.3.3.3/32 4.4.4.4/32

3—2—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

A router passes binding information to its peers after a specific label value is assigned to a FEC. The LER
receiving this binding information inserts the label value into the label information base associated with the
corresponding FEC.

The upstream LSR is then aware that if it is forwarding a packet associated with the particular FEC, it can use the
associated label value and the downstream LSR that the packet is forwarded to will recognize it as belonging to
that FEC. As this information is communicated along a chain of LSRs, a path will be set up along which a number
of hops can use label swapping and avoid the full layer 3 look-up.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 9
 1 Label Distribution Protocol
1.3 Example Label binding to a FEC

LER 1 LSR 2 LSR 3 LER 4

1/1/2 1/1/2 1/1/2 1/1/1

1/1/3 1/1/1 1/1/1 1/1/3
10.1.1.0/24 10.2.1.0/24
1.1.1.1/32 2.2.2.2/32 3.3.3.3/32 4.4.4.4/32
LER1 Prefix Operation Ing-Label Egr. Label Egr. Next-hop
• LER 1 LFIB Intf

1.1.1.1/32 Pop 131067 -- -- --

4.4.4.4/32 Push -- 131068 1/1/2 LSR2

• LSR 2 LSR2 Prefix Operation Ing-Label Egr. Label Egr. Next-hop

LFIB Intf

1.1.1.1/32 Swap 131067 131067 1/1/1 LER1

4.4.4.4/32 Swap 131068 131068 1/1/2 LSR3

LSR3 Prefix Operation Ing-Label Egr. Label Egr. Next-hop

• LSR 3 LFIB Intf

1.1.1.1/32 Swap 131067 131067 1/1/1 LSR2

4.4.4.4/32 Swap 131068 131071 1/1/2 LSR4

• LER 4 LER4 Prefix Operation Ing-Label Egr. Label Egr. Next-hop

LFIB Intf

1.1.1.1/32 Push -- 131067 1/1/3 LSR3

4.4.4.4/32 Pop 131071 -- -- --

3 — 2 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

The example on the slide above is simplified, since all the routers will have 4 prefixes (one for each router’s
system address). For proof of concept purposes, we will only focus on LER 1 and 4 and see how the labels are
propagated.

LER1:
1. If packet is received destined for 1.1.1.1/32 with ingress label 131067, it means that the label will be popped
(or removed) since it has arrived at its destination, LER1.
2. If a packet is received and destined for 4.4.4.4/32 from the 10.1.1.0/24 subnetwork, a label will be pushed
since the CE is not MPLS aware.

LSR 2 and 3:
1. If packet is received destined for 1.1.1.1/32, the label will be removed and a new one added (swap
operation) since this is not the destination.
2. If packet is received destined for 4.4.4.4/32, the label will be removed and a new one added (swap
operation) since this is not the destination.

LER 4:
1. If packet is received destined for 4.4.4.4/32 with ingress label 131071, it means that the label will be popped
(or removed) since it has arrived at its destination, LER4.
2. If a packet is received and destined for 1.1.1.1/32 from the 10.2.1.0/24 subnetwork, a label will be pushed
since the CE is not MPLS aware.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 10
 1 Label Distribution Protocol
1.4 LIB and LFIB

Table Meaning Contents Populated By

Name

RIB Routing Information Routing updates received Routing Protocol Exchange - Each routing
Base protocol has a separate RIB

FIB Forwarding Information Active routes RTM selects the active routes from all
Base protocol "Best" routes

LIB Label Information Base Locally generated and MPLS Label Exchange
received MPLS labels

LFIB Label Forwarding Labels used by the LSR The labels assigned to the active routes
Information Base (for each next-hop)

RIB OSPF
FIB
RIB IS-IS
LFIB

LIB LDP

3 — 2 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

The Label Information Base (LIB) is populated based on the label exchange process. The Label
Forwarding Information Base (LFIB) is built from the LIB and the Forwarding Information Base (FIB). The
LFIB contains only the labels that will be used for label switching packets. If a label is received from a
neighbor for a FEC, and the FIB contains a route for the same FEC for which the same neighbor is the
next-hop, then it is populated into the LFIB.

Difference Between the LIB/LFIB

The difference between the LIB and the LFIB is comparable to the difference between the Routing
Information Base (RIB) and the Forwarding Information Base (FIB) of a routing protocol.

RIB/FIB
In the RIB, all the routes learned by any routing protocol running on the router is stored in that specific
routing protocol RIB. The RIB is a collection of all the possibilities learned through a the routing
protocol. Out of all these possibilities only one route (no ECMP) can be used, and this route is selected
by the Route Table Manager (RTM) through the preference and metric procedures, and stored in the FIB.
In other words, the FIB represents the best routes of all the RIBs. The FIB has the actual outgoing port
defined where the traffic needs to be send.

LIB/LFIB
The LIB relates to the LFIB as the RIB relates to the FIB. The LIB contains all the labels learned while the
LFIB only stores the best label that will actually be used to forward traffic.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 11
 2 LDP Operation and Configuration

3 — 2 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 12
 2 LDP Operation and Configuration
2.1 Downstream Unsolicited Distribution Mode

Downstream: iLER
LIB
Prefix Next-hop Label
Advertising labels from downstream to the 3.3.3.3/32 LSR 2 131069
upstream direction.
3.3.3.3/32 LSR 3 131068

Unsolicited:
1.1.1.1/32 FEC:
2.2.2.2/32
Each LSR will originate a label for its 3.3.3.3/32
iLER LSR2
system address by default. Label mappings Label: 131069

are provided to all peers for which the local

LSR might be a next-hop, even when not
explicitly requested.
FEC: FEC:
3.3.3.3/32 3.3.3.3/32
Label: 131068 Label: 131071

LSR3
FEC: eLER
4.4.4.4/32 3.3.3.3/32
3.3.3.3/32
Label: 131071

3 — 2 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

The MPLS architecture allows an LSR to distribute label bindings to other LSRs that have not explicitly
requested them.

Downstream Unsolicited (DU) label distribution is not dependent on the data plane. Labels will be
generated and distributed strictly in the control plane prior to the arrival of any user originated traffic.

In Downstream Unsolicited mode, label mappings are provided to all peers for which the local LSR might
be a next-hop for a given FEC. This would typically be done at least once during the lifetime of a peer
relationship between adjacent LSRs. The label received from the router providing the active IGP route
for the FEC is used (from the best next-hop). In the example above, we see that iLER has two next-hops
to reach eLER 3.3.3.3/32. Keep in mind that only one label will be used (one egress interface) unless
ECMP is enabled. The egress interface is chosen based on the best IGP metrics.

Also, this technique allows the IGP routing topology to provide some level of redundancy should there
be any network issues. For example, should the router providing the active IGP route fail or the route
via that router become unavailable, once the IGP converged to a new active route (from another
router), the label for the FEC received from that peer will be immediately used.

The Alcatel-Lucent 7x50 family supports Downstream Unsolicited label distribution for LDP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 13
 2 LDP Operation and Configuration
2.2 Liberal Retention & Ordered Control Mode

Liberal Retention: Ordered Control:

The label received from the router The LSP will not pass data until the
providing the active IGP route for setup messages have propagated from
the FEC is used and the other labels end to end
are kept Label
2.2.2.2/32
131069
1.1.1.1/32 LSR2
iLER Prefix Next-hop Label
LIB iLER Step 2

3.3.3.3/32 LSR 2 131069

3.3.3.3/32 LSR 3 131068

Step 2
Label Label

Step 1
iLER 131068 131071
Prefix Next-hop
FIB
3.3.3.3/32 LSR 2

iLER Prefix Next-hop Label

LFIB
Step 1
3.3.3.3/32 LSR 2 131069 LSR3 eLER
Label
4.4.4.4/32 3.3.3.3/32
131071

3 — 2 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

This slide describes the Liberal Retention and Ordered Control modes:

Using Liberal Label Retention mode, all label mappings received from all peer LSRs are saved. This
approach consumes more memory on the LSR, but has the benefit of faster convergence. If the used
label is lost, a label for the same FEC may have been previously received from another peer and is
already present on the router, without the need for signaling.

In Ordered Control mode, LSP setup is initiated at one LSR and propagates from the eLER toward the
iLER. A feature of Ordered Control mode is that an LSP is not completely set up until the associated
control setup messages have propagated from end to end. As a consequence, data is not sent on the LSP
until it is known to be loop free.

Useful CLI commands:

•LIB – show router ldp bindings prefix <ip-prefix/ip-prefix-length>
•FIB – show router fib <slot-number>
•LFIB – show router ldp bindings active

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 14
 2 LDP Operation and Configuration
2.3 IGP convergence

LSP before the failure

LSP after the failure

1/1/2 LSR2
LSR4
1000
1/1/3

LER1 LER2
LSR1 10.10.10.1/32

LER 1 Prefix Ingress Egress Egress next-

LFIB Label Label Interface hop MPLS Convergence =
10.10.10.1/32 - 131068 1/1/2 LSR 2 Failure Detection Time +
IGP Convergence +
LER 1 Prefix Ingress Egress Egress next- LDP Convergence
LFIB Label Label Interface hop

10.10.10.1/32 - 131065 1/1/3 LSR 1

3 — 2 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

The IGP convergence requires a recalculation of the SPF algorithm and a new selection of the best
route. The IGP best route must then be offered to the Routing Table Manager (RTM) to determine if this
route is to be the active route and subsequently installed in the FIB.

In the use case shown on the slide, the new best and active route to the destination 10.10.10.1/32 is
the route via LSR1. LDP convergence may then follow. One benefit of liberal label retention mode is
that the label previously received from the new best route is already installed in the LIB. It has been
present all along, but until IGP routing converges, the LFIB may not be populated.

Now that IGP routing has converged, the LFIB may use the label from LSR2 since the next-hop now
belongs to the active route.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 15
 2 LDP Operation and Configuration
2.4 Minimum Configuration

PE1 P1 P2
PE2

Provider
Network

PE-3
P3

3 — 2 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

All interfaces that are facing the provider core must have LDP enabled. LDP must be enabled on each
router interface, to allow direct LDP sessions to be established between adjacent routers. Note that
LDP is not enabled on the router system interface.

This command enables the context to configure LDP interfaces and parameters applied to LDP
interfaces:

Context: config>router>ldp

Syntax: interface-parameters

This command enables LDP on the specified IP interface.

Context: config>router>ldp>if-params

Syntax: [no] interface ip-int-name

The no form of the command deletes the LDP interface and all configuration information associated
with the LDP interface. The LDP interface must be disabled using the shutdown command before it can
be deleted.

Parameters: ip-int-name - The name of an existing interface.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 16
 2 LDP Operation and Configuration
2.4 Minimum Configuration [cont.]

See below sample CLI configuration on PE1, as it peers with PE2 and PE3.

*A:PE1>config>router>ldp# info
----------------------------------------------
interface-parameters
interface "toPE2"
exit
interface "toPE3"
exit
exit
targeted-session
exit
----------------------------------------------
*A:PE1>config>router>ldp#

3 — 2 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

In CLI, LDP is configured under the “configure router ldp” context. Link interfaces are configured under
‘interface-parameters’ and target sessions under ‘targeted-session’.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 17
 Knowledge check

Determine whether each of the following statements is true or false:

a) The LDP works downstream on-demand.

b) The LFIB is used in the data plane.
c) The LDP does not rely on an IGP.

3 — 2 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) False
b) True
c) False

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 18
End of module
LDP

3 — 2 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — LDP
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.2 Edition N/A
Section 3 — Module 2 — Page 19
Learning experience powered by
Alcatel-Lucent University

Section 3
IP/MPLS
Module 3
RSVP-TE
TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

3—3—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 1
 Blank page

3—3—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 2
Module objectives

Upon completion of this module, you should be able to:

Explain the benefits of RSVP-TE.

List the different fast re-route options.

Identify the pros and cons of each fast re-route option.

Configure a basic LSP.

3—3—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 3
Module objectives [cont.]

3—3—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 4
 Table of Contents

1 RSVP-TE Introduction 7
Page
2 Traffic Engineering and Constraints 14
1 RSVP-TE Introduction
3 RSVP Fast Reroute 7 26
1.1 RSVP-TE characteristics 8
1.2 RSVP-TE message types 9
1.3 Label allocation 10
1.4 Optional object—Explicit Route Object (ERO) 11
1.5 Optional object—Record Route Object (RRO) 12
2 Traffic Engineering and Constraints 14
2.1 RSVP-TE: Alcatel-Lucent CSPF implementation 15
2.2 RSVP-TE: signaled LSPs with CSPF 16
2.3 RSVP-TE: LSP configuration 17
2.4 RSVP-TE: Strict and Loose hops 18
2.5 LSP redundancy 19
2.6 LSP with secondary path 20
2.7 Fast Reroute overview 21
2.8 RSVP-TE: LSP protection review 22
2.9 RSVP-TE: backup LSP—LSPs with Secondary Path 23
2.10 RSVP-TE: LSP Protection with a Secondary Path 24
3 RSVP Fast Reroute 26
3.1 One-to-one backup method —multiple LSPs 27
3.2 One-to-one backup method—path setup 28
3.3 One-to-one backup method—label exchange 29
3.43 —One-to-one
3—5
backup method—link or node failure 30
3.5IP/MPLS
Facility
— RSVP-TE backup method—link protection
7705 SAR — R6.0 Strategic Industries
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
31
3.6 Facility Backup—link protection label exchange 32
3.7 Facility backup—link failure 33

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 5
Table of Contents [cont.]

3—3—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 6
 1 RSVP-TE Introduction

3—3—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 7
 1 RSVP-TE Introduction
1.1 RSVP-TE characteristics

Advantage of using RSVP to establish LSP tunnels

RSVP enables the allocation of resources along the path. For example,
bandwidth can be allocated to an LSP tunnel using standard RSVP reservations
and Integrated Services service classes.

RSVP-TE includes traffic engineering capabilities

Unlike LDP, RSVP-TE can be signaled over a desired path, and the desired
amount of bandwidth can be requested for a specific traffic types.

Fast Reroute Capabilities

One-to-one backup—a backup LSP is created separately for each protected
LSP.

Facility backup—a bypass tunnel is created to protect a set of LSPs passing
over a common facility.

3—3—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The RSVP-TE operates in downstream-on-demand (DOD) label advertisement mode with ordered LSP control.

A request to bind labels to a specific LSP tunnel is initiated by an ingress node through the
RSVP Path message
 Labels are requested downstream and distributed (propagated) upstream by means of the RSVP
Resv message

RSVP-TE is an MPLS signaling protocol based on the resource reservation protocol originally used for
signaling IP quality of service connections.

RSVP-TE defines a set of traffic engineering extensions to the Resource Reservation Protocol (RSVP)
standard. RSVP-TE extensions provide a method by which RSVP may be used for traffic engineering
in MPLS environments. These extensions add support for assigning MPLS labels and specifying
explicit paths as a sequence of loose and strict hops. These extensions are supported by providing a
Label Request field and an Explicit Route Objects field in the path message. The destination LSR
responds to a label request by providing a label object in its RESV message. Labels are then
assigned at each intermediate node which processes the reserve message. RSVP-TE operates in
downstream-on-demand (DoD) label advertisement mode with ordered LSP control.

Since the flow along an LSP is identified by the label applied at the ingress node of the path, these
paths may be treated as tunnels. A key application of LSP tunnels is traffic engineering with MPLS.
The resulting label switched tunnels can be automatically routed away from network failures,
congestion, and bottlenecks.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 8
 1 RSVP-TE Introduction
1.2 RSVP-TE message types

Downstream on Demand
1.1.1.1/32 2.2.2.2/32

PATH message sent iLER LSR1
Path: 3.3.3.3
towards tunnel
destination.

Receiver sends RESV
Resv: label 131068
message back towards

Path: 3.3.3.3
sender .

Resv: label 131071

eLER sends label binding
info in RESV message.

Path Refresh and RESV
Refresh messages are sent
periodically.
LSR2 eLER
4.4.4.4/32 3.3.3.3/32

3—3—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The RSVP is a network control protocol used by a host to request specific qualities of service from the network
for particular application data streams or flows. RSVP is also used by routers to deliver quality of service (QoS)
requests to all nodes along the path(s) of the flows and to establish and maintain state to provide the requested
service. RSVP requests generally result in resources reserved in each node along the data path. MPLS leverages
this RSVP mechanism to set up traffic engineered LSPs. RSVP requests resources for simplex flows. It requests
resources in only one direction (unidirectional).

RSVP treats a sender as logically distinct from a receiver, although the same application process may act as both
a sender and a receiver at the same time. Duplex flows require two LSPs, one to carry traffic in each direction.
RSVP is not a routing protocol, it operates with unicast and multicast routing protocols. Routing protocols
determine where packets are forwarded and RSVP consults local routing tables to relay RSVP messages.

The sender (the ingress LER), sends PATH messages toward the receiver (the egress LER) to indicate the FEC for
which label bindings are desired. PATH messages are used to signal and request label bindings required to
establish the LSP from ingress to egress. Each router along the path observes the traffic type. PATH messages
facilitate the routers along the path to make the necessary bandwidth reservations and distribute the label
binding to the router upstream. The egress LER sends label binding information in the RESV messages in response
to PATH messages received. The LSP is considered operational when the ingress LER receives the label binding
information.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 9
 1 RSVP-TE Introduction
1.3 Label allocation

After the RESV message is propagated upstream to the sender node, a

label-switched path is effectively established.

iLabel eLabel Action iLabel eLabel Action

--- 131068 Push 131068 131071 Swap

2.2.2.2/32
LSR1

1.1.1.1/32
iLER

eLER
3.3.3.3/32

LSR2 iLabel eLabel Action

131071 --- Pop
4.4.4.4/32
3 — 3 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

RSVP Path messages use a label request attribute and await a label reply in the RSVP Resv message. Once the
Resv message is received, a label mapping is created in the LIB which provides a POP, SWAP, or Push action. The
terminology of ingress or egress label is used with respect to the data plane of the packet flow.

Once an LSP is established, the traffic through the path is defined by the label applied at the ingress node of the
LSP. The set of packets that are assigned the same label value by a specific node are considered to belong to the
same FEC which defines the RSVP flow.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 10
 1 RSVP-TE Introduction
1.4 Optional object—Explicit Route Object (ERO)
RSVP Path
LSP Tunnel (IPv4)
Label_Request
ERO: 10.12.1.2
10.23.1.3
10.34.1.4

Session_Attributes

ERO provides specific 1.1.1.1/32 RRO: 10.12.1.1 2.2.2.2/32
PE1 PE2
path information for .1 .2
the RSVP Path message 10.12.1.0/29 RSVP Path
to follow LSP Tunnel (IPv4)
Label_Request
ERO: 10.23.1.3

If ERO is not present 10.14.1.29/29
.1 .2
10.23.1.0/29
10.34.1.4
then IGP determines .4 .3 Session_Attributes
the RSVP Path RRO: 10.23.1.2
10.12.1.1
10.34.1.0/29

ERO can be manually 1/1/2

provided or computed .4 RSVP Path .3

LSP Tunnel (IPv4)
based on RSVP PE4 Label_Request PE3
4.4.4.4/32 ERO: 10.34.1.4 3.3.3.3/32
requirements such as
Session_Attributes
bandwidth, hop limit, RRO: 10.34.1.3
10.23.1.2
link coloring 10.12.1.1

3 — 3 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

An RSVP PATH message contains the following objects:

Label Request Object (Mandatory)
• Request intermediate and receiver nodes to provide a label binding for the session

• If a node does not supported this object or is incapable of providing a label binding, it sends a PathErr
message to the ILER

Explicit Route Object (ERO) (optional)
• Sent in the PATH message to specify the path to be followed independent of the IGP shortest path

• If ERO is not present then IGP is used to follow the path

• Can be manually provided or computed based on RSVP requirements such as QoS and policy criteria

• Stored in the path state block on each node along the path

Record Route Object (RRO) (optional)

• Records hop-by-hop path information

• Allows the sender and receiver to know the actual route that the LSP tunnel traverses

• May be used for loop detection

Session Attribute Object (optional)

• Includes control information such as the path setup and hold priorities and local-protection

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 11
 1 RSVP-TE Introduction
1.5 Optional object—Record Route Object (RRO)

RSVP Resv
LSP Tunnel (IPv4)
Label: 65
Session_Attributes
RRO: 10.12.1.2
10.23.1.3

Record Route Object 1.1.1.1/32 10.34.1.4 2.2.2.2/32
(RRO) of RSVP-TE is used PE1 PE2
for route recording .1 .2
10.12.1.0/29
purpose. RSVP Resv
LSP Tunnel (IPv4)

RRO records the actual .1 .2 Label: 13
route a packet 10.14.1.29/29 10.23.1.0/29 Session_Attributes
.3 RRO: 10.23.1.3
traversed. .4 10.34.1.4

Recording the path 10.34.1.0/29
allows the iLER to know,
.4 RSVP Resv .3
on a hop-by-hop basis, PE4 LSP Tunnel (IPv4) PE3
which LSRs the path 4.4.4.4/32 Label: 100 3.3.3.3/32
Session_Attributes
traverses. RRO: 10.34.1.4

3 — 3 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The RSVP RESV message is sent back upstream to the ILER following the path created by the PATH message, in
reverse order. The message contains the following objects:

Label Object (Mandatory)
• Sent in response to a PATH message including a Label Request
• A node receiving a Label object uses that label for outgoing traffic associated with this LSP tunnel
• If the node is not ILER, it allocates a new label and places it in the LABEL object sent upstream

Record Route Object (RRO) (Optional)
• Used by the RESV message to follow the same set of hops back to the RSVP originator, reserving resources
along the path and confirming the tunnel creation

Session Attribute Object (Optional)
• Includes control information

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 12
 Knowledge check

Determine whether each of the following statements is true or false:

a) RSVP-TE works downstream on-demand.

b) RSVP-TE uses path and RESV messages to set-up a LSP.
c) RSVP-TE relies only on IGP to set up its LSP path.

3 — 3 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) True
b) True
c) False

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 13
 2 Traffic Engineering and Constraints

3 — 3 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 14
 2 Traffic Engineering and Constraints
2.1 RSVP-TE: Alcatel-Lucent CSPF implementation

Constraints
The Constraint-based Shortest Path First (CSPF) functionality provides the
capability to traffic engineer LSPs based on the following constraints:

Link constraints (include/exclude)

Bandwidth requirements

Hop count limitations

A:PE>config>router>ospf$ traffic-engineering
- no traffic-engineering
- traffic-engineering

A:PE>config>router>isis$ traffic-engineering
- no traffic-engineering
- traffic-engineering

3 — 3 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This slide describes the constraints supported by the CSPF functionality, and shows the SR-OS CLI context where
you can enable traffic-engineering on OSPF.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 15
 2 Traffic Engineering and Constraints
2.2 RSVP-TE: signaled LSPs with CSPF

TE Capable IGP
OSPF-TE
IS-IS-TE

Traffic Constrained
User
Routing Table Engineering Shortest Path First
Requirements
Database (TED) (CSPF)

Explicit Route
Object (ERO)

A:PE>config>router>mpls>lsp$ cspf
- cspf [use-te-metric]
- no cspf
Signaling
<use-te-metric> : keyword

3 — 3 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The Constraint-based Shortest Path First (CSPF) process is an extension to the SPF process performed by
link state routing protocols. The CSPF calculation uses constraints, obtained from the traffic engineering
database (TED) and local input, to compute the shortest path that matches the configured
requirements. Once the CSPF finds a path, the explicit route object (ERO) in the RSVP message is
updated with the path requirement information and RSVP uses the CSPF path to request the LSP set-up.

The CSPF takes into account the following constraints:

Admin groups, including link colors and resource classes (from TED)

Bandwidth

Hop limits

RSVP-TE can also use to calculate the detour routes when fast-reroute is enabled (avoiding a particular
link is a constraint as well).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 16
 2 Traffic Engineering and Constraints
2.3 RSVP-TE: LSP configuration

10.10.43.3

10.10.42.3
10.10.10.99 10.10.10.101

10.10.10.102

10.10.44.3

10.10.10.100 10.10.10.103

RSVP PATH
“Primary_Path”
config>router# mpls
config>router>mpls#lsp “LSP_99_103”
config>router>mpls>lsp# to 10.10.10.103
config>router>mpls>lsp# cspf
config>router>mpls>lsp# primary
“Primary_Path"
config>router>mpls>lsp>primary# hop-limit 4
config>router>mpls>lsp>primary# bandwidth
256
config>router>mpls>lsp>primary# no shutdown

3 — 3 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This slide illustrates the steps required to configure LSP

1. Enable TE on OSPF/ISIS
• CSPF must be enabled if constraint-based LSPs are required or if FRR is to be used.
2. Enable MPLS on the router
• MPLS is automatically enabled upon creation.
• The system interface is automatically added into the MPLS instance.
3. Configure MPLS on the network interfaces
• Interfaces must already be configured
• RSVP is enabled by default with MPLS.
4. Create an MPLS Path
• The path is a list of constraints that are applied to an LSP
• A path can be used by multiple LSPs
5. Configure an MPLS LSP
• Specify the IP address of the egress router
• Specify the primary MPLS path to be used
• Specify bandwidth/hop limit/admin group constraints, if any
• Specify any secondary paths

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 17
 2 Traffic Engineering and Constraints
2.3 RSVP-TE: LSP configuration [cont.]

CLI Configuration:
1. 1. configure router ospf|isis traffic-engineering
2. 2. configure router mpls
3. 3. configure router mpls interface “interface-name”
4. 4. configure router mpls path “path-name”
5. 5. configure router mpls lsp “lsp-name”

3 — 3 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This slide illustrates the steps required to configure LSP

1. Enable TE on OSPF/ISIS
• CSPF must be enabled if constraint-based LSPs are required or if FRR is to be used.
2. Enable MPLS on the router
• MPLS is automatically enabled upon creation.
• The system interface is automatically added into the MPLS instance.
3. Configure MPLS on the network interfaces
• Interfaces must already be configured
• RSVP is enabled by default with MPLS.
4. Create an MPLS Path
• The path is a list of constraints that are applied to an LSP
• A path can be used by multiple LSPs
5. Configure an MPLS LSP
• Specify the IP address of the egress router
• Specify the primary MPLS path to be used
• Specify bandwidth/hop limit/admin group constraints, if any
• Specify any secondary paths

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 18
 2 Traffic Engineering and Constraints
2.3 RSVP-TE: LSP configuration [cont.]

CLI Configuration Example:

*A:PE1>config>router>ospf# *A:PE1>config>router>mpls#
---------------------------------------------- path "loose"
traffic-engineering no shutdown
---------------------------------------------- exit
exit lsp "to_PE2"
to 10.10.10.2
cspf
*A:PE1>config>router>mpls# fast-reroute one-to-one
---------------------------------------------- exit
interface "system" primary "path_toPE2"
exit exit
interface "toPE2" secondary "path_toPE2_secondary"
exit standby
interface "toPE3" exit
exit secondary "loose"
exit exit
---------------------------------------------- no shutdown
exit

3 — 3 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This slide illustrates the steps required to configure LSP

1. Enable TE on OSPF/ISIS
• CSPF must be enabled if constraint-based LSPs are required or if FRR is to be used.
2. Enable MPLS on the router
• MPLS is automatically enabled upon creation.
• The system interface is automatically added into the MPLS instance.
3. Configure MPLS on the network interfaces
• Interfaces must already be configured
• RSVP is enabled by default with MPLS.
4. Create an MPLS Path
• The path is a list of constraints that are applied to an LSP
• A path can be used by multiple LSPs
5. Configure an MPLS LSP
• Specify the IP address of the egress router
• Specify the primary MPLS path to be used
• Specify bandwidth/hop limit/admin group constraints, if any
• Specify any secondary paths

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 19
 2 Traffic Engineering and Constraints
2.4 RSVP-TE: Strict and Loose hops

2.2.2.2/32
1.1.1.1/32
PE2
PE1
Example of strict and loose path Blue Path 10.12.1.2
Blue path: ERO defines strict hops

ERO explicitly defines the path PE2>PE3>PE4
Red Path: ERO defines only loose hops

ERO defines only 4.4.4.4 as loose

Red Path 10.23.1.3

PE4
10.34.1.4
4.4.4.4/32 PE3
3.3.3.3/32

A:PE1>config>router>mpls# path “toPE4_blue_strict”

A:PE1>config>router>mpls>path$ hop 1 10.12.1.2 strict
A:PE1>config>router>mpls>path# hop 2 10.23.1.3 strict
A:PE1>config>router>mpls>path# hop 3 10.34.1.4 strict
A:PE1>config>router>mpls>path# no shutdown
A:PE1>config>router>mpls>path# exit

A:PE1>config>router>mpls# path “loose“

A:PE>config>router>mpls>path# no shutdown

3 — 3 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This slide describes the RSVP-TE strict and loose hops.

Strict hop—next hop address must be directly connected.

Loose hop—next hop does not need to be directly connected.

The slide shows the PE1 commands used to define strict and loose hoops.

Paths can also use a combination of loose and strict hops.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 20
 2 Traffic Engineering and Constraints
2.5 LSP redundancy

Primary LSP path

One primary path per LSP

Can be protected by up to 7 secondary LSPs

LSP 1 – Primary
Path

LSP 1 – Secondary
Path

Secondary LSP path

Alternative path that the LSP uses when the primary path is not available;
when the primary path is re-established, the traffic is switched back to the
primary path.

Up to 8 secondary paths can be specified. 7 if there is a primary path.

All secondary paths are considered equal and the first available path is used

No switchback among secondary paths

Similar to the primary path: reserved bandwidth, hop-limit count and
inclusion/exclusion of admin groups can be specified.

3 — 3 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The following parameters can be configured for the primary and secondary LSPs to ensure redundancy:

Bandwidth—the amount of bandwidth needed for the secondary LSP can be reserved and can be any value; it
does not need to be identical to the value reserved by the primary LSP. Bandwidth reservation can be set to 0,
which is equivalent to reserving no bandwidth.

Inclusion and exclusion of nodes—by including or excluding certain nodes, you can ensure that the primary and
secondary LSPs do not traverse the same nodes and therefore ensure successful recovery. Each secondary LSP can
have its own list of included and excluded nodes.

Hop limit—the hop limit is the maximum number of LSR nodes that a secondary LSP can traverse, including the
ingress and egress LER nodes

Standby (secondary LSPs only)—when a secondary LSP is configured for standby mode, it is signaled immediately
and is ready to take over traffic the moment the LER learns of a primary LSP failure. This mode is also called hot-
standby mode. When a secondary LSP is not in standby mode, then it is only signaled when the primary LSP fails.
If there is more than one secondary LSP, they are all signaled at the same time (upon detection of a primary LSP
failure) and the first one to come up is used.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 21
 2 Traffic Engineering and Constraints
2.6 LSP with secondary path

LSP 1 – Primary
Path
X
LSP 1 – Secondary
Path

A:PE1>config>router>mpls>lsp# secondary “Secondary_Path"

A:PE1>config>router>mpls>lsp>secondary# hop-limit 4
A:PE1>config>router>mpls>lsp>secondary# bandwidth 256
A:PE1>config>router>mpls>lsp>secondary# standby
A:PE1>config>router>mpls>lsp>secondary# no shutdown

3 — 3 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

This slide describes an LSP with secondary path.

The following considerations apply when the secondary LSP path is in Standby:

The path is signaled and maintained indefinitely in a hot-standby state.

There is double reservation of resources.

Reduced latency is associated with a failed path.

The following considerations apply when the secondary LSP path is not in Standby:

The path is not signaled until a network failure causes the primary path to fail.

When the ILER node is aware of the failure, it signals the secondary path to become active.

There is no double reservation of resources.

Increased latency is associated with recovering a failed path.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 22
 2 Traffic Engineering and Constraints
2.7 Fast Reroute overview

Disadvantages of Secondary Path only Protection

Failure downstream might take a while to reach the head of LSP

Double booking of resources (if hot-standby enabled)

No selective protection of node or link

Fast Reroute characteristics

Fast Reroute (FRR) is used to establish backup label-switched path (LSP)
tunnels for local repair of LSP tunnels.

FRR defines ways of pre-configuring and signaling backup paths before a
failure.

The mechanisms enable the redirection of traffic onto backup LSP tunnels
within 50 ms upon failure.

When Fast Reroute is enabled, each node along the path of the LSP tries to
establish a backup LSP.

FRR is only available for the Primary path.

CSPF must be enabled for FRR to work.

3 — 3 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The following considerations apply to the Fast Reroute mechanism:

•When Fast Reroute is enabled, each node along the path of the LSP tries to establish a backup LSP
• Each upstream node sets up a backup LSP that avoids only the immediate downstream node ( by default node
protection is enabled)
• The Point of Local Repair (PLR) looks for the backup path which merges back to the protected LSP sooner;
that is, the Merge Point (MP) is closer to the PLR
• The backup LSP may take one or more hops merging back to the main LSP or it may only merge at the eLER
• If it is not possible to set up a backup LSP that avoids the immediate downstream node, a backup can be set
up to the downstream node on a different interface
•In case of failure, traffic is immediately rerouted by the PLR onto the pre-computed backup LSP, minimizing
packet-loss
•When the upstream node (ILER) is informed by the PLR that a downstream router is using its backup LSP, the
iLER switches traffic to a standby path if one was set up for the LSP
•A locally repaired LSP (i.e., using the backup path) will try to globally revert back when the retry timer expires
•FRR is only available for primary path
•No configuration is required on the transit hops of the LSP (except Manual Bypass Tunnel)
•CSPF must be enabled for Fast Reroute to work

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 23
 2 Traffic Engineering and Constraints
2.8 RSVP-TE: LSP protection review

The path protection mechanism provides the following features:

Primary LSP with Secondary LSP

Primary LSP with Secondary Standby LSP

The Fast Reroute mechanism provides the following features

One-to-One Backup

Facilities Backup

The next section in this module describes the Fast Reroute mechanism.

3 — 3 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

An important concept of RSVP-TE LSPs is the ability for fast recovery—unlike LDP, which is dependent on
the re-convergence time of the underlying IGP.

Next to a primary path, up to 7 secondary paths can be defined, if the primary path becomes
unavailable due to link or node failures. Once the iLER notices a problem further along the primary
path, it switches traffic to a secondary path that can be configured (non-standby) or configured and
signalled in advance (hot standby).

For even faster, sub 50 ms, convergence, Fast Reroute can be activated. Fast Reroute provides a backup
path for every link or node on the path. As a result, when a link or node failure occurs, every node can
instantly switch to this backup temporarily until the iLER decides to use the secondary path.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 24
 2 Traffic Engineering and Constraints
2.9 RSVP-TE: backup LSP—LSPs with Secondary Path

A failure in the primary path triggers

the switchover to the secondary LSP. The secondary path can be in the
non-standby or hot-standby state.

R3
R2
R1

R6 R9
R7 R4

R8

Primary LSP: R1 > R2 > R3 > R4

Secondary LSP: R1 > R6 > R7 > R8 > R9 > R4

3 — 3 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Only one primary path can be defined for a Label Switched Path. The primary path is the main path for
the LSP and is used in normal conditions.

If the primary path becomes unavailable, up to 7 additional paths can be defined to take over. If a
secondary path is configured as “hot-standby”, the labels for this path have been signaled and
maintained upon creation; this results in faster convergence but more used resources. This is a trade-off
that the network designer must face according to the network requirements. When the secondary path
of the LSP is not in standby, it will be signaled as soon as a network failure causes the primary path to
fail, and the head-end node is informed of the failure. After the switchover from the primary to the
secondary, the software continuously tries to revert to the primary path.

Up to 8 paths can be specified (7 if there is a primary path being used) and are considered equal with
the first available path being used. The software will not switch back among secondary paths. The
Primary and Secondary paths can be configured with a combination of strict or loose hops, or without
any hops specified.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 25
 2 Traffic Engineering and Constraints
2.10 RSVP-TE: LSP Protection with a Secondary Path

Advantages

Deterministic data flow during any point in primary path.

Multiple failures along the primary path can be handled by the same
secondary path.

When statically configured, no nodes or links should be shared by the Primary
and Secondary paths (otherwise if that link or node goes down, both are lost).

The entire path is protected.

Disadvantages

Notification of a link or node failure can take a while to reach the head of
the tunnel.

Full path resources are reserved over both Primary and Secondary paths,
therefore there is “double booking” if hot-standby is enabled.

Selective protection of link or node is not possible only end-to-end.

3 — 3 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Primary and Secondary paths, when statically configured, are deterministic and will allow specific path
protection as configured. The benefit to configuring Primary and Secondary paths is that path
protection is guaranteed regardless of the location of the failure or if multiple failures exist. When
statically configuring the Primary and Secondary paths, it is not advisable to configure common links
since the failure of the common link will result in the failure of both LSPs. However, if the Primary and
Secondary LSP are created using a Loose path, or if portions of the LSPs are making use of Loose path
then it is entirely possible that the IGP path chosen will cause both LSPs to make use of a common link.

Primary and Secondary paths protect the entire path. However, a failure anywhere along the path
requires the LSP head end to be notified that a failure has occurred. It’s only the LSP head end that can
signal the activation of the Secondary LSP. It might take some time for the head of the LSP to be
notified via a PathError message that a failure has occurred downstream. Furthermore, by creating
Primary and Secondary paths, network resources are being reserved for each LSP. This results in “double
booking” the resources and overstating the actual resource utilization for the network, especially with
hot standby secondary LSPs.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 26
 Knowledge check

Answer these questions:

a) What IGP command needs to be configured in order to make CSPF

work?
b) If the primary path fails, what command needs to be enabled in order
to have the secondary path immediately available?
c) CSPF is optional, if traffic engineering is desired, in order to enable
Fast ReRoute. True/False

3 — 3 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

a) traffic-engineering
b) Standby
c) False – CSPF is mandatory.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 27
 3 RSVP Fast Reroute

3 — 3 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 28
 3 RSVP Fast Reroute
3.1 One-to-one backup method —multiple LSPs

R10
R3
PLR
R2
R1 MP
PLR PLR
R5 MP
R4
MP
(2)
(1)
R9
R6
R7 R8

(1)

Protected LSP 1: R2 backup for protected LSP 1:

R1 > R2 > R3 > R4 R2 > R7 > R8 > R9 > R4
(2)

Protected LSP 2: R2 backup for Protected LSP 2:

R10 > R2 > R3 > R4 R2 > R7 > R8 > R9 > R4

3 — 3 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

In the case of the one-to-one backup solution, every LSP creates its own detour LSPs to protect itself.
The slide shows only Point of Local Repair (PLR) at R2 (other routers can also create detour LSPs). Two
different LSPs with their own labels are created and have the same Merge Point (the point where the
detour merges with the original path): R4 in this example.

The Facility Backup method, explained further in this course, creates only one bypass and therefore
uses fewer labels than the one-to-one Backup method.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 29
 3 RSVP Fast Reroute
3.2 One-to-one backup method—path setup

PLR
R3
R2 PLR Merge Point
R1 (MP)

R5 (3)
PLR R4

(1) (2)
R9
R6
R7 R8

Detour Tunnel

Protected LSP: (1) (3)

R1 > R2 > R3 > R4
R1 backup: R3 backup:
R1 > R6 > R7 > R8 > R9 > R4 R3 > R9 > R4
(2)
R2 backup:
R2 > R7 > R8 > R9 > R4

3 — 3 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Each router along the LSP path establishes a detour LSP, which is the best path to the destination node
that avoids the node and/or link at the point of failure. For each LSP that is backed up, a separate
backup LSP is established.

In the example shown on the slide, the protected LSP runs from R1 to R4. Router R2 can provide user
traffic protection by creating a partial backup LSP, which is the best path to R4 that avoids the link
between R2 and R3 (in case of link protection) and the node R3 (in case of node protection). The partial
one-to-one backup LSP (R2 > R7 > R8 > R9 > R4) is called a detour.

To fully protect an LSP that traverses N nodes, there can be as many as (N - 1) detours. The slide shows
the paths for the detours necessary to fully protect the LSP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 30
 3 RSVP Fast Reroute
3.3 One-to-one backup method—label exchange

Inner Inner Inner

label 21 label 32 label 54

PLR
R3 54
R2 32
21
R1 MP
R4

159
172
198
187

R9
R8
R7
Protected LSP:
R1->R2->R3->R4

R2 backup: Control plane (label propagation)

R2 > R7 > R8 > R9 > R4

3 — 3 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Labels along the Protected LSP path are advertised along the control plane according to the common
label propagation rules. Labels are propagated along the backup path in the same manner. The CSPF
process is needed to perform these operation, and is enabled automatically on the transit routers.

As a result, the backup path is signaled, established, and prepared for the eventuality of a failed link.
The only difference between the primary LSP and the backup LSP is that the primary LSP is being used
in the data plane, while the backup LSP is not.

If the link R2-R3 fails, or if the node R3 fails, the PLR (R2) swaps incoming packets that have label 21
with label 172, and sends them out the interface to R7. The MP (R4) recognizes that the packets arriving
on its interface to R9 with label 159 need to be transferred since it is the termination point of the
protected LSP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 31
 3 RSVP Fast Reroute
3.4 One-to-one backup method—link or node failure

Inner Inner Inner

label 21 label 32 label 54

R3
R2 PLR
21 MP
R1
X R4
Inner
label
21 159
172
198 Inner
Inner
187 159
172 label
label
R9
R7
R8
Inner Inner
187 label
198
label
Protected LSP:
R1 > R2 > R3 > R4

Control Plane (label propagation)

R2 backup:
R2 > R7 > R8 > R9 > R4

3 — 3 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

If the link R2-R3 fails, the PLR warns the upstream iLER about the failure and swaps the traffic over the
detour LSP by swapping the outer label with the label received from R7 when the detour was created.
The label stack depth is unchanged (as opposed to the Facility Bypass method), and only the outer label
has a different value (and a different egress interface).

The MP router R4 receives the traffic with a different transport label over a different ingress interface
than before the link failure.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 32
 3 RSVP Fast Reroute
3.5 Facility backup method—link protection

R10
R2 R3 R3
R2
R1
MP
PLR

R4

R6 R9
R6 R9
R7
R7 R8
R8

Protected LSP 1: Bypass tunnel

R1 > R2 > R3 > R4 R2 > R7 > R8 > R3

Protected LSP 2:
R10 > R2 > R3 > R4

3 — 3 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The facility backup technique uses a different approach. Instead of creating a separate LSP for every
backed-up LSP, the technique creates a single LSP, which serves to backup up a number of LSPs. This
type of LSP tunnel is called a bypass tunnel. The advantage of this method is the efficient use of labels
in comparison with the one-to-one backup method.

When a bypass tunnel is created from a PLR to a downstream MP, all the original LSPs that are using this
partial path are candidates to use this bypass tunnel to protect themselves.

In slide, R2 has created a bypass tunnel that protects against the failure of link R2-R3. The doubled lines
represent the bypass tunnel. Both the protected LSPs, regardless of their source and destination
endpoints, can use the bypass tunnel, which provides a scalability improvement.

As with the one-to-one backup technique, to fully protect an LSP that traverses N nodes, there can be
as many as (N - 1) bypass tunnels. However, each of those bypass tunnels can protect a set of LSPs.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 33
 3 RSVP Fast Reroute
3.6 Facility Backup—link protection label exchange

Inner Inner Inner

label 21 label 32 label 54

MP
PLR
32 R3 54
21 R2
R1
R4

172
138

R8
R7 187
Protected LSP:
R1 > R2 > R3 > R4

R2 backup: Control plane (label propagation)

R2 > R7 > R8 > R3

Under normal conditions, this technique works the same as the one-to-one backup

3 — 3 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The data plane functions the same way in the stable LSP scenario as it functions in a one-to-one backup
setup. The control plane prepares a bypass tunnel by signaling available labels from the MP to the PLR
as a response to the PLR RSVP-TE DoD request.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 34
 3 RSVP Fast Reroute
3.7 Facility backup—link failure

Inner
label 32 Inner
Inner
21 label 54
label MP
PLR 32
R3 54
R2
21
R1
X R4

172 Inner
label 32 138
Inner
label 32 172 138

R8
Protected LSP: R7 187
R1 > R2 > R3 > R4 Inner
label 32 187

R2 backup:
R2 > R7 > R8 > R3 Control Plane (label propagation)

The MP receives same label from the backup link as it would from the primary LSP

3 — 3 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

The example shown on the slide illustrates the facility backup method. If the link R2-R3 fails, the PLR
first swaps the outer label to label 32 because this is the label that R3 expects. On top of that label, the
label 172 is pushed, and the label stack has increased with one extra label. This packet is sent over the
backup egress interface, and all the intermediate routers of the bypass tunnel (R7 and R8) perform the
normal swap operations on this extra outer label. It is the MP that transfers this label, investigates the
32 label and performs the SWAP like in a normal operation.

This method allows the “tunneling” of multiple LSPs through the bypass tunnel, and improves the
scalability of the protected paths.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 35
 Knowledge check

Answer these questions:

a) What is the difference between loose and strict hops?

b) What is the major benefit of FRR compared to primary/secondary
backup?
c) What are the two methods of Fast Re-route?

3 — 3 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) A strict hop needs to be directly connected. A loose hop can have multiple hops in between
b) Faster fault detection time
c) One-to-one and facility

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 36
End of module
RSVP-TE

3 — 3 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

IP/MPLS — RSVP-TE
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 3.3 Edition N/A
Section 3 — Module 3 — Page 37
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 1
Services Overview
TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 1
 Blank page

4—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 2
Module objectives

Upon completion of this module, you should be able to:

Identify the types of services supported on the 7705 SAR.

Describe the components of a service.

Configure a basic service.

4—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 3
Module objectives [cont.]

4—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 4
 Table of Contents

1 Service overview 7
Page
2 Internet Enhanced Service 19
1 Service
3 Epipeoverview
service 7 26
1.1 Service categories 8
4 Internet
1.2 VPLS Enhanced Service 9 33
1.3 Virtual Private Wire Service 10
5 VPWS
1.4 VPRNimplementation 11 39
1.5 VPWS benefits 12
1.6 Epipe service 13
1.7 Virtual Private LAN Service 14
1.8 Virtual Private Routed Network 15
1.9 Logical Service Level Connectivity 16
1.10 Service Components 17
2 Internet Enhanced Service 19
2.1 Internet Enhanced Service overview 20
2.2 IES interface—IP interface comparison 21
2.3 IES configuration 22
2.4 Internet Enhanced Service (IES) 23
2.5 IES in Routing Protocols 24
3 Epipe service 26
3.1 Epipe service overview 27
3.2 Distributed Epipe 28
3.3 Epipe configuration 29
3.44 —Epipe
1—5
SAP configuration parameters 30
3.5Services
Epipe SDP
— Services Overviewbindings
7705 SAR — R6.0 Strategic Industries
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
31
4 VPLS 33
4.1 VPLS as switch 34
4.2 VPLS over MPLS 35
4.3 VPLS customer operation 36
4.4 Configuring full-mesh VPLS service 37
5 VPRN 39
5.1 VPRN overview 40
5.2 VPRN route distinguisher 41
5.3 VPRN Route Target 42
5.4 VPRN and MP-BGP 43
5.5 Prerequisite step: configuring full-mesh MP-BGP sessions 44
5.6 Verifying the full-mesh MP-BGP session configuration 45
5.7 VPRN data plane—transport tunnel 46
5.8 VPRN VPN label 47
5.9 VPRN configuration 48
5.10 VPRN configuration 49

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 5
Table of Contents [cont.]

4—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 6
 1 Service overview

4—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 7
 1 Service overview
1.1 Service categories

Services

VPN Non-VPN
services services

Layer 2 VPN Layer 3 VPN Routed IES

services services services

Point-to- Layer 3 VPN

Point-to-point
multipoint services
services
services or VPRN

VLL or pipe Layer 2 VPN

services: services
apipe, epipe, or VPLS
ipipe, cpipe,
fpipe, hpipe

4—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The majority of services are VPN services: either L2 or L3 VPN services. The non-VPN service of the SR-OS product
family is the Internet Enhanced Service, a routed service that offers IP connectivity.

The L2 VPN services can be further split up in to point-to-point and point-to-multipoint services. The point-to-
point services are known as pseudowires, virtual leased lines (VLL) or pipe services, and come into different
variants. The variants depend on what access technology need to be carried inside the VPN. In the point-to-
multipoint services, there is the virtual private LAN service (VPLS), which can be compared to an Ethernet
switched network.
Virtual private routed network is an L3 point-to-multipoint type of service VPN that offers routed services to
customers.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 8
 1 Service overview
1.2 Internet Enhanced Service

Internet

Company C

PE C
PE A Service Provider
Network

Company A PE B

Company B

IES provides direct internet access with the following features:

Direct connection to a routed service for the customer.

Service providers can apply billing, ingress/egress shaping and policing.

4—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide describes the non-VPN routed Internet Enhanced Service (IES): a routed connectivity service where the
subscriber communicates with an IP router interface to send and receive routed Internet traffic. However, the IES
does not always need to be connected to the Internet; it can also be connected to a routed private network.
From the customer perspective, IES provides a direct connection to a routed service, like an IP interface.
However, because this is a service and not a regular IP interface on a service router, the service provider can
apply billing and ingress/egress shaping, or apply a service policy.
The PE devices buffer service traffic and shape it to conform to SLA parameters. Buffer allocation is
programmable per-service to accommodate different maximum burst sizes. Each service can use multiple queues
to enable shaping, policing and marking of different flows. The PE device can also shape and police on service
egress so customers can purchase sub-rate services with asymmetric SLAs.
The connection to the customer is SAP based and not interface based. The SAP supports multiple encapsulation
types, including Ethernet null, dot1q and q-in-q, SONET/SDH-IPCP, BCP-null, BCP-dot1q and ATM. As with any SAP
on a service, it can contain filter, accounting, and QoS policies.
The IES interface does support all the relevant IP routing protocols such as RIP, OSPF, IS-IS, and BGP. However,
the IES service interface supports IPv6.
Although the IES is a non-VPN service, it has the ability to connect to a pseudowire and complete the L3
termination.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 9
 1 Service overview
1.3 Virtual Private Wire Service

Customer 1 Customer 2
IP-MPLS Network

VPWS Service 1

VPWS Service 2

Customer 2 Customer 1

4 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide describes the L2 VPN point-to-point service or Virtual Private Wire Service (VPWS) service.
The VPWS is a layer 2 point-to-point connection service providing an emulation of layer 2 technologies such as
Ethernet, IP, ATM, Frame Relay, E1/T1 and HDLC.
A VPWS service is also known under different names such as pseudowire service, VLL service, PWE3 service,
martini service, and pipe service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 10
 1 Service overview
1.4 VPWS implementation

I-Pipe
E-Pipe
F-Pipe
A-Pipe
C-Pipe
H-Pipe
4 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The Alcatel-Lucent Service Portfolio implements VPWS as E-pipe, I-pipe, A-pipe, F-pipe, H-pipe and C-pipe
services. These VPWS implementations are based on the IETF “Martini Drafts” and on the IETF Ethernet Pseudo-
wire Drafts.

These are layer 2 point-to-point services, which encapsulate and transport customer data across a service
provider IP or MPLS network. The VPWS service is completely transparent to the subscriber data and protocols.
The VPWS does not perform any MAC learning.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 11
 1 Service overview
1.5 VPWS benefits

Ethernet, ATM, FR, Layer 2 Tunnel Ethernet, ATM, FR,

HDLC, E1/T1, IP HDLC, E1/T1, IP

Customer Customer
Site A Pseudowire Site B

Emulated Service

The pseudowire connection enables you to emulate or to carry legacy Layer 2

services over a cost-effective and predominant IP/MPLS network. It decouples
the services protocols and applications from the underlying facilities that
carry them.

4 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The main VPWS benefit is that service providers can offer multiple services across a common packet switched
network.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 12
 1 Service overview
1.6 Epipe service

PE B

PE A PE C

IP/MPLS
Network

Epipe service

PE D

An Epipe service provides a point-to-point connection between two nodes.

The Epipe service appears to the customer as a leased link between two
locations. The service provider can apply billing, ingress/egress shaping and
policing. No MAC learning is required.

4 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This service is a Layer 2 point-to-point VLL service. The Alcatel-Lucent implementation of an Ethernet
VLL is called an Epipe. The Epipe service encapsulates customer Ethernet data and transports it across a
service provider IP or MPLS network in a GRE or MPLS tunnel.

Customer access to the service provider network is through a SAP on a PE router. An Epipe service
connects two of those SAPs on the same node, and is called a local service. The Epipe service can also
connect two SAPs on different nodes, called a remote service, through two uni-directional tunnels.

The customer is unaware of the Epipe service, which appears as a direct Ethernet connection, while the
two sides of the Epipe can be at different locations.
The service provider can apply QoS and filter ingress and egress policies to Epipe services.
Anything that is sent to the SAP, exits on the other PE side on a SAP. There is no MAC learning required.
However, some MAC addresses is not passed due to a filter policy applied to the SAP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 13
 1 Service overview
1.7 Virtual Private LAN Service

PE B
VPLS Service
IP/LSP Full-
Mesh

PE A PE C

IP / MPLS
Network

PE D

VPLS is an Alcatel-Lucent implementation of a point-to-multipoint L2 VPN.

From the customer perspective, all sites appear to be connected to a single
switched VLAN. The service provider can reuse the IP/MPLS infrastructure to
offer multiple services. The Service provider can apply billing, ingress/egress
shaping and policing.

4 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The Alcatel-Lucent point-to-multipoint L2 VPN is called a Virtual Private LAN Service (VPLS).
The VPLS allows multiple customer sites to be connected in a single bridged domain contained within a
provider-managed IP/MPLS network. Customer sites in the VPLS appear to be on the same LAN, even
though the sites are at different geographical location.
The VPLS uses only Ethernet interfaces on the customer access side. It enables customers to control
and simplify routing strategies because all routers in the VPLS are part of the same LAN. Each customer
connected to the PE is in the same subnet.
The VPLS can span a single node or multiple nodes. On a VPLS that spans a single node, subscriber data
is distributed through multiple SAPs on the node. A VPLS on a single node does not require service MPLS
or GRE tunnels.
On a VPLS that spans multiple sites, customer data enters the service using at least one SAP on each
node. Data is transported among the nodes through service tunnels over an IP/MPLS provider core
network. A VPLS that spans multiple nodes requires at least one tunnel at each node.
The VPLS service switches traffic based on MAC addresses.
Although a VPLS is a Layer 2 VPN service and allows the use of Layer 2 switches as the CE device, most
customers use routers at the LAN/WAN boundary.
When a router is used as a CE device, the PE device needs to learn only one MAC address per site per
service.
When a Layer-2 switch is used as the CE device, the PE device needs to learn multiple MAC addresses
per site per service. The number of MAC addresses that the PE device has to learn can be limited
through the use of MAC filters and/or by limiting the maximum number of MAC addresses accepted by
the PE device.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 14
 1 Service overview
1.8 Virtual Private Routed Network

MP-BGP Route RI-1 VPRN

Exchange Service
For all Services RI-2 Red
PE B

PE A PE C

RI-1 RI-1
RI-2 RI-2
IP / MPLS
Network

VPRN
Service
PE D RI-1 Green
RI-2

The VPRN is a class of VPN that allows the connection of multiple sites in a
routed domain over a provider managed IP/MPLS network.
From the customer perspective, all sites appear to be connected to a private
routed network administered by the service provider for that customer only.
Each VPRN appears like an additional routing instance, and the routes for a
service between the PEs are exchanged using MP-BGP.

4 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The Virtual Private Routed Network (VPRN) is a method of distributing routing information and
forwarding data to provide a Layer 3 Virtual Private Network service to customers.
A VPRN consists of a set of customer sites connected to one or more PE routers. Each associated PE
router maintains a separate IP forwarding table for each VPRN. Additionally, the PE routers exchange
the routing information configured or learned from all customer sites via a multi-protocol BGP peering.
Each route within a VPN is assigned an MPLS label. When the BGP distributes a VPN route, it also
distributes an MPLS label for that route.
Before a customer data packet travels across the service provider backbone, the data packet is
encapsulated with the MPLS label that corresponds, in the customer VPN, to the route which best
matches the packet destination address. The MPLS packet is further encapsulated with either another
MPLS label or a GRE tunnel header, so that it gets tunneled across the backbone to the appropriate PE
router. Each route exchanged by the MP-BGP protocol includes a route distinguisher, which identifies
the VPRN association; therefore, the backbone core routers do not need to know the VPN routes.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 15
 1 Service overview
1.9 Logical Service Level Connectivity

SDP binds multiple services

to a tunnel.

Egress and ingress VC label

provisioned or dynamically Tunnel supporting Martini-type
assigned. Uniquely service encapsulations. Tunnels
Identifies the service to the are unidirectional, but are
tunnel’s far end. usually paired to provide a
bidirectional service.

SAP is the customer point

of access

PE-A VC VC PE-B
SDP SDP Label
Label
SAP SAP
VC
VC Label Label Service 1
Service 1 Demux
Demux

TLDP/MP-BGP

4 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The SAP is the customer access point to the service. A SAP can be provisioned only on ports configured
as access. A port is either access or network. A port has a default setting of “access”, and this setting
needs to be changed ports are required to be network. You may also need to specify an encapsulation
type.
The SAP is connected by configuration to only one service. But a service can contain multiple SAPs.
When the service is a distributed service (it covers more than two PE sites), the SDPs need to be
connected to the service. An SDP is identified by a locally unique ID number, and represents a GRE or
MPLS tunnel to transport the data traffic to the other end.
The SDP is unidirectional, but almost always paired with another SDP to provide a bidirectional service.
Before the data traffic is tunneled and sent to the other side, an additional label next to the MPLS
transport label is added. This label—called an inner label, service label or VC label—uniquely identifies
the service with the tunnel far end. The far end has a de-multiplexer mechanism so that, after the MPLS
transport label is processed, the VC label indicates to which service the traffic belongs to. A service
router can contain multiple services that use the same SDP or service tunnel.
The VC labels are significant only at both sides of the PE router. The intermediate P routers are
unaware of this inner label and leave the label untouched.

The T-LDP or MP-BGP protocol performs the VC label negotiation or distribution.

•T-LDP or targeted LDP is an adaptation of the known LDP MPLS label distribution mechanism. LDP
distributes label between directly connected peers and T-LDP distributes service labels between service
PE routers. T-LDP is using the system address to distribute label to the other PE side. T-LDP service
label distribution works in a point to point way.
•MP-BGP is an extension to BGP and can carry service labels as well.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 16
 1 Service overview
1.10 Service Components

Service Service Service Service

Access Distribution Distribution Access
Subscribers Points Path Path Points Subscribers

Service 50 Service 50 Customer

Customer SAP
100 SAP 100
Customer 100
Customer 100

SDP 3 Demux

Demux SDP 5
Customer 200 Customer 200
Customer Customer
SAP SAP 200
200 Service 25 Service 25

Service Tunnels

4 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide provides a review of the major components of a service.

A service uses an SDP service tunnel to direct traffic from one router to another. The service tunnel
is provisioned with an encapsulation type of GRE or MPLS and services are mapped to the service
tunnel that most appropriately supports the service requirements. An SDP is configured before one
or more services can use this tunnel. An SDP is not a protocol, but a logical entity represented by a
number that is linked to, for example, an LSP in the case of an MPLS RSVP-TE SDP.

A SAP is a logical entity that serves as the customer point of access to a service. Each subscriber
service is configured with at least one SAP. A SAP can be configured only on an access port. The
SAPs for IES and VPRN services are configured on IP interfaces within the service.

An SDP acts as a logical way of directing traffic from one router to another through a unidirectional
service tunnel. An SDP originating on one node terminates at a destination node, which then directs
incoming packets to the correct service egress SAPs on that node. A multi-node service needs at
least one SAP and one SDP on each node. For a service to be bidirectional, an SDP must be
provisioned on each node participating in the service.

The customer ID is a mandatory part of the service creation. The customer ID is a locally significant
number that is mainly used to link customer credentials to a service. These credentials can be a
phone number, a name and an address. When a relevant customer ID is not required, the default
customer ID value of 1 can be used.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 17
 Knowledge check

Answer the following questions

a) Is VLL a point-to-point or a point-to-multipoint service?

b) Is MAC learning performed by a VPLS, a VLL or a VPRN service?
c) Which component directs traffic from one router to another: SDP or
SAP?

4 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) VLL is a point-to-point service.
b) VPLS performs MAC learning.
c) SDP directs traffic from one router to another.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 18
 2 Internet Enhanced Service

4 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This section describes the Internet Enhanced Service (IES).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 19
 2 Internet Enhanced Service
2.1 Internet Enhanced Service overview

CE PE

Global Routing Core

Internet
Customer access to internet IES
SAP

The IES is a layer 3 service, and uses the global routing table to route traffic
from the customer to the destination. The access point for the customer
towards the subscriber network is a SAP connected to an IP interface. The IES
allows the customer that is facing IP interfaces to participate in the same
routing instance used for network core routing connectivity.

4 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The Internet Enhanced Service is a non-VPN type of service. The IES provides direct Internet
access to customers OR any other layer 3 private network.
The “I” in IES can be misleading; an IES can participate in the public IP scheme, but can also
participate only in a private IP network.
We will discuss other options to perform L3 pseudowire termination later in this module.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 20
 2 Internet Enhanced Service
2.2 IES interface—IP interface comparison

IES 500 Interface

Interface OSPF OSPF

SAP Port

IES interface IP interface

An IES can have more than one logical IP routing interfaces each with a SAP which
acts as the access point to a subscriber network.

4 — 1 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The IES is a routed connectivity service in which the subscriber communicates with an IP router interface to send
and receive Internet traffic. The IES is comparable to a regular router interface, and it seems that it behaves the
same as any IP interface on a service router. You can even consider offering a Layer 3 non-VPN type of services
with a regular IP interface.
However, an IP interface is connected to a port and an IP interface within an IES service is connected to a SAP.
This is the fundamental difference between an IP interface and an IES, as most of the policies are service
oriented. The SAP ingress and egress QoS, filter and accounting policies work on the basis of a SAP.
Like a regular IP interface, an IES interface can run a routing protocol; on this slide, the routing protocol is OSPF.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 21
2 Internet Enhanced Service
2.3 IES configuration

CLI Configuration of an IES service.

Configuring IES Service:

*A:P1# configure service ies 500 customer 100 create

Interface on IES context:

*A:P1>config>service>ies# interface "to-CE" create
*A:P1>config>service>ies>if$ address 192.168.10.1/24
*A:P1>config>service>ies>if$ sap 1/1/5:500 create

4 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 22
 2 Internet Enhanced Service
2.4 Internet Enhanced Service (IES)

SAP
ePipe 200

IES 500 IES 520 SDP

OSPF
SDP
SAP SAP

The interface of an IES service can be included in static, RIP, OSPF, ISIS, and
BGP routing protocols. The IES interface runs the routing protocol signaling
with the customer as any other routed IP interface.

4 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

There is an option not to make the connection directly to a routed network, but use the IES to connect to an SDP.
The SDP pseudowire on a PE is bounded to the IES service, and the SDP pseudowire on the other is PE bound to
another non-IES service. Typically, the non-IES service is a VPLS, Ipipe or Epipe service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 23
2 Internet Enhanced Service
2.5 IES in Routing Protocols

IES interface is visible at the base router context

*A:P1# show router interface

============================================================================
Interface Table (Router: Base)
============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
----------------------------------------------------------------------------
system Up Up/-- Network system
10.10.10.1/32 n/a
to-Client Up UP/-- IES 1/1/5:500
192.168.10.1/24 -

4 — 1 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 24
 Knowledge check

Indicate if each of the following statements is true or false.

a) An IES is a VPN type of service

b) An IES is switched service
c) An IES interface can be set in the OSPF context

4 — 1 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) False—although there is an option to terminate a VPN service to an IES.
b) False—the IES is routed service.
c) True

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 25
 3 Epipe service

4 — 1 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 26
 3 Epipe service
3.1 Epipe service overview

Epipe service

PE A PE C

IP / MPLS
Network
PE B

The Epipe service provides an Ethernet point-to-point connection between

two locations. From the customer perspective, the Epipe operates as a VLL
between the two locations.

4 — 1 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The Epipe service does not require MAC learning, so all traffic presented on the Ethernet SAP on one
side will be sent over the pseudowire to the Ethernet SAP on the other side. However, the operator has
the option to apply billing, ingress and egress QoS and filter policies.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 27
 3 Epipe service
3.2 Distributed Epipe

Epipe Epipe
SDP SDP SAP
SAP

A distributed Epipe service always involves two PEs. Each PE has one Epipe
service instance configured, and one SAP and one SDP connected.
Traffic that comes from a SAP is sent to the SDP. Traffic that comes from the
SDP is sent to the SAP.

4 — 1 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

A distributed Epipe service always involves two PEs. Each PE has one Epipe service instance configured, and one
SAP and one SDP connected.
Traffic that comes from the SAP is sent to the SDP. Traffic that comes from the SDP is sent to the SAP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 28
 3 Epipe service
3.3 Epipe configuration

Epipe service creation

PE1# configure service epipe 500 customer 100 create

PE1>config>service>epipe$ description “epipe service”
PE1>config>service>epipe# no shutdown

PE1>config>service>cust$

[no] contact - Configure contact Information

[no] description - Description for this customer
[no] multi-service-* + Configure a multi-service site for
this customer
[no] phone - Phone numbers for the contact

The customer ID is useful for troubleshooting. When a particular customer ID

is applied multiple times to certain services, it is easier to retrieve all service
information associated with a specific customer ID.

4 — 1 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide shows the command to create Epipe service. The service ID is 500, and the customer ID is 100. You need
to assign the service to a customer ID only when creating the Epipe service.
The Epipe service description is optional, but it can be useful for troubleshooting and verifying service
information.

The slide also shows the SR-OS CLI command context for specifying customer information. Contact, description,
multi-service site and phone number are the options that you can configure for a customer.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 29
 3 Epipe service
3.4 Epipe SAP configuration parameters

SAP parameters

PE1>config>service>epipe
PE1>config>service# epipe 500
PE1>config>service>epipe# sap 2/1/3:0
PE1>config>service>epipe>sap# ingress
PE1>config>service>epipe>sap>ingress# qos 555
PE1>config>service>epipe>sap>ingress# filter ip 1
PE1>config>service>epipe>sap>ingress# exit
PE1>config>service>epipe>sap# egress
PE1>config>service>epipe>sap>egress# qos 627
PE1>config>service>epipe>sap>egress# scheduler-policy alpha
PE1>config>service>epipe>sap>egress# exit
PE1>config>service>epipe>sap#

The SAP ingress and egress configuration steps are optional here.

4 — 1 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide shows the commands required to add a SAP to the service (SAP 2/1/3:0), and to configure the following
SAP parameters:
a) ingress qos
b) ingress IP filter policy
c) egress qos
d) egress scheduler policy

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 30
 3 Epipe service
3.5 Epipe SDP bindings

SDP configuration

User-assigned
Service ID SDP number vc-id

PE1>config>service>epipe
PE1>config>service# epipe 500
PE1>config>service>epipe# spoke-sdp 2:500 create
PE1>config>service>epipe>spoke-sdp$ no shutdown
PE1>config>service>epipe>spoke-sdp$ exit
PE1>config>service>epipe# no shutdown
PE1>config>service>epipe# exit all

The vc-id identifies the pseudowire used between the two PE routers. A
combination of sdp-id and vc-id uniquely identifies the pseudowire.

4 — 1 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

After creating the Epipe service and associating it with a SAP, you need create an SDP on the service. The
example on this slide shows the commands to add SDP 2 with a vc-id of 500 to the e-pipe service 500.

The vc-id must match the vc-id of the SDP on the other sides. This is the ID that is used during the TLDP
negotiation. The type of spoke is the only type of SDP possible; there cannot be any loops in a point-to-point
service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 31
 Knowledge check

Indicate if each of the following statements is true or false.

a) The customer ID needs to be the same on both sides of a distributed

Epipe service.
b) The service ID needs to be the same on both sides of a distributed
Epipe service.
c) The VC-ID needs to be the same on both sides of a distributed Epipe
service.

4 — 1 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) False
b) False
c) True—the VC-ID is the only ID setting that needs to match on both sides of an Epipe service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 32
 4 VPLS

4 — 1 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This section describes the Virtual Private LAN Service (VPLS).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 33
 4 VPLS
4.1 VPLS as switch

PE B

PE A PE C

Switch
IP/MPLS
Network
LSP full-mesh

PE D

The VPLS acts as an intelligent switch where customers are connected to

geographically separate PEs.

4 — 1 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

A distributed VPLS service is a VPLS that includes more than one PE router, and acts as an intelligent switch. All
SAPs towards the CEs can be perceived as the ports of the switch, and all the SDPs act as the internal traffic
paths of the switch.
The FDB MAC table is spread amongst all PE routers. A separated FDB table is kept for each VPLS service instance
on a PE.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 34
 4 VPLS
4.2 VPLS over MPLS

PE B

VPLS service

VPLS service

PE A PE C

IP / MPLS
Network
LSP full-mesh

PE D

For each VPN at each site, a Customer Edge device connects to the Provider Edge
router via a point-to-point access connection.

4 — 1 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Ethernet serves as the framing technology between the CE device and the PE router in the provider
network. Frames can include IEEE 802.1Q Ethernet VLAN tags, which allow customers to segment their
networks and assign quality-of-service priorities to LAN traffic. VPLS also supports “QinQ”
encapsulation, where a second VLAN tag is added as a service delimiter. From the customer
perspective, the entire VPN looks like a single Ethernet switched LAN, with the PE acting as a switch
that switches frames on the basis of their Layer-2 destination MAC addresses.

On the provider side, however, PEs are connected by GRE and/or MPLS tunnels.
•If the PEs are connected by GRE tunnels, traffic is encapsulated and routed through the core network
using standard IP frame formats and addressing.
•If PEs are connected by MPLS tunnels, traffic is encapsulated in an MPLS frame and transmitted using
MPLS labels.

In a basic configuration, all PEs need to be fully meshed to connect all PEs to a VPLS service.
However, a different SDP is available so that there is no need for a full mesh, as discussed later in
the module.
The VC label negotiation uses draft-martini/TLDP on a point-to-point basis. Therefore, for 4 PEs, 6
bidirectional point-to-point TLDP sessions are established.

Unknown data traffic or broadcast traffic is replicated in the VPLS service domain. Unknown data
traffic arriving on a SAP is flooded to all SDPs belonging to the VPLS service. At the same time, MAC
addresses are learned over the SDP tunnels and SAP access ports.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 35
 4 VPLS
4.3 VPLS customer operation

CE B
CE A VPLS 1
10.10.1.x

CE B VPLS 2 CE A
20.20.2.x

CE A CE B

The addition of a new site requires no configuration of the service provider

equipment or of the customer equipment at existing sites.

4 — 1 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Customers maintain complete control over their routing. The provider is never interfering at the IP level. This
clear demarcation of functionality between the service provider and customer makes troubleshooting easier.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 36
 4 VPLS
4.4 Configuring full-mesh VPLS service
PE1>config>service# info PE2>config>service# info
---------------------------------------------- ----------------------------------------------
... Output omitted ... ... Output omitted ...
vpls 316 customer 300 create vpls 316 customer 300 create
sap 1/1/5:316 create sap 1/1/5:316 create
exit exit
mesh-sdp 32:316 create mesh-sdp 31:316 create
no shutdown no shutdown
exit exit
mesh-sdp 33:316 create mesh-sdp 33:316 create
no shutdown no shutdown
exit exit
no shutdown no shutdown
exit exit

The VC ID for mesh SDPs does not

PE1 PE2 need to be entered; by default, it
is equal to the VPLS ID (316).

PE3>config>service# info
----------------------------------------------
... Output omitted ...
vpls 316 customer 300 create
sap 1/1/5:316 create
exit
mesh-sdp 31:316 create
no shutdown
exit
mesh-sdp 32:316 create
no shutdown
exit
no shutdown
exit
PE4 PE3

4 — 1 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide outlines how to create a full-mesh of SDPs on PE1, PE2, and PE3. This configurations prevents the
formation of loops. A mesh SDP never forwards traffic to another mesh SDP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 37
 Knowledge check

Indicate if each of the following statements is true or false.

a) A VPLS is a Layer 2 VPN.

b) A VPLS learns destination data MAC addresses automatically.
c) A VPLS learns source data MAC addresses automatically.

4 — 1 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) True
b) False
c) True

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 38
 5 VPRN

4 — 1 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This section describes the Virtual Private Routed Network (VPRN). The VPRN is a network exhibiting at least some
of the characteristics of a private network, even though it uses the resources of a public switched network.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 39
 5 VPRN
5.1 VPRN overview
Route table for VPRN 1

192.168.2.0/24
192.168.1.0/24 Customer 1
VPRN
Customer 1 Customer 1

Customer 2
VPRN 192.168.2.0/24
192.168.1.0/24 Customer 2
Customer 2

Route table for VPRN 2

VPRN instance 1
VPRN instance 2

The PE router contains a separate route table for each VPN instance. This table is
known as the Virtual Routing and Forwarding (VRF) table.

4 — 1 — 40 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide shows an example of VPRN. The VPRN implementation is based on RFC 4364.

The VPRN is designed to meet the following goals:

•connectivity between remote customer sites
•isolation of routing and traffic from different VPNs
•potential use of private address spaces in each site

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 40
 5 VPRN
5.2 VPRN route distinguisher

Different customers can use the same IP addresses in their networks. An

identifier called Route Distinguisher is added to all IPv4 prefixes to ensure
that the IP addresses remain unique.

Route distinguisher + IPv4 prefix = VPN-IPv4 prefix

8 bytes 4 bytes 12 bytes

Route Table (Router: Base) Route Table (Router: Base)

================================ =================================
Dest Address Next Hop Proto Dest Address Next Hop Proto
-------------------------------- ---------------------------------
192.168.1.0/24 CE_Blue BGP 65530:20:192.168.1.0/24 CE_Blue BGP
192.168.1.0/24 CE_Red BGP 65530:10:192.168.1.0/24 CE_Red BGP

Conflict

4 — 1 — 41 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The Route Distinguisher value is needed to make the VPN routes unique. This is necessary because all VPN routes
are carried in the same routing protocol (MP-BGP).

Different customers can use the same IP addresses within their respective networks. A method is needed to
ensure that the IP addresses remain unique when they are distributed across the service provider network. This is
achieved by prefixing the 4-byte IPv4 address with an 8-byte Route Distinguisher value to form a new address
called VPN-IPv4 address. A distinct Route Distinguisher value can be associated with individual routes or with all
routes learned from a particular CE.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 41
 5 VPRN
5.3 VPRN Route Target

MP-BGP Update
(Prefix
=65530:20:192.168.1.0
RT = 65530:20)
192.168.1.0/24 CE1 VRF1 target
Customer 1

Customer 1 = 65530:20 CE1

CE1 PE1 PE2

CE1
VRF2 target
= 65530:10 Customer 2
Customer 2

In simple VPN cases and for provisioning consistency, the chosen RT value can be
the same as the RD value. However, the RT and RD do not mean the same thing.

4 — 1 — 42 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide describes the VPRN Route Target.

In some situations, the same set of PE routers may need to exchange routes corresponding to different
VPRN service instances. In addition, to improve scalability, the PE routers establish a single MP-BGP
session for the VPN-IPv4 family of prefixes.
Some mechanism is needed to determine to which VRF each route belongs. A Route Target value was
defined to address this issue. The Route Target (RT) is the closest approximation to a VPN membership
identifier in the VPRN architecture, and identifies to the receiving PE the VRF table that a prefix is
associated with.
The Route Target is an MP-BGP extended community. One or more MP-BGP community attributes can be
associated to any route; as a result, one or more Route Target values can be associated to any route.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 42
 5 VPRN
5.4 VPRN and MP-BGP

MP-BGP Update
(Prefix
=65530:20:192.168.1.0
RT = 65530:20)
192.168.1.0/24 CE1 VRF1 target
Customer 1

Customer 1 = 65530:20 CE1

CE1 PE1 PE2

CE1
VRF2 target
= 65530:10 Customer 2
Customer 2

The multiprotocol BGP (MP-BGP) capability allows routers to carry VPN-IPv4

prefixes, along with the RT as an extended community attribute. Only the
provider edge routers need to know the VPN-IPv4 addresses.

4 — 1 — 43 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

In a VPRN implementation, BGP is used with Multiprotocol BGP extensions to distribute VPRN routing
information across the service provider network.
To carry VPN-IPv4 prefixes in BGP, support for the additional address family is required. Separate BGP
sessions must be enabled between every pair of routers for each of the address families they need to
exchange. When BGP is configured or enabled in this fashion, it is referred to as Multiprotocol BGP or
MP-BGP.

The Multiprotocol nature of MP-BGP allows the overlapping routing information to be transported across
the provider core as VPN-IPv4 addresses. VPRN routes are not distributed as IPv4 routes, but as 12 byte
VPN-IPv4 routes consisting of a concatenation of the Route Distinguisher and the IPv4 prefix.

It is important to note that the VPN-IPv4 address family is used only in the control plane when
exchanging MP-BGP routing updates between PEs. The data plane remains as standard IPv4. VRFs store
IPv4 prefixes without RD or RT values, and all data traffic is carried in standard IPv4 packets.

The customer is unaware of the existence of VPN-IP addresses. The translation between customer IP
routes in a particular VPN and VPN-IP routes distributed between provider routers is performed by the
PE routers.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 43
 5 VPRN
5.5 Prerequisite step: configuring full-mesh MP-BGP sessions

MP-BGP session configuration

PE1>config>router# info
#--------------------------------------------------
echo "IP Configuration"
#--------------------------------------------------
... Output omitted ...
autonomous-system 64500
#--------------------------------------------------
echo "BGP Configuration"
#--------------------------------------------------
bgp
group "VPRN-GROUP"
family vpn-ipv4
peer-as 64500
neighbor 10.10.10.2
exit
neighbor 10.10.10.3
exit
neighbor 10.10.10.4
exit
exit
no shutdown
exit

4 — 1 — 44 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

When creating a distributed VPRN, you need to establish MP-BGP sessions between all the PE routers that are part
of the VPRN.
The slide shows the configuration commands for the PE1 router in a VPRM that contains PE1, PE2, PE3, and PE4.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 44
 5 VPRN
5.6 Verifying the full-mesh MP-BGP session configuration

Show router BGP configuration

PE1# show router bgp summary

============================================================================
BGP Router ID:10.10.10.1 AS:64500 Local AS:64500
============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 3
... Output omitted ...
============================================================================
BGP Summary
============================================================================
Neighbor AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr
Family)
PktSent OutQ
----------------------------------------------------------------------------
10.10.10.2 64500 13 0 00h05m40s 0/0/0 (VpnIPv4)
13 0
10.10.10.3 64500 14 0 00h05m40s 0/0/0 (VpnIPv4)
15 0
10.10.10.4 64500 14 0 00h05m40s 0/0/0 (VpnIPv4)
15 0

4 — 1 — 45 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

You can use the command show router bgp summary on each PE router to verify that the configuration has
been successful. On this slide, the command output shows that BGP is operationally enabled, and that the router
has three BGP peers. The output also indicates that the family of the prefixes to be exchanged with each
neighbor is VPN-IPv4, and that the routers have not exchanged any prefixes yet.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 45
 5 VPRN
5.7 VPRN data plane—transport tunnel

192.168.1.0/24 CE1 Customer 1

Customer 1 PE1 PE2 CE1

LSP

CE1 LSP
CE1
Customer 2
Customer 2

Each PE that is part of a VPRN needs to have a tunnel to every other PE in the
same VPRN service. The PE-to-PE tunnels carry the customer VPN traffic from
one site to another.

4 — 1 — 46 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

After establishing the routing topology in the provider core, you need to create a full mesh of transport
tunnels between the PEs in the same VPRN service. Each PE that is part of a VPRN service needs to be
configured with a tunnel to every other PE in the same VPRN service. The transport tunnel can be either
an MPLS LSP or a GRE point-to-point tunnel. The tunnels serve as label switched paths for customer
packets across the provider core network.

The tunnel is created in one of the following ways:

through the configuration of an SDP that is bound to the service
or

through the auto-bind option used when creating a VPRN service instance.

The auto-bind option is possible for VPRN, but not for the other service types, because in this case an
MP-BGP session is established between every pair of PE routers that participate in the service in order
for them to exchange routing information (VPN prefixes). So the PE peers have been identified.
Therefore, when the auto-bind command is issued, LSPs are automatically created from a router to each
of the other routers with which an MP-BGP session is established for the VPN family of prefixes.

If SDP tunnels are used, they need to be created prior to the creation of the VPRN services.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 46
 5 VPRN
5.8 VPRN VPN label
MP-BGP Update
(Prefix
=65530:20:192.168.1.0
RT = 65530:20
192.168.1.0/24 CE1 VPN Label = 131068) Customer 1

Customer 1 CE1

CE1 PE1 PE2

CE1
Customer 2
Customer 2

VPN
MPLS IP Data
Layer 2 Label
Label
131068

For data traffic at an egress PE, the router needs to decide how to forward
each packet, depending on the customer that the packet belongs to. The
router uses the VPN (service) label distributed by MP-BGP with the route for
this purpose.

4 — 1 — 47 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

The purpose of the VPN label is to demultiplex VPN traffic arriving at the PE. The distribution of the
VPN label is done using BGP along with the VPN route information. The distribution of the VPN tunnel
information is automatic, and does not require manual intervention.

The service label scheme is configurable for the VPRN as either a service label per VRF or as a service
label per next-hop. When a VPRN is configured for service label per next-hop, MPLS allocates one
unique (platform-wide) service label for every next-hop IP address of the VPRN. When the PE receives a
terminating MPLS packet, the PE forwards the packet to the next-hop that the service label is
associated with, without any VRF lookup.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 47
 5 VPRN
5.9 VPRN configuration

1 Create the VPRN and associate it with a customer ID.

Specify Route Distinguisher (route-distinguisher) and Route Target

2 (vrf-target) parameters.

Create transport tunnels (individual SDPs to other PEs or through

3 the auto-bind option); step required only for distributed VPRNs.

Create VPRN interfaces, as needed, to interact with customer sites

4 (same steps as when creating an interface for an IES service).

3
Configure the routing protocol used to exchange routing
5 information with the customer.

4 — 1 — 48 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide outlines the steps required to configure a VPRN.

In VPRNs, the MP-BGP is the protocol in charge of allowing PE routers to share the routing information that they
have, corresponding to the different customer sites. In preparation for a (distributed) VPRN configuration, a mesh
of MP-BGP sessions among the PE routers needs to be established. Once an MP-BGP session has been established,
it can be reused to share routing information belonging to as many VPRN services as there can be between pairs
of PE routers.

Creating an interface for a VPRN requires the same steps as for creating an interface for an IES service. The
following components are needed:
•Interface name
•Interface IP address
•A way of receiving/sending IP packets from/to the customer

There are three options for receiving/sending IP packets:

•Through a SAP—if the customer is directly connected to the PE router
•Through an SDP—if the PE router is connected to the customer by way of a spoke SDP that originates on another
router (coming from an Epipe, Ipipe or VPLS service)
•Through a VPLS—if the same layer-3 interface is used to provide services to several customer locations that
belong to the same virtual private LAN (routed VPLS)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 48
 5 VPRN
5.10 VPRN configuration

1 Configuring L3VPN/VPRN:
*A:P1# configure service vprn 1500 customer 1 create

2 Route Distinguisher and Route Target:

*A:P1>config>service>vprn$ route-distinguisher 1500:64500
*A:P1>config>service>vprn$ vrf-target "target:1500:64500“

Transport Tunnels:

3 *A:P1>config>service>vprn$ auto-bind {ldp|gre|rsvp-

te|mpls|mpls-gre}
*A:P1>config>service>vprn# spoke-sdp <sdp-id> create

Interface on VPRN context:

4 *A:P1>config>service>vprn# interface "to-CE" create
*A:P1>config>service>vprn>if$ address 192.168.10.1/24
*A:P1>config>service>vprn>if$ sap 1/1/5:1500 create
3
Routing Protocols on VPRN context:
5 *A:P1>config>service>vprn# ospf
*A:P1>config>service>vprn# bgp
*A:P1>config>service>vprn# rip

4 — 1 — 49 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

This slide outlines the CLI configuration based on the steps of the previous slide.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 49
 Knowledge check

Indicate if each of the following statements is true or false.

a) A VPRN uses T-LDP to distribute service labels.

b) Route targets are used to make routes unique in MP-BGP.
c) Each VPRN has its own routing table, called a VRF table.

4 — 1 — 50 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) False
b) False
c) True

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 50
End of module
Services Overview

4 — 1 — 51 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.1 Edition N/A
Section 4 — Module 1 — Page 51
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 2
Services Components
TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—2—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 1
 Blank page

4—2—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 2
Module objectives

Upon completion of this module, you should be able to:

Describe the components of a service.

SAP

Mesh SDP

Spoke SDP

Describe how traffic is flooded within the components of a service

4—2—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 3
Module objectives [cont.]

4—2—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 4
 Table of Contents

1 Services Components 7
Page

1 Services Components 7
1.1 Service Components 8
1.2 Customers or Subscribers 9
1.3 Service Access Points 10
1.4 Service Distribution Point 11
1.5 SDP Creation 12
1.6 SDP Types 13
1.7 SAP Interaction 14
1.8 Spoke SDP Interaction 15
1.9 Mesh SDP Interaction 16
1.9 Mesh SDP Interaction 17

4—2—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 5
Table of Contents [cont.]

4—2—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 6
 1 Services Components

4—2—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 7
 1 Services Components
1.1 Service Components

Service Service Service Service

Access Distribution Distribution Access
Subscribers Points Point Point Points Subscribers

Service 50 Service 50 Customer

Customer SAP
100 SAP 100
Customer 100
Customer 100

SDP 3 Demux

Demux SDP 5
Customer 200 Customer 200
Customer Customer
SAP SAP 200
200 Service 25 Service 25

Service Tunnels

4—2—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

This slide provides a review of the major components of a service.

A service uses an SDP service tunnel to direct traffic from one router to another. The service tunnel
is provisioned with an encapsulation type of GRE or MPLS and services are mapped to the service
tunnel that most appropriately supports the service requirements. An SDP is configured before one
or more services can use this tunnel. An SDP is not a protocol, but a logical entity represented by a
number that is linked to, for example, an LSP in the case of an MPLS RSVP-TE SDP.

A SAP is a logical entity that serves as the customer point of access to a service. Each subscriber
service is configured with at least one SAP. A SAP can be configured only on an access port. The
SAPs for IES and VPRN services are configured on IP interfaces within the service.

An SDP acts as a logical way of directing traffic from one router to another through a unidirectional
service tunnel. An SDP originating on one node terminates at a destination node, which then directs
incoming packets to the correct service egress SAPs on that node. A multi-node service needs at
least one SAP and one SDP on each node. For a service to be bidirectional, an SDP must be
provisioned on each node participating in the service.

The customer ID is a mandatory part of the service creation. The customer ID is a locally significant
number that is mainly used to link customer credentials to a service. These credentials can be a
phone number, a name and an address. When a relevant customer ID is not required, the default
customer ID value of 1 can be used.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 8
 1 Services Components
1.2 Customers or Subscribers

•When configuring a service, the customer id will need to be specified

within the service creation.
•If no customer id is associated, the system will not allow the creation of
the service.
•Once the customer has been linked to the service, this may not be
changed and a different service instance will have to be created.
•Multiple services may be linked to a specific customer.
•Customer 1 is the default customer in the SR-OS.
customer 1 create
description "Default customer"
exit
Default Customer
customer 100 create
description "Acme Networks - IPTV
services"
Custom Customer contact "John Doe"
phone "(XXX)XXX-XXXX"
exit

4—2—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

A new customer or subscriber is created by typing the following command “configure service customer
<customer-id> create”. Within the customer context, there are several fields that can be entered in order to help
the user distinguish the multiple customers that an equipment may have.

*A:SAR8_210>config>service# customer 100 create

*A:SAR8_210>config>service>cust$
[no] contact - Configure contact Information
[no] description - Description for this customer
[no] phone - Phone numbers for the contact

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 9
 1 Services Components
1.3 Service Access Points

Service Access Points (SAPs) serves as a customer point of entry to a

service. Depending on the encapsulation type a SAP can be used for one
or multiple services.

In the 7705, ports are automatically configured with ‘access mode’ and
‘null’ encapsulation. If a SAP is to be used in multiple services, the
encapsulation type will need to be changed dot1q or qinq depending on
service requirements.

*A:SAR8>config>port# info
description "port 1/3/2 10/100 Ethernet TX«
ethernet
mode access
encap-type {dot1q|null|qinq}

4 — 2 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Service Access Points are used as the entry points for customer traffic. These SAPs can be tied to one service or
multiple services depending on the encapsulation of the port (qinq, dot1q, or the default null). SAPs have a
default MTU of 1514 bytes.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 10
 1 Services Components
1.4 Service Distribution Point

Service Distribution Point (SDP) serves to direct traffic in a service from

one router to another. SDPs can use MPLS (LDP or RSVP-TE) or GRE to be
established.

Creating a GRE based SDP:

*A:SAR8# configure service sdp 100 create

Creating a LDP based SDP:

*A:SAR8# configure service sdp 120 mpls create
*A:SAR8>config>service>sdp$ ldp

Creating a RSVP-TE SDP:

*A:SAR8# configure service sdp 140 mpls create
*A:SAR8>config>service>sdp$ lsp "to-R4"

4 — 2 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

These are just quick examples of different types of SDPs. A GRE SDP does not use “mpls” in the creation of an
SDP. For LDP or RSVP-TE based SDPs, “mpls” should be used when the SDP creation. If this step is forgotten, ldp
or lsp will not be able to be specified within the SDP context. The newly created SDP will have to be deleted, and
recreated with the “mpls” context in the SDP creation.

Now, when a LDP based SDP creation “ldp” will have to be used in the SDP’s context, but before the system will
take the “ldp” command the far-end address will have to be configured. The same applies for the enablement of
a RSVP-TE or LSP based SDP, as the far-end will need to be configured appropriately. Another important criteria
is to ensure that the address configured under the LSP matches the far end address under the SDP or the
following error will be displayed.

MINOR: SVCMGR #1914 The specified LSP-id is invalid or does not terminate at the SDP's far-end address

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 11
 1 Services Components
1.5 SDP Creation

In order to create a basic SDP the following will need to be configured.

For this example a LDP based SDP will be configured.

•SDP ID: In the example below 120 was used, but this number is locally
significant.
•Far-End: The SDP endpoint of the tunnel, typically the system address is
used.
•LDP – enables LDP to be used as the SDP transport method
•No shutdown – brings the SDP up, as it is shutdown by default

*A:SAR8_210# configure service sdp 120 mpls create

*A:SAR8_210>config>service>sdp$ far-end 3.3.3.3
*A:SAR8_210>config>service>sdp$ ldp
*A:SAR8_210>config>service>sdp$ no shutdown

4 — 2 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

The configuration shown above is the bare minimum to bring up a LDP based SDP. Keep in mind that the far-end
should be IP reachable in order for the SDP to come up. The transport method, in this case LDP, should also be
operational and a label should be available to 3.3.3.3. Once IGP and MPLS are operating correctly, the SDP will
come up. This can be verified by running “show service sdp <sdp-id>”.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 12
 1 Services Components
1.6 SDP Types

In order for SDP to be fully functional, it should be bound to a service. An

SDP may be of either type spoke or mesh. The type of SDP will indicate
how flooded traffic is transmitted

Spoke SDP: Similar to a traditional bridge port behavior. Traffic that is

received is transmitted to all other “ports”, except for the “port” in
which it was received. In this case traffic that is received on a Spoke SDP
is transmitted to all other SAPs, Spoke or Mesh SDPs.

Mesh SDP: Traffic that is received on a Mesh SDP is transmitted to all SAPs
and Spoke SDPs. Traffic will not be forwarded to another Mesh SDP. As of
now, Mesh SDPs are only allowed to be configured in VPLS services.

4 — 2 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Spoke SDPs may be used in all services, and as mentioned above will transmit traffic to all service interfaces
(SAPs, Mesh SDPs, Spoke SDPs) except on the service interface that received the traffic. Loops may be caused by
this method, with incorrect configuration and network management. Mesh SDPs is used in VPLS services for that
same reason, to prevent loops.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 13
 1 Services Components
1.7 SAP Interaction

Flooded traffic received on a SAP is replicated to all service interfaces

(Spoke and Mesh SDPs and other SAPs).

SAP

S-SDP
SAP Service 50

M-SDP

M-SDP

4 — 2 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Flooded traffic that is received on a SAP is replicated to all other service interfaces as observed above.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 14
 1 Services Components
1.8 Spoke SDP Interaction

Flooded traffic received on a Spoke SDP is replicated to all service

interfaces (Spoke and Mesh SDPs and SAPs).

SAP

S-SDP
S-SDP Service 50

M-SDP

M-SDP

4 — 2 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Flooded traffic that is received on a Spoke SDP is replicated to all other service interfaces as observed
above.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 15
 1 Services Components
1.9 Mesh SDP Interaction

Flooded traffic received on a Mesh SDP is replicated to all service

interfaces (Spoke SDPs and SAPs), but not to other Mesh SDPs.

SAP

S-SDP
M-SDP Service 50

M-SDP

M-SDP

4 — 2 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Flooded traffic that is received on a Mesh SDP is replicated to all SAPs and Spoke SDPs as observed
above.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 16
End of module
Services Components

4 — 2 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — Services Components
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.2 Edition N/A
Section 4 — Module 2 — Page 17
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 3
C-Pipe
TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—3—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 1
 Blank page

4—3—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 2
 Module objectives

Upon completion of this module, you should be able to:

Identify the applications for Cpipe.

List the building blocks of a Cpipe.

Describe the different E1/T1 mode of operations (SAToP/CESoP).

Explain the relationship between packet size and latency.

4—3—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This module covers the Cpipe service. A Cpipe, or circuit emulation VLL service, provides a point-to-point CEM
service between users who connect to devices in an IP/MPLS network directly. The endpoints of a Cpipe use CEM
encapsulation.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 3
Module objectives [cont.]

4—3—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 4
 Table of Contents

1 Cpipe Overview 7
Page
2 TDM options 18
1 Cpipe Overview
3 Packet size and latency 7 26
1.1 Cpipe Applications 8
1.2 Service Configuration Model 9
1.3 SAP Configuration Overview 10
1.4 SDP Configuration Overview 11
1.5 SDP configuration—VC labels 13
1.6 Service configuration summary: SDP to SAP 14
1.7 Pseudowire overview 15
1.8 SAP and SDP flooded traffic 16
1.9 Anatomy of Circuit Emulation Services over MPLS 17
2 TDM options 18
2.1 E1 frame 19
2.2 7705 SAR end-to-end TDM transport model 20
2.3 Transport of structured and unstructured connections 21
2.4 Encapsulation 22
2.5 Channel group timeslots for CESoPSN—E1 frame 23
2.6 Channel group timeslots for CESoPSN—T1 frame 24
3 Packet size and latency 26
3.1 Packet size vs. packet latency 27
3.2 Packet size and packet latency calculations 28
3.3 Exercise 29
3.44 —Encapsulation
3—5
into TDM PW packets (SAToP, RFC4553) 30
3.5Services
Packet— C-Pipe jitter
7705 SAR — R6.0 Strategic Industries
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
31
3.6 Jitter buffer 32
3.7 Handling packet loss 33
3.7 Handling packet loss 34

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 5
Table of Contents [cont.]

4—3—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 6
 1 Cpipe Overview

4—3—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 7
 1 Cpipe Overview
1.1 Cpipe Applications

Legacy technologies
E1/T1
E3/T3 SDI E&M
FXS/FXO

Cpipe service

PE A PE B

IP/MPLS
network

4—3—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Legacy technology that required PDH/SDH technology in the past can now be transported through an IP/MPLS
network with one service: Cpipe (Circuit Emulation Pipeline).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 8
 1 Cpipe Overview
1.2 Service Configuration Model

Customer Customer
100 SAP SAP 100
SDP 3 Label Switched Path Demux
Service 50 Service 50

Demux Label Switched Path SDP 3

SAP is the Tunnels are SDP binds multiple

customer point of unidirectional and are services to a tunnel
access paired to provide a
bidirectional service

A Cpipe service is based on SAPs, SDPs, and tunnel encapsulation.

4—3—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide shows the service configuration model, and describes the service components.

To create and provision a Cpipe service, you need to configure the following parameters:
•Customer ID
•Service type
•Service Access Point (SAP)—logical entry/exit point for the service.
•Service Distribution Point (SDP)—unidirectional connection between services distributed across an MPLS
network.

The next slides describe the main service components: SAPs, SDPs, and tunnels.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 9
 1 Cpipe Overview
1.3 SAP Configuration Overview
*A:PE1>config>service>cpipe$
[no] description - Description for the service
[no] endpoint + Configure a service end-point Cpipe
[no] sap + Provision a SAP
[no] service-mtu - Configure service MTU configuration
[no] service-name - Configure a service name options
[no] shutdown - Administratively enable/disable the service
[no] spoke-sdp + Provision a spoke SDP binding
*A:PE1>config>service>cpipe$ sap
- no sap <sap-id>
- sap <sap-id> [create] [no-endpoint] SAP
- sap <sap-id> [create] endpoint <endpoint-name> configuration
... output ommitted ...
options

<create> : keyword - mandatory while creating an entry.

<endpoint-name> : [32 chars max]
<no-endpoint> : keyword - used to remove an endpoint association

[no] accounting-pol* - Configure accounting-policy to be used

cem + Configure CEM properties
[no] collect-stats - Enable/disable statistics collection
[no] description - Description for the SAP
[no] dist-cpu-prote* - Assign Distributed CPU protection policy for the SAP
egress + Configure egress policies
ingress + Configure ingress policies
[no] multi-service-* - Specify the multi-service-site to which this SAP belongs
[no] shutdown - Administratively enable/disable the SAP
[no] tod-suite - Configure a time-of-day suite for this SAP

4 — 3 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide shows the SR-OS CLI context for the configuration of a Cpipe service, and the parameter options
available for the SAP configuration. You will have the chance to practice the creation and configuration of a
Cpipe service in the lab module associated with this topic.

Now let us review some consideration that apply to the SAP configuration:
•A SAP is locally unique (the SAP ID value can be used on another device)
•A SAP is associated with a single service and can be configured only on an access port
•A port or channel can contain more than one configured SAP
•All SAPs must be created, and administratively enabled at the time of creation (no default SAPs)
•VLAN IDs have local significance.
• A SAP can be configured with:
• Ingress and egress filter policy
• Ingress and egress QoS policy
• Ingress and egress scheduler policy
• Accounting policy

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 10
 1 Cpipe Overview
1.4 SDP Configuration Overview

*A:PE1>config>service>cpipe$ spoke-sdp
- no spoke-sdp <sdp-id:vc-id> SDP
- spoke-sdp <sdp-id:vc-id> [create] [no-endpoint]
- spoke-sdp <sdp-id:vc-id> [create] endpoint <endpoint-name> [icb] configuration
options
<sdp-id:vc-id> : sdp-id - [1..17407]
vc-id - [1..4294967295]
<create> : keyword - mandatory while creating an entry.
<endpoint-name> : [32 chars max]
<no-endpoint> : keyword - used to remove an endpoint association
<icb> : keyword - configure spoke-sdp as inter-chassis backup

[no] accounting-pol* - Configure accounting-policy to be used

[no] bandwidth - Configure the spoke-sdp bandwidth
[no] collect-stats - Enable/disable statistics collection
[no] control-word - Enable/disable setting the CW bit in the label message
[no] description - Set description for spoke-sdp
egress + Spoke SDP egress configuration
ingress + Spoke SDP ingress configuration
[no] precedence - Configure the spoke-sdp precedence
[no] pw-path-id + Configure PW path identifier information
[no] shutdown - Administratively enable/disable the spoke SDP binding

4 — 3 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide shows the SR-OS CLI context for the addition of an SDP to a Cpipe. Remember that each multi-site
service must have an SDP defined for every remote PE to provide Cpipe, Epipe, VPLS, and VPRN services.

Look at next slide to see how to configure an SDP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 11
 1 Cpipe Overview
1.4 SDP Configuration Overview [cont.]
*A:PE1>config>service# sdp
- no sdp <sdp-id> SDP
- sdp <sdp-id> [delivery-type] [create] configuration
options
<sdp-id> : [1..17407]
<delivery-type> : gre|mpls|l2tpv3
<create> : keyword - mandatory while creating an entry.
[no] accounting-pol* - Configure accounting-policy to be used
[no] adv-mtu-overri* - Override the advertised VC MTU
[no] bgp-tunnel - Enable/disable BGP tunnels
binding + Configure binding information
[no] booking-factor - Configure the SDP booking-factor
[no] class-forwardi* + Configure class-based forwarding
[no] collect-stats - Enable/disable statistics collection
[no] description - Description for SDP
[no] far-end - Configure far-end address
keep-alive + Configure keep alive parameters
[no] ldp - Enable/disable LDP-signaled LSP's
[no] local-end - Configure local-end of the L2TP v3 tunnel
[no] lsp - Configure LSP to be used by SDP
[no] metric - Configure SDP Metric
[no] mixed-lsp-mode + Enable/disable Mixed LSP mode
[no] network-domain - Associate a network-domain
[no] path-mtu - Configure path MTU
[no] pbb-etype - Configure PBB ethertype
[no] sdp-group - Configure SDP group
[no] shutdown - Administratively enable/disable the SDP
signaling - Configure type of VC label signaling
[no] source-bmac-lsb - Configure lsb for Backbone MAC
[no] tunnel-far-end - Configure tunnel-far-end address
[no] vlan-vc-etype - Configure VLAN VC ethertype

4 — 3 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide shows the SR-OS CLI context for the configuration of an SDP. Let us review some SDP characteristics
that can help us configure SDPs:
•SDPs can be created as either GRE or MPLS.
•A service must be bound to an SDP. By default, no SDP is associated with a service. Once an SDP is created,
services can be associated with that SDP.
•An SDP is not specific or exclusive to any service or any type of service. An SDP can have more than one service
bound to it.
•To configure an MPLS SDP, an MPLS infrastructure must be in place. LDP or LSP transport tunnels can be chosen.
•In the SDP configuration, the automatic ingress and egress labeling (targeted LDP) mechanism is enabled by
default. Ingress and egress VC labels are signaled over a TLDP connection between two PE routers.

Note: If signaling on an SDP is disabled, service labels must be manually configured. The next slide describes the
SDP VC label (vc-id parameter on the slide).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 12
 1 Cpipe Overview
1.5 SDP configuration—VC labels

VC label/service label
An inner label (vc-id parameter) identifies traffic as it exits the MPLS network.
Egress and ingress VC labels uniquely identify the service. Incoming traffic is
passed to the appropriate service based on the VC Label.

MPLS VC
DA SA 0x8847 Label Label Payload

Payload Payload

SAP SAP
SDP 3 Label Switched Path Demux
Service 50 Service 50

Demux Label Switched Path SDP 3

4 — 3 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

When an SDP is configured, automatic ingress and egress labeling (targeted LDP) is enabled by default and ingress
and egress “service” labels are signaled over a TLDP connection. If signaling is turned off on an SDP, ingress and
egress “service” labels must be manually configured when the SDP is bound to a service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 13
 1 Cpipe Overview
1.6 Service configuration summary: SDP to SAP

Create Create a Assign a

Customer pseudowire Assign a sap
an SDP spoke-sdp
service

MPLS GRE Cpipe

CESoPSN SAToP E1 CAS TDM E&M SDI

E1 DS1

CAS Channelized Unchannelized

4 — 3 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide shows the steps and workflow that apply to configuring a Cpipe service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 14
 1 Cpipe Overview
1.7 Pseudowire overview

Pseudowire overview
Pseudowire is a service that provides a point-to-point connection between two
nodes. To the access points, a pseudowire behaves as if a leased link existed
between the two locations, and the leased link delivered ATM traffic (Apipe),
TDM traffic (Cpipe), Ethernet traffic (Epipe), and any internetworking
combination between Ethernet and PPP encapsulation (Ipipe).

IP/MPLS network
IP
TDM Tunnel
ATM
Ethernet 7705 SAR
7670 RSP, 7750 SR

4 — 3 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide describes the pseudowire implementation supported by the 7705 SAR, as it relates to various types of
traffic, including Cpipe traffic.

The two locations served by a pseudowire deployment are part of the same Layer 2 network:
•The IP/MPLS core is invisible to the customer.
•The service provider can apply billing.
•The service provider can apply ingress/egress shaping and policing.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 15
1 Cpipe Overview
1.8 SAP and SDP flooded traffic

Cpipe 100 Cpipe 100

SDP SDP SAP
SAP

Flooded traffic received on SAPs and SDPs

When flooded traffic is received, the node replicates it on all other ports
within the service (SDPs and SAPs). The node does not replicate the flooded
traffic on the port it was received on.
•Flooded traffic received on a SAP is replicated to other SAPs, spoke SDPs,
and mesh SDPs. Except SAP in which it was received.
• Flooded traffic received on a spoke SDP is replicated to other SAPs, spoke
SDPs, and mesh SDPs.

4 — 3 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 16
 1 Cpipe Overview
1.9 Anatomy of Circuit Emulation Services over MPLS

5620 SAM
T1/E1
T1/E1

7705 SAR
T1/E1
7705 SAR T1/E1
7705 SAR
T1/E1 7705 SAR
T1/E1
MPLS Transport
nxDS0 or T1/E1 traffic with
the proper encapsulation
CES CES CES
Identifier for the CES Packet Packet Packet
Connection from end to end.
Service Label Service Label Service Label The far end reproduces the
Identifier used for transport MPLS Label MPLS Label MPLS Label
CES Data onto the line and
through the MPLS Network delivers the packets to the
L1/L2 Encap L1/L2 Encap L1/L2 Encap end customer device
Encapsulation dependent on
the physical connectivity Inspection of the Service
The transport network treats Label identifies the context
the service label and the CES for the circuit
information as transparent

4 — 3 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide illustrates the anatomy of Circuit Emulation Services over MPLS.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 17
 2 TDM options

4 — 3 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

The Cpipe service is the Alcatel-Lucent implementation of TDM PW VLL as defined in the IETF PWE3 working
group.
The 7705 SAR can support TDM circuit applications that are able to transport delay-sensitive TDM traffic over a
packet network. Cpipe services over MPLS or GRE tunnels are supported.

This section describes the Time-Division Multiplexing (TDM) options.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 18
 2 TDM options
2.1 E1 frame

Eachtime
Each timeslot carries8 8
slots carries bits
bits of
of dataData or 1 byte
Timeslot
Timeslot 00
1000100010001000
(Reservered)
(reserved)

0 1 2 3 31 1 2
One
One E1E1basic
Basic Frame
frame
(8 (8
+ +3131*8
x 8 ==256
256bits)
bits)

E1 frame details
The E1 frame timeslots are sampled at 8000 times a second. Each E1 frame is
sent every 125 µm. Every millisecond, 8 E1 frames are sent (8 x 125us = 1ms).

4 — 3 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

The Cpipe service supports TDM SAP-to-SAP connections any T1/E1 port or channel that is configured for access
mode and circuit emulation service and another port or channel with the same configuration (endpoint type, bit
rate, payload size, CAS enabled/disabled, and RTP enabled/disabled).

This slide provides general details about the E1 frame.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 19
 2 TDM options
2.2 7705 SAR end-to-end TDM transport model
TDM packets moving in this direction

DS1/E1 Packet Switched DS1/E1

DS1/E1 Packetization Network Jitter buffer DS1/E1
Access (IP/MPLS) Access
circuit circuit

Packetization Network Playout

As TDM traffic from the Fixed delay The TDM PW packets are
access circuit (AC) is • Packet transfer delay received from the PSN and
received, it is packetized and based on link speeds and stored into a configurable
transmitted to the PSN distances from end to end jitter buffer.

Two modes of operation: Variable delay Play-out of the TDM data

• CESoPSN (RFC5086) • The number of and type back into the AC when it is
for structured of switches at least 50% full.
nxDS0/64k channels • Queuing point in the
• SAToP (RFC4553) for switches
unstructured T1/E1
QoS is key to ensure effective
service delivery
4 — 3 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

In the 7705 SAR end-to-end TDM transport model, the size of the packet is driven by the number of frames
transported per packet. It defines the packetization delay; that is, the delay that a frame incur when sitting in a
buffer waiting for the packet to complete.

The size of the payload can vary. A minimum of 8 bytes per transported timeslot is required. The maximum size
depends on the service MTU.

Smaller packets allow for smaller packetization delays. Bigger packets allow for more efficient network usage.
The packet size parameter must be carefully chosen based on the application and network environment. If you
are unsure how to configure it, just use the default.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 20
 2 TDM options
2.3 Transport of structured and unstructured connections

Principal services used for structured and unstructured connections

CESoP (Circuit Emulation Service over Packet)—provides fractional services
(nxDS0), and this results in individual timeslots.
SAToP (Structure Agnostic TDM over Packet)—provides structured T1/E1
services, and this results in full E1/T1.

TDM TDM

MPLS Tunnel
CES IWF CES IWF

The CES Interworking Pseudowires (PWE3) MPLS Tunnels Flexible configuration of buffers
Function (IWF) applies the identify the specific CES transport traffic within the CES IWF allows control
proper encapsulation to the connection from point A to B of packetization, latency and jitter
nxDS0 or T1/E1 traffic which meets the requirements for
TDM services.

The CESoP and SAToP services are collectively referred to as Circuit Emulation
Services (CES). They are transported over an MPLS-enabled Metro Network
using Pseudowire (PWE3) point-to-point tunnels.

4 — 3 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

For private-line and leased-line applications, a fundamental requirement is the ability to transport TDM voice and
data while maintaining timing and not introducing significant delay and jitter into the path. Circuit Emulation
Services over PSN (CESoPSN) and Structure-Agnostic TDM over Packet (SAToP) are two types of TDM pseudowire.

CESoP is a structure-aware emulation for the transport of structured TDM:

•Structured mode is supported for DS1, E1 and n x 64 kbps
•Full DS1 or E1s can be transported by selecting all 24 DS0 timeslots (channels 1-24) and 32 (channels 2-32)
respectively
•Framing bits are reproduced at the far end
•Individual timeslots can be sent to different destinations

SAToP is a structure-agnostic emulation for the transport of unframed TDM:

•Unstructured mode
•Does not align to any framing
•TDM traffic is packetized and encapsulated in an MPLS or GRE (IP) tunnel
•The uplink media is FE/GE or n x T1/E1 MLPPP
•Configurable packetization delay and jitter buffer sizing

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 21
 2 TDM options
2.5 Channel group timeslots for CESoPSN—E1 frame

Basic E1 frame
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Timeslot notation
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
X
2-16 TS17 is not included 18-32
in this channel group

tdm
e1 1.1.1
clock-source node-timed
channel-group 1
timeslots 2-16,18-32
no shutdown
exit
no shutdown
exit
no shutdown

4 — 3 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide identifies the timeslots within the channel group for CESoPSN—E1 frame.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 22
 2 TDM options
2.6 Channel group timeslots for CESoPSN—T1 frame

Basic T1 frame
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Timeslot notation
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
X
1-16 TS17 is not included 18-24
in this channel group

tdm
ds1
channel-group 1
encap-type cem
timeslots 1-16, 18-24
no shutdown
exit
no shutdown
exit
exit

4 — 3 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

This slide identifies the timeslots within the channel group for CESoPSN—T1 frame.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 23
 Knowledge check

Answer the following questions

a) If individual timeslots out of an E1 need to be transported over the

Cpipe, does the Cpipe service type/VC-type need to be configured as
SAToP or CESoP?
b) True or False: Is SAToP referred to as structure agnostic?

4 — 3 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) CESoP
b) True

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 24
 3 Packet size and latency

4 — 3 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 25
 3 Packet size and latency
3.1 Packet size vs. packet latency

DS1/E1 Data Gigabit Ethernet

DS1/E1 Packetization
Access
circuit Signal

Packet size
The packet size is a user-configurable value expressed in bytes. The packet
size needs to be a multiple of the number of timeslots by T1/E1 frame (N).
•The minimum packet size is based on 8 frames (T1/E1) per packet.
•The maximum packet size is 1514 bytes.

Packet latency
With a smaller packet size, the packet latency is reduced. However, a small
packet size results in higher overhead as a percentage of the traffic.

4 — 3 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Packet size is a user-configurable value expressed in bytes. The packet size needs to be a multiple of the number
of timeslots by T1/E1 frame (N).
•The minimum packet size is based on 8 frames (T1/E1) per packet.
•The maximum packet size is 1514 bytes.

With a smaller packet size, the packet latency is reduced. However, a small packet size results in higher
overhead as a percentage of the traffic.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 26
 3 Packet size and latency
3.3 Exercise

a) True or False: would a CESoPSN with just 16 timeslots have half of

the packet delay?

4 — 3 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) False. The packet delay is double. More frames (32 vs. 16) will have to wait until the packet is full. You can
reduce the delay by reducing the size of the payload.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 27
 3 Packet size and latency
3.5 Packet jitter

Perfect data stream

Time

Overflow Underflow
Same stream with
Ethernet jitter

Time

Packet jitter
Packet jitter is the time difference between the packet actual arrival time and
expected arrival time caused by network congestion, timing drift, or route
changes.
If packets are delayed by the network, some packets arrive in bursts with
intervals between packets shorter than when they were transmitted, while
other packets are delayed.

4 — 3 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Several network impairments prevent IP networks from carrying emulated circuit-switched traffic such as a E1.
An E1 line delivers a constant bit-rate stream from node A to node B on the other side of the network. As packets
travel through the network, delay accumulates at each intermediary node. To compensate for this delay, node B
needs to use a jitter buffer to further delay packets in order to guarantee that there is always a packet ready to
be transmitted. However, each packet arrives with a different delay and this creates problems. The range of
delay with which packets arrive is known as time delay variation (TDV) or jitter. Typically, with a large enough
jitter buffer, packets arrive in time to be useful. In extreme cases, packets can be discarded if their time delay
variation exceeds the maximum that the jitter buffer can accommodate.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 29
 3 Packet size and latency
3.6 Jitter buffer

...

...

Buffer
Time

Packet jitter buffer

To smooth the varying input stream arrival times, the node receiving the
packets buffers the incoming data just enough to accommodate and correct
instances where input streams have overflowed the capacity or did not fill it.
These buffers (queues) must also be sized appropriately to handle stream
fluctuations without delaying the data so much that the receiving end is
impacted.

4 — 3 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

The larger the variation, the larger the buffer that is required to smooth it out since the buffer
must be able to handle the maximum tolerated variation. Tthe buffer size is not determined by
how much end-to-end delay there is, but rather by how much variance there is in the delay
between packets.

Large buffers become a problem when the additional latency that they add to already delayed
packets causes packets to be timed out. The additional latency is bounded by the most delayed
packet; slow packets delay every other packet in the buffer, even those that have arrived quickly.
An emulated T1 line may already be stressed because of delays inherent in network routing, and
additional delay of an adequate jitter buffer can be enough to affect the delivery of real-time
data.
For each circuit, the maximum receive jitter buffer is configurable. The jitter buffer range is from
2 to 250 ms
Playout from this buffer starts when the buffer is 50% full. This gives an operational packet delay
variance of half the max buffer size.

The default values are:

•N=1: 32 ms
•2<=N<= 4: 16 ms
•5<=N<= 15: 8 ms
•N>=16: 5 ms

For CESoPSN with CAS, the default jitter buffer is 12 ms for T1 and 8 ms for E1.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 30
End of module
C-Pipe

4 — 3 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — C-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.3 Edition N/A
Section 4 — Module 3 — Page 32
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 4
E-Pipe
TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—4—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 1
Blank page

4—4—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 2
Module objectives

Upon completion of this module, you should be able to describe:

Epipe Characteristics

Epipe Configuration

4—4—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 3
Module objectives [cont.]

4—4—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 4
 Table of Contents

1 — Characteristics of an ePipe service 7

Page
2 — Steps to configure an ePipe service 9
1 — Characteristics of an ePipe service 7
1.1 ePipe Service 8
2 — Steps to configure an ePipe service 9
2.1 Prerequisites 10
2.2 Creating an ePipe Service 11
2.3 SAPs and Spoke-SDPs 12
2.4 SAP Encapsulations for ePipe Services 13
2.5 ePipe Configuration 14
2.6 ePipe Configuration 15
2.7 ePipe SDP Bindings 16
2.8 ePipe Service Management 17
2.8 ePipe Service Management 18

4—4—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 5
Table of Contents [cont.]

4—4—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 6
 1 — Characteristics of an ePipe service

4—4—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 7
 1 — Characteristics of an ePipe service
1.1 ePipe Service

An ePipe service corresponds to the

Virtual Leased Line (VLL) service
family

It provides a point to point connection
between two nodes

From the customer’s perspective it
operates as a leased line between the
two locations ePipe Service

The Service provider can apply billing,
ingress/egress shaping and policing PE A PE C

No MAC learning required

IP / MPLS
Network

PE B

4—4—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Characteristics
 Point-to-point Ethernet service
 Provides same functionality as a private line/leased line service
 Transparent to higher-layer traffic
 Customer data is encapsulated and transported across an IP/MPLS network
 Does not perform any MAC learning
 Troubleshooting aids such as SDP Ping and Service Ping aid in reducing the complexity of setting
up and maintaining the service

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 8
 2 — Steps to configure an ePipe service

4—4—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 9
2 — Steps to configure an ePipe service
2.1 Prerequisites

Before any services are provisioned, the following tasks need to be

completed:

Build the IP core network (cards, ports, interfaces)

Configure an IGP (routing protocol)

Configure MPLS LSPs via LDP or RSVP-TE (not needed if GRE tunnels are used)

Build a mesh of SDPs interconnecting PEs Only needed for a

Create customer accounts distributed ePipe

Create template QoS, scheduler, and accounting policies

4 — 4 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 10
 2 — Steps to configure an ePipe service
2.2 Creating an ePipe Service

Customer Customer
access access
ports SDP ports
SAP
Service-id Demux Service-id
Demux SAP
Customer SDP Customer
CORE
PE-A PE-B

STEP Information needed

Create service Service type: ePipe
Service ID
Customer ID
Add Service Access Points Selectport and encapsulation IDs
SelectFilter policies (optional)
SelectIngress/Egress QOS Policies (optional)
Selectscheduler policy (optional)
SelectAccounting Policy (optional) Only needed for a
Add Service Distribution Points SDP ID, Virtual Circuit (VC) ID distributed ePipe

4 — 4 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Service-specific Tasks Include:

 Creating the service
 Configure interfaces and SAPs; apply optional QoS, filter, accounting, and scheduler policies
 Bind SDP to the service

When an SDP is bound to an ePipe, it is always done so using the spoke option. For VPLS services, one
has the option of binding an SDP using the spoke or the mesh option. The rules as to how to forward
traffic received on one or the other are explained later.

When an SDP is bound to a service, a Virtual Circuit (VC) ID needs to be specified. This is the ID that will
be used by TLDP as the FEC (Forwarding Equivalence Class) when it negotiates the service or VC label.
The VC ID value configured on one router does not have to be equal to the service ID (although it is good
practice), but it does need to match the VC ID value selected on the router located at the far end of the
SDP. SDP IDs, however, are allowed to be different.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 11
 2 — Steps to configure an ePipe service
2.3 SAPs and Spoke-SDPs

Flooded traffic received on SAPs and spoke SDPs:

Replicated on all other ports within the service (spoke-SDPs and SAPs)

Not replicated on the port it was received on

SAP
ePipe 200

ePipe 200 SDP

SDP
 SAP – Floods to everybody
SAP
 Spoke SDP – Floods to everybody

4 — 4 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Generally speaking, when flooded traffic is received on a Spoke SDP it is replicated onto SAPs, other
Spoke SDPs, and Mesh SDPs.

Similarly, in general, when flooded traffic is received on a SAP it is replicated onto other SAPs, Spoke
SDPs, and Mesh SDPs.

Specifically for an ePipe, since it is a point-to-point service, all traffic received on the Spoke SDP will
be forwarded onto the SAP and vice versa.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 12
 2 — Steps to configure an ePipe service
2.4 SAP Encapsulations for ePipe Services

Port Type Encapsulation

Ethernet NULL

Ethernet Dot1Q

Ethernet QinQ

SONET / SDH IPCP

SONET / SDH BCP-Null

SONET / SDH TDM BCP-Dot1Q

SONET / SDH TDM ATM

SONET / SDH FR FR

4 — 4 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Null – Supports a single service on the port. For example, a single customer edge device attached to
the port
Dot1q – Supports multiple services on the port. For example, a customer edge device running Virtual
LANs
QinQ – Supports tags within tags
IPCP – Internet Protocol Control Protocol is typically used for interconnection using point-to-point
protocol (PPP)
Bridging Control Protocol (BCP-null) is typically used for bridging a single service between two devices
using PPP over SONET/SDH with an encap ID of 0
Bridging Control Protocol (BCP-dot1q) supports multiple services on the SONET/SDH port/channel

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 13
2 — Steps to configure an ePipe service
2.5 ePipe Configuration

Creating a customer

Syntax:

config>service# customer customer-id create

contact contact-information
description description-string
phone phone-number

Example:

configure service customer 100 create

config>service>cust$ description "Alcatel Customer"
config>service>cust$ contact "John Smith, Technical Support"
config>service>cust$ phone "650 555-5100"

4 — 4 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 14
2 — Steps to configure an ePipe service
2.6 ePipe Configuration

Creating an ePipe Service:

config>service# epipe 5500 customer 100 create

config>service>epipe$ description “epipe service”
config>service>epipe# exit

Add SAP and apply Ingress and Egress parameters:

config>service# epipe 5500

config>service>epipe# sap 2/1/3:10 create
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# qos 555
config>service>epipe>sap>ingress# filter ip 1
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# egress
config>service>epipe>sap>egress# qos 627
config>service>epipe>sap>egress# scheduler-policy alpha
config>service>epipe>sap>egress# exit
config>service>epipe>sap#

4 — 4 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 15
 2 — Steps to configure an ePipe service
2.7 ePipe SDP Bindings
Do not have to match,
but do match in many
applications

Service ID
After you have created an SDP
VC ID

config>service# epipe 5500

config>service>epipe# spoke-sdp 2:5500 create
config>service>epipe>spoke-sdp$ no shutdown
config>service>epipe>spoke-sdp$ exit
config>service>epipe# no shutdown
config>service>epipe# exit all
User-assigned
SDP ID

4 — 4 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

The service ID has local significance. However, the local VC ID must be the same as the one
configured on the far-end PE; otherwise the SDP will not become operational as a component of
this service.

An SDP may be transferring data packets between dissimilar services on the involved PEs. In other
words, the SDP may be a component of an ePipe on one PE and of a VPLS or an IES on the other. As
long as the VC IDs match on both ends, the SDP will become operational and function properly.

It is good practice, and it is exactly what is observed in many applications, to set the VC ID to the
same value as that of the service ID. Although it is not a requirement, doing so facilitates the
analysis of the system and troubleshooting if a problem should arise.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 16
 2 — Steps to configure an ePipe service
2.8 ePipe Service Management

You can perform the following ePipe management tasks:

Modify the ePipe service

Disable and re-enable the service

Delete the ePipe service

To delete an ePipe, all of its components (SAPs and SDPs) need to be

deleted first.

To delete a SAP or an SDP, it has to be disabled (shut down) first, and then
removed.

The same applies to the other service types as well.

4 — 4 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

ePipe Service Management

Modifying
Display the information for the service and select the parameter that you want to modify.

Disabling the Service

You can shut down an ePipe service without deleting the service parameters.
Example:
config>service# epipe 2
config>service>epipe# shutdown
config>service>epipe# exit

Re-enabling the Service

Example:
config>service# epipe 2
config>service>epipe# no shutdown
config>service>epipe# exit

Deleting
Copyright © 2014 Alcatel-Lucent. All Rights Reserved.
Perform the following steps prior toTER36055_V3.0-SG-R6.0-Ed1
deleting an Epipe service:
Module 4.4 Edition N/A
Section 4 — Module 4 — Page 17
1. Shut down the SAP.
End of module
E-Pipe

4 — 4 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — E-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.4 Edition N/A
Section 4 — Module 4 — Page 18
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 5
A-Pipe
TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—5—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 1
Blank page

4—5—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 2
Module objectives

Upon completion of this module, you should be able to describe:

Overview of ATM

Apipe Functionality

4—5—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 3
Module objectives [cont.]

4—5—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 4
 Table of Contents

1 — ATM Overview 7
Page
2 — Apipe Overview 14
1 — ATM Overview 7
1.1 ATM Cell Format 8
1.2 ATM Header Format 9
1.3 Virtual Path and Virtual Channels 10
1.4 Virtual Channels and Virtual Paths 11
1.5 7705 Supported ATM VC-Types 12
1.6 ATM Service Categories 13
2 — Apipe Overview 14
2.1 aPipe Overview 15
2.2 ATM Cell forwarding 16
2.3 ATM Cell forwarding 17
2.4 aPipe Packet Structure (Single ATM Cell) 18
2.5 ATM Cell Concatenation 19
2.6 aPipe Packet Structure (Multiple ATM Cells) 20
2.7 ATM Encapsulation over PSN – Control Word 21
2.8 ATM Cell Concatenation 22
2.9 Inverse Multiplexing over ATM (IMA) 23
2.9 Inverse Multiplexing over ATM (IMA) 24

4—5—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 5
Table of Contents [cont.]

4—5—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 6
 1 — ATM Overview

4—5—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 7
 1 — ATM Overview
1.1 ATM Cell Format

ATM uses a fixed size cell consisting of 53 Bytes

First 5 Bytes contains header information such as the connection
identifier

Remaining 48 Bytes contains the data or Payload

5 Bytes 48 Bytes

Header Payload

53 Bytes

4—5—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

What is ATM? ATM was ddesigned for the high-speed transfer of Voice, Video and Data using cell relay technology
Uses small, Fixed-size Cells
Connection-oriented Service
Supports multiple service types
Applicable to LAN and WAN

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 8
1 — ATM Overview
1.2 ATM Header Format

ATM UNI Cell

User to Network Interface (UNI) Format

Network to Network Interface (NNI) Format

ATM NNI Cell

GFC - Generic Flow Control – Provides Local Functions such as flow control (UNI Only)
VPI - Virtual Path Identifier
VCI - Virtual Channel Identifier
PTI - Payload Type Identifier – Indicates User/Control Data
CLP - Cell Loss Priority Bit – Indicates whether cell should be discarded
HEC - Header Error Check – 8 Bit CRC

4—5—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 9
1 — ATM Overview
1.3 Virtual Path and Virtual Channels

Virtual Channels (VC)

Virtual Path (VP)

ATM Physical Link

STM1/E3/E1
OC3/DS3/DS1 Virtual Path (VP)

Virtual Channels (VC)

Virtual Path Virtual Channel

(VP) (VC)
Contains Multiple VCs Logical Path
Between ATM End Points

Connection Identifier = VPI/VCI

4 — 5 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 10
1 — ATM Overview
1.4 Virtual Channels and Virtual Paths

Virtual Channel Connection (VCC)

Virtual Path
Connection (VPC)

UNI
UNI
NNI NNI
VC VP VC
Switch Switch Switch

VPI = 1 VPI = 2 VPI = 26 VPI = 20

VCI = 1 VCI = 44 VCI = 44 VCI = 30

This hop-by-hop forwarding is known as cell relay

4 — 5 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 11
 1 — ATM Overview
1.5 7705 Supported ATM VC-Types

The VC-type is a 15-bit value that defines the type of VC signaled to the
peer

ATM-VCC (Default on the 7705)
 Virtual Circuit Connection. An ATM connection that is switched based on the cell
header’s VCI – Requires VPI/VCI identifier to be specified

ATM-VPC
 Virtual Path Connection. An ATM connection that is switched based on the cell
header’s VPI – Requires VPI identifier to be specified
The vc-type must be specified at the time of aPipe service creation and cannot
be changed without deleting the service first.

*A:PoC3B# configure service apipe 10 vc-type atm-vcc customer 1 create

*A:PoC3B>config>service>apipe$

4 — 5 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

MPLS Pseudowire VC-Types

PW type Description Reference

0x0001 Frame Relay DLCI ( Martini Mode ) [FRAME]
0x0002 ATM AAL5 SDU VCC transport [ATM]
0x0003 ATM transparent cell transport [ATM]
0x0004 Ethernet Tagged Mode [ETH]
0x0005 Ethernet [ETH]
0x0006 HDLC [PPPHDLC]
0x0007 PPP [PPPHDLC]
0x0008 SONET/SDH Circuit Emulation Service Over MPLS [CEP]
0x0009 ATM n-to-one VCC cell transport [ATM]
0x000A ATM n-to-one VPC cell transport [ATM]
0x000B IP Layer2 Transport [RFC3032]
0x000C ATM one-to-one VCC Cell Mode [ATM]
0x000D ATM one-to-one VPC Cell Mode [ATM]
0x000E ATM AAL5 PDU VCC transport [ATM]
0x000F Frame-Relay Port mode [FRAME]
0x0010 SONET/SDH Circuit Emulation over Packet [CEP]
0x0011 Structure-agnostic E1 over Packet [SAToP]
0x0012 Structure-agnostic T1 (DS1) over Packet [SAToP]
0x0013 Structure-agnostic E3 over Packet [SAToP]
0x0014 Structure-agnostic T3 (DS3) over Packet [SAToP]
0x0015 CESoPSN basic mode [CESoPSN]
Copyright © 2014 Alcatel-Lucent. All Rights Reserved.
TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 12
 1 — ATM Overview
1.6 ATM Service Categories

ATM Provides five standard service Categories

Service Typical Application Traffic

Category Parameters
CBR Circuit Emulation Services PCR
RT-VBR Interactive Multimedia PCR, SCR, MBS
NRT-VBR Bursty applications – File Transfers PCR, SCR, MBS
ABR* Best Effort service with flow control feedback PCR, MCR
UBR LAN Traffic (no guarantees)

• *ABR is not supported on the 7750 or 7705 Products

4 — 5 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

CBR – Constant Bit Rate

RT-VBR – Variable Bit Rate Real-Time
NRT-VBR – Variable Bit Rate Non-Real Time
ABR* – Available Bit Rate
UBR – Unspecified Bit Rate

Traffic parameters
– Peak cell rate (PCR)
– Sustainable cell rate (SCR)
– Burst tolerance, conveyed through the maximum burst size (MBS)
– Cell delay variation tolerance (CDVT)
– Minimum cell rate (MCR)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 13
 2 — Apipe Overview

4 — 5 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 14
2 — Apipe Overview
2.1 aPipe Overview

aPipe service provides a bi-directional layer 2 connection of ATM

service between two users/sites through an IP/MPLS network

aPipe is supported on a T1/E1 ASAP port, E3/DS3 port, OC3/STM1 port,
or clear-channel or channelized OC3 port when the port is configured
for ATM or IMA

ATM cells received on the ATM SAP are encapsulated into PW packets to
be transported over IP/MPLS outer tunnels

Targeted LDP signaling is commonly used to setup the PW

ATM ATM
Node B IP/MPLS
7705 SAR 7710/ 7750 SR
7670 RSP

4 — 5 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 15
2 — Apipe Overview
2.2 ATM Cell forwarding

The vc-type of an aPipe specifies which cells will be accepted by the

corresponding SAP and carried to the far end via the pseudo-wire

The vc-type can configured upon creation as:

atm-cell (all cells received or cells from a range of VPIs are associated to the SAP)

atm-vpc (cells from an individual VPI are associated to the SAP)

atm-vcc (cells from a specific VPI/VCI combination are associated to the SAP)

atm-sdu (cells from a specific VPI/VCI combination are associated to the SAP,
but the higher-layer packet –SDU– is reassembled before forwarding it)

ATM ATM
Node B IP/MPLS
7705 SAR 7710/ 7750 SR
7670 RSP

4 — 5 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 16
 2 — Apipe Overview
2.3 ATM Cell forwarding

The default operation of an aPipe when the vc-type is configured as

atm-vcc, atm-vpc, or atm-cell, is to forward each cell inside a separate
pseudo-wire packet

The incurred overhead is large but the end-to-end delay and jitter of
each cell are small

ATM Cell IP/MPLS Header

ATM
Node B IP/MPLS ATM

7705 SAR
7710/ 7750 SR
7670 RSP

4 — 5 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

The default vc-type on a 7705 SAR is atm-vcc. So, by default, the behavior described in the figure will
be observed.

The default vc-type on a 7750 SR is atm-sdu, so the behavior described in the figure will not be
observed in that case since an entire SDU will be carried inside a VLL payload (unless the SDU exceeds
the MTU size, in which case the SDU will be fragmented into a small number of pseudo-wire packets).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 17
2 — Apipe Overview
2.4 aPipe Packet Structure (Single ATM Cell)

VCC Ethereal Hex Trace (Single Cell)

0000 00 03 fa 73 69 01 00 16 4d 65 57 cd 88 47 1f ff
0010 4a ff 1f ff 2b ff 00 00 0c 80 2d aa aa aa aa aa
0020 aa aa aa aa aa aa aa aa aa aa 72 aa aa aa aa aa
0030 aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
0040 aa aa 42 aa aa aa aa aa aa aa

Key: Ethernet Frame

MPLS Outer Label
MPLS Inner Label
ATM VPI Value = 0

ATM VCI Value = 200

ATM Payload Type Identifier

Payload

4 — 5 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 18
 2 — Apipe Overview
2.5 ATM Cell Concatenation

An aPipe can be configured to supports cell concatenation to save on

MPLS packet overhead

This behavior is referred to as ATM N-to-1 cell mode

Cell concatenation packs more than one ATM cell in a VLL payload
(maximum number N of cells is configurable)

When traffic is not sensitive to delay or jitter, the number of cells in a
single VLL frame can grow up to the VLL MTU size

ATM Cells IP/MPLS Header

ATM ATM
Node B IP/MPLS
7705 SAR 7710/ 7750 SR
7670 RSP

4 — 5 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

This operation mode is known as N-to-1 cell mode

The cell mode part of the name comes from the fact that ATM cells are carried from end to end, as
opposed to the SDU mode in which an entire ATM Service Data Unit (SDU) – e.g. a packet received
from the upper layer – is reassembled before being forwarded. In the SDU mode, ATM headers are not
transported and the AAL5 overhead is removed on ingress and regenerated on egress before re-
fragmenting the SDU to forward it to the customer as ATM cells.

The N-to-1 part of the name comes from the fact that N (N >= 1) cells may be concatenated together
to be forwarded inside the service provider network as a single pseudowire packet. ATM cells are
individually forwarded to the customer after exiting the far end of the pseudo-wire.

A SAP working in cell mode can concatenate cells corresponding to a specific VPI/VCI combination, to
an individual VPI, to an ATM virtual trunk (a range of VPI values on an ATM port), or simply all cells
arriving on a given ATM port.

Thus, the endpoints of an N-to-1 mode VLL can be:

 ATM VCs — VPI/VCI translation is supported (i.e., the VPI/VCI at each endpoint does not need to
be the same).
 ATM VPs — VPI translation is supported (i.e., the VPI at each endpoint need not be the same, but
the original VCI will be maintained).
 ATM VTs (a VP range) — No VPI/VCI translation is supported (i.e., the VPI/VCI of each cell is
maintained across the network).
 ATM ports — No translation is supported (i.e., the VPI/VCI of each cell is maintained across the
network).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 19
 2 — Apipe Overview
2.6 aPipe Packet Structure (Multiple ATM Cells)

VPC cell concatenation (hex trace)

0000 00 03 fa 73 69 01 00 16 4d 65 57 cd 88 47 1f ff
0010 0a ff 1f ff 7b ff 06 60 03 70 dc 82 95 e5 a7 eb
0020 0a 91 c6 d5 c4 c4 40 21 18 4e 55 86 f4 dc 8a 15
0030 a7 ec 92 df 93 53 30 18 ca 34 bf a2 c7 59 67 8f
0040 ba 0d 6d d8 2d 7d 54 0a 9e 21 06 60 04 20 9e 38
0050 98 88 7f c6 60 94 ed 1e 7c d8 a9 1c 6d 5c 4c 44
0060 02 11 84 e5 58 6f 4d c8 a1 5a 7e c9 2d f9 35 33
0070 01 8c a3 4b fa 2c 75 96 78 fb a0 d6 16 57

Key: Ethernet Frame

MPLS Outer Label
MPLS Inner Label
ATM VPI Value

ATM VCI Value

ATM Payload Type Identifier

Payload
4 — 5 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

As the cells are being packed, the concatenation can be terminated and the packet is transmitted by
whichever occurs first:

 Max-cells is reached:
 It is the maximum number of ATM cells to concatenate in one packet
 max-cells <cell-count> : Value [1..29}

 Max-delay timer is expired: maximum delay for ATM cells in hundreds of microseconds
 max-delay <delay-time> : Value [1…400]

 CLP-change is triggered: allows the CLP change to be an indication to complete the cell
concatenation
 clp-change/ no clp-change

If more than one of the afore mentioned options are configured, the MPLS Packet is sent immediately
when the first option is met

Even if none of the above conditions is met, concatenation is terminated and the packet is forwarded
when the maximum configured Service MTU is reached or when the last cell of the current SDU is
received.

The default Service MTU is set to 1514 bytes. Taking into account N-to-1 mode carries 52 bytes as
payload for each 53 byte ATM cell, the maximum cell-range is set to 29

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 20
 2 — Apipe Overview
2.7 ATM Encapsulation over PSN – Control Word

If the payload is sensitive to packet misordering it MUST employ a

mechanism which prevents packet misordering
The Control Word contains:

Protocol specific flag bits, generated from the original Layer 2 PDU

Length bits

Sequence Numbers
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PSN Transport Header (As Required) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
| Pseudowire Header |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ATM Control Word +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+PSN Transport Header (As Required) |
| ATM Service Payload +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ pseudowire Header |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0| Flags |Res| Length | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ATM Service Payload |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

4 — 5 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

As shown above, the ATM Control Word is inserted before the ATM service payload. It may contain a length field
and a sequence number field in addition to certain control bits needed to carry the service.

In the above diagram, the first 4 bits MUST be set to 0 to indicate PW data. They MUST be ignored by the
receiving PE.
The next 4 bits provide space for carrying protocol-specific flags.
The next 6 bits provide a length field. Note that the length field is not used in the N-to-one mode and it is set to
0. The last 16 bits provide a sequence number that can be used to guarantee ordered packet delivery. The
processing of the sequence number field is OPTIONAL.

The sequence number space is a 16-bit, unsigned circular space. The sequence number value 0 is used to indicate
that the sequence number check algorithm is not used.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 21
 2 — Apipe Overview
2.8 ATM Cell Concatenation

The ATM Cell encapsulation consists of the optional control word and
one or more ATM cells

Each ATM cell has a 4-byte ATM cell header and a 48-byte ATM cell
payload
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Control word ( Optional ) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VPI | VCI | PTI |C|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Encapsulated | ATM Payload ( 48 bytes ) |
ATM Cell 1 | " |
| " |
| " |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VPI | VCI | PTI |C|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Encapsulated | ATM Payload ( 48 bytes ) |
ATM Cell 2 | " |
| " |
| " |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

4 — 5 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Max-delay – Amount of time to wait while performing ATM concatenation process

 User configurable in hundreds of microseconds. The delay times are rounded up to one of the following
values 1,5,10,50,100,200,300 and 400. (Default is 400 or 40ms). Between the values 10 and 50 (1ms and
5ms) a specific value can now be entered on 7705
Max-cells – Maximum number of ATM cells to accumulate into an MPLS Packet
 Max-cells value is limited by the MTU size of the ATM interface, therefore the range for a 7705 is between 1-
29 cells and the range on the 7750 is between 1 – 128. (Default is 1 cell)
CLP-Change
 Enables the Cell Loss Priority (CLP) change to be an indication to complete the cell concatenation operation
When the first of the above conditions is met the PWE3 frame is sent.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 22
 2 — Apipe Overview
2.9 Inverse Multiplexing over ATM (IMA)
IMA Group IMA Group
PHY Path #0 1 PHY
Transmit Receive
Path #1 2
3 2 1 PHY PHY 3 2 1
Single ATM Cell Stream

Path #2 3
PHY PHY

NodeB 7705 SAR

IMA Virtual Link

IMA is a cell based protocol where an ATM cell stream is inverse-

multiplexed across multiple paths to form a higher bandwidth logical link

The “logical link” concept is called an “IMA Group”

4 — 5 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

IMA is a standard developed to address the increasing need for bandwidth greater than the DS1 or E1 link speeds
(1.544 or 2.048 Mb/s, respectively) but less than higher link speeds such as DS3 (44.736 Mb/s). IMA combines the
transport bandwidth of multiple DS1 or E1 channels in a logical link (called an IMA group) to provide scalable
bandwidth.

In the ingress direction:

 Trafficcoming on a single card over multiple paths configured as part of a single IMA Group, is converted
into a single ATM stream

In the egress direction:

 Single
ATM stream (after service functions were applied) is distributed over all paths that are part of an IMA
Group (Towards the CE)

The higher layers see only an IMA Group and not individual links, therefore service configuration and management
is done using IMA Groups, and not individual links

All IMA member links in a IMA group must be on the same ASAP card.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 23
End of module
A-Pipe

4 — 5 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — A-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.5 Edition N/A
Section 4 — Module 5 — Page 24
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 6
I-Pipe
TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—6—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 1
Blank page

4—6—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 2
Module objectives

Upon completion of this module, you should be able to describe:

Functionality of an iPipe

Ipipe configuration

4—6—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 3
Module objectives [cont.]

4—6—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 4
 Table of Contents

1 — Characteristics of an iPipe service 7

Page
2 — Steps to configure an iPipe service 14
1 — Characteristics of an iPipe service 7
1.1 What is an iPipe? 8
1.2 What is an iPipe? (continued) 9
1.3 ePipe vs. iPipe 10
1.4 Distributed iPipe 11
1.5 IP packet forwarding: example 12
1.6 IP packet forwarding: example (continued) 13
2 — Steps to configure an iPipe service 14
2.1 iPipe Service : Configuration Overview 15
2.2 iPipe Service : Configuration Overview 16
2.3 ARP cache on Ethernet SAP 17
2.4 Mac-refresh: Refresh ARP cache on Ethernet SAP 18
2.4 Mac-refresh: Refresh ARP cache on Ethernet SAP 19

4—6—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 5
Table of Contents [cont.]

4—6—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 6
 1 — Characteristics of an iPipe service

4—6—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 7
 1 — Characteristics of an iPipe service
1.1 What is an iPipe?

An iPipe belongs to the Virtual Leased Line (VLL) family

It is a point-to-point Layer 2 service

Provides IP connectivity between a CE attached to an Ethernet
interface and a CE attached to a non-Ethernet interface (e.g. PPP, ATM,
FR)

Requires for both ends to carry IPv4 packets

Non-Ethernet side Ethernet side

SDP
SDP IP/MPLS Network
SAP SAP
PPP/ML-PPP IP/Ethernet

4—6—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

An iPipe belongs to the Virtual Leased Line (VLL) family of services, also known as Virtual Private Wire Services
(VPWS).
An iPipe can provides IP connectivity between a host attached to an Ethernet interface with routed IPv4
encapsulation and a host attached to a non-Ethernet interface, such as a point-to-point access circuit (PPP),
ATM or Frame Relay.
A typical use of this application is in a Layer 2 VPN when upgrading a hub site to Ethernet while keeping the
access side with their existing PPP encapsulation.

Supports:
 Ethernet SAP with Null or dot1p encapsulation
 PPP/ML-PPP SAP with IPCP encapsulation
 ATM SAP
 FR SAP

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 8
1 — Characteristics of an iPipe service
1.2 What is an iPipe? (continued)

Layer 3 IGP/EGP routing protocols that run over IP can be run over an
iPipe (e.g. OSPF, RIP, BGP)

IS-IS uses Layer 2 for its routing messages and is therefore not supported
within an iPipe

A typical example: interim step during migration from PPP to Ethernet
network

SDP
SDP MPLS Network
SAP IP Pseudo-Wires SAP
PPP/ML-PPP IP/Ethernet

4—6—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 9
 1 — Characteristics of an iPipe service
1.3 ePipe vs. iPipe

ePipe iPipe

Provides Ethernet VPWS
Provides IP interworking VPWS

Supports bridged encapsulation
Supports routed encapsulation

More network overhead because
Less network overhead because

Ethernet header is transported layer-2 header is taken out

Both hosts appear to be the same
Both hosts appear to be on the

Ethernet LAN same IP subnet or network

No Mac learning
Mac learning on behalf of non-

Ethernet side

Easier to configure
Local & Remote CE IP address

configuration is required

4 — 6 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

It is worth mentioning that, on 7750 SR, an ePipe can be used for Ethernet VPWS Interworking to provide
connectivity between Ethernet and ATM/FR sites where bridged encapsulation is being used over the ATM/FR
links (i.e. the ATM/FR side actually carries IP/Ethernet frames encapsulated in ATM/FR headers).

Bridged mode encapsulation enables network interworking at layer 2 by allowing the Ethernet frame to be
transported across the IP/MPLS intermediary network.

When routed encapsulation is used, in which the IP packets are carried using different encapsulation
technologies at layer-2, an iPipe is needed to allow service interworking between the two different layer 2
technologies.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 10
1 — Characteristics of an iPipe service
1.4 Distributed iPipe

Physical View

RNC

IP/MPLS
SAR
SR
138.120.122.1/29 138.120.122.2/29

Logical View Same IP

subnetwork
RNC

138.120.122.1/29 138.120.122.2/29

4 — 6 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 11
 1 — Characteristics of an iPipe service
1.5 IP packet forwarding: example

The SAR receives an IP packet on the PPP SAP

The SAR removes the layer-2 header and encapsulates the IP packet
directly into a PW without a control word

The SR receives packet and removes the PW encapsulation

The SR validates the IP destination address of the received packet and
adds Ethernet header before delivering to the local CE

To know the MAC address of local CE, the SR will send ARP request

MPLS/PW IP Data

PPP/IPCP IP Data Ethernet IP Data

iPipe ARP Req

IP/MPLS
ARP Rsp

PPP/ML-PPP SAR Ethernet

SR

4 — 6 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

In this example, there is wireless base station (NodeB) that needs to send data traffic to its Radio
Network Controller (RNC). Both will be referred to generically as CE (Customer Edge device). Next to
the NodeB there is a Service Access Router (SAR), and next to the RNC there is a more powerful
Service Router (SR).

To forward unicast frames destined to the RNC, the SR needs to know the RNC MAC address. When
the iPipe SAP is first configured and administratively enabled, the SR sends an ARP request message
for the RNC MAC address over the Ethernet SAP.

The SR does not flush the ARP cache unless the SAP goes admin or operationally down. To refresh the
ARP cache, the SR sends unsolicited ARP requests.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 12
 1 — Characteristics of an iPipe service
1.6 IP packet forwarding: example (continued)

In the opposite direction, if MAC address is unknown to the CE it will
ARP and the SR will respond on behalf of CE on the far end

SR will lend its chassis MAC address pretending to be the far-end CE

The SR receives an IP packet on the Ethernet SAP

The SR removes the layer-2 header and encapsulates the IP packet
directly into a PW without a control word

The SAR receives packet and removes the PW encapsulation

The SAR validates the IP destination address of the received packet
and adds PPP header before delivering to the local CE

MPLS/PW IP Data

PPP/IPCP IP Data Ethernet IP Data

iPipe ARP Req

IP/MPLS
ARP Rsp

PPP/ML-PPP SAR IP/Ethernet

SR

4 — 6 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

In the opposite direction, if the MAC address is unknown to the CE (RNC), it will send an ARP Request
message. Since the CE on the far end is not running Ethernet, the SR will intercept the ARP request
and respond to it on behalf of CE at the far end.

The response transmitted by the SR indicates that the MAC address to be associated to the IP address
is its chassis MAC address. In a way, the SR pretends to be the far-end CE so that communication can
happen.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 13
 2 — Steps to configure an iPipe service

4 — 6 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 14
2 — Steps to configure an iPipe service
2.1 iPipe Service : Configuration Overview

The following steps are required to configure a distributed iPipe service:

Configure an iPipe Service with Customer ID

Configure a SAP and associate it with the iPipe service

Assign the local IP address to the SAP

Configure a spoke-SDP and associate it with iPipe service

Assign a remote IP address to the spoke-SDP

138.120.121.1
local remote

SDP iPipe SDP

SAP SAP
138.120.121.1 138.120.121.2

remote local
138.120.121.2

4 — 6 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 15
2 — Steps to configure an iPipe service
2.2 iPipe Service : Configuration Overview
Example
7705 SAR 7750 SR

iPipe 400 customer 1 create iPipe 400 customer 1 create

sap 1/1/5 create sap 1/1/2 create
ce-address 138.120.121.1 ce-address 138.120.121.2
spoke-sdp 12:200 create spoke-sdp 21:200 create
ce-address 138.120.121.2 ce-address 138.120.121.1

138.120.121.1

SDP iPipe SDP

SAP SAP
138.120.121.1 138.120.121.2

138.120.121.2

4 — 6 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 16
 2 — Steps to configure an iPipe service
2.3 ARP cache on Ethernet SAP
SR>config>service>iPipe# show service id 400 sap 1/1/2
===========================================================
Service Access Points (SAP)
===========================================================
Service Id : 400
SAP : 1/1/2 Encap : null
Admin State : Up Oper State : Up
...
Ce IP Address : 138.120.121.2
SAP MAC Address : 00:1a:f0:a2:6d:49 Mac Refresh Inter*: 60
-------------------------------------------------------------
iPipe SAP ARP Entry Info
-------------------------------------------------------------
138.120.121.2 00:1a:f0:b8:d6:1e dynamic 00h01m00s

Ethernet II, Src: 00:1a:f0:a2:6d:49 , Dst: 00:1a:f0:b8:d6:1e null

Internet Protocol, Src: 138.120.121.1 Dst: 138.120.121.2
ICMP Echo (ping) request

Ethernet II, Src: 00:1a:f0:b8:d6:1e, Dst: 00:1a:f0:a2:6d:49 null

Internet Protocol, Src: 138.120.121.2 Dst: 138.120.121.1
ICMP Echo (ping) reply

138.120.121.2

SDP iPipe SDP 00:1a:f0:b8:d6:1e

SAP SAP
138.120.121.1
00:1a:f0:a2:6d:49
4 — 6 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 17
 2 — Steps to configure an iPipe service
2.4 Mac-refresh: Refresh ARP cache on Ethernet SAP

The MAC-Refresh timer on the SR router (Ethernet side) is used as the

keep-alive mechanism

When the timer expires, the node will ARP again for the MAC address
iPipe 400 customer 1 create
sap 1/1/2 create
ce-address 138.120.121.2
mac-refresh 60
spoke-sdp 21:200 create
ce-address 138.120.121.1

SR>config>service>iPipe# show service id 200 sap 1/1/2

===========================================================
Service Access Points (SAP)
===========================================================
Service Id : 400
SAP : 1/1/2 Encap : null
Admin State : Up Oper State : Up
...
Ce IP Address : 138.120.121.2
SAP MAC Address : 00:1a:f0:a2:6d:49 Mac Refresh Inter*: 60
--------------------------------------------------------------
iPipe SAP ARP Entry Info
--------------------------------------------------------------
138.120.121.2 00:1a:f0:b8:d6:1e dynamic 00h01m00s

4 — 6 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Keepalive function optional for broadcast networks to see if the CE is still alive
 This is accomplished by having the PE perform an ARP function on a regular basis
 Keep alive functionality achieved through the use of a configurable MAC refresh timer
 The default value for the timer is 4 hours or 14400 seconds
 When mac-refresh timer expires, the PE initiates an unsolicited ARP to notify the local attached CE

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 18
End of module
I-Pipe

4 — 6 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — I-Pipe
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.6 Edition N/A
Section 4 — Module 6 — Page 19
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 7
VPLS
TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—7—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 1
Blank page

4—7—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 2
Module objectives

Upon completion of this module, you should be able to describe:

Characteristics and benefits of a VPLS service

Configuration of a VPLS service in SR-OS

4—7—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 3
Module objectives [cont.]

4—7—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 4
Table of Contents

1 — Preliminary concepts Page 7

2 — Configuration of a VPLS service
1 — Preliminary concepts 7 12
1.1 Populating a Forwarding Database (FDB) 8
1.2 Forwarding Databases Using Tagging 9
1.3 Ethertype 10
1.4 Ethertype – VLAN tagging 11
2 — Configuration of a VPLS service 12
2.1 Building a Local Virtual Private LAN Service (VPLS) 13
2.2 Building a Local Virtual Private LAN Service (VPLS) 14
2.3 Building a Distributed Virtual Private LAN Service (VPLS) 15
2.4 Building a Distributed Virtual Private LAN Service (VPLS) 16
2.5 Flooding Traffic within a VPLS 17
2.6 VPLS - VC Label 18
2.7 VPLS Packet Walkthrough - VPLS Learning 19
2.8 VPLS Packet Forwarding 20
2.9 Routed VPLS 21
2.9 Routed VPLS 22

4—7—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 5
Table of Contents [cont.]

4—7—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 6
 1 — Preliminary concepts

4—7—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 7
1 — Preliminary concepts
1.1 Populating a Forwarding Database (FDB)

Host A sends a frame to Host C

1. The switch receives a frame on port 1/1/1
 Host A’s MAC address is learned from the frame’s Source Address field and is
associated with port 1/1/1
2. If the Destination Address is not already in the FDB, the switch floods the
frame out all ports except for the source port 1/1/1
3. Host C responds to Host A, and all other devices drop the flooded frame
 From Host C’s response frame, the switch associates Host C’s MAC address with
port 1/1/3

FDB Learning MAC Addresses

1/1/1 00-00-5e-00-01-8e
1/1/3 00-e0-b1-83-32-d8

Host C
Host A

DA SA payload Host B

4—7—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 8
1 — Preliminary concepts
1.2 Forwarding Databases Using Tagging

Virtual LANs (VLANs) are used to split a single switch into multiple virtual
switches, each with the ability to service the hosts associated within that
VLAN
As an example Hosts A B C are part of VLAN 3, Host D is part of VLAN 6
1. The switch receives a frame on port 1/1/1:3 (:3 signifies VLAN 3)
• Host A’s MAC address is learned and is associated with in VLAN 3’s FDB
2. If the Destination Address is not already in the FDB, the switch floods the
frame out all ports associated with VLAN 3
• Host D will not necessarily receive a copy of the frame; even if it does, it will drop
it because it belongs to a different VLAN than his
3. Host C responds to Host A, and all other devices drop the flooded frame
• From Host C’s response frame, the switch populates Host C’s MAC address in VLAN
3’s FDB
6 Host D
3 3

Host A
Host C
DA SA VLAN 3 payload
Host B
4—7—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 9
 1 — Preliminary concepts
1.3 Ethertype

The Ethertype field describes the payload of the Ethernet frame

Ethertype for some Protocol
common Protocols
0x0800 Internet Protocol, Version 4 (IPv4)
0x0806 Address Resolution Protocol (ARP)
0x8100 VLAN – Tagging (Dot1Q)
0x9100 VLAN – Tagging (QinQ)
0x86DD IPv6
0x8847 MPLS unicast
0x88a8 Provider Bridging

For example Etype 8847 identifies this packet as Unicast MPLS

0
MPLS VC
DA SA 0x8847 Payload FCS
Label Label
Etype

4 — 7 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

EtherType numbering generally starts from 0x0800. In the example used, Etype 8847 indicates a
unicast MPLS Ethernet frame. When the 7750 SR looks at the Etype field and sees 8847, it immediately
proceeds to process the MPLS labels.
As we have seen, two MPLS labels are included in the service encapsulation when an MPLS SDP is
bound to the service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 10
 1 — Preliminary concepts
1.4 Ethertype – VLAN tagging

Ethernet port encapsulation type can be configured as one of the

following:

Null Header (Raw Mode), all bits after the ‘type’ field are treated as data

Dot1q Header (Single tag header), adds an additional 4 byte “TAG”

QinQ Header (Two tags header), adds two TAGs after Source Address field

0 Null – No Tagging – SAP 1/1/1

DA SA 0x0800 Payload FCS
1514

0 Dot1Q – One Tag – SAP 1/1/1:3

DA SA 0x8100 Tag 3 Payload FCS
1518

0 QinQ – Stacked Tags - SAP 1/1/1:5.10

DA SA 0x9100 Tag X 0x8100 Tag Y Payload FCS
1522

4 — 7 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

When creating a SAP on a port, the selected encapsulation type must be taken into consideration. If it
is a Dot1Q port, a VLAN tag value must be specified in addition to indicating the port ID. If the SAP is
created over a QinQ port, then two VLAN tag values must be specified in addition to indicating the
port ID. Examples:
 Dot1Q – One Tag – SAP 1/1/1:3
 QinQ – Stacked Tags - SAP 1/1/1:5.10

The Physical MTU on an Ethernet access interface also needs to be set accordingly:
 1514 with encap-type null (1500 + 14 DLC header)
 1518 with encap-type Dot1Q (1500 + 14 DLC header + 4 dot1q tag)
 1522 with encap-type QinQ (1500 + 14 DLC header + 4 dot1q tag + 4 additional Q tag)

SAP Ingress:
 Any frame received with VLAN tags that do not match one of the SAPs defined on the port, will be
dropped
 Tags that are explicitly matched become stripped on ingress
 A wildcard can be used as a SAP defined tag (SAP:* or SAP:X.*), this has a 4-byte impact upon the
service MTU as the tag is retained rather that stripped

SAP Egress:
 SAP:X push dot1q-etype and tag X on egress frames
 SAP:X.Y push QinQ-etype and tag X / Dot1q-etype and tag Y on egress
 Default and wildcard SAPs do not regenerate tags on egress

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 11
 2 — Configuration of a VPLS service

4 — 7 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 12
 2 — Configuration of a VPLS service
2.1 Building a Local Virtual Private LAN Service (VPLS)

Creating a Local VPLS Service, meaning a service that exists solely on a

single node:

Change the ports facing customers to mode access
 Ethernet mode access

Enable tagging on the ports, if needed
 Ethernet encap-type dot1q

Create Service Access Points (SAPs) within the VPLS service using the
desired port/tag
 VPLS 300
 sap 1/1/1:10
 sap 1/1/1:20 1/1/3
 sap 1/1/2:3
 VPLS 600 Host E
 sap 1/1/2:6
 sap 1/1/3 Host A 1/1/1:10 1/1/2:6
Host D
1/1/1:20 1/1/2:3

Host B Host C
DA SA 0x8100 VLAN 3 payload

1518
4 — 7 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPLS
7705 SAR — R6.0 Strategic Industries

All frames that ingress to a service are compared to the FDB to determine which SAP or SDP the frame
is to be forwarded out. If the egressing port is a SAP, the frame will be regenerated with the
appropriate tags (dot1Q and QinQ) based on the SAP definition. For example, a dot1q SAP that is
provisioned as 1/1/1:3 will have the dot1q tag 3 inserted into all frames that egress that port based
on the FDB.

When a wildcard is used, for example 1/1/1:* although the SAP is defined as dot1Q, no additional tags
are added on egress.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 13
2 — Configuration of a VPLS service
2.2 Building a Local Virtual Private LAN Service (VPLS)
config# port 1/1/[1..3] shutdown
config# port 1/1/[1..3] ethernet mode access
config# port 1/1/[1..2] ethernet encap-type dot1q
config# port 1/1/[1..3] no shutdown

config# service vpls 300 customer 200 create

config>service>vpls$ sap 1/1/1:10 create
config>service>vpls>sap$ exit
config>service>vpls$ sap 1/1/1:20 create
config>service>vpls>sap$ exit
config>service>vpls$ sap 1/1/2:3 create
config>service>vpls>sap$ exit
config>service>vpls$ no shutdown
config>service>vpls$ exit

config>service# vpls 600 customer 300 create

config>service>vpls$ sap 1/1/2:6 create 1/1/3
config>service>vpls>sap$ exit
config>service>vpls$ sap 1/1/3 create Host E
config>service>vpls>sap$ exit
config>service>vpls$ no shutdown Host A 1/1/1:10 1/1/2:6
Host D
1/1/1:20 1/1/2:3

Host B

4 — 7 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 14
 2 — Configuration of a VPLS service
2.3 Building a Distributed Virtual Private LAN Service (VPLS)
Creating a Distributed VPLS Service, meaning a service that involves
several PE routers:

Build a mesh of MPLS LSPs interconnecting PE routers

Build a mesh of SDPs interconnecting PE routers

Change the ports facing customers to port mode access
 Ethernet mode access

Enable tagging on the access ports, if needed
 Ethernet encap-type dot1q

Create Service Access Points (SAPs) within the
VPLS service using the desired port/tag
 VPLS 300
1/1/1:3
 sap 1/1/1:3 VPLS 300

Bind Service Distribution Points (SDPs) SDP 21 SDP 23

to the VPLS service, connecting it to PE1 PE3

other PEs PE2
 VPLS 300
 mesh-sdp 12:300 SDP 12 SDP 32
 mesh-sdp 13:300 VPLS 300 VPLS 300
Host A Host B
SDP 13 SDP 31
1/1/1:3 1/1/1:3

4 — 7 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

VPLS Service
For each VPN at each site, a Customer Edge (CE) device connects to the Provider Edge (PE) router via
a point-to-point access connection.

Ethernet serves as the framing technology between the CE device and the PE router in the provider’s
network. Frames can include IEEE 802.1Q Ethernet VLAN tags, which allow customers to segment their
networks and assign quality of service priorities to LAN traffic. VPLS also supports “QinQ”
encapsulation, where a second VLAN tag is added as a service delimiter. From the customer’s
perspective, the entire VPN looks like a single Ethernet LAN, with the PE acting as a bridge that
switches frames on the basis of their Layer-2 destination MAC addresses.

On the provider’s side, however, PEs are interconnected with Generic Routing Encapsulation (GRE)
and/or Multiprotocol Label Switching (MPLS) tunnels. If PEs are connected using GRE tunnels traffic is
encapsulated and routed through the core network using standard IP frame formats and addressing. If
PEs are connected using MPLS tunnels traffic is encapsulated in an MPLS frame and transmitted using
MPLS labels. MPLS routes can be signaled using RSVP-TE or LDP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 15
 2 — Configuration of a VPLS service
2.4 Building a Distributed Virtual Private LAN Service (VPLS)
Configuration on PE1 (similar on other PEs):

PE1>config# port 1/1/1 shutdown

PE1>config# port 1/1/1 ethernet mode access
PE1>config# port 1/1/1 ethernet encap-type dot1q
PE1>config# port 1/1/1 no shutdown

PE1>config# service vpls 300 customer 200 create

PE1>config>service>vpls$ sap 1/1/1:3 create
PE1>config>service>vpls>sap$ exit
PE1>config>service>vpls$ mesh-sdp 12:300 create
PE1>config>service>vpls>sdp$ exit 1/1/1:3
VPLS 300
PE1>config>service>vpls$ mesh-sdp 13:300 create SDP 21 SDP 23

PE1>config>service>vpls>sdp$ exit
PE1>config>service>vpls$ no shutdown PE1 PE3
PE2
PE1>config>service>vpls$ exit
SDP 12 SDP 32
VPLS 300 VPLS 300
Host A Host B
SDP 13 SDP 31
1/1/1:3 1/1/1:3

4 — 7 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Core Network
Before a service is provisioned the following tasks should be completed:
 Build the IP or MPLS core network
 Configure routing protocols
 Configure MPLS LSPs (if MPLS used)
 Construct the core SDP service tunnel mesh for the services

Service Administration
 Configure group and user access privileges
 Build templates for QoS, filter and/or accounting policies needed to support core services
 Configure customer accounts

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 16
 2 — Configuration of a VPLS service
2.5 Flooding Traffic within a VPLS

SAP
MESH SDP

VPLS 300 MESH SDP

SPOKE SDP
SAP MESH SDP
SPOKE SDP
VPLS 300 MESH SDP
SAP – Floods to everybody
SPOKE SDP
SAP

Spoke SDP – Floods to everybody MESH SDP

VPLS 300 MESH SDP

SPOKE SDP
SAP

Mesh SDP – Floods to SAPs and Spoke SDPs only

4 — 7 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPLS
7705 SAR — R6.0 Strategic Industries

When the destination MAC address of a frame has already been learned, meaning that there is already
an entry for that address in the FDB (Forwarding Data Base), the frame is only forwarded on the
egress interface (SAP or SDP) pointed to by the FDB.

However, for a frame that has an unknown unicast destination MAC address or a multicast or
broadcast destination MAC address, for which there will be no entry in the FDB, the frame has to be
flooded throughout the entire broadcast domain. The following rules apply when flooding a frame is
necessary.

 Flooded traffic received on a SAP is replicated to other SAPs, Spoke SDPs, and Mesh SDPs
 Flooded traffic received on a Spoke SDP is replicated to other SAPs, Spoke SDPs, and Mesh SDPs
 Flooded traffic received on a Mesh SDP is replicated to other SAPs, and Spoke SDPs, but is not
transmitted on other Mesh SDPs

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 17
 2 — Configuration of a VPLS service
2.6 VPLS - VC Label

VC-label Signaling between PEs per VPLS service instance

Each PE automatically initiates a targeted LDP (TLDP) session to the far-end
System IP address as soon as an SDP is bound to a layer-2 service

TLDP is used to negotiate the VC (or service) label that will be used when
sending data packets for the service

TLDP uses the VC ID to identify the service tunnel, so it must match between
PE nodes (best practice is to set VC ID the same as the service ID)

The VC label allocated by each PE may be different PE2 M-3

131069
PE1
PE1->PE2: For VC-ID 102 Use VC-label 131069 131066

131068
PE2->PE1: For VC-ID 102 Use VC-label 131066 M-1 131065
VPLS
PE1->PE3: For VC-ID 103 Use VC-label 131070 131070

PE3->PE1: For VC-ID 103 Use VC-label 131055

131055

PE2->PE3: For VC-ID 203 Use VC-label 131068

PE3 M-4
PE3->PE2: For VC-ID 203 Use VC-label 131065

4 — 7 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Customer packets are transported either inside an IP packet (GRE) or inside an MPLS packet.

The packet carries an inner (VC) label that identifies the service the packet belongs to. This label is
sometimes referred to as the Martini label which is an MPLS label that identifies the particular
service that is being transported through the MPLS tunnel.

When a packet arrives at the destination, the outer IP address or MPLS label is stripped off. At this
point the inner label is examined to determine which service the packet belongs to.

After determining which service the packet belongs to, the customer’s Ethernet packet is examined
and its MAC address is looked up in a table on the PE to determine which SAP the packet should go
to.

VC labels can be assigned manually or automatically using targeted LDP (TLDP). The TLDP protocol is
used to dynamically negotiate VC labels between PE’s. This method is not error prone and scales
much better than manually assigning labels.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 18
 2 — Configuration of a VPLS service
2.7 VPLS Packet Walkthrough - VPLS Learning

MAC 3
1/1/2 Location
MAC Mapping
MAC3 Local 1/1/2
MAC Location Mapping
MAC3 Remote Tunnel to PE2 PE 2
1/1/1 1/1/2
MAC 1
PE 1 PE 3 MAC 4
1/1/3 Location
MAC 2 MAC Mapping
MAC3 Remote Tunnel to PE2
Send a packet from MAC 3 to MAC 1

PE2 learns that MAC 3 is reached on Port 1/1/2

PE2 floods to PE1 with VC-label pe2-1 and PE3 with VC-label pe2-3

PE1 learns that MAC 3 is behind PE2

PE3 learns that MAC 3 is behind PE2

PE3 sends on Port 1/1/2

PE1 sends on Port 1/1/1 & 1/1/3
4 — 7 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPLS
7705 SAR — R6.0 Strategic Industries

PE routers learn the source MAC addresses of the traffic arriving on their access and network ports.
Each PE router maintains a Forwarding Data Base (FDB) for each VPLS service instance and learned
MAC addresses are populated in the FDB table of the service.
All traffic is switched based on MAC addresses and forwarded between all participating PE routers
using the LSP tunnels.
Unknown packets (i.e. destination MAC address has not been learned) are forwarded on all the LSPs
to the participating PE routers for that service until the target station responds and the MAC address
is learned by the PE routers associated with that service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 19
2 — Configuration of a VPLS service
2.8 VPLS Packet Forwarding

MAC 3
MAC Location Mapping
1/1/2
MAC3 Local 1/1/2
MAC1 Remote Tunnel to PE1

PE 2
1/1/1 1/1/2
MAC 1
PE 1 PE 3 MAC 4
1/1/3
MAC 2
MAC Location Mapping Reply with a packet from M1 to M3
MAC3 Remote Tunnel to PE2
PE1 learns M1 is on Port 1/1/1

PE1 knows that M3 is reachable via PE2
MAC1 Local 1/1/1
PE1 sends to PE2 using VC-label pe1-2

PE2 learns MAC 1 is reachable via PE1

PE2 knows that M3 is reachable on Port 1/1/2

4 — 7 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 20
 2 — Configuration of a VPLS service
2.9 Routed VPLS

In order to interconnect a VPLS domain with a Layer 3 domain, e.g. VPLS

backhaul to a Layer 3 service, a routed VPLS allows the binding of IP
interfaces in IES or VPRN services to be bound to VPLS services.

VPLS

VPLS

VPLS
VPLS Routed VPLS
VPRN
IES Layer 3
Interface

Routed-VPLS service:

Internal VPLS to IES interface

Internal VPLS to VPRN interface

4 — 7 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

See Section 12 – Module – IES for a more detailed example.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 21
End of module
VPLS

4 — 7 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPLS
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.7 Edition N/A
Section 4 — Module 7 — Page 22
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 8
VPRN
TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—8—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 1
Blank page

4—8—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 2
Module objectives

Upon completion of this module, you should be able to:

The need for layer-3 VPNs

VPRN setup and configuration

Packet walkthrough

4—8—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 3
Module objectives [cont.]

4—8—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 4
 Table of Contents

1 — The need for layer-3 VPNs 7

Page
2 — L3VPN Overview 11
1—3— The need for
Local vs layer-3 VPNs VPRN
distributed 7 23
1.1 Need for VPRNs: Single Routing Table 8
4 Need
1.2 — VPRN setupOverlapping
for VPRNs: and configuration
IP addresses 9 25
2 — L3VPN Overview 11
5 L3
2.1 — VPN:
Packet walkthrough
Introduction 12 36
2.2 L3 VPNs: Basic Requirements 13
2.3 L3VPN: VRF instances on the PE 14
2.4 L3VPN: VPRN Terminology – CE, PE, P 15
2.5 L3VPN: Route Distinguisher 16
2.6 L3VPN: Which routes go into which VRF ? 17
2.7 L3VPN and MP-BGP 18
2.8 L3 VPN: Import/Export Policy 19
2.9 L3VPN: Route-distinguisher vs route-target 20
2.10 L3 VPN: Data Plane – Transport Tunnel 21
2.11 L3 VPN: VPN Label 22
3 — Local vs distributed VPRN 23
3.1 Local vs distributed VPRN 24
4 — VPRN setup and configuration 25
4.1 VPRN configuration steps 26
4.2 L3 VPN: CE to PE Route Distribution 27
4.3 L3VPN: PE to PE Route Distribution 29
4.44 —L3VPN:
8—5
Populating a VRF 30
4.5Services
L3VPN:— VPRN Monitoring a VRF
7705 SAR — R6.0 Strategic Industries
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
31
4.6 L3 VPN: Monitoring MP-BGP learned routes (RIB-In) 32
4.7 L3 VPN: Monitoring MP-BGP learned routes (RIB-In) 33
4.8 L3 VPN: Monitoring MP-BGP advertised routes (RIB-Out) 34
4.9 L3 VPN: Monitoring MP-BGP advertised routes (RIB-Out) 35
5 — Packet walkthrough 36
5.1 L3 VPN: Data Plane – Transport Tunnel 37
5.2 L3 VPN: Forwarding Traffic 38
5.2 L3 VPN: Forwarding Traffic 39

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 5
Table of Contents [cont.]

4—8—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 6
 1 — The need for layer-3 VPNs

4—8—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 7
 1 — The need for layer-3 VPNs
1.1 Need for VPRNs: Single Routing Table

Customer 1 Customer 2
CE3
CE1 Provider 192.168.2.0/24
192.168.1.0/24 PE1 PE2
core routes

CE4 192.168.12.0/24
CE2
192.168.1.0/24 Route Table (Router: Base)
Customer 1
=========================================
Customer 2 Dest Address Next Hop Type Proto
-----------------------------------------
192.168.1.0/24 CE2 Remote OSPF
150.215.34.0/24 Provider_core Remote OSPF
192.168.2.0/24 CE3 Remote BGP

If the same routing instance is used for all customers:

 All routes are mixed together in a single PE routing table
 There can be conflicts if two customers use overlapping address ranges
 Large amount of information may be exchanged when routing changes

4—8—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Without the L3 VPN:

 Each customer must use a separate IP address range
 All customer routes are carried natively in the provider core

There is no isolation between the routing information of different customers and there is no isolation of
the provider network routes from the customer routes. All routes are mixed in a common routing table
on all routers in the provider core network.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 8
 1 — The need for layer-3 VPNs
1.2 Need for VPRNs: Overlapping IP addresses

Customer Red Customer Red

CE1 CE3 192.168.2.0/24

192.168.1.0/24

CE4 192.168.2.0/24

192.168.1.0/24
Route Table (Router: Base)
CE2 ========================================= Customer Blue
Customer Blue Dest Address Next Hop Type Proto
-----------------------------------------
192.168.1.0/24 CE2 Remote OSPF By default, not
192.168.1.0/24 CE1 Remote OSPF allowed to add
repeated entries
Drawbacks:

By default, only the best route is selected in routing table

If ECMP is enabled, packets from one customers may be forwarded to another
⇒ Routing problems
4—8—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPRN
7705 SAR — R6.0 Strategic Industries

By default, it is not allowed to add repeated entries for the same prefix in a route table. So, if two
customers are using the same address, only one of them will receive all the traffic addressed for both.

If ECMP is enabled to be able to install two entries in the route table for the same prefix, as shown in
the figure, one of them will be selected pseudo-randomly using a hash function when a packet arrives.
In this situation, there is still a potential problem since packets from one customers may be forwarded
to the other.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 9
 1 — The need for layer-3 VPNs
1.2 Need for VPRNs: Overlapping IP addresses [cont.]

A VPN: Switch to notes view!

 Provides connectivity between separate sites.
 Is private because it gives the same properties and guarantees as a privately owned network,
both in terms of network operations (addressing space, routing) and in terms of packet
forwarding (traffic isolation).
 Is virtual because the provider may use the same resources and facilities to provide services to
more than one customer.

Main Benefits :
 Simplifies the routing topology at each customer site
 The service provider manages the core network and the customer routes
 Customers receive the redundancy benefits designed into the provider core
 Security is similar to existing layer 2 technologies (ATM or Frame Relay)
 Layer 2 independent - allows different layer 2 connectivity at customer sites
 Allows the use of overlapping private IP address space between different customers

Layer
4 — 83— 10Backbone VPNs are commonly known as Border Gateway Protocol (BGP)/MPLS-based VPNs as
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPRN
per 7705
the SAR standard RFC 2547bis, which is co-authored by Alcatel-Lucent. They are also known as Virtual
— R6.0 Strategic Industries

Private Routed Networks (VPRN), Layer 3 MPLS-based VPNs or MPLS-based IP-VPNs.

RFC 2547bis is an extension to the original RFC 2547, which details a method of distributing routing
information and forwarding data to provide a Layer 3 Virtual Private Network (VPN) service to end
customers. Although RFC 2547bis has long been quoted as an industry standard and is used in common
terminology to define this class of VPN, this RFC has since been updated as RFC 4364.

RFC 2547bis describes a method to provide a Layer 3 VPN service by providing the following functions
to the customer:
 Distribution of the customer’s routing information between sites
 Forwarding of the customer’s data packets to the appropriate destination
 Provision of a secure layer 3 routing connectivity between the various customer sites

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 10
 2 — L3VPN Overview

4 — 8 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 11
 2 — L3VPN Overview
2.1 L3 VPN: Introduction

192.168.2.0/24
192.168.1.0/24 Customer 1

Customer 1
VPRN Customer 1

Customer 2
VPRN 192.168.2.0/24
Customer 2
Customer 2
192.168.1.0/24

L3 VPN = Alcatel-Lucent VPRN

VPRN Instance #1
Goals :
VPRN Instance #2
 Connectivity between remote customer sites
 Isolation of routing and traffic from different VPNs
Route table for VPRN 1
 Potential use of private address spaces in each site
Route table for VPRN 2

4 — 8 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

At a given PE router, there will be a separate route table for each VPN instance, known as a the Virtual
Routing and Forwarding table, or VRF.

Implementation based on RFC 4364 (Formerly RFC 2547bis).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 12
2 — L3VPN Overview
2.2 L3 VPNs: Basic Requirements

From a customer’s perspective:

Customer can choose their IP addressing scheme
 Private addresses, overlapping addresses, etc.

Transparency: customer equipment is unaware of VPN

Security: separation of routing information and data among customers

QoS as defined in an SLA

Different sites may use different layer-2 access technologies

From a provider’s perspective:

Scalability:
 of the backbone network (signalling, state, etc.)
 # VPNs/backbone, # sites/VPN, # routes/VPN, etc.

Ease of provisioning: addition of a site to a VPN, creation of a new VPN,
merging of VPNs, etc.

4 — 8 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 13
 2 — L3VPN Overview
2.3 L3VPN: VRF instances on the PE

PE
CE1

VRF1

CE2
VRF2

Each PE router maintains a separate logical routing table for each VPRN

This table is referred to as a Virtual Routing and Forwarding table (VRF)

Contains customer destination routes
 local sites
 remote sites.

MP-BGP is used to carry the VPN routes from one PE to the others

4 — 8 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

VPRN services use Virtual Routing and Forwarding tables (VRF) within a PE device to maintain forwarding
information on a per site basis. A VRF is a logical private forwarding table created within a PE router.

Each PE may maintain multiple separate VRFs depending on the number of VPRN service instances it has.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 14
 2 — L3VPN Overview
2.4 L3VPN: VPRN Terminology – CE, PE, P

Customer Edge Router (CE) Provider Edge Router (PE)

Customer interface to the service
Interface between the customer and
provider’s network the service provider’s network

Exchange of IP routing information
Exchanges IP routing information with
with Corporate and PE routers CE and other PE routers

Different protocols possible
MP-BGP is used to carry the VPN
internally and with the PE routes between PE routers

CE1 CE3 Customer 1

PE1 PE2
Customer 1 P
P P

CE4
CE2

Customer 2

Customer 2 Provider Router (P)

Forms the service provider core network

Exchanges IP routing information with PE and P routers

An IGP (internal gateway protocol) is used to carry the
core routes
4 — 8 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPRN
7705 SAR — R6.0 Strategic Industries

Customer Edge (CE) Device

The Customer Edge (CE) router is the interface from the customer site to the service provider network.
In the VPRN context, the CE must be layer-3 aware.
The CE also runs a common routing protocol with the service provider router in order to exchange
routes with the provider network. This routing protocol may be the same or different than the routing
protocol used internally at the customer site or in the provider network.
The CE is typically unaware of the existence of the MPLS protocol or the VPNs, and runs standard IP
routing protocols.

Provider Edge (PE) Device

Provider Edge (PE) routers are the devices that provide the interface to the provider network for one or
more CE devices, from one or more distinct customers.

Provider (P) Devices

Provider (P) routers are the devices that comprise the internal provider network core. These devices
may be connected to other PE or P routers, but do not have any connections to the CE.
The P routers do not have a direct interface to any CE, but may have direct interfaces to PE routers.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 15
 2 — L3VPN Overview
2.5 L3VPN: Route Distinguisher

Different customers may use the same IP addresses within their

respective networks

An identifier called the Route Distinguisher (RD) is added to all IPv4
prefixes to ensure that the IP addresses remain unique

Route Distinguisher + IPv4 Prefix = VPN-IPv4 Prefix

8 bytes 4 bytes 12 bytes

Route Table (Router: Base) Route Table (Router: Base)

================================ =================================
Dest Address Next Hop Proto Dest Address Next Hop Proto
-------------------------------- ---------------------------------
192.168.1.0/24 CE_Blue BGP 65530:20:192.168.1.0/24 CE_Blue BGP
192.168.1.0/24 CE_Red BGP 65530:10:192.168.1.0/24 CE_Red BGP

Conflict

4 — 8 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Route Distinguisher (RD)

The Route Distinguisher is needed to make the VPN routes unique. This is necessary because all VPN
routes are carried in the same routing protocol (MP-BGP).

Different customers may use the same IP addresses within their respective networks. A method is
needed to ensure that the IP addresses remain unique when they are distributed across the service
provider network. This is achieved by pre-pending the 4-byte IPv4 address with an 8-byte Route
Distinguisher to form a new address called the “VPN-IPv4 address”. A distinct RD value can be
associated with individual routes or with all routes learned from a particular CE.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 16
 2 — L3VPN Overview
2.6 L3VPN: Which routes go into which VRF ?

The same set of PEs may need to exchange routes for different VPRNs

PEs establish a single MP-BGP session for the VPN-IPv4 family of prefixes

Some mechanism is needed to determine which VRF a route belongs to
 Mark a route by attaching a MP-BGP extended community attribute:
Route Target (RT)
 In many cases, the RT value chosen will be the same as the RD

MP-BGP Update
(Prefix =65530:20:192.168.1.0
RT = 65530:20)

192.168.1.0/24 CE1 Customer 1

VRF1 target
Customer 1 = 65530:20 CE3

CE2 PE1 PE2

CE4
VRF2 target
= 65530:10 Customer 2
Customer 2

4 — 8 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Route Target (RT)

The same set of PE routers may need to exchange routes corresponding to different VPRN service
instances. In addition to that, to improve scalability PE routers establish a single MP-BGP session for the
VPN-IPv4 family of prefixes.

Some mechanism is needed to determine to which VRF a route belongs. A Route Target was defined to
address this issue. The Route Target (RT) is the closest approximation to a VPN membership identifier in
the VPRN architecture, and identifies to the receiving PE the VRF table that a prefix is associated with.

Route Target is a MP-BGP extended community. One or more MP-BGP community attributes may be
associated to any route, therefore one or more Route Targets may be associated to any route.

In simple VPN cases and for provisioning consistency, the Route Target value chosen is often the same as
the Route Distinguisher value, however they should not be interpreted as meaning the same thing.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 17
 2 — L3VPN Overview
2.7 L3VPN and MP-BGP

The MultiProtocol BGP (MP-BGP) capability allows routers to carry VPN-

IPv4 prefixes, along with the RT as an extended community attribute

VPN-IPv4 addresses only need to be known by the provider’s edge
routers

MP-BGP Update
(Prefix =65530:20:192.168.1.0
RT = 65530:20)

192.168.1.0/24 CE1 Customer 1

VRF1 target
Customer 1 = 65530:20 CE3

CE2 PE1 PE2

CE4
VRF2 target
= 65530:10 Customer 2
Customer 2

4 — 8 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

BGP is used with Multiprotocol BGP extensions to distribute VPRN routing information across the service
provider’s network.

In order to carry VPN-IPv4 prefixes in BGP, support for the additional address family is required.
Separate BGP sessions must be enabled between every pair of routers for each of the address families
they need to exchange. When BGP is configured or enabled in this fashion, it is referred to as
Multiprotocol BGP or MP-BGP.

The Multiprotocol nature of MP-BGP allows the overlapping routing information to be transported across
the provider core as VPN-IPv4 addresses. VPRN routes are not distributed as IPv4 routes, but as 12 byte
VPN-IPv4 routes consisting of a concatenation of the Route Distinguisher and the IPv4 prefix.

It is important to note that the VPN-IPv4 address family is used only in the control plane when
exchanging MP-BGP routing updates between PEs. The data plane remains as standard IPv4. VRFs store
IPv4 prefixes without RD or RT values, and all data traffic is carried in standard IPv4 packets.

The customer is unaware of the existence of VPN-IP addresses. The translation between customer IP
routes in a particular VPN and VPN-IP routes distributed between provider routers is performed by the
PE routers.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 18
 2 — L3VPN Overview
2.8 L3 VPN: Import/Export Policy

Routes are tagged with one or more RTs

Routes are carried as VPN-IPv4 routes via
MP-BGP to the remote PE

192.168.1.0/24 192.168.1.0/24

VRF1 Import target

VRF1 Export target
65530:20
65530:20 MP-BGP Update
(Prefix =65530:20:192.168.1.0
RT = 65530:20)
192.168.1.0/24 CE1
Customer 1
Does RT =
CE2 PE1 PE2 VRF Import Target ?
Customer 2

VRF2 Import target

65530:10

4 — 8 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Routes are tagged with a route target value before sharing them with remote PEs due to the VPRN
configuration (vrf-target parameter). Alternatively, export policies can be defined to add route target
values (community attribute) to a route advertised to remote PEs. Upon receipt of a VPN-IPv4 route, a
PE router will by default add the route to the VRF associated to the route target value received with
the route. Import policies can be used to decide whether to add a given route to a VRF.

Route isolation between VRFs is accomplished through careful policy administration. An administrator
determines the appropriate export and import target relationships.

Since RTs are applied at the time the route is exported, they are called export-RT. In the above
example, a single RT is attached to each route.

The decision to import the route into the VRF is done by matching the received routes against locally
defined per-VRF import policies expressed in terms of RTs (import-RT). If the Router import RT matches
the update RT, it is stripped of the RD and imported into the VRF.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 19
 2 — L3VPN Overview
2.9 L3VPN: Route-distinguisher vs route-target

RT RD
Route-target Route-distinguisher

Part of VPN-IPv4 prefix N Y

Part of BGP attributes Y N

Makes a route unique N Y

Unique per VRF /VPRN N N

Unique per VRF/VPRN per node N Y

Only one per VPNv4 route N Y

Can be used in policies Y N

4 — 8 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

The route-target is part of the BGP attributes, whereas the route-distinguisher is part of the prefix, also
known as Network Layer Reachability Information (NLRI).

RD + subnet/mask makes the NLRI unique. Route-targets can be used by multiple VRF’s and thus do not
make the NLRIs unique.

One VRF, spread over multiple PEs, can make use of more than one RD and more then one RT. VRF A on
PE-1 can have a different RT and RD compared to VRF A on a different PE (PE-B).

On a PE, a single VRF/VPRN can only assign one RD, but it is possible to use more then one RT.

One VPNv4 route, has only one RD, as part of the NLRI, but can have more then one RT (multiple
extended communities can be sent with one NLRI).

Routing policies can check (match) on extended communities and/or add communities as a result of a
match condition. RDs can not be used in policies.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 20
 2 — L3VPN Overview
2.10 L3 VPN: Data Plane – Transport Tunnel

192.168.1.0/24 CE1 Customer 1

PE1 PE2
Customer 1 CE3
LSP

CE2
LSP
CE4
Customer 2
Customer 2

Each PE involved in a VPRN must have a tunnel to every other PE

participating in the same VPRN service

These tunnels will carry the customer’s VPN traffic from one site to
another

4 — 8 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

After the establishment of the routing topology in the provider core, a full mesh of transport tunnels
must be created between the PE’s. In other words, each PE involved in a given VPRN service must be
configured with a tunnel to every other PE participating in the same VPRN service in order to transport
a customer’s VPN traffic from one site to another. The transport tunnel is either an MPLS LSP or a GRE
point-to-point tunnel between PE’s.

The tunnels serve as the label switched paths the customer packets will take as they cross the provider
core network.

The tunnel is created either through the configuration of an SDP that is bound to the service or using
the auto-bind option when creating a VPRN service instance. The auto-bind option is possible for VPRN,
and not for the other service types, because in this case an MP-BGP session is established between every
pair of PE routers that participate in the service in order for them to exchange routing information (VPN
prefixes). So, its peers have been identified. Therefore, when the auto-bind command is issued, SDPs
are automatically created from the router to each of the other routers with which there exists an MP-
BGP session for the VPN family of prefixes.

If SDP tunnels are used, they must be created prior to the creation of the VPRN services.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 21
 2 — L3VPN Overview
2.11 L3 VPN: VPN Label

For data traffic at an egress PE, a decision must be made as to how to forward
each packet, depending on the customer it belongs to

The VPN (service) label distributed by MP-BGP with the route is used for this
 Associate a label (the VPN label) with a VPN data packet at the ingress PE
 Demux the traffic based on VPN label at egress PE

The VPN label in a data packet indicates either:
 which VRF must be used to resolve the next hop for the destination address, or
 the next-hop itself (as of Release 9.0.R1)

MP-BGP Update
(Prefix =65530:20:192.168.1.0
RT = 65530:20
192.168.1.0/24 CE1 VPN Label = 131068) Customer 1

Customer 1 CE3

PE1 PE2
CE2
CE4
Customer 2
Customer 2 MPLS
VPN
IP Data
Layer 2 Label
Label
131068

4 — 8 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

The purpose of the VPN label is to demultiplex VPN traffic arriving at the PE.
The distribution of the VPN label is done using BGP along with the VPN route information.
The distribution of the VPN tunnel information is automatic and does not require manual intervention.
Prior to Release 9.0.R1, the VPRN implementation allocated one unique (platform-wide) service label
per VRF. All IP-VPN routes exported by the PE from a particular VPRN service had the same service
label. When the PE received a terminating MPLS packet, the service label value determined the VRF to
which the packet belongs. A lookup of the IP packet destination address in the forwarding table of the
selected VRF determined the next-hop interface.
Release 9.0.R1 modifies the existing implementation by allowing the service label scheme to be
configurable per VPRN as either service label per VRF (the existing scheme and the default in Release
9.0) or service label per next-hop. When a VPRN is configured for service label per next-hop, MPLS
allocates one unique (platform-wide) service label for every next-hop IP address of the VPRN. When the
PE receives a terminating MPLS packet, it will be forwarded to the next-hop that the service label is
associated with, without any VRF lookup.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 22
 3 — Local vs distributed VPRN

4 — 8 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 23
 3 — Local vs distributed VPRN
3.1 Local vs distributed VPRN

A VPRN can be local (only one PE provides the service) or distributed (two or
more PEs collaborate to provide the service)

In a distributed VPRN, each PE needs to:

establish MP-BGP sessions with the other PEs to exchange routing information residing
in their respective VRFs

create SDPs towards the other PEs to carry the customer data

In a local VPRN, however, there is no need

to run MP-BGP or
Private

to create SDPs network Private
site network
Private site
network
Private site
network Private CE router
site network CE router
site CE router
Private
Private
CE router
PE router
VPRN
network
network site VPRN
site
VPRN CE router
IP/MPLS
PE router
Backbone
PE router VPRN
CE router CE router
PE router

Local VPRN Distributed VPRN

4 — 8 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPRN
7705 SAR — R6.0 Strategic Industries

In a local service, the PE may still need to run BGP (not MP-BGP) on one or more VPRN interfaces if that is the
protocol that the PE and the CE agree to use to exchange local routing information relative to the specific
location where the subscriber is situated.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 24
 4 — VPRN setup and configuration

4 — 8 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 25
 4 — VPRN setup and configuration
4.1 VPRN configuration steps

The following configuration steps are needed for an operational VPRN:

Establish MP-BGP sessions between PE routers that participate in VPRN

 Family of prefixes is VPN-IPv4
Only required for
distributed VPRN

Create VPRN
 Associate to customer
 Specify Route Distinguisher (RD) and Route Target (RT)
 Create transport tunnels (individual SDPs to other PEs or auto-bind)
 Create interfaces, as needed, to interact with customer sites *
 Configure the routing protocol used to exchange routing information with
customer

* Note: VPRN interface configuration requires exactly the same steps as creating an
interface for an IES service
4 — 8 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — VPRN
7705 SAR — R6.0 Strategic Industries

Creating an interface for a VPRN requires exactly the same steps as creating an interface for an IES service.
Namely, the following components are needed:

 Interface name
 Interface IP address
 A way of receiving/sending IP packets from/to the customer. For this, there are three alternatives:

 Through a SAP if the customer is directly connected to the PE router

 Through an SDP if the PE router is connected to the customer via a spoke SDP that originates on
another router (coming from an ePipe, iPipe or VPLS service)
 Through a VPLS if the same layer-3 interface is used to provide services to several customer locations
that belong to the same virtual private LAN (routed VPLS)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 26
 4 — VPRN setup and configuration
4.2 L3 VPN: CE to PE Route Distribution

The following route distribution options are available on the 7750 SR:

Static routes

RIP

BGP static-route 192.168.1.0/24 next-hop 192.168.11.1

OSPF
autonomous-system 65530
bgp
router-id 1.1.1.1
group "to-CE"
neighbor 192.168.11.1
vprn 20 customer 1 create export “mpbgp->bgp"
route-distinguisher 65530:20 peer-as 65530
vrf-target target:65530:20
auto-bind ldp
interface "to-CE1" create ospf
address 192.168.11.2/29 asbr
sap 1/1/4 create export "mpbgp->ospf"
rip area 0.0.0.1
export “mpbgp->rip” interface "to-CE1"
group "to-CE"
neighbor “CE1"

4 — 8 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

PE to CE Routing
Every prefix that is learned by the PE through the routing protocol it is running with its neighboring CE, will be
automatically installed in the VRF and shared with other PE routers via MP-BGP. However, the prefixes that are
learned by the PE through MP-BGP, advertised by remote PEs, are not automatically shared with the CE. An
export policy is needed to control what is shared and what is not.

If static routes are configured at the PE towards the CE, they will be shared with other PEs via MP-BGP. However,
if there is no dynamic routing protocol running between PE and CE, the routes learned by the PE through MP-BGP,
advertised by remote PEs, will not be shared with the CE; in this case, the CE will have to rely on a default route
to the PE.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 27
4 — VPRN setup and configuration
4.2 L3 VPN: CE to PE Route Distribution [cont.]

The following route distribution options are available on the 7705 SAR:

Static routes

OSPF

BGP static-route 192.168.1.0/24 next-hop 192.168.11.1

autonomous-system 65530
bgp
router-id 1.1.1.1
group "to-CE"
neighbor 192.168.11.1
vprn 20 customer 1 create export “mpbgp->bgp"
route-distinguisher 65530:20 peer-as 65530
vrf-target target:65530:20
auto-bind ldp
interface "to-CE1" create ospf
address 192.168.11.2/29 asbr
sap 1/1/4 create export "mpbgp->ospf"
area 0.0.0.1
interface "to-CE1"

4 — 8 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 28
4 — VPRN setup and configuration
4.3 L3VPN: PE to PE Route Distribution

CE1 MP-BGP CE3

PE1 PE2

CE2 CE4

config router
autonomous-system 65530
bgp
family vpn-ipv4
group "bgp-core"
peer-as 65530
neighbor 2.2.2.2

4 — 8 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 29
 4 — VPRN setup and configuration
4.4 L3VPN: Populating a VRF
PE-PE
(2) MP-BGP protocol (8)
(1) (9)
Import Export
RIB-in policy RIB policy RIB-Out

(3) (7)
OSPF

Control (MP-BGP)
(4) RTM
BGP Control (internal)
RTM
Data-stream (IP)
(5)

STATIC

(6)
VRF
VRF
RIP

Separate RTM and VRF per VPRN

PE-CE protocols

4 — 8 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

1. A MP-BGP process receives updates from its peers and collects them in the RIB-IN (RIB stands for
Routing Information Base).
2. After applying import policies (if configured) to reject unwanted prefixes, the best routes selected
based on BGP criteria are sent to the RIB.
3. All routes in the RIB are offered to the RTM (Route Table Manager).
4. The RTM collects the routes received from MP-BGP peers and also those discovered by the routing
protocols that are running between the PE and CE (it could be OSPF, BGP, RIP or static). It selects
from those the ones that will be used based on preference values among protocols. Note that there
will be a separate RTM per VPRN.
5. If a route is selected by the RTM to be used to forward data packets, it will be installed in the
corresponding VRF and downloaded on all forwarding complexes of the IOM.
6. At this point, the selected routes can be used to make forwarding decisions for data packets.
Incoming IP traffic will do LPM (longest prefix match) on the VRF to make a forwarding decision.
7. MP-BGP routes that were selected by the RTM to be used are marked as such in the RIB.
8. By default, all routes marked as used in the MP-BGP RIB will be copied into the RIB-OUT database to
be advertised to the MP-BGP peers. Likewise, routes discovered by means of the PE-CE protocols
that are chosen by the RTM will by default be copied into the RIB-OUT database. Export policies can
be created to keep some of these routes from ending up in the RIB-OUT and from being advertised to
MP-BGP peers.
9. Prefixes in the RIB-OUT are shared with MP-BGP peers.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 30
 4 — VPRN setup and configuration
4.5 L3VPN: Monitoring a VRF

Verify the VPRN routing table of the PE

PE1# show router 20 route-table
===============================================================================
Route Table (Service: 20)
===============================================================================
Dest Prefix Type Proto Age Pref Metric
Next Hop[Interface Name]
-------------------------------------------------------------------------------
192.168.2.0/24 Remote BGP VPN 01d01h48m 170 0
2.2.2.2
192.168.1.0/24 Remote OSPF 01d01h48m 150 1
192.168.11.1
192.168.11.0/29 Local Local 01d01h48m 0 0
to-CE1
-------------------------------------------------------------------------------
No. of Routes: 3
===============================================================================
PE1#

4 — 8 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

The show router <service-id> route-table command (in this case PE1) is used to verify the contents of
the routing instance for the specified service.

As shown above, this table should contain customer routes such as physical links to the CE devices,
system interfaces of the CE devices and internal customer networks.

The prefixes received from the local CE will be learned via the configured PE-CE protocol, in this case
OSPF, and the prefixes received from the remote CE will be learned via the BGP VPN (MP-BGP) protocol.

Notice that in the VRF, the RD and RT have been removed before the prefix is imported into the VRF
table.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 31
 4 — VPRN setup and configuration
4.6 L3 VPN: Monitoring MP-BGP learned routes (RIB-In)

A:PE2# show router bgp routes 65530:20:192.168.1.0/24 detail

======================================================
To find out the VPN label and the Route BGP Router ID : 2.2.2.2 AS : 65530 Local AS : 65530
Target: ======================================================

No command like : Status codes : u - used, s - suppressed, h - history, d - decayed,
 #show router bgp rib-in * - valid Origin codes : i - IGP, e - EGP, ? - incomplete, > - best

Possible commands ======================================================
 # show router bgp routes vpn-ipv4 BGP Routes

 # show router bgp neighbor 1.1.1.1 Network : 192.168.1.0/24

received-routes vpn-ipv4 Nexthop : 1.1.1.1
 # show router bgp routes Route Dist. : 65530:20 VPN Label : 131070
65530:20:192.168.1.0/24 detail From : 1.1.1.1
Res. Nexthop : 192.168.12.1
Local Pref. : 100 Interface Name : pe2-1
Aggregator AS : none Aggregator : none
Atomic Aggr. : Not Atomic MED :1
Community : target:65530:20
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 1.1.1.1
Flags : Used Valid Best IGP
AS-Path : No As-Path

4 — 8 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

show router bgp routes 65530:20:192.168.1.0/24 details

This command shows all routes with this prefix that are received. Per route, there is an output on the
original and modified path attributes. The route is displayed with its original attributes, as it was
received from its peer before applying the import policies (if configured). If no import policies are
configured, the original and modified attributes are equal.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 32
 4 — VPRN setup and configuration
4.7 L3 VPN: Monitoring MP-BGP learned routes (RIB-In)

BGP updates carry the Route Distinguisher and VPN Label, identifying the remote VRF

A:PE2# show router bgp neighbor 1.1.1.1 received-routes vpn-ipv4

===============================================================================
BGP Router ID : 1.1.1.1 AS : 65530 Local AS : 65530
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best

===============================================================================
BGP Routes
===============================================================================
Flag Network LocalPref MED
Nexthop VPN Label
As-Path
-------------------------------------------------------------------------------
u*>i 65530:20:192.168.1.0/24 100 1
1.1.1.1 131070
No As-Path

4 — 8 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

show router bgp neighbor < . . . > received-routes

This command shows all routes that are received from this BGP-peer. There is no “detail” option
available for this, so for more detailed information, a “per-route” display needs to be done.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 33
 4 — VPRN setup and configuration
4.8 L3 VPN: Monitoring MP-BGP advertised routes (RIB-Out)
No command like :
#show router bgp rib-out
Two possible commands
# show router bgp neighbor 1.1.1.1 advertised-routes vpn-ipv4
# show router bgp routes 65530:20:192.168.2.0/24 hunt

A:PE2# show router bgp neighbor 1.1.1.1 advertised-routes vpn-ipv4

===============================================================================
BGP Router ID : 2.2.2.2 AS : 65530 Local AS : 65530
===============================================================================
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
BGP Routes
===============================================================================
Flag Network LocalPref MED
Nexthop VPN Label
As-Path
-------------------------------------------------------------------------------
i 65530:20:192.168.2.0/24 100 1
10.1.1.22 131057
No As-Path

4 — 8 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

show router bgp neighbor < . . . > advertised-routes

This command shows all routes that are advertised to this BGP-peer. There’s no “detail” option
available for this, so for more detailed information, a “per-route” display needs to be done

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 34
 4 — VPRN setup and configuration
4.9 L3 VPN: Monitoring MP-BGP advertised routes (RIB-Out)

BGP updates carry the VPN label and the RT which identifies the remote VRF
PE1# show router bgp routes 65530:20:192.168.1.0/24 hunt
===============================================================================
BGP Router ID : 1.1.1.1 AS : 65530 Local AS : 65530
===============================================================================
Legend -Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best
===============================================================================
BGP Routes – RIB Out
===============================================================================
Network : 192.168.1.0/24
Nexthop : 2.2.2.2
Route Dist. : 65530:20 VPN Label : 131057
To : 2.2.2.2
Res. Nexthop : n/a
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : none Aggregator : none
Atomic Aggr. : Not Atomic MED : 1
Community : target:65530:20
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 2.2.2.2
Origin : IGP
AS-Path : No As-Path
===============================================================================
PE1#

4 — 8 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

show router bgp routes 200:20:192.168.1.0/24 hunt

This command shows all peers that have received this route. There is an output of the route-per-peer,
after applying potential export-policies. Since export policies can be applied on a per-peer basis, the
routes can have a different content, that’s why they are displayed per-peer.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 35
 5 — Packet walkthrough

4 — 8 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 36
 5 — Packet walkthrough
5.1 L3 VPN: Data Plane – Transport Tunnel

192.168.1.0/24 CE1 Customer 1

PE1 PE2
Customer 1 CE3
MPLS LSP

CE2 GRE
CE4
Customer 2
Customer 2

spoke-sdp 1002 create auto-bind gre auto-bind ldp/rsvp-te

vprn 20 customer 1 create

route-distinguisher 65530:20
vrf-target target:65530:20
interface "to-CE1" create
address 192.168.11.2/30
sap 1/1/4 create

4 — 8 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Each PE involved in a given VPRN service must be configured with a tunnel to every other PE
participating in the same VPRN service in order to transport a customer’s VPN traffic from one site to
another. The transport tunnel is either an MPLS LSP or a GRE point-to-point tunnel between PE’s.

The tunnel is created either through the configuration of an SDP or using the auto-bind option. When
the auto-bind command is issued, SDPs are created from the router to each of the other routers with
which there exists an MP-BGP session for the VPN family of prefixes.

If SDP tunnels are used, they must be created prior to the creation of the VPRN services and then bound
using the spoke-sdp option.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 37
 5 — Packet walkthrough
5.2 L3 VPN: Forwarding Traffic

192.168.1.0/24 CE1 Customer 1

Customer 1 CE3
LSP

PE1 PE2
CE2
CE4
Customer 2
Customer 2

Layer Layer LSP VPN Layer

IP Packet IP Data IP Packet
2 2 Label Label 2

LSP Label will change VPN Label will not

at each P router change between PEs
CE to PE PE to PE PE to CE

4 — 8 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Shown above are the data packet formats visible in an MPLS network. Note that the packet is a standard
IP packet to which MPLS labels have been inserted in the provider core. The Route Distinguisher and the
Route Target are not used in the data plane.

Between the PE and the CE, only unlabeled data packets should be seen.

From PE to PE in the provider core, customer VPRN traffic will have a label stack consisting of 2 MPLS
labels. The outer label (LSP label) is used to propagate the packet from PE to PE across the provider
core. The inner label (VPN label) identifies the VPRN to the egress PE.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 38
End of module
VPRN

4 — 8 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — VPRN
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.8 Edition N/A
Section 4 — Module 8 — Page 39
Learning experience powered by
Alcatel-Lucent University

Section 4
Services
Module 9
IES
TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

4—9—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 1
Blank page

4—9—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 2
Module objectives

Upon completion of this module, you should be able to:

Features of an Internet Enhanced Service

Basic configuration of an IES

4—9—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 3
Module objectives [cont.]

4—9—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 4
 Table of Contents

1 — Features of an Internet Enhanced Service 7

Page
2 — Basic configuration of an IES 18
1 — Features of an Internet Enhanced Service 7
1.1 Internet Enhanced Service (IES) Overview 8
1.2 Internet Enhanced Service (IES) – Interface Types 9
1.3 Internet Enhanced Service (IES) - SAP 10
1.4 Internet Enhanced Service (IES) - SDP 11
1.5 Internet Enhanced Service (IES) - rVPLS 12
1.6 IES Routed Connectivity Service Example 13
1.7 Spoke termination for IES 14
1.8 Spoke termination for IES - ePipe 15
1.9 Spoke termination for IES - VPLS 16
1.10 Routed VPLS 17
2 — Basic configuration of an IES 18
2.1 Configuring an IES 19
2.2 IES Management 20

4—9—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 5
Table of Contents [cont.]

4—9—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 6
 1 — Features of an Internet Enhanced Service

4—9—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 7
 1 — Features of an Internet Enhanced Service
1.1 Internet Enhanced Service (IES) Overview

An IES is a routed, layer-3 connectivity service, that can have one or more
layer-3 interfaces associated to it

From the customer’s point of view, an IES interface is no different from a
standard layer-3 interface

It gives the customer access to the IP networks that the PE router is aware of
(the customer can participate in the same routing instance as the PE router)

IES Interfaces can be included in the following routing protocols: Static, RIP, OSPF, IS-
IS, and BGP

From the service provider point of view, however, it allows the application of
policies to provide QoS and for accounting/billing

IES Layer-3
interface

IES 500
OSPF

4—9—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Internet Enhanced Service (IES) is a routed connectivity service where the subscriber communicates
with an IP router interface to send and receive Internet traffic.
An IES:
 Has one or more logical IP routing interfaces, each with its own IP address and connected to one or
more customer locations
 Allows customer-facing IP interfaces to participate in the same routing instance used for service
network core routing connectivity
 Requires that the IP addressing scheme used by the subscriber be unique relative to other provider
addressing schemes and potentially the entire Internet

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 8
1 — Features of an Internet Enhanced Service
1.2 Internet Enhanced Service (IES) – Interface Types

A standard layer-3 interface has an IP address and a port associated to it

Similarly, an IES interface has an IP address associated to it and a way of receiving/sending IP packets
from/to the customer

There are three alternatives:

Through a SAP if the customer is directly connected to the PE router

Through an SDP if the PE router is connected to the customer via a spoke SDP that originates on another router
(coming from an ePipe, iPipe or VPLS service)

Through a VPLS if the same layer-3 interface is used to provide services to several customer locations that
belong to the same virtual private LAN

Note: These alternatives apply, not only to IESs , but also to VPRNs (Virtual
Private Routed Networks).

4—9—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 9
1 — Features of an Internet Enhanced Service
1.3 Internet Enhanced Service (IES) - SAP

First alternative:

The IES interface is directly connected to the customer through a SAP

IES Layer-3
interface
ies 500 customer 1 create
interface "int_1" create
SAP IES 500 address 138.120.121.7/24
sap 1/1/2 create

4 — 9 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 10
1 — Features of an Internet Enhanced Service
1.4 Internet Enhanced Service (IES) - SDP

Second alternative:

The IES interface is connected to the customer through a spoke SDP that
originates on another router (coming from an ePipe, iPipe or VPLS service)

IES Layer-3
interface
ies 500 customer 1 create
interface "int_1" create
SAP ePipe 200 SDP SDP IES 500 address 138.120.121.7/24
spoke-sdp 5:200 create

4 — 9 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 11
 1 — Features of an Internet Enhanced Service
1.5 Internet Enhanced Service (IES) - rVPLS

Third alternative (routed VPLS):

The IES interface is connected to customers through a VPLS that is used
to provide services to several customer locations that belong to the same
virtual private LAN

IES Layer-3
interface
SAP VPLS 300 SDP

ies 500 customer 1 create

interface "int_1" create
SAP VPLS 300 SDP SDP VPLS 300 IES 500 address 138.120.121.7/24
vpls "vpls-one" create

SAP VPLS 300 SDP

4 — 9 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

In the configuration of this example, all customers see the same IES interface, with the same IP
address, as a potential next-hop towards external networks. In addition to that, all customers see each
other as participants of the same LAN.

The VPLS, even though it is a service in itself, becomes a component of another service; namely, of the
IES layer-3 interface.

This option, known as routed VPLS, is available as of software release 9.0. An IES IP interface cannot
be bound to a service name unless the system is configured in chassis mode D.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 12
 1 — Features of an Internet Enhanced Service
1.6 IES Routed Connectivity Service Example

Traffic in an IES service is exchanged using an IP interface that

can participate in the core routing instance

Contrary to VPNs, an IES does not require the configuration of
an SDP to tunnel traffic from one PE to another

No SDP to another
Edge Router
ies 500 customer 1 create (IES is not a VPN)
interface server create
address 138.120.121.7
sap 1/1/2 create

ospf
area 0.0.0.0
... IES 500
interface server
OSPF
SAP

Edge Router

4 — 9 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Traffic in an IES service is exchanged using an IP interface that participates in the same routing instance as the
core routers. Because of that, contrary to VPNs, an IES does not require the configuration of an SDP to tunnel
traffic from one PE to another. An SDP can be configured for a given interface, instead of a SAP, but that is to
terminate a spoke-SDP that carries traffic to and from a customer connected through a layer-2 service; this is
better explained in the next slide.

Since IES interfaces are part of the core routing domain, a portion of the service provider IP address space can be
reserved for IES service provisioning. The reserved portion is user-configurable.

SAP Encapsulations Supported:

 Ethernet: null, dot1q, and q-in-q
 SONET/SDH: IPCP, BCP-null, and BCP-dot1q
IP Interface:
 Most options found on core IP interfaces
 VRRP – for IES with more than one IP interface
 Secondary IP addresses
 ICMP options
Routing Protocols Supported:
 RIP
 OSPF
 IS-IS

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 13
 1 — Features of an Internet Enhanced Service
1.7 Spoke termination for IES

Instead of configuring a SAP for an IES interface, an SDP can be bound

to it

Still connecting customer to core routing, but not directly at the Edge
Router but indirectly through a presumably less powerful Access Router

Introduces the ability to cross-connect traffic entering on a spoke SDP
to an IES

A spoke SDP could be tied to an ePipe, an iPipe, or a VPLS service

Still no SDP to
another Edge Router
(IES is not a VPN)

ePipe 200 IES 520

SDP SDP
12 21 OSPF
SAP

Access Router Edge Router

(low-end) (high-end)
4 — 9 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — IES
7705 SAR — R6.0 Strategic Industries

This feature provides the ability to cross-connect traffic entering on a spoke SDP, used for Layer 2 services (VLLs
or VPLS), on to an IES or VPRN service. From a logical point of view the spoke SDP entering on a network port is
cross-connected to the layer 3 service as if it had entered via a service SAP. The traffic entering the Layer 3
service via a spoke SDP is handled via network QoS policies rather than an access QoS policies.

Traffic to be terminated on a given IES or VPRN service is identified by the MPLS labels present in the service
packet, identifying the transport tunnel and service tunnel.

The SDP IDs on the ePipe and IES sides do not have to match, but the VC IDs need to be the same.

Note:
 As of R9.0, only SDPs coming from an Ethernet later-2 service (ePipe or VPLS) or from an iPipe are supported
for spoke termination
 ATM and Frame Relay VLLs are not supported
 ECMP is not supported on the SDP tunnel

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 14
 1 — Features of an Internet Enhanced Service
1.8 Spoke termination for IES - ePipe

ies 520 customer 1 create

interface ePipe200 create
address 138.120.121.8
spoke-sdp 21:200 create
ip-mtu 1500

ospf
area 0.0.0.0
epipe 200 customer 1 create
...
sap 1/1/5 create
interface ePipe200
spoke-sdp 12:200 create

ePipe 200 IES 520

SDP SDP
12 21 OSPF
SAP

 Service MTUs must be equal

 IES can only terminate a spoke-SDP, not a mesh-SDP
4 — 9 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Services — IES
7705 SAR — R6.0 Strategic Industries

spoke-sdp sdp-id:vc-id vc-type {ether|ipipe} binds a service to an existing SDP

In this configuration it is important to note that during the VC Label signalling process, if the VC MTU does not
match the service will be operationally down.

The command show service id 520 base displays the Operational MTU for the IES
The command show service id 200 base displays the Operational MTU for the ePipe

The default VC MTU for a layer-2 service (VLL or VPLS), which is the maximum IP payload that the service will
carry, is 1500 bytes. That is why the IP-MTU for the IES interface has to be set to the same value.

As an alternative to changing the MTU for the IES interface (ip-mtu 1500), the SDP MTU could have been changed
(path-mtu 1514) but this would impact all services carried by the SDP. Any service requiring a larger MTU than
1514 would go operationally down.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 15
 1 — Features of an Internet Enhanced Service
1.9 Spoke termination for IES - VPLS

ies 530 customer 1 create

interface VPLS300 create
address 138.120.121.9
spoke-sdp 21:300 create
ip-mtu 1500

vpls 300 customer 1 create ospf

sap 1/1/5 create area 0.0.0.0
spoke-sdp 12:300 create ...
mesh-sdp 15:300 create interface VPLS300

SDP
15
VPLS 300 IES 530
SDP SDP
12 21 OSPF
SAP

4 — 9 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

spoke-sdp sdp-id:vc-id vc-type {ether|ipipe} binds a service to an existing SDP

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 16
 1 — Features of an Internet Enhanced Service
1.10 Routed VPLS
vpls 300 customer 1 create
service-name "vpls-one"
allow-ip-int-binding
spoke-sdp 21:300 create
...
ies 530 customer 1 create
interface VPLS300 create
address 138.120.121.9
vpls "vpls-one"
ip-mtu 1500
...
vpls 300 customer 1 create
ospf
sap 1/1/5 create
area 0.0.0.0
spoke-sdp 12:300 create
...
mesh-sdp 15:300 create
interface VPLS300

SDP
15
VPLS 300
SDP SDP
VPLS 300 IES 500
12 21
SAP OSPF

4 — 9 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

spoke-sdp sdp-id:vc-id vc-type {ether|ipipe} binds a service to an existing SDP

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 17
 2 — Basic configuration of an IES

4 — 9 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 18
 2 — Basic configuration of an IES
2.1 Configuring an IES

 Create an IES service and associate it with a customer ID

 Create an interface within the IES and associate IP address

Define SAP parameters on the interface
o Select port and encapsulation

Alternatively, define SDP parameters on the interface
o Select SDP and VC-ID

As a third option, specify VPLS to be used to connect to subscribers
o Select VPLS name
 Optional - select QoS policies other than the default (configured in the
config>qos context)
 Optional - select filter policies (configured in the config>filter context)
 Optional - select accounting policy (configured in the config>log context)
 Optional - add more interfaces as needed
 Enable the service.

4 — 9 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Example:

1. Create an IES service and associate it with a customer ID.

config>service# ies 1000 customer 50 create

config>service>ies# description “to-internet”

2. Create an interface.

config>service>ies$ interface ToWeb create

config>service>ies>if$ address 10.10.36.2/24

3. Define SAP parameters on the interface. A SAP is a combination of a port and optional encapsulation
parameters which identifies the service access point on the interface and within the ESS. Each SAP must be
unique within a router.

config>service>ies>if# sap 5/1/3:0 create

or
config>service>ies>if# spoke-sdp 5:100 create

4. Enable the IES.

config>service>ies# no shutdown

Notes:
 You can configure an IES interface as a loopback interface by issuing the loopback command instead of the sap
sap-id command.
 The loopback flag cannot be set on an interface where a SAP is already defined and a SAP cannot be defined
on a loopback interface.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 19
 2 — Basic configuration of an IES
2.2 IES Management

You can perform the following management tasks on an IES:

Disable the service

Re-enable the service

Modify service parameters

Delete the service

4 — 9 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Disabling an IES

You can shut down an IES service without deleting the service parameters.

config>service# ies 1000

config>service>ies# shutdown
config>service>ies# exit

Re-enabling an IES

config>service# ies 1000

config>service>ies# no shutdown
config>service>ies# exit

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 20
End of module
IES

4 — 9 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Services — IES
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 4.9 Edition N/A
Section 4 — Module 9 — Page 21
Learning experience powered by
Alcatel-Lucent University

Section 5
Synchronization
Module 1
Synchronization Overview
TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

5—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 1
Blank page

5—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 2
Module objectives

Upon completion of this module, you should be able to describe:

Describe the need for synchronization

Identify the different synchronization methods

Explain the pros and cons of each synchronization method

5—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 3
Module objectives [cont.]

5—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 4
Table of Contents

1 — What is Synchronization? 7
Page
2 — Network Synchronization Types 21
1 — What is Synchronization? 7
1.1 Synchronization Overview 8
1.2 Time Synchronization 9
1.3 Frequency Synchronization 10
1.4 Phase Synchronization 11
1.5 Synchronization Accuracy Examples 12
1.6 Primary Reference Clock 13
1.7 Primary Referency Clock (continued) 14
1.8 Synchronization Requirements 15
1.6 Synchronisation Issues 16
1.7 Synchronization Issue Example 17
1.8 Strategic Industries – Power Utility 18
1.9 Strategic Industries – Railway Operations 19
2 — Network Synchronization Types 21
2.1 Timing/Synchronization 22
2.2 Network timing and synchronization 23
2.3 Synchronous Networks 24
2.4 Timing Domains 25
2.5 Network Synchronization Options 26
2.6 BITS: External Synchronization 27
2.7 Line Synchronization 28
5—1—5
2.8 Synchronous Ethernet 29
2.9
Synchronization Synchronous-Ethernet:
— Synchronization Requirements
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Overview
7705 SAR — R6.0 Strategic Industries
30
2.10 Adaptive Clock Recovery 31
2.11 ACR synchronization source clock protection 32
2.12 IEEE 1588v2 Overview 33
2.13 IEEE1588v2 PTP Timing and Resiliency Model 34
2.14 Best Master Clock (Unicast Mode) 35
2.14 Best Master Clock (Unicast Mode) 36

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 5
Table of Contents [cont.]

5—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 6
 1 — What is Synchronization?

5—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 7
1 What is Synchronization?
1.1 Synchronization Overview

What is synchronization?

The ability to achieve equivalent values for time, frequency, and phase
within different elements in a network.

•Time (time of day) – Much needed for event correlation. ie. alarms,
billing

•Frequency (timing, synchronization) – Needed for carrier alignment and

the avoidance of overruns and underruns.

•Phase – Needed for avoidance of misreading symbol stream. Necessary

for avoiding impact in handoff between eNodeBs. Required by W-CDMA
TDD and WiMAX and is currently achieved by using a GPS.

5—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 8
 1 What is Synchronization?
1.2 Time Synchronization

In technologies using Time Division Duplexing, ie. WiMAX and TD-SCDMA,

there must be synchronization between base stations in order to avoid
transmission overlap within TDD frames.

Synchronization allows for reduced guardbands to ensure high bandwidth

utilization and tighter accuracy.
•Guardband gaps allows the the base stations to change from transmit to
receive modes of operation.

5—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

NTP has been used to provide Time of Day synchronization to devices connected over the public and private
Internet. It works well with synchronization requirements to 10s of milliseconds of UTC, but it was not designed
for highly accurate frequency distribution nor for accurate phase requirements of TDD mobile technologies.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 9
 1 What is Synchronization?
1.3 Frequency Synchronization

•Frequency Synchronization must be accurate in order to ensure service

continuity. ie. successful handoff – handset moving from one nodeB to
another.
•Frequency stability of 50-250 ppb is required to avoid interference and
roaming issues. Poor frequency synchronization may drop calls on
handoff.
• Measured in parts per billion (ppb)

5 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Studies have shown significant reduction in call drops when good synchronization is in place; enhanced QoE

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 10
1 What is Synchronization?
1.4 Phase Synchronization

•Distributing time synchronization is one way of achieving phase

synchronization.
•UMTS based cells (TDD-based) require accuracy of better than 2.5 µs
beween cells. Also, in order to carry audio and video applications time
synchronization in sub µs range is required.

5 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 11
 1 What is Synchronization?
1.5 Synchronization Accuracy Examples

Radio Frequency Accuracy These accuracies are achieved using either

GSM: 50 ppb
GPS connected to the basestations

WCDMA TDD: 50 ppb

WCDMA FDD: 50 ppb OR

CDMA2000: 50 ppb

WiMAX: 2 ppm
Highly accurate local oscillator in
basestation
Phase Accuracy
OR

WCDMA TDD – 2.5 us between Node B’s

CDMA2000 – 10 us of UTC

by using the T1/E1 interface provided by
the backhaul network.

5 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

If the T1/E1 from the mobile backhaul network is used, the basestation has to average the received timing signal
to ensure it can extract the fundamental frequency to an accuracy that allows it to achieve its radio frequency
accuracies
The basestation will be designed to expect a signal that conforms to the network limit of wander for either the
Traffic Interface or the Synchronisation Interface

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 12
1 What is Synchronization?
1.6 Primary Reference Clock

Another option for frequency synchronization reference is the one

generated by a Primary Reference Clocks (PRCs) and distributed through
the network. Primary Reference Clock

Stratum 1
Gateway
Class 1 or 2 CO

Stratum 2
ST 2 ST 2
Class 2 or 3
Central Office

Stratum 3 ST 3 ST 3 ST 3 ST 3 ST 3
Class 4 or 5
Toll/End Office

Stratum 4
Customer Prem ST 4 ST 4 ST 4 ST 4 ST 4 ST 4 ST 4

Primary Reference
Secondary Reference

5 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 13
 1 What is Synchronization?
1.7 Primary Referency Clock (continued)

Stratum Frequency Pull-In-Range Stability Time To First

Accuracy/Adjust Frame Slip
Range

1 1 x 10-11 N/A N/A 72 Days

2 1.6 x 10-8 Must be capable of synchronizing to 1 x 10-10/day 7 Days

clock with accuracy of +/-1.6 x 10-8

3E 1.0 x 10-6 Must be capable of synchronizing to 1 x 10-8/day 3.5 Hours

clock with accuracy of +/-4.6 x 10-6

3 4.6 x 10-6 Must be capable of synchronizing to 3.7 x 10-7/day 6 Minutes (255 in

clock with accuracy of +/-4.6 x 10-6 24 Hrs)

4E 32 x 10-6 Must be capable of synchronizing to Same as Accuracy Not Yet Specified

clock with accuracy of +/-32 x 10-6

4 32 x 10-6 Must be capable of synchronizing to Same as Accuracy N/A

clock with accuracy of +/-32 x 10-6

5 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Slide displays different stratum levels associated with detailed information such as their accuracy range and
stability, and the minimum requirement ‘pull-in-range’ to synchronize with another clock.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 14
1 What is Synchronization?
1.8 Synchronization Requirements
Radio System Frequency Time/Phase Solutions
Accuracy Accuracy
GSM 50 ppb No requirement Timing Over Packet (ACR, 1588v2)
Sync E
E1/T1 Line Timing

UMTS (FDD mode) ± 50 ppb No Requirement Timing Over Packet

observed over a Sync E
period of one
timeslot

UMTS (TDD mode) ± 50 ppb <2.5 µs phase Timing Over Packet

observed over a accuracy Sync E
period of one between inputs
timeslot for RF to any of the
frequency NodeB’s with
generation daisy chained
synched ports
LTE FDD ± 50 ppb 10 to 100 ms Timing Over Packet
LTE MBMS observed over a Sync E
period of one
timeslot

5 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 15
1 What is Synchronization?
1.6 Synchronisation Issues

The need for synchronization is focused in three principal areas:

Radio Framing Accuracy between the handset and the base station.
Handoff Control.
Backhaul Transport Reliability.

Some examples may include issues such as but not limited to the ones
below:

•Voice traffic will experience clicks

•Faxes can duplicate lines or drop whole lines
•Modems can loose lock and have to retrain
•Data requires higher level error detection and then retransmission
•Failed calls and handovers

5 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 16
1 What is Synchronization?
1.7 Synchronization Issue Example

•When a handoff takes place, both BTS need to be synchronized in terms

of frequency.
•If the frequency drifts outside the 50 ppb window, the call will be
dropped.
•Mobile needs to lock to the destination BTS, and having frequency
synchronized is a major factor.

5 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 17
 1 What is Synchronization?
1.8 Strategic Industries – Power Utility

5 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Example of wireless technologies (WiMAX/LTE) being used in a power utility. Power utilities are transitioning
from TDM based technologies towards IP/MPLS in order to reduce cost, increase power quality, and improve
outage response.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 18
 1 What is Synchronization?
1.9 Strategic Industries – Railway Operations

5 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Example of railway operations in an IP/MPLS communications network. Traditionally, railway operators have used
technologies such as SDH/SONET/PDH/TDM-based technologies and are transitioning to IP/MPLS.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 19
 1 What is Synchronization?
1.9 Strategic Industries – Railway Operations [cont.]

To deliver TDM service through a packet network, the same or better

synchronization must be achieved. In the example below, synchronous
ethernet is being used to achieve frequency synchronization.

5 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Synchronous ethernet is used to achieve frequency synchronization and to allow the benefits of an Ethernet
network infrastructure to be realized without any change to the existing TDM network applications. GSM-R is used
as a secure platform for voice and data communication between railway operational staff.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 20
 2 — Network Synchronization Types

5 — 1 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 21
2 — Network Synchronization Types
2.1 Timing/Synchronization

The 7705 SAR has sophisticated synchronization functionality to operate

in traditional TDM as well as packet networks:

Physical-Layer
 External BITS clock
 Line reference
 Local Stratum 3 holdover/free run
 Synchronous Ethernet (ITU G.826)

Packet-Based
 Adaptive Clock Recovery (ACR)
 IEEE 1588v2 slave

7750 SR synchronization timing:

 BITS port

5 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 22
 2 — Network Synchronization Types
2.2 Network timing and synchronization

Synchronization is as basic to network operation as power and grounding

Primary
An all-packet infrastructure requires special consideration and capabilities Reference
Central Clock
Access Aggregation Point Office
PDH/
T1/E1 SONET SONET SDH
TDM Network Network

External L2 or
Synchronization L3 PSN
Sync and Timing

Sync and Timing

Line
Synchronization PDH, SDH,
NTR, I-frame

Synchronization Options
Timing over Packet L2 or L3 PSN
Adaptive Clock Recovery
(Adaptive Clock PRC
Recovery, IEEE 1588v2)

External Synchronization
Constant rate Packet flow
Line Synchronization
Client

Synchronous Ethernet

IEEE 1588v2
Synchronous Synchronous
Ethernet Ethernet

5 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

The 7705 SAR supports external reference timing, line timing and adaptive timing in R1.0.
The adaptive timing is fully capable of offering end-to-end synchronisation. The
IEEE1588v2 standard defines a method to minimize the effects of delay and delay
variation (jitter). This is accomplished by a combination of built-in platform architectural
features and also powerful QoS mechanisms to minimize the delay experienced by
synchronization traffic. The SyncE feature is a hardware level synchronization which
happens at level 1 similar to SONET/SDH timing mechanisms implemented today. These
are a cornerstone of the design of the 7705 SAR. A built-in Stratum-3 clock is available in
the control module to assist in sync maintenance.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 23
2 — Network Synchronization Types
2.3 Synchronous Networks

Proper synchronization is essential for wireless carriers to ensure smooth

call hand-off between base stations

When a packet switched network is used to deliver traffic in a
synchronized network, the synchronization chain is broken so the timing
has to be recovered

Primary Reference Clock (PRC)

Packet
Switched
BSC
SAR Network
SR
(IP/MPLS)

5 — 1 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 24
 2 — Network Synchronization Types
2.4 Timing Domains

One misconception for maintaining network synch in large networks is

that the same clocking source used at the BSC/RNC must be the timing
source at the BTS/Node B
Multiple clocking sources may be required to maintain clocking quality
and to maintain end-to-end synchronization

In this case, each 7705 at a cell site within a local domain derives a clock from
a strategically placed central PW source

The timing domains are chosen such that they are manageable in size, each
deriving a clock from a different source
Timing Domain 2

(PRC)

Timing Domain 1 (PRC)

5 — 1 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Distributed Clocking Sources

In general, the amount of noise introduced by the network increases with the number of network elements
between a PRC master and the client device. Therefore it is always good to minimize the number of network
hops between the master and the client. This may be achieved by distributing the PRC around the network, or by
the use of strategically placed boundary clocks to terminate the timing fow, and re-generate for the next
network segment. For example, in it is better to place a boundary clock after 5 hops than to attempt to span the
entire 10 hop network.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 25
 2 — Network Synchronization Types
2.5 Network Synchronization Options

Synchronization architecture depends on the option selected for the

deployment:

BITS: Using a GPS clocking module co-located at the cell site

Line: Using a T1/E1 channel available at the cell site either via a GPS based
CDMA basestation or a collocated PDH/SDH/SONET backhaul network

Synchronous Ethernet (SyncE)

Adaptive Clock Recovery (ACR): Using clock propagation from Core network
through RNC-7750-7705 to Node B

ACR

7710SR SyncE

BITS

7750SR
7450ESS
7705 SAR
Line MTSO

5 — 1 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Distribution of clocking within traditional SDH/SONET networks has been defined for two applications.
Synchronization reference distribution and traffic transport. Each application has its own performance target
which is expressed in defined limits to accumulated jitter and wander. The jitter is fairly easy to remove but the
wander tends to accumulate and becomes the more important limit to monitor. In addition, mobile operators are
more concerned with the 50 ppb accuracy of the intended frequency reference.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 26
 2 — Network Synchronization Types
2.6 BITS: External Synchronization

One deployment example is to use equipment based on GPS clocking

facilities to generate the clocking necessary for the platforms
Signals from GPS satellites are used to correct a local oven controlled
crystal oscillator which results in a low cost frequency reference that is
comparable to that of a Cesium clock
The outputs of these GPS synch units can be fed to the external clocking
interface or a T1/E1 port on an ASAP MDA on the 7705 and used as a
reference
GPS

Primary Reference Clock (PRC)

SR

TDM Service Clock SAR Packet Switched

Network

5 — 1 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

The external clocking interface of the 7705 allows for three different clocking frequencies to be used as external
references for the system clock:
 2.048 MHz, 5 MHz, and 10 MHz
The SR and ESS platforms have a standard BITS interface that can also provide a synchronization source to the
clocks on the system

Differential methods
According to the differential methods, the difference between the service clock and the reference clock is
encoded and transmitted across the packet network. The service clock is recovered on the far end of the packet
network making use of a common reference clock

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 27
 2 — Network Synchronization Types
2.7 Line Synchronization

In PDH/SDH/SONET networks, available interfaces can be used to

transmit a PRC traceable signal between the RNC and Node B
If a PRC traceable signal is not possible through the aggregation network,
then the accessibility to one T1/E1 line signal that is PRC traceable is
sufficient to get a clock reference to the Node Bs

SR

TDM Service Clock SAR

Line
(PRC)

5 — 1 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

If a PRC traceable signal is not possible through the aggregation network, then the accessibility to one T1/E1 line
signal that is PRC traceable is sufficient to get a clock reference to the Node Bs
 On the 7705 SAR, an ASAP MDA port is configured as the Synchronization Supply Unit (SSU) reference source
 Eachadapter card can only supply a single monitored timing reference to the SSU, except on the 7705 SAR-F
which supports multiple (two) line references from the same MDA

Adaptive methods
In the adaptive methods, the timing can be recovered based on the inter-arrival time of the packets or on the
fill level of the jitter buffer. It should be highlighted that the method preserves the service timing

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 28
 2 — Network Synchronization Types
2.8 Synchronous Ethernet

Synchronous Ethernet enables the SSU to derive its clock from an

Ethernet based port as it had traditionally done with SONET/SDH ports

The physical layer Tx clock is locked to a high-quality frequency reference
clock (eventually PRC traceable clock)

The receiver at the far end locks to the physical layer clock of the Rx signal,
gaining access to a highly accurate reference
(PRC)
SyncE

SR

TDM Service Clock SAR

Note: In order for Synchronous

Ethernet to work, each node along
the path must have a Sync-E SFP

5 — 1 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Using SyncE the usually free running Ethernet physical layer clocks are synchronized to a network clock. At the
inter-working function, the primary reference clock (PRC) is used to drive the Ethernet PHY. The clock is
extracted from the PHY layer at each packet-switching node, filtered and used for system and downstream
clocking to extend the idea of synchronous networks to the Ethernet. ITU-T G.8262, describes the timing
characteristics of the Synchronous Ethernet Equipment Slave Clock (EEC). The EEC clocks are specified to
perform in a manner consistent with existing synchronous equipment slave clock in the SDH domain.

G.8262 outlines minimum requirements for timing devices used in synchronizing network equipment supporting
the Synchronous Ethernet architecture. The specification outlines requirements for clock accuracy, noise
(Jitter and Wander - transfer, tolerance and generation) transient and holdover performances.

Similar to G.813 which describes SDH Equipment Clock, the Ethernet Equipment Clock also contains two
options: EEC option 1 applies to Synchronous Ethernet equipments that are designed to inter-work with
networks optimized for the 2,048kbps hierarchy and EEC-Option 2 applies to Synchronous Ethernet equipments
that are designed to inter-work with networks optimized for the 1,544kbps hierarchy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 29
 2 — Network Synchronization Types
2.9 Synchronous-Ethernet: Requirements

What do I need for Synchronous-Ethernet?

Every node and every interface between the synch source and
destination needs to be Sync-E capable

Synch-E requirements on the 7705 SAR

SAR-8: Ethernet V2 adapter card

SAR-F: Sync-E is supported

Only SFP ports support Sync-E

Not all SFPs support Sync-E (see notes)

5 — 1 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Part # Short Description

3HE00027AA PBA GIGE SX SFP OPTICS MODULE - LC
3HE00028AA PBA GIGE LX SFP OPTICS MODULE - LC
3HE00867AA KIT GIGE EX SFP OPTICS MODULE - LC
3HE00029AA PBA GIGE ZX SFP OPTICS MODULE - LC
3HE00024AA PBA 100FX SFP OPTICS MODULE - LC
3HE00266AA KIT 100FX SFP OPTICS MODULE - SM 24km – L

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 30
 2 — Network Synchronization Types
2.10 Adaptive Clock Recovery

Adaptive Clock Recovery (ACR) uses an averaging process that negates the
effect of the packet delay variation by averaging the rate of incoming
packets of encapsulated TDM traffic
ACR is possible since the source TDM device is producing bits at a
constant rate determined by its clock
When ACR is used, the more packets sent on the cpipe, the more accurate
the ACR algorithm will be

The configurable limit for the 7705 SAR is currently 4000 packets-per-second

SR

TDM Service Clock SAR

TDM Service Clock
recovered based on
the ACR algorithm

5 — 1 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

The most economical option for ACR is to use a 7705 to source it. If redundant sources are desired, then two 7705
chassis can be used.
When ACR is used, the more packets sent on the cPipe, the more accurate the ACR algorithm will be. The
configurable limit for the current release of the 7705 is 4000 packets-per-second. That being the case, for a
single timeslot, the SAP should configure payload size to be 8 bytes. This value comes from the fact that a single
timeslot can transmit 8 KB per second, so stuffing 8 bytes per packet gives a total of 1000 pps.

CES PW starts at either a 77x0 SR or 7705. The PRC quality reference signal can come from RNC, BITS, or
reference line signal.
No more than 3 heavily loaded intermodal links between the ACR source node and the cell site’s 7705 SAR. The
CES PW is to be sized to allow 1000 packets/sec and priority NC.
No more than 80% traffic loading on any of the inter-nodal links.
APS Protection of CES origination at 7750 SR

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 31
 2 — Network Synchronization Types
2.11 ACR synchronization source clock protection

In order to protect ACR synchronization source clocks, one solution is to source

ACR from two 7705s with two different CESoPSN PW
This configuration provides ACR source protection at the head-end, including
multi-chassis redundancy

SR

TDM Service Clock

TDM Service Clock
recovered based on
SAR the ACR algorithm

5 — 1 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Note: On the receive end, the redundant sources must terminate on two different ASAP MDAs on a 7705 SAR-8 .
Alternatively, on the 7705 SAR-F available in R1.1, support for multi-sync on the same ASAP adapter is available.

Requirements for ACR:

CES PW starts at either a 77x0 SR or 7705 SAR. The PRC quality reference signal can come from RNC, BITS, or
reference line signal.
No more than 3 heavily loaded intermodal links between the ACR source node and the cell site’s 7705 SAR. The
CES PW is to be sized to allow 1000 packets/sec and priority NC.
No more than 80% traffic loading on any of the inter-nodal links.
APS Protection of CES origination at 7750 SR

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 32
 2 — Network Synchronization Types
2.12 IEEE 1588v2 Overview
1588 is a form of delivering network clock over a packetized network,
using Precision Time Protocol (PTP)

Pure IP; no service (PW) is needed for delivering the PRC

Uses UDP/IP messaging (multicast and unicast) over Ethernet

Server/Client model (Master/Slave clock)

Advantage of 1588

Lower BW requirement for delivering the Network clock
 With 7705 SAR default setting ≈ 46.5 Kbps

Network core does not need to be PTP-aware

Synchronized with nanosecond accuracy

Not susceptible to the “beating effect” that may impairs ACR
performance

5 — 1 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

7705 SAR approximates BW requirement for 1588v2:

-Announce message is (110 octets) at 1msg/2s = 440 bps
-Sync message (90 octets) at 64pk/s = 45.08 Kbps

UDP port 319 and 320

What is supported by 7705 SAR:

 7705 operates in slave-only mode.
 7705 supports Unicast Sync Negotiation mode with the GM.
 7705 supports frequency transports.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 33
 2 — Network Synchronization Types
2.13 IEEE1588v2 PTP Timing and Resiliency Model
1588v2 Ethernet
Grand CSM A
Master Master 1 Ref 1 CSM B
PTP Clock

Master 2
Nodal Clock Internal
With DPLL (Node)
Ethernet
1588v2 Timing
Grand Master 1 Ref 2 Reference
Master PTP Clock

Master 2

Each 7705 has a nodal clock implemented in redundant CSMs (Control and
Switching Module)
Each PTP clock can be configured to receive timing from 2 PTP Master clocks in
the network

Each of the 2 Master clocks has its own configuration for IP Address/packet rate/etc and
statistics/alarms/events

The Best Master Clock Algorithm (BMCA) is used by each PTP clock to select the best
Master clock available. This dynamic selection is based on data connectivity to each
master as well as clock master

Master 1 and 2 in the 2 PTP clocks can point to the same 2 masters or to a maximum of
4 different masters
The 2 PTP clocks can be simultaneously synced to a master (same or different)
and be available as hot standby references to the nodal clock

5 — 1 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

2 x PTP per SAR Node:

2 PTP instances can be the source of reference to the SSU:
 SAR-8
— 2 instances must exist on two separate Ethernet-V2 MDA.
 SAR-F
— Can only support one PTP instance.
 Automatically switches between ref1/ref2 on port, fiber or MDA failure detection.
 The two PTP instances are hot redundant.

2 x Designated master per PTP Instances:

 Automatically tries to sync with the alternate master if the current master is not available.
 User configured timeout must expire before declaring the master unavailable.
 PTP reference is disqualified if both masters are timed out/not available.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 34
 2 — Network Synchronization Types
2.14 Best Master Clock (Unicast Mode)

M1 M2

S
S
S1 S2

Each slave device sends unicast sync request to both masters

Based on information received from both masters, the slave runs the
BMC algorithm and decides which master to sync to
If the communication with the master is lost, the slave will attempt to
communicate and sync to the alternate master

5 — 1 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

The Best Master Clock Algorithm (BMCA) is defined to dynamically determine which Master to sync to. The
BMCA determines the best clock based on the content obtained from each received GM,s announce message.

Clock attributes (considered in the order given)

1. Priority1 (User configurable level 0 to 255)
2. Clock Class (6 is stratum 1 synchronized, 255 is Ssave clock)
3. Clock Accuracy (defines the accuracy of the GM clock),
4. PTP variance
5. Priority2 (User configurable level 0 to 255)
6. Grand Master’s Clock Identity
7. Distance (number of boundary clock)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 35
End of module
Synchronization Overview

5 — 1 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Synchronization — Synchronization Overview
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 5.1 Edition N/A
Section 5 — Module 1 — Page 36
Learning experience powered by
Alcatel-Lucent University

Section 6
Quality of Service
Module 1
Quality of Service
TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

6—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 1
 Blank page

6—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 2
 Module objectives

Upon completion of this module, you should be able to:

Explain the need for QoS

Discuss in detail the different steps in QoS
 Classification
 Queuing
 Scheduling
 (Re)Marking

Differences between 7750 SR and 7705 SAR

6—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Upon completion of this module, you should be able to:

 Explain the need for QoS
 Discuss in detail the different steps in QoS
 Classification
 Queuing
 Scheduling
 (Re)Marking
 Differences between 7750 SR and 7705 SAR

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 3
Module objectives [cont.]

6—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 4
 Table of Contents

1 QoS overview 7
Page
2 End-to-End Solution 10
1 QoS overview
3 Classification 7 17
1.1 QoS application example 8
4 QoS
1.2 Queuing
need on 7705 SAR 9 28
2 End-to-End Solution 10
5 SAP
2.1 Scheduling
ingress 11 46
6 (Re)Marking
2.2 Queuing at network egress 12 56
2.3 Queuing at network ingress 13
7 SAP-egress
2.4 Differences between 7705 SAR and 7750 SR
policies 14 61
2.5 Applying 7705 SAR QoS policies 15
2.6 Applying 7705 SAR QoS policies 16
3 Classification 17
3.1 Classification Overview 18
3.2 Forwarding classes 19
3.3 Access ingress classification options 20
3.4 Classification of traffic on SAP ingress 21
3.5 SAP-Ingress Policy Classification Order 22
3.6 SAP-ingress QoS Policy Creation 23
3.7 Network ingress classification options 24
3.8 Network Ingress Policy Classification Order 25
3.9 Network Ingress QoS Policy Creation 26
4 Queuing 28
4.16 —Queuing
1—5
Overview 29
4.2Quality
Queuing Buffer
of Service — Quality of ServicePool Allocation
7705 SAR — R6.0 Strategic Industries
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
30
4.3 Traffic buffering 31
4.4 Access Queue Configuration 32
4.5 Queuing Buffer Admission Control 33
4.6 Queue Mode 34
4.7 Priority-Mode Queue Operation 35
4.8 High-Priority Only or HPO 36
4.9 Queue Configuration 37
4.10 Applying a QoS Access Policy 38
4.11 Queuing: network egress 39
4.12 Queuing: network egress—default settings 40
4.13 Network Queue Configuration 41
4.14 Queuing: network ingress—application 44
5 Scheduling 46
5.1 Scheduling 47
5.2 Scheduling Types 48
5.3 Profiled scheduling 49
5.4 Expedited vs. Best-effort scheduling 50
5.5 Expedited/Best-effort profiled scheduling or 4-Priority 51
5.6 16 Priority Overview 52
5.7 16-priority CLI 53
5.10 Shaping with 16-Priority Behavior 54
5.14 Scheduling on a Network Port 55
6 (Re)Marking 56
6.1 (Re)Marking 57
6.2 (Re)Marking at SAP Egress 58
6.3 (Re)Marking at Network Egress 59
6.4 (Re)Marking at Network Egress (continued) 60
7 Differences between 7705 SAR and 7750 SR 61
7.1 Differences between 7705 SAR and 7750 SR 62
7.1 Differences between 7705 SAR and 7750 SR 63

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 5
Table of Contents [cont.]

Page

6—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 6
 1 QoS overview

6—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 7
 1 QoS overview
1.1 QoS application example

6—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

The 7705 SAR platform transports all types of traffic coming from customers to higher hierarchical aggregation
point of presence or to the MTSO (Mobile telephone Switch Office) over a PSN (Public Switched Network). This
slide shows a typical W-CDMA/GSM operator has 2G Radio(s), the BTS, 3G Radio(s), the Node-B and additional
applications generating low bandwidth traffic at the cell site.
The service needs a mechanism to distinguish between different types of traffic in order to allocate resources
with priority and utilize the bandwidth efficiently.
All customer traffic in this example from the cell site towards the aggregation site is subject to a SAP-ingress
policy, followed by a network egress policy when leaving the 7705 SAR. All returning traffic is first inspected by a
network-ingress policy and, when leaving the 7705 SAR towards the cell site, is inspected by a SAP-egress policy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 8
 1 QoS overview
1.2 QoS need on 7705 SAR

The traffic at the access point of a 7705 SAR can be of the following types:

TDM (Cpipe)

ATM (Apipe)

IP (Ipipe —VPRN)

Ethernet (Epipe—VPLS)

Frame Relay (Fpipe)

HDLC (Hpipe)

Service providers need QoS to prioritize traffic and use resources efficiently

6—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

The traffic at the access point to a 7705 SAR can be of multiple types.
The service providers need a mechanism to perform the following tasks:

Distinguish between different types of traffic in order to allocate resources with priority.

Utilize the bandwidth efficiently.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 9
 2 End-to-End Solution

6 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 10
 2 End-to-End Solution
2.1 SAP ingress

SAP Service QoS Policies SAP

Service Network IP/MPLS Network Service

Ingress Egress Network Ingress Egress

Network QoS Policies

Characteristics of a SAP-ingress QoS policy

Defines traffic queues: type, en-queuing and de-queuing parameters, mode,
and so on.
Assigns forwarding classes to queues
Maps traffic to a forwarding class based on user-defined match criteria and
assigns in or out-of-profile status to the packets.
Gets applied to SAPs

6 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

At the service access point (SAP) ingress to the 7705 SAR, traffic can be classified into one of eight forwarding
classes (FC) and mapped to a queue. Traffic classification is achieved with ingress QoS policy match criteria.
For each of the eight forwarding classes, a queue for the following four types of traffic can be defined:
1. unicast
2. multicast
3. broadcast
4. unknown traffic

This means that a total of 32 queues are possible for a SAP-ingress policy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 11
 2 End-to-End Solution
2.2 Queuing at network egress

SAP Service QoS Policies SAP

Service Network IP/MPLS Network Service

Ingress Egress Network Ingress Egress

Network QoS Policies

Characteristics of a network-queue QoS policy

Each network egress port supports a unicast and multipoint queue for each of
the 8 internal forwarding classes; queues are created automatically when a
port is configured as a network port. Network queue policy defines the
mapping of forwarding classes to the queues.
Queue parameters are defined in a network-queue QoS policy; on network
egress, the policy is applied to an entire port.

6 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This slide describes the characteristics of a network-queue QoS policy.

The characteristics of a network QoS policy are as follows:

Marks EXP or dot1p according to the FC of the traffic.

The marking will be used by the Network Ingress of the PE on the other side of the IP/MPLS Network to classify
the traffic.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 12
 2 End-to-End Solution
2.3 Queuing at network ingress

SAP Service QoS Policies SAP

Service Network IP/MPLS Network Service

Ingress Egress Network Ingress Egress

Network QoS Policies

Network QoS policy

The network QoS policy defines the mapping of EXP bits to one of the router
forwarding classes.

Network-queue QoS policy

The network-queue QoS policy specifies the queue to host the traffic of one or
more forwarding classes.

6 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This slide describes the network QoS and network-queue QoS policies.
Network ingress queues are created automatically when a port is placed in network mode. The queue parameters
are defined in a network-queue QoS policy. On ingress, the policy is applied at the MDA level to all network
ingress ports on that MDA.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 13
 2 End-to-End Solution
2.4 SAP-egress policies

SAP Service QoS Policies SAP

Service Network IP/MPLS Network Service

Ingress Egress Network Ingress Egress

Network QoS Policies

SAP-egress QoS policy mapping definition

A SAP-egress QoS policy defines the forwarding class to output queue mapping,
as well as the in- and out-of-profile marking to high/low priority mapping.

6 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

A SAP-egress QoS policy defines the following aspects:

•forwarding class to output queue mapping
•in- and out-of-profile marking to high/low priority mapping

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 14
 2 End-to-End Solution
2.5 Applying 7705 SAR QoS policies

SAP-ingress policy
Network-queue policy SAP-egress policy

Ing. MDA Egr. MDA Ing. MDA Egr. MDA

port port port

port

SAP SAP
i/f i/f

Network policy

Customer traffic

6 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This slides gives an overview on where to apply all the policies.

•The SAP-ingress and SAP-egress are applied in the SAP context within the service; one policy per SAP per
direction.
•The network policy is applied on a port configured as network and applied to an interface.
•The network-queue policy is applied to the port for traffic that leaves the router, and applied to the MDA for the
traffic that enters the router.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 15
 2 End-to-End Solution
2.6 Applying 7705 SAR QoS policies

Ing. MDA Egr. MDA

FABRIC
Queue 1 Queue 8

Queue 2 Queue 7
Ingress Egress

Queue 7 Queue 2

Queue 8 Queue 1

1. Classify 3. Schedule 5. Classify 7. Schedule

2. Queue 4. (Re)Mark 6. Queue 8. (Re)Mark

6 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This slides gives an overview on the different processes that go on in a 7705 SAR from ingress to egress.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 16
 3 Classification

6 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 17
3 Classification
3.1 Classification Overview

SAP Service QoS Policies SAP

Service Network IP/MPLS Network Service

Ingress Egress Network Ingress Egress

Network QoS Policies

SAP-ingress QoS policy characteristics

In a SAP-ingress QoS policy traffic is mapped to a forwarding class based on
user-defined criteria and assigns in- or out-of-profile status to the packets.

6 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 18
 3 Classification
3.2 Forwarding classes

FC FC name Class type Notes

NC Network control Real time For network control traffic.
H1 High-1 Real time For delay/jitter sensitive data.
EF Expedited Real time For delay/jitter sensitive data.
H2 High-2 Real time For delay/jitter sensitive data.
L1 Low-1 NRT – Assured For assured traffic
AF Assured NRT – Assured For assured traffic
L2 Low-2 NRT – Best effort For BE traffic.
BE Best Effort NRT – Best effort For BE traffic.

6 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

The Alcatel-Lucent 7705 SAR uses 8 forwarding classes: NC, H1, EF, H2 , L1, AF, L2 and BE.
The table provided on the slide describes the forwarding classes, and gives you an idea of the type of
traffic that is mapped to each forwarding class. However, the information is based on the best
practices. The QoS designers has the flexibility to define their own rules of classification and
scheduling.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 19
3 Classification
3.3 Access ingress classification options

DSCP
This option supports the mapping of ingress traffic (64 different service
options) to up to 8 internal forwarding classes, and is supported for up to the
double tagged Ethernet frames (qinq).

Ethernet Priority bits (dot1p)

This option supports the mapping of ingress traffic to up to 8 internal
forwarding classes.

6 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 20
 3 Classification
3.4 Classification of traffic on SAP ingress

Network Control <NC>

SAP High Priority 1 <H1>
Expedited Forwarding <EF>
Packet headers High Priority 2 <H2>
Low Priority 1 <L1>
Assured Forwarding <AF>
Low Priority 2 <L2>
Best Effort <BE>

DATA

The classification search is stopped when a match is made.

6 — 1 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

As the traffic enters the ingress forwarding complex, datagrams are classified into one of several
forwarding classes, as determined by SAP ingress QoS policies. The mapping of traffic to forwarding
classes is based on the multi-field (MF) classification rules.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 21
 3 Classification
3.5 SAP-Ingress Policy Classification Order

The classification rule order is as follows:

1. DSCP bits (IP Header)
2. Dot1p bits (Ethernet Header)
3. Default FC and priority

*A:SAR8_210>config>qos>sap-ingress#
[no] default-fc - Configure default forwarding class for this policy
[no] default-priori* - Configure default priority for this policy
[no] description - Description for this policy
[no] dot1p - Specify 802.1 priority mappings
[no] dscp - Specify DSCP mappings
[no] fc + Configure forwarding-class to queue mappings
[no] queue + Configure a queue
[no] scope - Specify scope of the policy

Note: Priority will be explained in the next section.

6 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

There are several options to classify traffic on a SAP-Ingress policy, and in this slide the order is displayed.

1. DSCP bits (IP Header)

2. Dot1p bits (Ethernet Header)
3. Default FC and priority

If traffic matches the DSCP bit entry, then it will be classified as such. If there is no match for the DSCP entry, or
if there is no DSCP match criteria on the ingress policy, then it will continue to match the Dot1p bit. If there is no
match for the Dot1p entry, then it will go to the default FC. If the default-fc is not changed (left as default in the
config) it will go to forwarding-class “be”:

*A:SAR8_210>config>qos>sap-ingress# info detail

----------------------------------------------
description "Default SAP ingress QoS policy."
scope template
queue 1 priority-mode auto-expedite create
adaptation-rule pir closest cir closest
rate max cir 0
mbs default
cbs default
high-prio-only default
slope-policy "default" Copyright © 2014 Alcatel-Lucent. All Rights Reserved.
exit TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 22
default-fc "be"
 3 Classification
3.6 SAP-ingress QoS Policy Creation

Classification in a SAP-Ingress Policy:

*A:SAR8_210>config>qos# sap-ingress <policy-id>
create
1. Create the SAP-Ingress Policy. Keep
<policy-id>
<create>
: [1..65535]
: keyword - mandatory while
in mind that sap-ingress 1, is the
creating an entry. default policy and cannot be
modified.
*A:SAR8_210>config>qos# sap-ingress 30 create

*A:SAR8_210>config>qos>sap-ingress$ fc <fc-name>
[create]

<fc> : <class> be|l2|af|l1|h2|ef|h1|nc 2. Create the forwarding class desired.

<create> : keyword - mandatory while creating an
entry.

*A:SAR8_210>config>qos>sap-ingress$ fc af create

*A:SAR8_210>config>qos>sap-ingress# dscp
- dscp <dscp-name> [fc <fc>] [priority {low|high}]

*A:SAR8_210>config>qos>sap-ingress# dot1p
- dot1p <dot1p-priority> [fc <fc>] [priority
{low|high}] 3. Match traffic towards forwarding
<dot1p-priority> : [0..7]
<fc> : <class> be|l2|af|l1|h2|ef|h1|nc class and set priority.
*A:SAR8_210>config>qos>sap-ingress$ dscp af21 fc af
priority high

6 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Throughout the module, the configuration and function of QoS policies will be explained from an end-to-end
perspective. The first configuration example observe is classification at a SAP-Ingress policy. In order to have a
fully operational SAP-Ingress policy, more components will need to be added which will be discussed in the
sections to come. This portion of the SAP-Ingress Policy configuration only covers classification of traffic.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 23
3 Classification
3.7 Network ingress classification options

DSCP
This option supports the mapping of ingress traffic (64 different service
options) to up to 8 internal forwarding classes, and is supported for up to the
double tagged Ethernet frames (qinq).

EXP-bits
This option makes use of a 3 bit field in the MPLS header, namely, the MPLS
experimental bits (EXP) field. This field will dictate the QoS treatment (per-
hop behavior) that a node will give to a packet. Typically the information
encoded in the IP DSCP can also be carried in the EXP bits.

6 — 1 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 24
 3 Classification
3.8 Network Ingress Policy Classification Order

The classification rule order is as follows:

1. EXP bits (MPLS packets)
2. DSCP (IP-packets)
3. Default FC and priority

*A:SAR8_210>config>qos>network$ ingress
- ingress

default-action - Specify default forwarding class and profile marking

[no] dscp - Configure DSCP mappings
[no] lsp-exp - Configure LSP-EXP mappings

Note: Priority will be explained in the next section.

6 — 1 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

There are several options to classify traffic on a SAP-Ingress policy, and in this slide the order is displayed.

1. EXP bits (MPLS packets)

2. DSCP (IP-packets)
3. Default FC and priority

If traffic matches the EXP-bit entry, then it will be classified as such. If there is no match for the EXP-bit entry,
or if there is no EXP-bit match criteria on the ingress policy, then it will continue to match the DSCP bit. If there
is no match for the DSCP entry, then it will go to the default FC. If the default-fc is not changed (left as default
in the config) it will go to forwarding-class “be”:

*A:SAR8_210>config>qos>network>ingress# info detail

----------------------------------------------
default-action fc be profile out
dscp be fc be profile out
dscp ef fc ef profile in
dscp cs1 fc l2 profile in
dscp nc1 fc h1 profile in
dscp nc2 fc nc profile in
dscp af11 fc af profile in
dscp af12 fc af profile out
dscp af13 fc af profile out
Copyright © 2014 Alcatel-Lucent. All Rights Reserved.
dscp af21 fc l1 profile in TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 25
dscp af22 fc l1 profile out
 3 Classification
3.9 Network Ingress QoS Policy Creation

Classification in a Network Ingress

Policy:
*A:SAR8_210>config>qos#
- network <network-policy-id> [create] [network-
policy-type {ip-interface|ring|default}]
<network-policy-id> : [1..65535]
<create> : keyword - mandatory while
1. Create the network policy. Keep in
creating an entry. mind that network 1, is the
default policy and cannot be
*A:SAR8_210>config>qos# network 2 create modified.

*A:SAR8_210>config>qos>network>ingress 2. Go under the ingress context.

*A:SAR8_210>config>qos>network>ingress# lsp-exp
- lsp-exp <lsp-exp-value> fc <fc-name> profile
{in|out}
<lsp-exp-value> : [0..7]
3. Select the classification option, in
<fc-name> : be|l2|af|l1|h2|ef|h1|nc this example EXP-bit. Select the
<in|out>
marking to be done
: keywords - specify type of parameter (ie. 0), and classify it
as be traffic and out of profile.
*A:SAR8_210>config>qos>network>ingress# lsp-exp 0 fc
be profile out

*A:SAR8_210>config>qos>network>ingress#
- default-action fc <fc-name> profile {in|out}
4. Default action is also configurable.
*A:SAR8_210>config>qos>network>ingress# info detail In the example, unclassified traffic
----------------------------------------------
default-action fc be profile out will be be and out of profile.

6 — 1 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Throughout the module, the configuration and function of QoS policies will be explained from an end-to-end
perspective. The first configuration example observe is classification at a SAP-Ingress policy. In order to have a
fully operational SAP-Ingress policy, more components will need to be added which will be discussed in the
sections to come. This portion of the SAP-Ingress Policy configuration only covers classification of traffic.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 26
 Knowledge check

Answer the following questions:

a) How many forwarding classes are available for classification?

b) Can there be multiple fields specified to classify traffic in one policy?
c) If traffic does not match any criteria, to what forwarding class does a
QoS policy map the traffic?

6 — 1 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) 8
b) Yes
c) The default forwarding class is: BE

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 27
 4 Queuing

6 — 1 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 28
 4 Queuing
4.1 Queuing Overview

SAP Service QoS Policies SAP

Service Network IP/MPLS Network Service

Ingress Egress Network Ingress Egress

Queuing Queuing

Queuing Overview
Once traffic ingresses a SAP, and it has been classified by the SAP-Ingress
policy the forwarding class is respected until it egresses the router. Each
forwarding class is associated to a queue, in which different treatment will be
given to the different forwarding classes based on the network’s requirements
of the SLA. This will ensure that resources are distributed fairly.

6 — 1 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

At service ingress to the 7705 SAR, traffic can be classified into one of eight forwarding classes (FC) and mapped
to a queue. A SAP-ingress QoS policy supports 32 queues, one queue for each forwarding class:
•8 unicast queues
•8 broadcast queues
•8 multicast queues
•8 unknown queues

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 29
 4 Queuing
4.2 Queuing Buffer Pool Allocation
There are two major components when Queuing is discussed.
1. Buffer Pool Allocation
2. Buffer Admission Control

The following slides will cover on how the buffer space is divided among
queues.
Committed Burst Size (CBS)
This is a part of the overall buffer space allocated to a specific queue. This buffer space
cannot be used by other queues, even if it is not being consumed by packets at the time.
The sum of the CBS values of all the queues in a buffer pool represents the Reserved
Buffer Portion of that pool. The CBS for a given queue can be configured, or assigned a
default value by the system.

Maximum Burst Size (MBS)

This is the maximum buffer space that a queue can use. If a queue used its reserved
CBS but did not reach the MBS value, it can contend with other queues to use, only for
that moment, buffer space in the Shared Buffer Portion. Once the queue has finished
using the shared buffer space, the memory is released to other queues. The MBS for a
given queue can be configured, or assigned a default value by the system.

6 — 1 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

See next page

This slide describes the queue parameters:
•Committed Burst Size (CBS): defines the amount of buffer space reserved for use by the queue.
•Maximum Burst Size (MBS): defines the maximum size to which a queue can grow.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 30
 4 Queuing
4.3 Traffic buffering

Queues are created and use Reserved

AND/OR Shared memory
Every buffer pool has
portions of reserved and
shared buffer space
Max x 0

MBS

Queue
High
Sum of CBS
priority
only
CBS
for all queues

High-Priority-Only
Mark

Reserved
Shared Buffers Buffers

Buffer Pool

6 — 1 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Each pool of buffer space has portions of reserved and shared buffer space. The Committed Burst Size (CBS) is
buffer space that is allocated to a specific queue and cannot be used by other queues, even if it is not being
consumed by packets at the time. The sum of the CBS values of the queues in a buffer pool represents the
Reserved Buffer Portion of that pool. The Shared Buffer Portion is unreserved memory that can be used on
demand by queues who need it temporarily, and freed when not needed so that other queues can use it as well.

The Shared Buffer Portion = Total Buffer Pool – Reserved Buffer Portion

In order to guarantee buffer space for queues within a buffer pool, ensure that the sum of the CBS of the queues
created does exceed the pool size.

It is possible to create queues that comprise only reserved buffer space, only shared buffer space, or a
combination of both. Combining reserved and shared buffer spaces allows an efficient use of memory to cope
with occasional traffic bursts, while providing a guaranteed buffer space during normal conditions.

A CBS of 0 means there is no guaranteed buffer space for a queue, and all its buffer space is drawn from the
shared portion of the buffer pool.

A certain portion of queue space can be reserved exclusively for high-priority (in-profile) traffic. This is known as
the HPO (High-Priority-Only) portion, and is defined as a percentage of MBS. As long as the queue occupancy is
less than MBS*(1-HPO), low-priority traffic will still be admitted. If occupancy goes above that threshold, low-
priority traffic will be discarded.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 31
 4 Queuing
4.4 Access Queue Configuration

Queuing will be added to previous

example:
*A:SAR8_210>config>qos>sap-ingress# queue <queue-
id> [<queue-type>] [<queue-mode>] [create]

<queue-id> : [1..8] 1. Create the desired Queue. Note that

<queue-type> : expedite|best-effort|auto-
expedite - keywords the default configuration will already
<queue-mode> : priority-mode - keywords have Queue 1 created.
<create> : keyword - mandatory while
creating an entry.

*A:SAR8_210>config>qos>sap-ingress# info
----------------------------------------------
queue 2 create
exit
fc "af" create 2. In the forwarding class, ensure that
exit
queue 2 the queue is specified.
dscp af21 fc "af" priority high
----------------------------------------------

*A:SAR8_210>config>qos>sap-ingress>queue#
- cbs <size-in-kbytes>
<size-in-kbytes> : [0..131072 | default]
3. Apply the required CBS and MBS
*A:SAR8_210>config>qos>sap-ingress>queue# based on your network
- mbs <size-in-kbytes>
<size-in-kbytes> : [0..131072 | default] requirements.

6 — 1 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This portion of the SAP-Ingress Policy configuration covers how traffic is mapped to a specific queue via the
forwarding class context in the SAP-Ingress policy. The CBS and MBS configuration within a queue are also
demonstrated.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 32
 4 Queuing
4.5 Queuing Buffer Admission Control
There are two major components when Queuing is discussed.
1. Buffer Pool Allocation
2. Buffer Admission Control

Once buffer space has been divided among the queues, control will
have to be applied in order to manage the resources accordingly.
Buffer admission control deals with the acceptance of traffic into a
queue. Priority settings will be set in order to give traffic more or less
priority in order for it to enter a queue.

Committed Information Rate (CIR)

This is the minimum guaranteed service rate of a queue.

Maximum Information Rate (PIR)

This is the maximum rate at which datagrams can exit a queue.

6 — 1 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

See next page

This slide describes the queue parameters:
•Committed Information Rate (CIR): minimum guaranteed service rate of a queue.
•Maximum Information Rate (PIR): maximum rate at which datagrams can exit a queue.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 33
 4 Queuing
4.6 Queue Mode

There are two different types of queue modes:

• Profile Mode (Supported in SR-OS 7750/7450)
• Priority Mode (Supported in SR-OS 7750/7450/7705)

Profile Mode
The forwarding class is either configured as in or out of profile, meaning high or low
priority respectively. The priority settings in the classification process will be ignored, and
the profile will take precedence. When a profile setting is not present, it will be
considered “in profile”.

Priority Mode
In this mode, the priority settings in the classification process will be considered. Recall
that when you configured classification for DSCP or dot1p, at the end a priority was set.
If there was no priority, the default priority will be used.

eg. dscp af21 fc af priority high

6 — 1 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

There are two types of queue modes, but this course will focus on Priority Mode as this type is the one supported
in the SR-OS 7705. In the next slide, you will see how there is only one option when we look at the CLI.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 34
 4 Queuing
4.7 Priority-Mode Queue Operation

In priority-mode the traffic is considered to be IN or OUT of profile based

on the following criteria:
• IN Profile: rate less than or equal to CIR
• OUT Profile: rate greater than CIR

Example: Configured CIR for Queue: 15 Mbps.

Rate (Tx) Profile after Queuing

10 Mbps IN
20 Mbps OUT

Once the packet has been categorized as IN Profile (IP) or Out Of Profile (OOP),
this state will remain unaltered by any other queues in the network.

6 — 1 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Is the name suggests, Commited Information Rate, commits the rate in which traffic will be marked as IN profile
(if it is less than this configurable value) or OUT of profile if it is greater than this value. Traffic that is marked as
IN profile has a higher chance of not being discarded then OUT of profile packets.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 35
 4 Queuing
4.8 High-Priority Only or HPO

In order to further guarantee preferential treatment for HIGH or IN

profile traffic, there is the “high-priority-only” configurable under the
queue.
*A:SAR8_210>config>qos>sap-ingress>queue#
- high-prio-only <percent>
- no high-prio-only

<percent> : [0..100 | default]

As it can be noted, the HPO value is a percentage. This value is a

percentage of the MBS.

Max x 0

MBS

Queue
High
priority
only
CBS

See notes for clarification.

6 — 1 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

In order to give priority to IN Profile or HIGH Priority packets, a portion of the MBS is configured to be allocated
for High-Priority Only traffic. HPO is configured as a percentage of the MBS. Using the numbers above, the MBS
pool is divided into two sections:
• Regular MBS
• High-Priority-Only MBS

High Priority traffic will always be accepted into the Queue as long as there are available resources on the MBS.
Low Priority traffic will be accepted into the Queue as long as there is space in the Regular MBS. If the MBS is full
up to the HPO, Low Priority traffic will be discarded.

• Total MBS: 36 Mbps

• CBS: 12 Mbps
• HPO: 33%
• HPO Depth: 24
• HPO Value: 12

The Total MBS is comprised of the “Regular MBS” or HPO Depth and “HPO MBS”.

Questions:

1. If the Buffer Utilization is at 20 Mbps. What will happen to Low Priority Traffic? High Priority Traffic?
2. If the Buffer Utilization is at 30 Mbps. What will happen to Low Priority Traffic? High Priority Traffic?
3. If the Buffer Utilization is at 36Copyright
Mbps. What
© 2014will happen toAllLow
Alcatel-Lucent. Priority
Rights Traffic? High Priority Traffic?
Reserved.
TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 36
 4 Queuing
4.9 Queue Configuration

Queuing will be added to previous

example:
*A:SAR8_210>config>qos>sap-ingress# queue <queue-
id> [<queue-type>] [<queue-mode>] [create]

<queue-id> : [1..8] 1. 7705 SAR only supports the queue-

<queue-type> : expedite|best-effort|auto-
expedite - keywords mode “priority-mode”.
<queue-mode> : priority-mode - keywords
<create> : keyword - mandatory while
creating an entry.

*A:SAR8_210>config>qos>sap-ingress>queue#
- no rate
- rate <pir-rate> [cir <cir-rate>]
- rate <pir-rate>
2. The PIR and CIR are configured as in
<pir-rate>
<cir-rate>
: [1..100000000|max] Kbps
: [0..100000000|max] Kbps
the example to the left. Basically,
rate <PIR-rate> cir <CIR-rate>.
*A:SAR8_210>config>qos>sap-ingress>queue# rate max Configuring no CIR will set the cir-
cir 1000000 rate to 0, if the following is done
“rate <PIR-rate>”.

6 — 1 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This portion of the SAP-Ingress Policy configuration covers how traffic is handled once it has been assigned to a
queue. The CIR and PIR parameters will determine what happens when traffic is considerd high or low priority.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 37
4 Queuing
4.10 Applying a QoS Access Policy

*A:S220>config>service>epipe# info
----------------------------------------------
sap 1/3/1 create
ingress
qos 30
exit
exit
no shutdown
--------------------------------------------- The SAP-ingress policy is applied in the
ingress direction under the SAP and
under the service

The SAP-egress policy is applied in the

*A:S220>config>service>epipe# info egress direction under the SAP and
---------------------------------------------- under the service
sap 1/3/1 create
egress
qos 20
exit
exit
no shutdown
---------------------------------------------

6 — 1 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 38
 4 Queuing
4.11 Queuing: network egress

SAP Service QoS Policies SAP

Service Network IP/MPLS Network Service

Ingress Egress Network Ingress Egress

Network QoS Policies

Network-Queue QoS policy

• Each network egress port supports a unicast and multipoint queue for each of the 8 internal FC queues
are created automatically when a port is configured as a network port. A network queue policy defines
the mapping of FCs to the queues.
• The queue parameters are defined in a network-queue QoS policy; on network egress, the policy is
applied to the entire port.

6 — 1 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This slide describes the following network egress policies:

•Network-Queue QoS policy
•Network QoS policy

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 39
 4 Queuing
4.12 Queuing: network egress—default settings
*A:SAR8_210>config>qos# network-queue default
*A:SAR8_210>config>qos>network-queue# info detail
----------------------------------------------
description "Default network queue QoS policy."
queue 1 auto-expedite create
no avg-frame-overhead
rate 100 cir 0
adaptation-rule pir closest cir closest
mbs 5
cbs 0.10
high-prio-only 10
slope-policy "default"
exit
queue 2 auto-expedite create
no avg-frame-overhead
rate 100 cir 25
adaptation-rule pir closest cir closest
mbs 5
cbs 0.25
high-prio-only 10
slope-policy "default"
exit
< snip >
fc be create
multicast-queue 9
queue 1
exit
fc l2 create
multicast-queue 10
queue 2
exit
< snip >

6 — 1 — 40 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Full Output:

*A:SAR8_210>config>qos>network-queue# info detail

----------------------------------------------
description "Default network queue QoS policy."
queue 1 auto-expedite create
no avg-frame-overhead
rate 100 cir 0
adaptation-rule pir closest cir closest
mbs 5
cbs 0.10
high-prio-only 10
slope-policy "default"
exit
queue 2 auto-expedite create
no avg-frame-overhead
rate 100 cir 25
adaptation-rule pir closest cir closest
mbs 5
cbs 0.25
high-prio-only 10
slope-policy "default"
Copyright © 2014 Alcatel-Lucent. All Rights Reserved.
exit TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 40
queue 3 auto-expedite create
 4 Queuing
4.13 Network Queue Configuration

Below are the steps required to

*A:SAR8_210>config>qos#
configure queuing under a network
- network-queue <policy-name> [create] policy:
- no network-queue <policy-name>

<policy-name> : [32 chars max] 1. Create the network queue policy. In

<create> : keyword - mandatory while this example “mynetwqueue” is used
creating an entry.
as a name.
*A:SAR8_210>config>qos# network-queue "mynetwqueue"
create

*A:SAR8_210>config>qos>network-queue# queue
- queue <queue-id> [multipoint] [<queue-type>]
[create]

<queue-id>: [1..16]
<multipoint>: keyword - mandatory while creating a 2. Create the desired Queue. Note that
multipoint queue
<queue-type>: expedite|best-effort|auto-expedite -
the default configuration will already
keywords have Queue 1 created.
<create>: keyword - mandatory while creating an
entry.

*A:SAR8_210>config>qos>network-queue# queue 2 create

6 — 1 — 41 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This portion of the SAP-Ingress Policy configuration covers how traffic is mapped to a specific queue via the
forwarding class context in the SAP-Ingress policy. The CBS and MBS configuration within a queue are also
demonstrated.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 41
 4 Queuing
4.13 Network Queue Configuration [cont.]

*A:SAR8_210>config>qos>network-queue#
- fc <fc-name> [create]
- no fc <fc-name>

<fc-name> : <be|l2|af|l1|h2|ef|h1|nc> - keywords

<create> : keyword - mandatory while creating an 3. Create a forwarding class.
entry.

*A:SAR8_210>config>qos>network-queue# fc af create

*A:SAR8_210>config>qos>network-queue# info
----------------------------------------------
fc af create
multicast-queue 9
queue 1
4. By default queue 1 and multicast
exit queue 9 is assigned to the fc
----------------------------------------------

*A:SAR8_210>config>qos>network-queue# fc af queue 2
*A:SAR8_210>config>qos>network-queue# info
----------------------------------------------
queue 2 create
5. Assign the desired queue to the fc.
exit Note that in the example queue 2
fc af create
multicast-queue 9
was added to the forwarding class.
queue 2 Multicast queue remains as default.
exit

6 — 1 — 42 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This portion of the SAP-Ingress Policy configuration covers how traffic is mapped to a specific queue via the
forwarding class context in the SAP-Ingress policy. The CBS and MBS configuration within a queue are also
demonstrated.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 42
 4 Queuing
4.13 Network Queue Configuration [cont.]

*A:SAR8_210>config>qos>network-queue>queue#
[no] adaptation-rule - Specify the CIR and PIR
adaptation rules
[no] avg-frame-over* - Configure average frame
overhead 6. Parameters configurable under the
[no] cbs - Specify CBS
[no] high-prio-only - Specify high priority only
network-queue policy queues.
burst size
[no] mbs - Specify MBS
[no] rate - Specify rates (CIR and PIR)
[no] slope-policy - Configure the slope policy

*A:SAR8_210>config>qos>network-queue>queue# cbs
- cbs <percentage>
<percentage> : [0.00..100.00]

*A:SAR8_210>config>qos>network-queue>queue# mbs
- mbs <percentage>
<percentage> : [0.00..100.00]
7. Configure the CBS and MBS under
*A:SAR8_210>config>qos>network-queue# info
----------------------------------------------
the queue. CBS and MBS under a
queue 2 create network queue are configured using
mbs 20
cbs 5
percentages as it can be observed.
exit
fc af create
multicast-queue 9
queue 2
exit
----------------------------------------------

6 — 1 — 43 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This portion of the SAP-Ingress Policy configuration covers how traffic is mapped to a specific queue via the
forwarding class context in the SAP-Ingress policy. The CBS and MBS configuration within a queue are also
demonstrated.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 43
4 Queuing
4.14 Queuing: network ingress—application

For INGRESS, a network queue-policy is applied under the adapter context

ie. ‘configure card X mda X network ingress’:

*A:SAR8_210>config>card>mda>network>ingress#
queue-policy
- no queue-policy
- queue-policy <name>

<name> : [32 chars max]

For EGRESS, a network queue-policy is applied under the network port

context ie. ‘configure port X/X/X’:

*A:SAR8_210>config>port>ethernet>network# info detail

----------------------------------------------
queue-policy "default"
scheduler-mode profile
----------------------------------------------
*A:SAR8_210>config>port>ethernet>network#

6 — 1 — 44 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 44
 Knowledge check

Answer the following questions:

a) What does the CIR of a queue mean?

b) What does the PIR of a queue mean?
c) Is the following statement True or False?
The HPO value specifies some space of a queue dedicated for low
priority traffic only.

6 — 1 — 45 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) CIR or Committed Information Rate is the minimum guaranteed service rate of a queue.
b) PIR or Peak Information Rate is the maximum rate at which datagrams can exit a queue
c) False—the HPO value specifies some space of a queue dedicated for high priority traffic only.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 45
 5 Scheduling

6 — 1 — 46 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 46
5 Scheduling
5.1 Scheduling
• Scheduling has to do with deciding which queue to serve first. Once a
decision is made, the packet at the head of the winning queue will be
removed from it and serviced.

Ing. MDA Egr. MDA

FABRIC
Queue 1 Queue 8

Queue 2 Queue 7
Ingress Egress

Queue 7 Queue 2

Queue 8 Queue 1

1. Classify 3. Schedule 5. Classify 7. Schedule

2. Queue 4. (Re)Mark 6. Queue 8. (Re)Mark

6 — 1 — 47 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 47
Scheduling is about deciding which queue to serve first. Once a decision has been made, the packet at the head
of the winning queue is removed from the queue and forwarded.
This slide describes the types of scheduling:
•Profiled scheduling
•Expedited vs. best-effort scheduling
•Expedited/best-effort profiled scheduling

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 48
 5 Scheduling
5.3 Profiled scheduling

Ensures that traffic up to the traffic contract (CIR) from

CIR
all the queues is serviced prior to traffic exceeding the S
traffic contract. T
In-Prof R
CoS-8 I
C
T
CIR traffic from any queue is scheduled as “In-Profile”. CIR PIR
P
R
CoS-6 Out-Prof I
O
Traffic over CIR but less than PIR is scheduled as R
“Out-of-Profile”. CIR PIR I
T
Y
CoS-1
Each packet can go to In- or Out-of-Profile depending
Per Dest MDA
on the rate of the queue. Per F.C
priority based
Queuing
Scheduling

The Profiled scheduling is also known as Rate-based scheduling

6 — 1 — 49 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Default (profiled) :This is rate based scheduling, which uses the CIR and PIR to select the queue to serve.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 49
 5 Scheduling
5.4 Expedited vs. Best-effort scheduling

By default, two levels of priorities based on FCs (CoS):

CIR
•Expedited scheduler: NC, H1, EF, H2 S
•Best-effort scheduler: L1, AF, L2, BE T
EX R
CoS-8 I
C
The CoS queues marked with Expedited priority are T
CIR PIR
scheduled exhaustively before the Best-effort queues.
P
R
CoS-6 BE I
There is a round robin within Expedited queues and O
R
within Best-effort queues. CIR PIR I
T
Y
If a packet arrives to any of the Expedited Queues, the CoS-1
scheduler finishes servicing the current packet, and Per Dest MDA
Per F.C
then returns to the Expedited queues immediately. priority based
Queuing
Scheduling

6 — 1 — 50 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This slide describes the Expedited vs. Best-effort scheduling, which is a qeue type base scheduling.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 50
 5 Scheduling
5.5 Expedited/Best-effort profiled scheduling or 4-Priority

The CoS Queues marked with Expedited priority

In-profile are scheduled exhaustively before the other
packets
CIR
S
EX IN T
The CoS queues marked with Best-effort In-profile are R
CoS-8 I
scheduled exhaustively before the other packets which C
are out-of-profile. BE IN T
CIR PIR
P
EX R
There is a round robin within Expedited queues CoS-6 I
OUT
In-profile and Out-of-profile, and Best-effort queues O
In-profile and Out-of-profile. R
CIR PIR BE I
OUT T
Y
If a packet of higher priority arrives, the scheduler CoS-1
finishes servicing the current packet, and then returns Per Dest MDA
Per F.C
to service the higher priority packet immediately. priority based
Queuing
Scheduling

6 — 1 — 51 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This slide describes the Expedited/Best-effort profiled scheduling, which combines the Profiled scheduling and
the Expedited vs. Best-effort scheduling.

Essentially traffic is serviced in the following priority, per 4-priority:

• CoS-8 to CoS-5 Expedited in-profile

• CoS-4 to CoS-1 Best Effort in-profile
• CoS-8 to CoS-5 Expedited out-of-profile
• CoS-4 to CoS-1 Best Effort out-of-profile

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 51
5 Scheduling
5.6 16 Priority Overview

hi_prio
With 16-priority scheduling, sap CoS-8
nc S
MaxDP

(CoS - 8) queue 8 has h1

. .
CoS-7
MinTMaxT
4-Priority
Exp.In-Prof
T
R
aggregate
for unshaped SAPs
I
highest priority, then queue .
be
.
CoS-1
MaxDP

MinTMaxT
Scheduling
Strict Priority among
C
T

7 (CoS - 7) , and so on until low_prio priorities:

• Exp.in-profile
BE.In-Prof

queue 1 (CoS - 1) is reached sap CoS-8 • BE.in-profile

P
R
nc
I 4-priority
h1 • Exp.out-of-profile Exp.Out-Prof
which has the least priority. . .
CoS-7
• BE.out-of-profile
O
R
I
scheduled
. . Un-Shaped SAPs S
T
T
be R
CoS-1 BE.Out-Prof Y
I
In-Prof C

The above scheduling is sap

nc
CoS-8
T

performed based on the h1

. .
CoS-7 CoS-8
in-prof
S
T
per
SAP Out-Prof
P
R
R I
highest queue having higher .
be
. 16 priority I
C 16-priority
O

scheduling CoS-1
preference for IN profile CoS-1
CoS Q-8 to CoS Q-1 in-prof
T
scheduled
conforming
packets (SAP conforming sap
nc
CoS-8
hi_prio
then
CoS-8
Out-Prof
P
R
Shaped or
O Un-Shaped SAPs
I
CoS Q-8 to CoS Q-1
traffic), and then on the h1
. .
CoS-7
MaxDP

MinTMaxT
non-conforming R
I per
CoS-1
OUT of profile packets (SAP .
be
. MaxDP Out-Prof
T
Y
SAP
CoS-1
uncoforming traffic). eth
saps
MinTMaxT
Per SAP 2nd Tier
Aggr. Shaper
Classification Per Sap Buffer Mgmt via Queue Layer Aggregate Layer
Per Forwarding WRED or Tail Scheduling Scheduling
Class Queuing Drop for
Hi and Low Prio

6 — 1 — 52 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 52
5 Scheduling
5.7 16-priority CLI

By default, 4-priority scheduling mode is used

*A:SAR8_210>config>service>ies>if>sap# info detail
----------------------------------------------
ingress
qos 1
scheduler-mode 4-priority
no agg-rate-limit
exit
egress
qos 1
scheduler-mode 4-priority
no agg-rate-limit
exit

Enabling 16-priority:

Ingress: *A:SAR8_210>config>service>ies>if>sap>ingress#
- scheduler-mode {4-priority|16-priority}

Egress:
*A:SAR8_210>config>service>ies>if>sap>egress#
- scheduler-mode {4-priority|16-priority}

6 — 1 — 53 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 53
5 Scheduling
5.10 Shaping with 16-Priority Behavior

• Shaping on a per SAP basis introduces the following parameters.

• agg-rate-limit
• cir-rate
*A:SAR8_210>config>service>ies>if>sap>egress#
- agg-rate-limit <agg-rate> [cir <cir-rate>]

<agg-rate> : [1..10000000|max] Kbps -

default max
<cir-rate> : [0..10000000|max] Kbps -
default 0 Kbps

•If the aggregate rate limit is reached and the aggregate CIR is less
than or equal to the aggregate rate limit, then the per-SAP aggregate
shaper throttles the traffic at the configured aggregate rate while
preserving the 16-priority scheduling priorities that are used on the
shaped SAPs.
•If the aggregate rate limit is reached and the aggregate CIR is greater
than the aggregate rate limit, then the per-SAP aggregate shaper
throttles the traffic at the configured aggregate CIR rate.

6 — 1 — 54 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 54
5 Scheduling
5.14 Scheduling on a Network Port

• Configuration is done at the port level, ‘configure port x/x/x’. Three

options profile, 4-priority, 16-priority. See notes for a quick recap.

*A:SAR8_210>config>port>ethernet>network# scheduler-mode
- scheduler-mode {profile|4-priority|16-priority}

<scheduler-mode>: profile - Basic in/out profile scheduling

4-priority - Expedited/best-effort plus in/out scheduling
16-priority - Straight Priority CIR/EIR scheduling

• There is no configurable aggregate rate under a network port, as was

done in the access ports. In other words, there is no 2nd tier scheduling
on a per-port basis.

6 — 1 — 55 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 55
 6 (Re)Marking

6 — 1 — 56 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 56
 6 (Re)Marking
6.1 (Re)Marking
• (Re)Marking is when the FC and the state of the packet is either added
(marking) or altered (remarking) to satisfy the demands of the network
design. In the 7705 (re)marking will only be done at egress.

Ing. MDA Egr. MDA

FABRIC
Queue 1 Queue 8

Queue 2 Queue 7
Ingress Egress

Queue 7 Queue 2

Queue 8 Queue 1

1. Classify 3. Schedule 5. Classify 7. Schedule

2. Queue 4. (Re)Mark 6. Queue 8. (Re)Mark

6 — 1 — 57 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

1. If traffic is originating from this 7705 SAR (packet leaving Fabric), it will be marked at the egress policy.
2. If traffic is transitting this network, network design can choose to leave trafic as is (no marking) or remark it to
meet its demands.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 57
6 (Re)Marking
6.2 (Re)Marking at SAP Egress

Different (re)marking options can be observed under the ‘configure qos

sap-egress X’ context.
1. First you select the forwarding class to be (re)marked.
*A:SAR8_210>config>qos>sap-egress# fc af

2. Then you select the option to (re)mark. Ie. dot1p, dscp

*A:SAR8_210>config>qos>sap-egress>fc#
[no] dot1p - Specify the dot1p value to be used
[no] dscp - Specify DSCP mappings
[no] queue - Specify the queue to forward this FC traffic

3. Lastly, the value used to (re)mark is chosen.

*A:SAR8_210>config>qos>sap-egress# info
----------------------------------------------
fc af create
dot1p 5
dscp af22
exit
----------------------------------------------

6 — 1 — 58 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 58
6 (Re)Marking
6.3 (Re)Marking at Network Egress

Different (re)marking options can be observed under the ‘configure qos

network X egress’ context.
1. First you select the forwarding class to be (re)marked.
*A:SAR8_210>config>qos>network>egress# fc af

2. Then you select the option to (re)mark. Ie. dot1p, dscp, EXP-bit
*A:SAR8_210>config>qos>network>egress>fc#
[no] dot1p - Specify Dot1p profile mapping
[no] dot1p-in-profi* - Specify Dot1p in profile mapping
[no] dot1p-out-prof* - Specify Dot1p out profile mapping
[no] dscp-in-profile - Specify DSCP in profile mapping
[no] dscp-out-profi* - Specify DSCP out profile mapping
[no] lsp-exp-in-pro* - Specify LSP-EXP in profile mapping
[no] lsp-exp-out-pr* - Specify LSP-EXP out profile mapping

6 — 1 — 59 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 59
6 (Re)Marking
6.4 (Re)Marking at Network Egress (continued)

3. Lastly, the value used to (re)mark is chosen.

*A:SAR8_210>config>qos>network>egress>fc# info
----------------------------------------------
dscp-in-profile af12
dscp-out-profile af22
lsp-exp-in-profile 6
lsp-exp-out-profile 5
dot1p-in-profile 5
dot1p-out-profile 6
----------------------------------------------

Disclaimer: The values chosen are simply to demonstrate CLI

configuration. In no way are they recommended values for a real
network. Each network’s qos policies are specifically tailored by a
network design team depending on the type of traffic and SLAs.

6 — 1 — 60 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 60
 7 Differences between 7705 SAR and 7750 SR

6 — 1 — 61 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 61
 7 Differences between 7705 SAR and 7750 SR
7.1 Differences between 7705 SAR and 7750 SR

Hardware set
The 7705 SAR utilizes a different hardware set from the 7750 SR.

QoS features
The 7705 SAR supports only a subset of the 7750 SR QoS features.

Queue mode support

The 7705 SAR supports priority-mode only, and not profile-mode queues.

6 — 1 — 62 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

This slide lists the major differences between the 7705 SAR and the 7750 SR.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 62
End of module
Quality of Service

6 — 1 — 63 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Quality of Service — Quality of Service
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 6.1 Edition N/A
Section 6 — Module 1 — Page 63
Learning experience powered by
Alcatel-Lucent University

Section 7
HA and Resiliency
Module 1
Resiliency and High Availibility
TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

7—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 1
 Blank page

7—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 2
Module objectives

Upon completion of this module, you should be able to:

Describe network resilience and high-availability

List network resilience and high-availability concepts and techniques:
 Multi-chassis synchronization
 Multi-chassis Line Aggregation Group
 Virtual Router Redundancy Protocol
 G.8032 Ethernet Ring Protection Switching
 Pseudowire with MC-LAG for VLL services

7—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 3
Module objectives [cont.]

7—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 4
 Table of Contents

1 Introduction to resilience and high availability 7

Page
2 Multi-chassis synchronization 13
1 Introduction to resilience
3 Multi-chassis LAG and high availability 7 18
1.1 Your network under adverse conditions 8
4 Carrier
1.2 Virtual Router
grade networkRedundancy
availability Protocol 9 23
1.3 Cost of network down time 10
5 Layer
1.4 Pseudowire with MC-LAG
2 service delivery networks for VLL 11 30
6 G.8032 Ethernet Ring Protection
2 Multi-chassis synchronization 13 38
2.1 Multi-chassis synchronization overview 14
2.2 Synchronization information 15
2.3 Multi-chassis synchronization database operations 16
3 Multi-chassis LAG 18
3.1 MC-LAG overview 19
3.2 MC-LAG in the network 20
3.3 MC-LAG benefits 21
4 Virtual Router Redundancy Protocol 23
4.1 Failure prevention 24
4.2 Router redundancy 25
4.3 VRRP virtual router 26
4.4 Concepts and components 27
4.5 How it works 28
5 Pseudowire with MC-LAG for VLL 30
5.1 Pseudowire redundancy 31
5.27 —Pseudowire
1—5
redundancy and MC-LAG 32
5.3HA VLL service
and Resiliency — Resiliencyendpoints
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
and High Availibility
7705 SAR — R6.0 Strategic Industries
33
5.4 Pseudowire active path 34
5.5 Pseudowire active path—access link failure 35
5.6 Pseudowire active path—SDP failure 36
6 G.8032 Ethernet Ring Protection 38
6.1 Ethernet ring overview 39
6.2 Description of ring automatic protection switching 40
6.3 Ring protection mechanism 41

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 5
Table of Contents [cont.]

7—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 6
 1 Introduction to resilience and high availability

7—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 7
 1 Introduction to resilience and high availability
1.1 Your network under adverse conditions

Internet

Content
in the cloud Industrial
espionage
Solar
storm

Internal IP/MPLS
threats Core

Access/ Core NEs

aggregation
NEs
Provider
Customer
edge NEs
edge
Internal
server

Recreational Flood
crackers

7—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

What is network resilience? Resilience is the ability of a network to operate and maintain an acceptable level of
service under adverse conditions. These conditions can be external or internal, as illustrated on the slide. External
adverse conditions include the following:
•large-scale natural disasters (for example, hurricanes, earthquakes, and floods)
•attacks against the network hardware, software, or protocol infrastructure by recreational crackers, industrial
espionage, terrorism, or warfare agents.

Internal adverse conditions can be

•natural faults of network components
•failures due to misconfiguration or operational errors
•unpredictably-long-delay paths either due to path length (in the case of satellite communication) or as a result of
episodic connectivity
•weak, asymmetric, and episodic connectivity of wireless channels
•high-mobility of NEs and subnetworks
•unusual but legitimate traffic load (for example, flash crowds)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 8
 1 Introduction to resilience and high availability
1.2 Carrier grade network availability

Network availability targets translated into downtime values

Network availability is measured as a percentage. Carrier grade network availability
target has been set to 99.999% (also known as five nines).

Downtime
Network
availability
Year Month Week

99.9 % 525.6 minutes 43.8 minutes 10.1 minutes

99.99 % 52.56 minutes 43.2 minutes 1.01 minute

99.999 % 5.26 minutes 25.9 seconds 6.05 seconds

There is very little time available to manually solve an existing issue. Proactive
measures must be in place.

7—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Network resilience and redundancy techniques outlined in this module are designed to ensure network high
availability, to prevent service-affecting issues, and to eliminate the downtime or reduce it to negligible amounts.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 9
 1 Introduction to resilience and high availability
1.3 Cost of network down time

Network status Quality of service

Normally degraded Acceptable service

Partially degraded Impaired service

Severely degraded Unacceptable service

Operational costs

Credibility costs

Revenue costs
Down time

7 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

A network can operate normally degraded, partially degraded or severely degraded. The state of the network
influences the quality of service, which can be acceptable, impaired or unacceptable.
Resilience ensures network reliability, redundancy and availability, and aims at eliminating the downtime or reducing
it to negligible amounts.

Down time means much more than just outage time for customers. Down time means significant costs in the
following areas:
•operational costs due to the additional support efforts
•credibility costs due to customer complaints if service level agreements (SLAs) are not respected
•revenue costs due to potential reductions in sales

A resilient carrier-grade network operates normally and provides an acceptable quality of service with little or no
down time.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 10
 1 Introduction to resilience and high availability
1.4 Layer 2 service delivery networks
Access Ethernet Aggregation MPLS Core/inter-domain Aggregation MPLS Access Ethernet
Resilience and Resilience and Resilience and Resilience and Resilience and
high-availability high-availability high-availability high-availability high-availability

PE PE PE
PE

L2 L2 L2 L2
CE MPLS MPLS MPLS CE
L2 L2 L2 L2

CE CE
PE PE
PE PE
Active/standby pseudowire Active/standby pseudowire Active/standby pseudowire
techniques for inter-domain techniques techniques: port-based or
dual-homing, square, or core full-mesh with VLAN-based for
and ring. Split-Horizon. dual-homing and ring.

Legend: Customer edge Service router Core router

7 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

You can implement resilience and high availability for Ethernet and MPLS connectivity in Layer 2 service delivery
networks by using SR-OS NEs. The SR-OS provides the most comprehensive resilience and security toolset for
Layer 2 services in the industry.

The 7705 SAR supports most of the SR-OS Layer 2 resilience and high-availability techniques described in this
module.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 11
 Knowledge check—resilience overview

Usually there is a lot of time available to solve service-affecting issues in

the network. Proactive measures are not always required.

True

False

Resilience is the ability of a network to operate and maintain an acceptable

level of service under adverse conditions. Which of the following conditions
are internal? Select all that apply.

natural disasters

failures resulting from operational errors

attacks by recreational crackers

high-mobility of NEs and subnetworks

A normally degraded network status is associated with impaired service.

True

False

7 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Usually there is a lot of time available to solve service-affecting issues in the network. Proactive measures are not
always required.
•True
•False

Resilience is the ability of a network to operate and maintain an acceptable level of service under adverse conditions.
Which of the following conditions are internal? Select all that apply. .
•natural disasters
•failures resulting from operational errors

•attacks by recreational crackers
•high-mobility of NEs and subnetworks

A normally degraded network status is associated with impaired service.

•True
•False

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 12
 2 Multi-chassis synchronization

7 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This section provides an overview of the multi-chassis synchronization feature.

The MCS is supported on specific 7705 SAR platforms, equipped with specific adapter cards. For details, see the
7705 SAR OS Software Release Notice for your release.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 13
 2 Multi-chassis synchronization
2.1 Multi-chassis synchronization overview +

7705 SAR-18
IP/MPLS network
DSLAM

7705 SAR-18

Multi-chassis synchronization (MCS)

Alcatel-Lucent proprietary mechanism that synchronizes dynamic state information
between redundant peer NEs. This NE state synchronization provides a solution for
redundant access in dual-homing configurations, in combination with subscriber
management and multi-chassis LAG. The peer NEs nodes need to run at the same
system times (NTP/SNTP), and to have the same local service configuration .

7 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

From an SR-OS perspective, the multi-chassis synchronization is a redundancy feature that synchronizes
configuration information between two peer NEs. Of course, you need to configure the multi-chassis
synchronization on both NEs. The following considerations apply:
•The MCS can be used only between two NEs of the same type and model; for example, a 7705 SAR-18 can be
synchronized only with another 7705 SAR-18.
• An NE can have up to four peers.
• The synchronization takes place between two peer NEs.
• In an MCS configuration, one of the peer NEs is active and the other NE is in standby mode. The NEs switch
between the active and standby roles, as required
•When a database object is instantiated on the active peer NE, the same object is instantiated on the standby
peer NE.
•The SR-OS NEs perform the synchronization over a redundant TCP routed connection.
•The MCS feature is not intended to be a failover mechanism.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 14
 2 Multi-chassis synchronization
2.2 Synchronization information +

IGMP protocol information

IGMP snooping information

7705 SAR-18

MLD snooping information

DSLAM
IP/MPLS network

DHCP server information

7705 SAR-18 SRRP protocol information

Subscriber management information

Subscriber host tracking information

7 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

The MCS feature can be configured to synchronize all or part of the following information on the peer NEs:
•IGMP protocol information
•IGMP snooping information
•DHCP server information
•MLD snooping information
•SRRP protocol information
•subscriber management information
•subscriber host tracking information

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 15
The synchronization process manages the MCS distributed database, which contains the dynamic state
information created on any of the NEs by any application. The individual entries in the MCS database are paired
by peering-relation, sync-tag and application-id attributes. At any time, an entry is related to the single
redundant-pair objects and stored in a local MCS database of the respective NEs.

The MCS mechanism translates the peering-relation and sync-tag into a port and encapsulation value identifying
the object (SAP) with which an entry is associated. The application-id identifies the application that creates the
entry on one of the NEs. The application can perform three basic operations on the MCS database:
•add-operation
•local-delete
•global-delete

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 16
 Knowledge check

A multi-chassis synchronization configuration can include SR-OS NEs of

multiple types.

True

False

Only two of the following items are MCS database operations—which ones?

local-add

local-delete

global-delete

global-add

7 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

A multi-chassis synchronization configuration can include SR-OS NEs of multiple types.

•True
•False

Only two of the following items are MCS database operations—which ones?
•local-add (does not exist—derived from add-operation)
•local-delete

•global-delete

•global-add (does not exist—derived from add-operation)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 17
 3 Multi-chassis LAG

7 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This section provides an overview of the multi-chassis LAG (MC-LAG) feature.

The MC-LAG is supported on specific 7705 SAR platforms, equipped with specific adapter cards. For details, see
the 7705 SAR OS Software Release Notice for your release.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 18
 3 Multi-chassis LAG
3.1 MC-LAG overview +

P1
MC-LAG
P1 P2
7705 SAR The routers exchange
P2 MC-LAG peering
P3 information through
the MC-LAG protocol.
P4
CE
P1
MC-LAG
P2
7705 SAR

Each router has one LAG connected to the same CE NE. The routers exchange
MC-LAG control protocol information to perform active/standby selection,
ensuring that only the LAG ports of one router are active and carrying the
traffic at a time. The routers perform a switchover when they detect a failure
in the active links.

7 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

The MC-LAG is an Alcatel-Lucent Service Router Portfolio proprietary solution that provides link and NE redundancy
through the use of Ethernet LAG. The MC-LAG is implemented between a CE NE and two routers in a dual-homing
configuration. The MC-LAG protects the SAPs on a router from link failures. The MC-LAG is transparent to the CE
NE, and needs to be configured and deployed only on the routers.
The MC-LAG control protocol is an extension of the LACP protocol, with the function of exchanging information
between MC-LAG peering routers.
From the perspective of the CE, four LAG ports are connected to the service provider network. All these ports are
active, but only two are operationally up at any time. On the side of the routers, two types of configuration are
required: LAG configuration, to define the ports facing the CE device, and MC-LAG configuration, to define the MC-
LAG peer and the LACP parameters.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 19
 3 Multi-chassis LAG
3.2 MC-LAG in the network +

PE1 PE3

IP/MPLS network

PE2
CE
CE

CE
CE
IP/MPLS network

Legend: PE5 PE4

LAG

MC-LAG

7 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

The MC-LAG solution requires two regular LAGs in two PE routers. Any PE router can have multiple LAGs running
the MC-LAG protocol to another PE router, or to different PE routers. The MC-LAG peering adjacency is always
point-to-point between two PE routers, and more than one MC-LAG can appear under the same pair of peering
routers. The MC-LAG control protocol supports adjacency over IP addresses. The two PE NEs participating in the
same MC-LAG do not need to be directly connected to each other by physical links.

The protocol provides a heartbeat monitoring mechanism (keep-alive) so that each router can monitor the health
of its MC-LAG peer. This feature enhances the network resilience: if one router fails, the MC-LAG peer detects
the remote failure and switches the active role to the peer router.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 20
 3 Multi-chassis LAG
3.3 MC-LAG benefits +

Transparent to the customer

The MC-LAG is configured only in the routers. The CE NE is not aware of the
MC-LAG.

No MPLS or service support required in the CE NE

The MC-LAG uses Ethernet links to connect to the CE device, and is deployed
on the router on the access port that has the SAPs. The CE device does not
need to be aware of MPLS and services.

STP and mVPLS not required in the service

With MC-LAG, the system achieves both redundancy and loop prevention
without using STP.

7 — 1 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Compared to other dual-homing techniques, the MC-LAG technique has the following benefits:
• Transparence to the customer—from the perspective of the CE NE, only one LAG is connected to the service
provider network. The customer side does not require any function or configuration changes to deploy MC-LAG,
which makes deployment and migration much easier.
• The CE NE does not require MPLS or service support—the CE device can be any equipment that has Ethernet
ports and supports link aggregation and LACP.
• Some customers and service providers prefer not to use STP for reasons such as convergence issues and vendor
equipment compatibility. The use of MC-LAG eliminates these issues. Compared to STP, the MC-LAG has quicker
convergence during network failure and recovery.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 21
 Knowledge check

The MC-LAG resilience mechanism needs to be configured on both the CE

NE and the router.

True

False

Only two of the following items are MC-LAG benefits—which ones?

fast network failure detection

transparence to the customer

efficient traffic spread among the links

no MPLS support required in the CE NE

The two routers participating in the same MC-LAG do not need to be

connected to each other by direct physical links.

True

False

7 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

The MC-LAG resilience mechanism needs to be configured on both the CE NE and the router.
•True
•False

Only two of the following items are MC-LAG benefits—which ones?

•fast network failure detection
•transparence to the customer

•efficient traffic spread among the links
•no MPLS support required in the NE CE

The two routers participating in the same MC-LAG do not need to be directly connected to each other by physical
links.
•True

•False

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 22
 4 Virtual Router Redundancy Protocol

7 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This section provides an overview of the Virtual Router Redundancy Protocol (VRRP) feature.
The VRRP is supported on specific 7705 SAR platforms, equipped with specific adapter cards. For details, see the
7705 SAR OS Software Release Notice for your release.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 23
 4 Virtual Router Redundancy Protocol
4.1 Failure prevention

IP network

Router

LAN
Network N1

Host 1 Host 2 Host 3 Host 4

7 — 1 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

In a LAN connected to a larger IP network that contains vital resources, the availability of network services is
critical. The IP router that provides network access to a LAN is known as a default router or a first hop router—
because it is the first router that the hosts need to use to reach any destination that they cannot reach through
direct routing. In the configuration illustrated on the slide, the router represents a single point of failure.

How do you prevent this type of failure? You add one or more redundant first-hop routers to your configuration.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 24
 4 Virtual Router Redundancy Protocol
4.2 Router redundancy

IP network

Router 1 Router 2 Router 3

LAN
Network N1

Host 1 Host 2 Host 3 Host 4

7 — 1 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Now that you added two routers to the configuration, you also need a mechanism that manages the routers and
performs the following actions:
•selects the active router (the master router)
•switches to a backup router when the master router fails
•decides to which backup router to switch when more than one backup routers are available

The Virtual Router Redundancy Protocol provides a mechanism designed to avoid and prevent single points of
failure. The VRRP implementation in SR-OS NEs performs all the actions listed above.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 25
 4 Virtual Router Redundancy Protocol
4.3 VRRP virtual router

IP network

R1 Master R2 Backup R3 Backup

10.11.11.1 10.11.11.2 10.11.11.3
VRRP virtual router
IP address: 10.11.11.1 / VRID: 5

LAN

Host 1 Host 2 Host 3 Host 4

7 — 1 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

The Virtual Router Redundancy Protocol implements a redundant IP interface that is shared between two or more
routers on a common LAN segment. As a result, a group of routers function as a single virtual router. The virtual
router IP interface is specified as a default gateway on hosts directly attached to the LAN, and the routers
sharing the IP interface prevent a single point of failure by limiting access to this gateway address. The VRRP is a
mechanism designed to protect the IP interface.
The VRRP feature is supported on the 7705 SAR under the IPv4 IES and IPv4 VPRN contexts.
All routers in the VRRP group share the same virtual IP address and the same virtual MAC address. One router is
elected as the master router, and is responsible for responding to neighbor discovery messages and for forwarding
packets coming from the local hosts. If the master virtual router fails, the backup router configured with the
highest priority becomes the master virtual router. The new master router takes over the packet forwarding for
the local hosts.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 26
 4 Virtual Router Redundancy Protocol
4.4 Concepts and components

Virtual router master: responsible for Virtual router: logical entity managed
forwarding packets sent to the VRRP IP by VRRP that acts as a default router
addresses for hosts on a shared LAN

Virtual router backups:

available to assume
R1 Master R2 Backup R3 Backup forwarding responsibility if
10.11.11.1 1 10.11.11.2 10.11.11.3 the current master fails
VRRP virtual router
IP address: 10.11.11.1 / VRID: 5

LAN
Virtual router ID:
configured with the same
value on all routers that
are part of the VRRP
virtual router.

Host 1 Host 2 Host 3 Host 4

VRRP owner: the VRRP router whose virtual router IP Primary IP address: an IP
address is the same as the real interface IP address. The address selected from the
owner is also the default master router. set of real interface
addresses.

7 — 1 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This slide describes some important VRRP concepts and components:

• Virtual router—logical entity managed by VRRP that acts as a default router for hosts on a shared LAN. It
consists of a Virtual Router Identifier (VRID) and a set of associated IP addresses across a common LAN. A
VRRP router can backup one or more virtual routers.
• Virtual router master—controls the IP address or addresses associated with a virtual router is called the
master. The master is responsible for forwarding packets sent to the VRRP IP addresses.
• Virtual router backup—VRRP selects a new virtual router master from the VRRP backup routers that are
available to assume forwarding responsibility if the current master fails.
• Primary and secondary IP addresses—selected from the set of real interface addresses. An IP interface must
always have a primary IP address assigned for VRRP to be active on the interface. Alcatel-Lucent routers
supports both primary and secondary IP addresses (multi-netting) on the IP interface.
• VRRP ownership—you can configure VRRP on a router in either owner or non-owner mode. The owner is the
VRRP router whose virtual router IP address is the same as the real interface IP address, and assumes the role
of default master virtual router. Only one virtual router in the domain can be configured as owner.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 27
 4 Virtual Router Redundancy Protocol
4.5 How it works

Virtual router master

At startup, the VRRP owner becomes the virtual router master. The master
router sends an ADVERTISEMENT message and issues an ARP gratuitous
request to claim the MAC address of the virtual router. Then it keeps sending
ADVERTISEMENT messages at regular intervals while processing data packets.

Virtual router backups

The virtual router backups listen for ADVERTISEMENT message and monitor the
status of the master router to determine if they need to apply to assume the
master role. The backups use the master down interval to determine the status
of the master router, and to detect when it is down.

New master election

After determining that the master router is down, the backup routers advertise
their availability and indicate their priority in the line to take over as master
router. In addition to the priority, there is also the preempt mode that can
influence the master election.

7 — 1 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This slide outlines how the VRRP mechanism works. After the system is initialized, the master router starts
sending ADVERTISEMENT messages to the backup routers. The message-interval setting sets the interval that
elapses between two ADVERTISEMENT messages.
The backup routers use the message-interval to calculate the master down interval. As soon as each backup
router determines that the master is down, it start to compete for the master position. The new master election
process takes into account factors such as the values of the priority and preempt mode VRRP configuration
parameters. In case of a tie, the backup router with the highest IP address takes over as the master router.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 28
 Knowledge check

You can configure VRRP on a router in either master or non-master mode.

True

False

What type of message does the VRRP router master send?

a. HEARTBEAT
b. NOTIFICATION
c. ADVERTISEMENT

7 — 1 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

You can configure VRRP on a router in either master or non-master mode.

•True
•False

The VRRP router master sends the following type of messages:

a) HEARTBEAT
b) NOTIFICATION
c) ADVERTISEMENT

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 29
 5 Pseudowire with MC-LAG for VLL

7 — 1 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This section describes the resilience and high-availability mechanism that uses pseudowire with MC-LAG for
virtual leased line (VLL) services.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 30
 5 Pseudowire with MC-LAG for VLL
5.1 Pseudowire redundancy

VLL service

SAP SAP
SDP binding

R1 R2
CE1 CE2

Pseudowire definition
Pseudowire (PW) is a mechanism that emulates the essential attributes of a
service such as ATM, frame relay, or Ethernet, low-rate TDM, or SONET/SDH
over a Packet Switched Network (PSN). The PSN can be MPLS, IP (either IPv4 or
IPv6), or Layer 2 Triple-Play v3.

7 — 1 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Pseudowire is a logical point-to-point MPLS connection between two service routers participating in the
same service. In an IP/MPLS network, service transport tunnels transport the VLL service traffic across
the core network.

A “traditional” VLL service—such as Epipe—has two components on each PE (Provider Edge) router.
These components serve as traffic entry and exit points for customer data:
•A SAP (service access point) to the CE (Customer Edge) equipment
•An SDP (service distribution path) binding to the provider core network; the SDP binding is called
pseudowire.

The MPLS protection mechanisms provides some redundancy to the SDP :

•Dynamic failover in LDP
•Secondary standby and Fast-Reroute paths in an RSVP-TE configuration

To improve redundancy on the access side, we can provision a dual-homing configuration.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 · Module 1 · Page 31
Section 7 — Module 1 — Page 31
 5 Pseudowire with MC-LAG for VLL
5.2 Pseudowire redundancy and MC-LAG

VLL service
R1 R2
T-LDP

SDP binding

MC-LAG MC-LAG

CE1 CE2
SDP binding
T-LDP

R4 R3

7 — 1 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This slide shows the use of both Multi-Chassis Link Aggregation (MC-LAG) in the access network and
pseudowire redundancy in the core network to provide a resilient end-to-end VLL service between
CE1 and CE2. The SDP bindings (pseudowires) have been established between endpoint components
on VLL service instances. The next slide provides details about endpoints.

The routers communicate using T-LDP (Targeted-Label Distribution Protocol) signalling.The Layer 2
VPN services, such as VLL, require T-DLP to establish the pseudowires. By default, the SDP signaling
method is configured as T-LDP.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 · Module 1 · Page 32
Section 7 — Module 1 — Page 32
 5 Pseudowire with MC-LAG for VLL
5.3 VLL service endpoints

R1 VLL service R2

SDP 12 SDP 21
SAP SAP
SDP 13 SDP 24

x y x y

MC-LAG MC-LAG

CE1 CE2
SDP 42 SDP 31
SAP SAP
SDP 43 SDP 34

x y x y

R4 R3

7 — 1 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This slide shows the VLL service with dual-homing towards the access side, and MC-LAG configured
between the routers connected to the CEs. The VLL service has two components:
•One side facing the customer
•Another side facing the network

The SR-OS supports the endpoint concept, which allows the provisioning of objects through which the
service moves traffic. Two endpoints can be configured in a VLL service instance on each router. On
this slide, the endpoints are called “x” and “y”, but they can have any name (of maximum 32
characters). You can provision two types of endpoint objects in the SR-OS: sap objects and sdp-spoke
objects.

An endpoint facing the access side can contain maximum one sap object and one ICB spoke-sdp object
(the sap needs to be part of a LAG if the ICB is already present).
An endpoint facing the network side can contain maximum 4 spoke-sdp objects, any combination of
the following:
•primary spoke-sdp (maximum 1 per endpoint, set to revertive)
•secondary spoke-sdp (maximum 4 per endpoint, not revertive, precedence)
•ICB spoke-sdp (maximum 1 per endpoint)

Traffic can be forwarded only between two endpoints. Objects that are associated with the same
endpoint cannot forward traffic to each other.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 · Module 1 · Page 33
Section 7 — Module 1 — Page 33
 5 Pseudowire with MC-LAG for VLL
5.4 Pseudowire active path
VLL service
R1 R2
PE2: SAP down
SDP 12 SDP 21
SAP SAP
R1: SAP up
SDP 13 SDP 24

x y x y

MC-LAG MC-LAG

CE1 R3: SAP up CE2

SDP 42 SDP 31
SAP SAP
R4: SAP down
SDP 43 SDP 34

x y x y

R4 R3

7 — 1 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

The routers notify each other of their SAP states using T-LDP (Targeted-Label Distribution Protocol)
signaling.
The VLL service forms a path following the LAGs that are active and the endpoint components that
are up.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 · Module 1 · Page 34
Section 7 — Module 1 — Page 34
 5 Pseudowire with MC-LAG for VLL
5.5 Pseudowire active path—access link failure
VLL service
R1 R2
R2: SAP up
SDP 12 SDP 21
SAP SAP
R1: SAP up
SDP 13 SDP 24

x y x y

MC-LAG MC-LAG

CE1 R3: SAP down CE2

SDP 42 SDP 31
SAP SAP
R4: SAP down
SDP 43 SDP 34

x y x y

R4 R3

7 — 1 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This slide shows what happens when there is an access link failure on R3. The MC-LAG switches
activity to the R2 SAP, and the spoke-sdp bindings are adjusted according to the new situation.
The VLL service forms a new forwarding path depending on the new situation.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 · Module 1 · Page 35
Section 7 — Module 1 — Page 35
 5 Pseudowire with MC-LAG for VLL
5.6 Pseudowire active path—SDP failure
VLL service
R1 R2
R2: SAP down
SDP 12 SDP 21
SAP SAP
R1: SAP up
SDP 13 SDP 24
X
x y x y

MC-LAG MC-LAG

CE1 R3: SAP up X CE2

SDP 42 SDP 31
SAP SAP
R4: SAP down
SDP 43 SDP 34

x y x y

R4 R3

7 — 1 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

It is assumed that the SDPs are on a protected path due to the core link redundancy LDP or
secondary/fast reroute protection mechanisms in RSVP-TE. This slide shows an example of failure of
the spoke-sdp binding between two active access sides. The failure cannot be resolved in this
configuration.

In a lab environment, this situation can de demonstrated by administratively shutting down SDP 13 on
R1 and SDP 31 on R3.

This type of failure can be prevented by implementing ICB (Inter-Chassis Backup) spoke-sdp objects.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 · Module 1 · Page 36
Section 7 — Module 1 — Page 36
 Knowledge check

Pseudowire is a logical point-to-point MPLS connection between multiple

service routers participating in the same service.

True

False

Only two of the following items are MC-LAG benefits—which ones?

1. sdp-spoke objects
2. rsvp objects
3. active-spoke objects
4. sap objects

7 — 1 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Statement
•True
•False
(Pseudowire is a logical point-to-point MPLS connection between two service routers participating in the
same service.)

Only two of the following items are MC-LAG benefits—which ones?

1. sdp-spoke objects

2. rsvp objects
3. active-spoke objects
4. sap objects

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 37
 6 G.8032 Ethernet Ring Protection

7 — 1 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

This section provides an overview of the G.8032 Ethernet Ring Protection mechanism.
The 7705 SAR does not support the G.8032 Ethernet Ring Protection feature. However, the 7705 SAR can be
connected to G.8032 Ethernet rings. If you are interested in getting an idea of the G.8032 Ethernet Ring
Protection mechanism, we can continue to cover this section.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 38
 6 G.8032 Ethernet Ring Protection
6.1 Ethernet ring overview

R1 R2

Ethernet ring topology

R4 R3

7 — 1 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

The G.8032 is an ITU-T (ITU Telecommunication Standardization Sector) recommendation that defines the APS
(Automatic Protection Switching) protocol and protection switching mechanisms for Ethernet-layer ring
topologies.

Ethernet rings provide wide-area multipoint connectivity more economically due to their reduced number of
links. Each ring node is connected to adjacent nodes participating in the same ring using two independent links. A
ring link is established between two adjacent nodes. A port for a ring link is called a ring port. The minimum
number of nodes on a ring is two.

Currently, the Alcatel-Lucent SR-OS supports the Ring Automatic Protection Switching protocol on 7450 ESS, 7750
SR and 7950 XRS PEs equipped with the appropriate IOMs or IMMs. For details, see the documentation of your
specific PE equipment. The SR-OS supports the G.8032 Ethernet ring protection for SAPs within a PBB VPLS, a
routed VPLS (R-VPLS) or a normal VPLS service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 39
 6 G.8032 Ethernet Ring Protection
6.2 Description of ring automatic protection switching

RPL
R1 R2
RPL owner

R1 R2 R1 R2

Physical Logical
topology Ethernet ring topology topology

R4 R3 R4 R3

R4 R3

Ring APS ERP data channel

Ring data channel

7 — 1 — 40 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

The G.8032 is an ITU-T (ITU Telecommunication Standardization Sector) recommendation that defines the APS
(Automatic Protection Switching) protocol and protection switching mechanisms for Ethernet-layer ring
topologies.
Ethernet rings provide wide-area multipoint connectivity more economically due to their reduced number of
links. Each ring node is connected to adjacent nodes participating in the same ring using two independent links. A
ring link is established between two adjacent nodes. A port for a ring link is called a ring port. The minimum
number of nodes on a ring is two.
The G.8032 ring protection switching architecture relies on the following:
•the principle of loop avoidance
•the use of learning, forwarding, and address table mechanisms defined in the Ethernet flow forwarding function
(ETH_FF) in the control plane.
The ring protection mechanism achieves loop avoidance by ensuring that, at any time, traffic flows on all but one
of the ring links. This particular link is called the Ring Protection Link (RPL). Under normal conditions, the RPL is
blocked, and not used for traffic. A designated router, the RPL owner, is responsible for blocking traffic over the
RPL at its end of the link. When a ring failure occurs, the RPL owner is responsible for unblocking the RPL and
allowing traffic over the RPL.
A ring failure triggers the protection switching of the traffic. The nodes use the Ring Automatic Protection
Switching (R-APS) protocol to coordinate the protection actions over the ring.
The slide shows a ring of four nodes, with the RPL owner on the top right (R2). One link of the RPL owner is
designated to be the RPL and is blocked to prevent the formation of a loop.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 40
 6 G.8032 Ethernet Ring Protection
6.3 Ring protection mechanism

RPL
R1 R2

RPL owner

Link failure
Ethernet ring topology

R4 R3

7 — 1 — 41 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

When the RPL owner and the RPL end are configured on R2, the link to R1 is the RPL when the ring is fully
operational. During normal operation, the RPL owner blocks the RPL. If a different ring link fails—for example the
link between R2 and R3, as shown on the slide—then the RPL owner unblocks the RPL, which starts being used for
ring traffic.

When the failed link recovers, one of its adjacent nodes (R2 or R3 on the slide) blocks it at first. The adjacent
blocking node sends an R-APS message across the ring to indicate that the error is cleared. After a configurable
time interval elapses, if reversion is enabled, the RPL reverts to being blocked and all other links are unblocked.
This ensures that the ring topology, when fully operational, is predictable.

The R-APS protocol ensures that one link is blocked even without a defined RPL owner. If a specific router is not
configured as RPL owner, then the last link to become active is blocked and the ring remains in this state until
another link fails.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 41
 Knowledge check

When a failed link recovers, one of its adjacent nodes unblocks it right
away, and all links in the ring are operational for a very short time until
the RPL is blocked.

True

False

In the G.8032 implementation, “owner” is used in the following context

(choose one):
a. VLPS owner
b. APS owner
c. RPL owner

7 — 1 — 42 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

When the failed link recovers, one of its adjacent nodes unblocks it right away and all links in the ring are
operational for a very short time until the RPL is blocked.
•True
•False

In the G.8032 implementation, “owner” is used in the following context (choose one):
a. VLPS owner
b. APS owner
c. RPL owner

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 42
 Module summary

In this module, you have learned:

What are network resilience and high-availability.

What are the concepts and techniques that you can apply to improve
network resilience and high-availability.

7 — 1 — 43 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

In this module, you have learned:

•What are network resilience and high-availability.
•What are the concepts and techniques that you can apply to improve network resilience and high-availability.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 43
End of module
Resiliency and High Availibility

7 — 1 — 44 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

HA and Resiliency — Resiliency and High Availibility
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 7.1 Edition N/A
Section 7 — Module 1 — Page 44
Learning experience powered by
Alcatel-Lucent University

Section 8
OAM
Module 1
ETH-OAM
TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

8—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 1
 Blank page

8—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 2
 Module objectives

Upon completion of this module, you should be able to:

Describe the Ethernet OAM principles

List the Ethernet CFM OAM components

Identify the Ethernet CFM OAM functionality and tests

Describe the EFM OAM functionality and operations

8—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Upon completion of this module, you should be able to:

•Describe the Ethernet OAM principles
•List the Ethernet CFM OAM components
•Identify the Ethernet CFM OAM functionality and tests
•Describe the EFM OAM functionality and operations

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 3
Module objectives [cont.]

8—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 4
 Table of Contents

1 Service OAM overview 7

Page
2 Ethernet CFM OAM components 11
1 Service
2 Eth-CFMOAM Configuration
overview 7 19
1.1 Fault management in the Ethernet Carrier network 8
3 Standards,
1.2 Ethernetrecommendations
CFM OAM operations
and technical specifications 9 25
1.3 Service OAM overview 10
4 Ethernet
2 Ethernet CFM in
OAMthe First Mile OAM
components 11 37
2.1 Hierarchical model 12
2.2 CFM OAM components 13
2.3 Ethernet CFM terminology 14
2.4 Maintenance Domain 15
2.5 Maintenance Association 16
2.6 Maintenance Association Endpoint 17
2 Eth-CFM Configuration 19
2.1 Configuration tasks 20
2.2 Global Eth-CFM Parameters ITU-T Y.1731 21
2.3 Global Eth-CFM Parameters IEEE 802.1ag 22
2.4 MEPs Definition in Service 23
2.5 Eth-CFM Verification 24
3 Ethernet CFM OAM operations 25
3.1 Supported operations 26
3.2 Continuity Check Messages 27
3.3 ETH-CC failure conditions 28
3.48 —Sample
1—5
Configuration: CCM 29
3.5OAMSample
— ETH-OAM Configuration: CCM (continued)
7705 SAR — R6.0 Strategic Industries
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
30
3.6 Sample Show Command: CCM Verification 31
3.7 Loopback 32
3.8 Generating and Verification of Loopback Tests 33
3.9 Linktrace 34
3.10 Generating and Verification of Linktrace Tests 35
4 Ethernet in the First Mile OAM 37
4.1 EFM OAM overview 38
4.2 EFM OAM configuration 39
4.3 EFM OAM tunneling 40
4.4 EFM OAM operations 41
4.5 EFM OAM status 42

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 5
Table of Contents [cont.]

8—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 6
 1 Service OAM overview

8—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 7
 1 Service OAM overview
1.1 Fault management in the Ethernet Carrier network

IP/MPLS network

Native
Ethernet
Ethernet
First Mile MPLS core

Service provider network

Subscriber network

8—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Today’s complex networks and service deployments require reliable mechanisms to quickly isolate and manage
failures. The responsibilities for monitoring and managing network segments are divided among the entities to
which the segments belong. The Ethernet service OAM kit includes tools that can accurately localize problems in
the network so that an automatic or manual action can be taken.

The service OAM tool kit is based on the contribution of recognized organizations, which have been working in
close cooperation to develop complementary and compatible standards, recommendations and technical
specifications for multi-domain Ethernet Service OAM.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 8
 1 Service OAM overview
1.2 Standards, recommendations and technical specifications

IEEE 802.1ag standard

Specifies protocols, procedures, and managed objects to support
transport fault management, including discovery and verification of a
path, detection and isolation of connectivity faults for each Ethernet
service instance.

ITU-T recommendation Y.1731

For the most part, the recommendation is identical to IEEE 802.1ag.
In addition, it addresses performance management topics.

Metro Ethernet Forum (MEF) technical specifications

Specifications include: MEF 30.1 Service OAM fault management
implementation agreement; MEF 25.(1) Test procedures based on a
combination of requirements for Service OAM; MEF 10.2/MEF 10.2.1
Performance Attributes; MEF35 Service OAM performance monitoring.

8—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The organizations have collaborated closely to work out interoperability issues among common functions. Their
contribution is based on years of experience that can be applied to the technology to facilitate a better
understanding of the following OAM-related topics:
•architectural components
•complexity and risks
•tool kit components and deployment options.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 9
 1 Service OAM overview
1.3 Service OAM overview

Service OAM architectural considerations

The Service OAM architecture is based on the standards, recommendations
and specifications outlined on the previous slide. The OAM architectural
considerations define the OAM tool kit behavior and functionality applicable to
Carrier Ethernet, with suggested defaults.

Fault management
The Service OAM kit deploys tools to locate and isolate fault conditions. The
tools perform on-demand testing of connectivity and service continuity, as
well as path validation. They also check proactively network segment
connectivity with optional network convergence.

Performance monitoring
The Service OAM performance monitoring tools capture key performance
metrics. They perform on-demand monitoring of services and network
segments of concern over time, as well as proactive reporting of
measurements of network segments and services.

8 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This slide provides a high-level service OAM overview, as well as descriptions of the fault management and
performance monitoring functions, as defined in the IEEE, ITU-T and MEF contributions.
The IEEE, ITU-T and MEF continue their collaboration on improving the tool interoperability and on adding new
functions.

The next section describes the Service OAM components.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 10
 2 Ethernet CFM OAM components

8 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This section describes the Ethernet CFM OAM components.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 11
 2 Ethernet CFM OAM components
2.1 Hierarchical model

8 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The service OAM implements a hierarchical model that includes domains or entities with administrative scope and
reach. The principles that govern the definition of components include the following:
•The wider-scope components are transparent to the narrower-scope components.
•The end-to-end network is divided into areas of responsibilities or roles.
•The network areas include endpoints that define closed management groups.
•The definition of areas of responsibilities or roles is based on segments of the end-to-end network.

This slide shows an end-to-end network divided into administrative domains or management entities.

The next slide describes the service OAM components.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 12
 2 Ethernet CFM OAM components
2.2 CFM OAM components

IEEE 802.1ag name ITU-T Y.1731 name Function

Maintenance Domain Maintenance Entity (ME) Administrative scope and reach

(MD)

Maintenance Domain MEG Level Numerical identifier of the domain

Level

Maintenance Association Maintenance Entity Group Grouping of service endpoints

(MA) (MEG)

Maintenance Association MEG Endpoint (MEP) Terminating and origination

Endpoint (MEP) endpoints

Maintenance Association MEG Intermediate Point Management points between

Intermediate (MIP) endpoints
Point (MIP)

The SR-OS service OAM implements the IEEE 802.1ag standard and uses its terminology

8 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This slide describes the service OAM components, as defined in the IEEE, ITU-T and MEF contributions to the
service OAM architecture and functionality. The IEEE 802.1ag standard, ITU-T Y.1731 recommendation and MEF
specifications are complementary. However, the SR-OS implements the service OAM tool kit according to the
concepts and principles of the IEEE 802.1ag standard, also referred to as the Ethernet Continuity Fault
Management (CFM) standard. The standard provides for consistent service monitoring and tools to isolate faults
and to verify connectivity between two points.

The standard includes concepts such as the following:

•Maintenance Domains and Associations used to define the scope of CFM operations
•relationship between Maintenance Domains and services that are being monitored or tested
•protocols and procedures to maintain and diagnose connectivity problems
•provisions for future expansion of service OAM functionality

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 13
 2 Ethernet CFM OAM components
2.3 Ethernet CFM terminology

Term Expansion Definition

MD Maintenance A network or part of a network (set of Ethernet network elements or ports)
Domain controlled by an operator, and for which connectivity faults can be managed.
MD boundaries are set by MEPs. In the SR-OS CLI command, it is identified by
an md-index from 1 to 4294967295.
MD Maintenance A user-configured value of 0 to 7 representing the hierarchy level of a given
Level Domain Level MD within a CFM architecture. The value 7 is the highest MD level, and 0 is
the lowest.
MA Maintenance A grouping of MEs that need to be managed as part of a given service. In the
Association SR-OS CLI command, it is identified by an ma-index value from 1 to
4294967295.
MEP Maintenance An edge point that can terminate, respond to, or initiate OAM messages for a
Association configured MA-MD combination
End Point
ME Maintenance An Ethernet port or endpoint that is managed as part of Ethernet CFM OAM.
Entity An endpoint can be a SAP or a spoke-SDP object.
MIP Maintenance An intermediate point that can forward or respond to OAM messages
Association initiated by MEPs in the same MD. Connectivity fault management (CFM)
Intermediate messages intended for other MIPs or MEPs are transparent to MIPs.
Point The 7705 SAR does not supports MIPs.

8 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The table provided on this slide builds on the concepts introduced on the previous slide, and defines commonly
used Ethernet CFM terms. To apply the service OAM tools, you need to configure the Ethernet CFM components
such as a Maintenance Domain Level, Maintenance Associations, and Maintenance Association End points. You
perform these operations in the configure>eth-cfm context of the SR-OS CLI.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 14
 2 Ethernet CFM OAM components
2.4 Maintenance Domain

OPERATOR A: level 1 OPERATOR B: level 1

SERVICE PROVIDER MD: level 3

SUBSCRIBER MD: level 7

Where MDs overlap, the OAM generated within the higher level MD transits the lower
order MD to its destination. A CFM action generated within the customer MD (level 7)
transits both the provider and operator MDs. However, a CFM OAM action originating
from the provider MD does not go to the customer MD.
8 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Now let us review the Ethernet CFM components. This slide describes the Maintenance Domain component.
The Ethernet CFM (ETH-CFM) mechanism is based on the principle that maintenance actions are contained within
a defined scope, or service. The admin scope component is the Maintenance Domain (MD). An MD is a provider-
defined administrative container used to define the scope, reach and boundary for the fault monitoring actions of
the application. The MD is identified by a name and a level that you can define in the SR-OS.

The IEEE 802.1ag specifies 8 MD levels ranging from 0 to 7, with 0 being the lowest level and 7 being the highest
level. Higher numbered levels indicate larger spans within the network. An end-to-end network includes the
following MD types:
•The subscriber MD extends between routers, usually including the SAPs, and is assigned level 6 or 7.
•The service provider MD extends across the core routers, and is usually assigned levels 3 to 5.
•The operator MD typically extends from one provider core to the interface with another provider network, and
has the shortest span. The operator MD is usually assigned level 1 or 2.

Where MDs overlap, the OAM generated within the higher level MD transits the lower order MD to its destination.
However, a lower order MD OAM action does not transit a higher level MD. A CFM action generated within the
customer MD (level 7) transits both the provider and operator MDs. However, a CFM OAM action originating from
the provider MD does not go to the customer MD.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 15
 2 Ethernet CFM OAM components
2.5 Maintenance Association

MA 1 “SAR-1_to_SR-B”
MA 2 “SAR-2_to_SR-A”
SAR-22
SAR-1

SR-A SR-B

MD 123

8 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

A maintenance association is a closed group of management end points. The MA allows service providers to
segment their service topology to better isolate fault locations. The ETH-CFM enables this segmentation through
the implementation of MAs. Each MD needs to have at least one MA defined within the MD span, even though the
service providers can define as many MAs as they require to monitor services within the scaling limits of the SR-OS
router.

To create an MA, you need to configure a unique MA ID, format type and name.

This slide illustrates the segmentation of the service contained within MD 123 into 2 MAs:
•MA 1, named “SAR-1_to_SR-B”
•MA 2, named “SAR-2_to_SR-A”

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 16
 2 Ethernet CFM OAM components
2.6 Maintenance Association Endpoint

UP MEP DOWN MEP

Switch Fabric Switch Fabric

Maintenance Association

•UP—the ETH-CFM frame is sent into the service (through the Switch
Fabric)
•DOWN—the ETH-CFM frame is sent out of the service (away from the
Switch Fabric)

8 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

We have learned from the previous slides that the MDs and MAs define the span of the ETH-CFM actions. The MEP
is a logical construct that processes Ethernet-type 0x8902 frames (SOAM) and prevents them from flowing outside
of the scope of responsibility. The MEP originates or terminates all ETH-CFM actions.

A MEP is defined at the limits of an MA and consists of a unique ID, within the range of 0 to 8191. The
combination of the MEP ID and MA uniquely identifies the MEP within the MD.

A MEP has an attribute that defines the direction of flow of the Ethernet SOAM frame relative to the router
Switch Fabric:
•UP—the ETH-CFM frame is sent into the service (through the Switch Fabric), and away from the entity on which
the MEP was created
•DOWN—the ETH-CFM frame is sent out of the service (away from the Switch Fabric) on the entity on which the
MEP was created

A MEP has also an Active or Passive side:

•Active—frames are compared to the existing level and processed accordingly
•Passive—packets are passed transparently through the MEP

The MEPs define which Service Access Points (SAPs) or Service Distribution Points (SDPs) actively run the CFM.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 17
 Knowledge checks

Indicate if each of the following statements is true or false.

a) The IEEE 802.1ag specifies 8 MD levels ranging from 0 to 7, with 0 being the
highest level and 7 being the lowest level.
b) The first step of configuring the ETH CFM is the maintenance domain
configuration.
c) A service provider can define more than one Management Association in the
same Management Domain.

8 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Correct answers:
a) False
b) True
c) True

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 18
 2 Eth-CFM Configuration

8 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 19
 2 Eth-CFM Configuration
2.1 Configuration tasks

Set the global Ethernet
Define the Maintenance Domain

1 CFM parameters
Define the

Define the
Domain Level
Maintenance Association

Define the Bridge Identifier

Define the Remote MEPs

Define the MEPs as
Determine where to create MEPs

2 required
Define the MD and MA

Set the MEP action (Up or Down)

Enable the CCM

Enable the ETH-CFM

Verify the configurations
Verify the ETH-CFM configuration at

3 and run the tests global and service levels

Review the CCM statistics

Run the Loopback and Linktrace
tests to verify service continuity

8 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This slide provides the high-level configuration steps required to perform the following tasks:
• Enable the IEEE 802.1ag ETH-CFM at the router global context.
• Configure MEPs in the service, as required.
• Verify 802.1ag configuration and run OAM tests to verify service continuity.

The student lab guide provides details about configuration commands and command syntax, as required.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 20
 2 Eth-CFM Configuration
2.2 Global Eth-CFM Parameters ITU-T Y.1731

Define the Maintenance Domain

Define the Domain Level

Define the Maintenance Association

Define the Bridge Identifier

Define the Remote MEPs

Y.1731 Specific Reqs

*A:SARF-51>config>eth-cfm# info
----------------------------------------------
domain 2 format none level 2
association 1 format icc-based name "Y.CARRIER.001"
bridge-identifier 100
exit
remote-mepid 215
exit
exit
----------------------------------------------

8 — 1 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

To configure an ITU-T Y.1731 MEP the maintenance domain has no name. It is only used as container to configure
the MEG level. The maintenance association becomes the MEG and must be configured with an icc-based name
(TLV: ICC-based(32) exactly 13 characters).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 21
 2 Eth-CFM Configuration
2.3 Global Eth-CFM Parameters IEEE 802.1ag

Define the Maintenance Domain

Define the Domain Level

Define the Maintenance Association

Define the Bridge Identifier

Define the Remote MEPs

802.1ag Specific Reqs

*A:SARF-51>config>eth-cfm# info
----------------------------------------------
domain 2 name "Carrier" level 2
association 1 format string name “Epipe100"
bridge-identifier 100
exit
remote-mepid 215
exit
exit
----------------------------------------------

8 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Unlike the Y.1731, 802.1ag requires the MEP to have a maintenance domain name. The maintenance association is
configured with a “string name”.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 22
 2 Eth-CFM Configuration
2.4 MEPs Definition in Service

Determine where to create MEPs

Define the MEP ID

Define the MD and MA

Set the MEP action (Up or Down)

Enable the CCM

Enable the ETH-CFM

epipe 100 customer 1 create

sap 1/2/3 create
eth-cfm
mep 115 domain 2 association 1 direction up
ccm-enable
no shutdown
exit
exit
exit

8 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Determine where to create MEPs

In this case the service was epipe 100 under sap 1/2/3. Keep in mind that the bridge identifier in the previous slide must
match this service ID.

Define the MEP ID

The MEP ID is specified once the MEP is being defined under the service.

Define the MD and MA

Set the MEP action (Up or Down)

Enable the CCM

In this example we are using ccm. See below the CLI context that can be enabled under the MEP.

Enable the ETH-CFM

By default it is ‘shutdown’. ‘No shutdown’ under the MEP to enable eth-cfm.

CLI:

*A:SARF-51>config>service>epipe>sap>eth-cfm>mep#
[no] ais-enable + Configure the generation and reception of Alarm Indication Signal (AIS)
message parameters
[no] ccm-enable - Enable/Disable Generation of CCM messages
[no] ccm-ltm-priori* - Configure the priority of CCM and LTM messages
[no] dual-ended-los* + Enable/Disable dual-ended loss measurement test functionality on MEP
[no] eth-test-enable + Enable/Disable eth-test functionality on MEP
low-priority-d* - Configure the Lowest Priority Defect for the MEP
one-way-delay-* - Configure the one-way-delay test threshold
[no] shutdown - Administratively enable/disable the MEP

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 23
2 Eth-CFM Configuration
2.5 Eth-CFM Verification

Verify the ETH-CFM configuration at global and service levels

show eth-cfm cfm-stack-table

show eth-cfm domain <md-index> detail

show eth-cfm association <ma-index> detail

show service id <service-id> all

show service id 100 all | match post-lines 10 "Eth-Cfm"
•Review the CCM statistics

show service id <service-id> all

show service id 100 all | match post-lines 10 "Eth-Cfm"
• show service id 100 all | match "CcmTx"

Run the OAM tests to verify service continuity
*A:SAR-1# oam eth-cfm
eth-test - Issue an eth-cfm eth-test
linktrace - Issue an eth-cfm linktrace test
loopback - Issue an eth-cfm loopback test
one-way-delay-* - Issue an eth-cfm one-way-delay-test
single-ended-l* - Issue an eth-cfm single-ended-loss-test
two-way-delay-* - Issue an eth-cfm two-way-delay-test

8 — 1 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 24
 3 Ethernet CFM OAM operations

8 — 1 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This section describes the Ethernet CFM OAM operations.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 25
 3 Ethernet CFM OAM operations
3.1 Supported operations

Continuity Check Messages (CCM)

The CCM operation monitors path connectivity between pre-defined
maintenance points.

Loopback
The loopback operation verifies connectivity to all maintenance points.

Linktrace
The linktrace operation verifies the hop-by-hop connectivity to a targeted
maintenance point.

8 — 1 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The IEEE 802.1ag CFM standard addresses the issue of monitoring service continuity within an Ethernet
environment. The CFM implementation establishes maintenance boundaries (MDs and MAs) and enables
mechanisms to generate, process and terminate CFM packets (MEPs and MIPs). With these components in place,
the IEEE 802.1ag CFM defines operations to monitor path status and to provide tools to help isolate failure
locations.

The Continuity Fault Management supports the following operations:

•Continuity Check Messages (CCM)
•Loopback
•Linktrace

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 26
 3 Ethernet CFM OAM operations
3.2 Continuity Check Messages

CCM PDU CCM PDU

MEP 101 PE1 MEP 102 PE2

Maintenance Association

The CCM is a multicast frame generated by a MEP and sent to its remote MEPs
in the same MA. The originating MEP does not require a reply message. To
identify faults, the receiving MEP maintains a MEP database with the MAC
addresses of the remote MEPs with which it expects to maintain connectivity
checking. If there is no CCM from a monitored remote MEP in a preconfigured
period, the local (receiving) MEP raises an alarm.

8 — 1 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The CFM monitors path connectivity through the use of Continuity Check Messages (CCM). The CCM is 100-byte
PDU multicast frame generated by the MEP and sent to all the MEPs in the same MA.

You need to enable the CCM manually in the MEP configuration context. Once enabled, the MEP sends CCM
frames at a time interval that can be configured with a value from 10 milliseconds to 600 seconds. The default
value is 10 seconds.

The originating MEP does not track the sent frame and does not expect a response from the MEPs to which the
frame was sent. Instead, the originating MEP maintains a list of MEPs from which it expects messages (the list of
MEPs needs to be manually configured). The originating MEP waits the response for 3.5 CCM intervals (35
milliseconds to 2100 seconds—the default value is 35 seconds). After the wait time expires, the originating MEP
declares a fault condition. The wait interval is not configurable—the SR-OS calculates it based on the CCM time
interval.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 27
 3 Ethernet CFM OAM operations
3.3 ETH-CC failure conditions

Defect Low Priority Description Cause Priority

Defect

DefNone N/A No faults in the Normal operations N/A

association

DefRDICCM allDef Remote Detect Indication Remote MEP is declaring a fault. This is a 1
unidirectional failure.

DefMACStatus macRemErrXcon MAC layer issue A remote MEP indicates that a remote port 2
(default) or interface is not operational.

DefRemCCM remErrXcon No communication from The MEP is not receiving CCMs from a 3
remote peer configured peer. MEP

DefErrorCCM errXcon Local and remote The CCM received from a remote MEP has 4
configurations do not inconsistent timers or lower MD level within
match required the same MA. The MEP receives CCM with
parameters its own MEP ID within the same MA.

DefXconn Xcon Cross Connected Service The MEP received CCMs from a different MA 5
This can indicate that two services have
merged or there is a configuration error, an
incorrect association identification.

8 — 1 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The IEEE 802.1ag ETH-CFM covers service continuity checking in Ethernet-based networks to signal path failures
and help isolate and identify fault conditions. This function is based on CCM frames that originate, are processed
or are terminated on MEPs. When a MEP determines that a CCM is invalid, the MEP signals the condition as a
alarm.
The IEEE 802.1ag standard specifies six failure conditions, described on this slide. Each failure condition is
identified by the following attributes: Defect, Low Priority Defect and Priority Level.
The Defect is the fault condition that the system records in the logs, and the Priority Level sets the order in
which the defects affect the service. For example, DefRemConn indicates that no CCM is being received from a
remote MEP, and DefErrorCCM indicates an incorrect MEP configuration. Low Priority Defect is a label through
which the provider can set a minimum level at which alarms are declared. An alarm is raised and a trap is sent if
the defect is greater than or equal to the configured Low Priority Defect value. This feature enables providers to
declare the alarms that are relevant to their configurations.

You can set this value using the low-priority-defect command in one of the following contexts:
•config>service>epipe>sap>eth-cfm>mep
•config>service>epipe>spoke-sdp>eth-cfm>mep

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 28
 3 Ethernet CFM OAM operations
3.4 Sample Configuration: CCM

CCM-Interval configured:
*A:SARF-52>config>eth-cfm# info
----------------------------------------------
domain 2 format none level 2
association 1 format icc-based name "Y.CARRIER.001"
bridge-identifier 100
exit
ccm-interval 1
remote-mepid 115
exit
exit
----------------------------------------------

Parameters:
*A:SARF-52>config>eth-cfm>domain>assoc# ccm-interval
- ccm-interval {interval}
- no ccm-interval

<interval> : {10ms|100ms|1|10|60|600} - default 10 seconds

8 — 1 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

If no interval is configured, the default interval will be 10 seconds.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 29
3 Ethernet CFM OAM operations
3.5 Sample Configuration: CCM (continued)

Enable CCM at the service level:

*A:SARF-52>config>service>epipe# info
----------------------------------------------
sap 1/2/4 create
eth-cfm
mep 215 domain 2 association 1 direction up
eth-test-enable
exit
ccm-enable
no shutdown
exit
exit
exit

8 — 1 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 30
 3 Ethernet CFM OAM operations
3.6 Sample Show Command: CCM Verification

*A:SARF-52# show service id <service-id> all

-------------------------------------------------------------------------------
Eth-Cfm Configuration Information
-------------------------------------------------------------------------------
Md-index : 2 Direction : Up
Ma-index : 1 Admin : Enabled
MepId : 215 CCM-Enable : Enabled
LowestDefectPri : macRemErrXcon HighestDefect : none
Defect Flags : None
Mac Address : 6c:be:e9:e8:69:57 ControlMep : False
CcmLtmPriority : 7
CcmTx : 262525 CcmSequenceErr : 0
Eth-1Dm Threshold : 3(sec)
DmrRepliesTx : 0
LmrRepliesTx : 0
Dual-Loss Test : Disabled
Eth-Ais: : Disabled
Eth-Tst: : Enabled Eth-Tst Pattern: : allZerosNoCrc
Eth-Tst dataLength : 64 Eth-Tst Priority: : 7
Eth-Tst Threshold : 1(bitError)
LbRxReply : 0 LbRxBadOrder : 0
LbRxBadMsdu : 0 LbTxReply (total) : 0
LbTxReplyFastPath : 0 LbTxReplySlowPath : 0
LbNextSequence : 1 LtNextSequence : 5
LtRxUnexplained : 0

-------------------------------------------------------------------------------

8 — 1 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Important to note that ccm-enable is indeed configured/enabled under the service. Also the CcmTx, counter
keeps track of the amount of CCM messages that are being transmitted.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 31
 3 Ethernet CFM OAM operations
3.7 Loopback

Loopback message (LBM)

MEP 101 MEP 102

PE1 PE2

Loopback response (LBR)

The Loopback IEEE 802.1ag OAM tool is used to determine whether remote
MEPs are reachable or not. The loopback tool is similar to the ICMP Ping tool
that is available in the IP suite. Explicitly generated by the provider, a
Loopback Message (LBM) is sent to the MAC of the router on which the remote
MEP resides, and from which a Loopback Response (LBR) is expected.

8 — 1 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Once enabled, the CCM provides continuous path status monitoring. Once the CCM has declared a defect (alarm
or fault condition), the service provider needs to determine where the break has occurred and then to take
action to restore service as quickly as possible.
The IEEE 802.1ag CFM includes two test utilities to help the provider locate the failure by leveraging the presence
of MEPs. These tools are the Loopback and Linktrace operations, which use OAM CFM messages to track the path
and identify where the fault has occurred.
In the slide, an eth-cfm loopback test is generated from the PE1 router targeting the MAC address associated with
the remote MEP on PE2. The MAC address can be statically assigned during the configuration procedures for the
MEP.
The IEEE 802.1ag ETH-CFM Loopback is a unicast mechanism that targets defined MAC addresses. An individual
test is required for each MEP on the service path; this makes isolating the fault location more complex.
The IEEE 802.1ag has provided an enhancement in the form of a multicast Loopback OAM test. When the
multicast parameter in used in running the test, the CFM sends an LBM to the multicast MAC 01:80:C2:00:00:3x,
where x is the domain level in which the MA is configured. In the case of a multicast Loopback OAM test, all the
MEPs respond with the MAC addresses of the NEs on which they are configured.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 32
 3 Ethernet CFM OAM operations
3.8 Generating and Verification of Loopback Tests

Generation:
oam eth-cfm loopback <mac-address> mep <mep-id> domain <md-index> association <ma-
index> send-count <send-count>

Verification:
show eth-cfm mep <mep-id> mep <mep-id> domain <md-index> association <ma-index>
loopback

8 — 1 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

show eth-cfm cfm-stack-table can be used on the destination router to retrieve the mac-address.

If the destination port is known, ‘show port x/x/x detail’ can also be used.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 33
 3 Ethernet CFM OAM operations
3.9 Linktrace

MEP 103
LTM MEP 102 LTM LTM
MEP 101 MEP 104

PE1 PE4

LTR PE2 LTR LTR

PE3

A Linktrace Message (LTM) is originated by a MEP and targeted to a peer MEP

in the same MA and within the same MD level. The Linktrace tool is similar to
traceroute in the IP suite. The peer MEP responds with a Linktrace Reply (LTR)
message after successful inspection of the LTM. The LTMs are multicast, while
the LTRs are unicast to the original source.

8 — 1 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Linktrace is the second IEEE 802.1ag OAM tool that you can use to isolate failures in the service path. Linktrace
allows the provider to determine the hop-by-hop continuity of the path from an originating MEP to a specific MAC
address on the service path. The originating message is called the Linktrace Message (LTM), and the response
message is called Linktrace Response (LTR).
All the MEPs with MAC addresses that are known by the router with the LTM-originating MEP generate an LTR. The
originating router keeps track of all the LTRs and of the hop count to be able to list the responses in the
appropriate order, simplifying the results for interpretation.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 34
 3 Ethernet CFM OAM operations
3.10 Generating and Verification of Linktrace Tests

Generation:
oam eth-cfm linktrace <mac-address> mep <mep-id> domain <md-index> association <ma-
index>

Linktrace:
show eth-cfm mep <mep-id> mep <mep-id> domain <md-index> association <ma-index>
linktrace

8 — 1 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

show eth-cfm cfm-stack-table can be used on the destination router to retrieve the mac-address.

If the destination port is known, ‘show port x/x/x detail’ can also be used.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 35
 Knowledge check

Arrange the ETH-CFM OAM configurations tasks in the correct sequence.

a) Define the MEPs as required.

b) Verify the configurations and run the tests.
c) Set the global Ethernet CFM parameters.

8 — 1 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Correct answers:
1) c
2) a
3) b

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 36
 4 Ethernet in the First Mile OAM

8 — 1 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

This section describes the OAM tools for Ethernet in the First Mile (EFM).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 37
 4 Ethernet in the First Mile OAM
4.1 EFM OAM overview

The IEEE 802.3ah Clause 57 defines the Ethernet in the First Mile (EFM) OAM sublayer,
which is a link-level Ethernet OAM mechanism. The 7705 SAR supports the EFM OAM on
Ethernet ports configured as network or access ports. The EFM OAM provides
mechanisms for monitoring link operations such as remote fault indication and remote
loopback control.

OAMPDU
EFM peer EFM peer

SAR-1 SAR-2
OAMPDU

The EFM OAM defines a set of events that may impact link operation. The
following events are supported:

Link fault—the PHY layer found a fault in the receive direction of the local DTE

Dying gasp—an unrecoverable local failure condition has occurred.

Critical event—an unspecified critical event has occurred.

8 — 1 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The EFM OAM gives network operators the ability to monitor the health of the network and to quickly determine
the location of failing links or fault conditions.
The EFM OAM provides data link layer mechanisms that complement applications that may reside in higher layers.
The OAM information is transported in frames called OAM Protocol Data Units (OAMPDU). The OAMPDUs contain
the appropriate control and status information used to monitor, test and troubleshoot EFM OAM-enabled links.
The OAMPDUs traverse a single link, being passed between peer OAM entities, and are not forwarded by MAC
clients.

The EFM OAM has the following characteristics.

•All EFM OAM, including loopbacks, operate on point-to-point links only.
•The EFM loopbacks are always line loopbacks (line Rx to line Tx).
•When a port is in loopback mode, all frames, except the EFM frames, are discarded.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 38
 4 Ethernet in the First Mile OAM
4.2 EFM OAM configuration

EFM peer EFM peer

1/1/5 1/1/7

SAR-1 SAR-2

*A:SAR-1# configure port 1/1/5 ethernet

*A:SAR-1>config>port>ethernet# efm-oam
- efm-oam

[no] accept-remote-* - Enable/disable reaction to loopback control OAMPDUs

[no] hold-time - Configure the EFM-OAM hold-time
mode - Configure EFM OAM DTE mode
[no] shutdown - Enable/disable EFM OAM operation
[no] transmit-inter* - Configure transmit interval of OAMPDUs
[no] tunneling - Enable/disable EFM OAM PDU tunneling

*A:SAR-1# configure port 1/1/5 *A:SAR-2# configure port 1/1/7

*A:SAR-1>config>port# info *A:SAR-2>config>port# info
---------------------------------------------- ----------------------------------------------
ethernet ethernet
efm-oam efm-oam
accept-remote-loopback accept-remote-loopback
transmit-interval 100 multiplier 5 transmit-interval 100 multiplier 5
no shutdown no shutdown
exit exit
exit exit
no shutdown no shutdown
---------------------------------------------- ----------------------------------------------

8 — 1 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

You need to configure the EFM OAM on an Ethernet or network port of each peer NE. The slide shows the SR-OS
CLI context for configuring EFH OAM and its parameters. You can configure the following parameters in the
config>port>ethernet# efm-oam context:
•accept-remote-loopback—this command enables reactions to loopback control OAMPDUs from peers.
•hold-time—this command sets the amount of time that EFM-OAM waits before going from a non-operational state
to an operational state.
•mode—this command configures the mode of OAM operation for the Ethernet port: active (default) or passive. An
active mode port initiates the negotiation process and continually sends out EFM OAM information PDUs. A passive
mode port waits for the peer to initiate the negotiation process, and cannot start monitoring activities (such as
loopback) with the peer.
•transmit-interval—this command configures the transmit interval of OAMPDUs.
•tunneling—this command enables EFM OAMPDU tunneling.

To enable Ethernet EFM OAM 802.3ah on the port, use the efm-oam>no shutdown command.
The slide also shows the ETH OAM configuration on the SAR-1 and SAR-2 NEs.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 39
 4 Ethernet in the First Mile OAM
4.3 EFM OAM tunneling
EFM peer 1/1/5 1/2/4 1/2/2 1/1/7 EFM peer

SAR-1 SAR-transit SAR-2

*A:SAR-transit# configure port 1/2/4 ethernet

*A:SAR-transit>config>port>ethernet# efm-oam
*A:SAR-transit>config>port>ethernet>efm-oam# tunneling
*A:SAR-transit>config>port>ethernet>efm-oam# back
*A:SAR-transit>config>port>ethernet# back
*A:SAR-transit>config>port# info
----------------------------------------------
ethernet
efm-oam
tunneling The OAMPDUs do not propagate beyond
exit a single hop. However, the SR OS supports the
exit tunneling of EFM PDUs through Epipe services.
no shutdown This is why an Epipe needs to be created and
---------------------------------------------- associated with the ETH OAM tunneling. The
…output omitted… ports configured for EFM OAM tunneling need
to be added as Null SAPs to the Epipe service.
*A:SAR-transit# configure service epipe 1002
*A:SAR-transit>config>service>epipe# info
----------------------------------------------
sap 1/2/2 create
exit
sap 1/2/4 create
exit
no shutdown

8 — 1 — 40 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The 7705 SAR supports EFM OAM tunneling on a transit router between EFM peer devices. The drawing on this
slide shows a new router, SAR-transit, introduced between SAR-1 and SAR-2. The SAR-transit router needs to be
configured for the EFM tunneling function so that SAR-1 and SAR-2 can support EFM OAM sessions.

The slide also shows the EFM tunneling configuration for port 1/2/4 of the SAR-transit router. The EFM tunneling
configuration for port 1/2/2 is identical, and has been omitted. Consider the following issues when configuring
EFM tunneling on SAR-transit:
•The EFM tunneling configuration can be applied only to access ports.
•You need to shut down the EFM OAM on SAR-1 and SAR-2 before enabling tunneling on SAR-transit.

The enabled tunneling feature on SAR-transit allows the PDUs to be mapped to Epipe services so that the OAM
frames can be tunneled over MPLS to the far end.
The slide shows the CLI output for an Epipe service created on the SAR-transit router. The ports configured for
EFM OAM tunneling have been added as Null SAPs to the Epipe service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 40
 4 Ethernet in the First Mile OAM
4.4 EFM OAM operations

*A:SAR-1# oam efm

- efm <port-id> local-loopback {start|stop}
- efm <port-id> remote-loopback {start|stop}

<port-id> : slot/mda/port
<local-loopback> : Start/stop local-loopback test on a port
<remote-loopback> : Start/stop remote-loopback test on a port

*A:SAR-1# oam efm 1/1/5 remote-loopback start

*A:SAR-1# oam efm 1/1/5 remote-loopback stop
*A:SAR-1# show port 1/1/5 statistics

===============================================================================
Port Statistics on Slot 1
===============================================================================
Port Ingress Ingress Egress Egress
Id Packets Octets Packets Octets
-------------------------------------------------------------------------------
1/1/5 669 42816 671 42944
===============================================================================

8 — 1 — 41 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

The commands to run EFM OAM operations are available in the oam efm SR-OS CLI context. The operations that
you can run are local-loopback and remote-loopback.

This slide shows the commands for starting and stopping a remote loopback operation, as well as the command to
display OAM EFM operation statistics.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 41
 4 Ethernet in the First Mile OAM
4.5 EFM OAM status
*A:SAR-1# show port 1/1/5 ethernet efm-oam

===============================================================================
Ethernet Oam (802.3ah)
===============================================================================
Admin State : up
Oper State : operational
Mode : active
Pdu Size : 1518
Config Revision : 6
Function Support : LB
Transmit Interval : 10000 ms
Multiplier : 5
Hold Time : 0
Tunneling : false
Loop Detected : false

Peer Mac Address : 9a:ce:01:01:00:04

Peer Vendor OUI : 00:16:4d
Peer Vendor Info : 00:00:00:00
Peer Mode : active
Peer Pdu Size : 1518
Peer Cfg Revision : 4
Peer Support : LB

Loopback State : None

Loopback Ignore Rx : Process
Ignore Efm State : false

===============================================================================
Ethernet Oam Statistics
===============================================================================
Input Output
-------------------------------------------------------------------------------
Information 690 691
Loopback Control 0 4
Unsupported Codes 0 0
Frames Lost 0
===============================================================================

8 — 1 — 42 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

To view the status of an EFM OAM session, use the command show port port_number ethernet efm-oam.
The slide shows a sample output for such a command.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 42
 Knowledge check

What operations are supported by the EFM OAM? Select all that apply.

a) tunneling
b) local-loopback
c) remote-linktrace
d) remote-loopback

8 — 1 — 43 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Correct answers: b) and d).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 43
 Module summary

In this module, you have learned:

What are the Ethernet OAM principles and components

What are the Ethernet CFM OAM functionality and tests

What are the EFM OAM functionality and operations

8 — 1 — 44 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

In this module, you have learned:

What are the Ethernet OAM principles and components

What are the Ethernet CFM OAM functionality and tests

What are the EFM OAM functionality and operations

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 44
End of module
ETH-OAM

8 — 1 — 45 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

OAM — ETH-OAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 8.1 Edition N/A
Section 8 — Module 1 — Page 45
Learning experience powered by
Alcatel-Lucent University

Section 9
Typical Applications
Module 1
Typical Applications
TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

9—1—1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 1
 Blank page

9—1—2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 2
 Module objectives

Upon completion of this module, you should be able to:

Describe the typical applications of the 7705 SAR.

Identify the benefits of each 7705 SAR typical application.

Define the position of the 7705 SAR in each typical application.

9—1—3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Upon completion of this module, you should be able to:

•Describe the typical applications of the 7705 SAR.
•Identify the benefits of each 7705 SAR typical application.
•Define the position of the 7705 SAR in each typical application.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 3
Module objectives [cont.]

9—1—4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 4
 Table of Contents

1 7705 SAR in the HLN 7

Page
2 OADM capabilities 9
1 7705 SAR in
3 Utility the HLN
networks 7 13
1.1 Role of 7705 SAR in the HLN 8
4 L2/L3
2 OADM business services
capabilities 9 15
2.1 7705 SAR OADM access 10
5 7705
2.2 Network transformation
SAR OADM mux/demux modules 11 17
6 Mobile backhaul
2.3 7705 SAR OADM and
typical 9500 MPR-e
deployment 12 19
3 Utility networks 13
3.1 Utilities network—the “Smart Grid” 14
4 L2/L3 business services 15
4.1 L2/L3 Business Services 16
5 Network transformation 17
5.1 Smooth network transformation 18
6 Mobile backhaul and 9500 MPR-e 19
6.1 IP/MPLS mobile backhaul transport : 2G, 3G and LTE 20
6.2 IP/MPLS mobile backhaul—complete end-to-end portfolio 21

9—1—5 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 5
Table of Contents [cont.]

9—1—6 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 6
 1 7705 SAR in the HLN

9—1—7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This section presents the role of the 7705 SAR in the High Leverage Network (HLN).

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 7
 1 7705 SAR in the HLN
1.1 Role of 7705 SAR in the HLN

A High Leverage NetworkTM

Open API
7705 SAR Open API exposure platform
framework Control Context
“Applicability Zone” Content Comms

Converged services
control
Wireless access

Aggregation and backhaul Converged backbone

Wireline access Converged edge

Devices
and users

Service-aware network management

The 7705 SAR adapts and aggregates traffic onto a modern, Ethernet-centric
infrastructure.

9—1—8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Most of today’s networks have been converged to an all-IP/MPLS network. In this way, network operators have
reduced their cost dramatically. But driven by all types of new video content the network faces an enormous
bandwidth explosion. The demand for online content is soaring and end-users have now significantly higher
bandwidth requirements and quality of experience expectations. Much of this content, which is preliminary video
is free for end users and paid by the advertisers. But for the network operator, that has to expand his network
continuously, it means an increase in both the CAPEX and OPEX.
The challenge of the network operator today is to monetize these bandwidth hungry services so that every bit is
worth its money.
The answer is building a High Leverage Network.
The HLN is a converged, scalable and intelligent all-IP network. It offers distributed service intelligence,
broadband access, scalable and efficient IP transport and at the lowest bit cost. But at the same time, it is able
to support innovative revenue generating services and business models.
The 7705 SAR is present in the aggregation and backhaul part of the HLN, where it adapts and aggregates traffic
onto a modern, Ethernet-centric infrastructure.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 8
 2 OADM capabilities

9—1—9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This section presents the OADM capabilities of the 7705 SAR.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 9
 2 OADM capabilities
2.1 7705 SAR OADM access
1 Color Optical Add/Drop 2 Color Optical Add/Drop

WEST EAST WEST EAST

λ1 West λ1 East λ1, λ2 West λ1, λ2 East

Transponder

Transponder
Transponder

Transponder

Transponder

Transponder
CWDM

CWDM
CWDM

CWDM

CWDM

CWDM
Existing GigE ports Existing GigE ports

The 1-color Optical Add/Drop card has 8 variants for SAR-8/-18 for each of the
8 colors, and 8 variants for the SAR-M for each of the 8 colors.

The 2-color Optical Add/Drop card has 4 variants for SAR-8/-18, each with a
pair of colors.

Modules support CWDM for GigE, but will also support 10GigE

9 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

An optical add-drop multiplexer (OADM) is used in wavelength-division multiplexing systems for multiplexing
and routing different channels of light into or out of a single mode fiber. The “add" and "drop" terms refer to the
capability of the device to add one or more new wavelength channels to an existing multi-wavelength WDM
signal, and/or to drop (remove) one or more channels, passing those signals to another network path. An OADM
may be considered to be a specific type of optical cross-connect.
The 7705 SAR supports different OADM plug-in cards. The difference between the cards is in the number of
wavelengths that can be added or dropped and the wavelength color.
A 1 color optical add/drop card can add and drop 1 color per direction (west and east).
A 2 color optical add/drop card can add and drop 2 colors per direction (west and east).
The 2 color optical add/drop card is available in 4 variants, and is not supported on the SAR-M. The SAR-F does
not support any OADM card, as this functionality is possible only on plug-in cards.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 10
 2 OADM capabilities
2.2 7705 SAR OADM mux/demux modules

Mux/Demux 4p Mux/Demux 8p

Expansion LINE LINE

λ1-λ4 λ1-λ8

The 4-color OADM card has two variants: one for the upper 4 and one for the
lower 4 colors.

The 8-color optical card can either drop or add all colors at once.

Modules support CWDM for GigE but will also support 10GigE

9 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

The 4- and 8-color optical OADM mux/demux variants are also available.
•The 4-color OADM card has two variants: one for the upper 4 and one for the lower 4 colors.
•The 8-color optical card can either drop or add all colors at once.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 11
 2 OADM capabilities
2.3 7705 SAR OADM typical deployment
7705 SAR-8 7705 SAR-8 7705 SAR-8

7705 SAR-8

7705 SAR-M

7705 SAR-8
7705 SAR-8/18

7705 SAR-8 7705 SAR-8 7705 SAR-8

There are two attachment types:

•Main termination site with 7705 SAR-18/-8, which optically terminates all
colors using 4- or 8-color mux/demux cards
•Intermediate OADM sites with SAR-8 or SAR-M NEs using the OADM cards..

9 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

At intermediate sites, there are add and drop specific colors for traffic in both directions, to be processed by the
router in that location. An intermediate site also provides optical express lane for all other colors.
The application is engineered for optical power budget, based on the CWDM transceiver, fiber type/distance,
OADM attenuation, and other factors.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 12
 3 Utility networks

9 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This section presents the 7705 role in utility networks.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 13
 3 Utility networks
3.1 Utilities network—the “Smart Grid”
Corporate HQ / NOC
Internet

Omni PCX SCADA

7705 SAR
7750 SR
5620 SAM

RTU
Power E&M
Generation ERP
TPR
LMR
IP/MPLS NOC

7705 SAR
Network

Substation
IED WiFi TDM Camera

Issues & Opportunities Value Proposition Differentiators & Credentials

• Need to reliably support crucial • Reliable and resilient support of • Deep corporate understanding of
legacy services e.g. SCADA, legacy and advanced services major strategic industry segments
Teleprotection • All networking infrastructure • Compact and ‘green’ platforms
• Opportunity to modernize the models supported – point to point, • Non-stop services and resilient,
infrastructure for capacity and Layer 2 and 3 VPNs flexible topologies
more efficient operations
• Two-time winner of UTC: “Best
Telecom Equipment “ Award

9 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Communications network transformation to a highly available IP/MPLS infrastructure for

mission-critical communications is fundamental to the Smart Grid architecture.
The implementation of Smart Grids is part of the new energy delivery strategy of many
power utilities around the world. Smart Grid applications provide utilities with better
automation and the benefits of reduced operating costs, increased power quality, and
improved outage response.
The Alcatel-Lucent 7705 solution supports the critical legacy services like SCADE and tele-
protection, while transporting these legacy and advanced applications over a reliable and
resilient IP/MPLS network.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 14
 4 L2/L3 business services

9 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This section describes the 7705 SAR support for L2/L3 business services.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 15
 4 L2/L3 business services
4.1 L2/L3 Business Services

VPRN
VPLS

VLL
5620 SAM

7705 SAR 7750 SR

Ch T1/E1 7705 SAR
Ch STM-1/OC-3

IP/MPLS
DS3 Network Ch T1/E1

7705 SAR 7705 SAR

PBX

Issues & Opportunities Value Proposition Differentiators & Credentials

• Common service model for private • Strong heritage in SR-OS based
• Existing data delivery networks are line data services (TDM, ATM, FR
reaching their product End of Life. Multiservice edge deployments
and PPP).
• Private line services are still needed • 7705 SAR is a uniquely modern
• Extend the model to deliver Layer product that support both
but IP and Ethernet centric services 2 and Layer 3 business services
are becoming the focus for new traditional private line and full,
revenue • Common infrastructure used to any-to any VPN services
establish a variety of services for
multi-generational technologies.

9 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

The Private Line Business Services represent a market that operators need to address. These services are typically
point-to-point TDM circuits that deliver secure, predictable and fixed bandwidth applications from small offices
or remote locations to office headquarters for voice and data services. As IP/MPLS network technologies mature,
they deliver the same quality of experience as the existing TDM network infrastructure with the same level of
predictability but at a reduced cost of ownership.
The 7705 SAR is a modern product that supports both traditional private lines and full L2/L3 VPN services.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 16
 5 Network transformation

9 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This section presents the role of the 7705 SAR in the larger context of network transformation.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 17
 5 Network transformation
5.1 Smooth network transformation
7750 SR
BRAS
VoIP 7705 SAR-18 &IPTV
CPE HSI STM-1
GigE/
10GigE
….
MESN
ATM 7750 SR
CPE DSLAM
GigE
7750 SR
…. BTV IP DSLAM CO
VoD
VoIP
HSI

Issues & Opportunities Value Proposition Differentiators & Credentials

• Uplink is a bottle-neck, but • 7705 SAR-18 addresses the balance •The 7705 SAR is unique in its
upgrading the ATM infrastructure transformational capability as it is a
between leveraging existing
is not a strategic investment.
investment in ATM DSLAMs while modern, compact IP/MPLS platform
• Operator wants to leverage sunk yet supports legacy interfaces.
investment in ATM DSLAMs but allowing for a strategic transition
establish a future-oriented towards Ethernet uplinks. • The 7705 SAR allows leverage of
infrastructure in networking
existing assets while investing for a
future-oriented architecture.

9 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Operators need to decide how to transform existing networks from SDH/SONET to MPLS, and how to effectively
serve their end customers. Operators are faced with changing network technologies in conjunction with a move
toward service-based applications. Their main goal is to reduce the operating cost and capital expenditures. At
the same time, the existing TDM networks are reaching the end of their lifecycle and need to be replaced. In this
context, operators need to consider how to leverage the new IP/MPLS network technology when migrating legacy
systems and services.
The 7705 SAR-18 addresses the balance between leveraging existing investment in ATM DSLAMs while allowing for
a strategic transition towards Ethernet uplinks.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 18
 6 Mobile backhaul and 9500 MPR-e

9 — 1 — 19 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This section describes the mobile backhaul 7705 SAR application with 9500 MPR-e.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 19
 6 Mobile backhaul and 9500 MPR-e
6.1 IP/MPLS mobile backhaul transport : 2G, 3G and LTE

BTS / 5620 SAM

Ethernet Carrier RNCs, BSCs,
NodeB/ Gateways

eNodeB Ethernet (MPLS)

OC3ch
T1/E1 TDM 7750 SR
Ethernet/DSL/GPON STM1ch
GSM or IP Network
BTS ATM/IMA Ethernet

NodeB (nxT1/E1) ATM

7705 SAR
(OC3/STM1)
nxT1/E1/DS3/STM-1
CDMA ILEC or Microwave
ML-PPP
BTS
TDM Network

Issues & Opportunities Value Proposition Differentiators & Credentials

• Cost effective transport of all
End to end MPLS OAM tool kit
• Massively growing traffic especially
generations of mobile traffic today
Deployed in over 65 LTE & LTE-
data
• Building a strategic infrastructure ready IP/MPLS backhaul networks
• Need to consolidate multiple
Flexible, accurate synchronization
for Long Term Evolution
generations of mobile base
stations • All networking infrastructure
Any access media
models supported – point to point,
Heavy Reading: “ Best backhaul
• Need to carry traffic over the most equipment footprint with those
Layer 2 and 3 VPNs
cost effective uplink media : operators that will be the first to
optical , copper, microwave launch LTE”

9 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

With mobile networks evolving to mobile broadband, MPLS is being deployed by many mobile service providers to
consolidate disparate transport networks for different radio technologies, reduce operating expenditures (OPEX)
and converge on a resilient and reliable infrastructure. This infrastructure is ready for further mobile evolution to
Fourth-Generation Mobile Network (4G) technologies such as Worldwide Interoperability for Microwave Access
(WiMAX) and Long Term Evolution (LTE) and full fixed-mobile convergence (FMC).
The Alcatel-Lucent IP/MPLS solutions for mobile service providers allow creating cost-effective mobile and
converged network architectures intended for voice, video and data delivery that can be leveraged as the
existing mobile networks evolve to an LTE-based network architecture.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 20
 6 Mobile backhaul and 9500 MPR-e
6.2 IP/MPLS mobile backhaul—complete end-to-end portfolio

Packet
Core

ANY ACCESS, ANY

SCALE BACKHAUL

Performance, Affordability, Resiliency,

Manageability, Adaptability, Scalability, Security 5620 SAM

9 — 1 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Alcatel-Lucent has a complete end-to-end portfolio for IP/MPLS mobile backhaul applications.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 21
 7705 SAR with 9500 MPR-e

Packet MW Card (PMC)

Sync over copper

2+0 Cross-
Polarization

Power Injector Card

(PIC)

f1h

Gigabit MW Link
@ 70/80 GHz
f1v

IP/MPLS Enabled
Microwave

9 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

The 7705 SAR has 9500 MPR-e integrated PIC (Power Injector Card) and PMC (Packet MW Card) cards.
The 9500 MPR facilitates legacy-to-packet transformation over a common, converged packet network. It also
offers the highest functionality with the smallest footprint, addresses any network topology, and is highly
scalable and resilient.
The 9500 MPR is ideally suited to address the needs of mobile backhaul, energy, transportation, and public sector
communications and last-mile service access.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 22
 7705 SAR with 9500 MPR-e
.1 IP/MPLS and microwave integration in the 7705 SAR

Edge
Power Injector Card Packet MW Card (PMC)
(PIC) Sync over copper
9500 MPR-e

IP/MPLS microwave links

Resilient Ring/mesh/linear topologies
9500 MPR
in mixed fiber-microwave networks: TE,
FRR, PW redirection etc

Resilient Synchronization Eth
site

Powerful e2e OAM tools across all 9500 MPR-e 7705 SAR
9500 MPR
interfaces

Common e2e service management:
5620 SAM 5620 SAM

Best cost and performance in all

scenarios 9500 MPR-e

Common Radio throughout the 9500 MPR-e

network (less CAPEX and OPEX)

Reduces amount of deployed indoor 7705 SAR
equipment at each site (less CAPEX)

E2e common OAM procedures and
protection over microwave and fixed
media (less OPEX) 7705 SAR 7705 SAR

Low power consumption at each site 7705 SAR
(less OPEX) Backbone

9 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

The Alcatel-Lucent 9500 MPR was designed with packet technology as its foundation to provide the lowest
total cost of ownership at the highest quality. Now the 7705 SAR has integrated 9500MPR packet microwave
cards and power injector cards.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 23
 7705 SAR with 9500 MPR-e
.2 Integrating Power Injector Card (PIC) into 7705 SAR-8/18
•Occupies one slot in the SAR-8/18 chassis
•Power sup to two 8500 MPR-e devices
•Provides lightning protection/voltage surge
•Injects power transparently onto 1000BT To power a node with 6 MW directions:

•Retains synchronization Battery-based PIC-based

Solution Solution
•No Ethernet frame regeneration
Need 2 VU to host Integrated into
Rack Space two PIBs chassis
MPT-HCv2

Need 6 extra No extra battery

# Battery Feeds battery feeds (2 feeds
per PIB)

CSM CSM
……
in out

Eth/PMC card Data over electrical PIC

9 — 1 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This slide describes the integration of the Power Injector Card (PIC) into the 7705 SAR-8/18.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 24
 7705 SAR with 9500 MPR-e
.3 ALU 7705 SAR microwave solution

7705 SAR 7705 SAR

(1+0, 2+0, N+0)

9500 MPR-e 9500 MPR-e

5620 SAM

End-to-End Element, Network and Service Management across IP and

Microwave domains:
•Point-and-click service provisioning end-to-end
•End-to-end fault management: ability to consolidate and customize alarm
classification, correlate alarms to backhaul services, initiate trouble shooting
•End-to-end performance management: collect and plot network performance
data.

9 — 1 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

This slide describes the ALU 7705 SAR microwave solution, which implements direct connectivity of 7705 SAR to
the 9500 MPR-e (standalone ODU).
This is a greener solution with reduced IDU footprint and power consumption, providing the following advantages:
•high availability for L1, L2 and L3 services
•integrated End-to-End network synchronization over Microwave, IP and third-party transport

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 25
 Knowledge check

Answer the following questions.

1) In which part of an HLN network is the 7705 SAR typically present?

2) In what type of the 7705 SAR product can the OADM modules be
installed?
3) Which of the following interfaces are supported on the 7705 SAR?
Select all that apply.
a) E&M
b) RS-232
c) ML-PPP
d) ATM
e) Packet Microwave

9 — 1 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Correct answers:
1) aggregation and backhaul
2) SAR-M, SAR-8 and SAR-18
3) a, b, c, d, e

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 26
End of module
Typical Applications

9 — 1 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Typical Applications — Typical Applications
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 9.1 Edition N/A
Section 9 — Module 1 — Page 27
Learning experience powered by
Alcatel-Lucent University

Section 10
Service Aware Manager
Module 1
5620 SAM
TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
7705 SAR
R6.0 Strategic Industries
TER36055_V3.0-SG Edition 1

10 — 1 — 1 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 1
 Blank page

10 — 1 — 2 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 YYYY-MM-DD Last name, first name First edition

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 2
 Module objectives

Upon completion of this module, you should be able to:

Describe the major components of the 5620 SAM.

List the 5620 SAM modules.

Configure Cpipe and Epipe services in the 5620 SAM.

Make and distribute policies.

Identify Ethernet OAM tools supported by the 5620 SAM.

10 — 1 — 3 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Upon completion of this module, you should be able to:

•Describe the major components of the 5620 SAM.
•List the 5620 SAM modules.
•Configure Cpipe and Epipe services the 5620 SAM.
•Make and distribute policies.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 3
Module objectives [cont.]

10 — 1 — 4 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This page is left blank intentionally

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 4
 Table of Contents

1 Introduction 7
Page
2 5620 SAM platform 11
1 Introduction
3 Modularity 7 18
1.1 Alcatel-Lucent 5620 Service Aware Manager (SAM) 8
4 Alcatel-Lucent
1.2 Launching management
the 5620 SAM GUI client 9 29
1.3 Alcatel-Lucent management architecture 10
5 Epipe
2 5620 SAM configuration
platform 11 38
6 Cpipe types
2.1 Platform configuration 12 55
2.2 Main server 13
7 Database
2.3 QoS 14 73
2.4
8 GUI clientdistribution
Policy 15 85
2.5 Redundancy overview 16
9 Redundancy
2.6 Ethernet OAM tools servers
and auxiliary 17 104
3 Modularity 18
10Modularity
3.1 Ethernet CFM OAM
overview 19 106
3.2
11License
EFM OAMKey Filediagnostics 20 115
3.3 SAM-E (Element Management) 21
3.4 SAM-P (Provisioning Management) 22
3.5 SAM-A (Assurance Management) 23
3.6 SAM-O (Operating Support System OSS Interface) 24
3.7 SAM-S (Supervision Module) 25
3.8 Mobile Services Package 26
4 Launching the 5620 SAM GUI client 29
4.110GUI
—1—5
client overview 30
4.2Service
Using a desktop
Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries
icon
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
31
4.3 Using a web browser 32
4.4 Using the CLI 33
4.5 Login window 34
4.6 Client software update 35
5 Epipe configuration 38
5.1 Access port configuration 39
5.2 Epipe service creation 40
5.4 View service topology 42
5.5 Adjust network port MTU value 43
5.6 Verify operational state 44
5.8 Epipe service creation—point-and-click method 46
5.10 Epipe site creation—point-and-click method 48
5.12 Access interface creation—point-and-click 50
5.13 Spoke SDP binding creation—point-and-click 52
6 Cpipe configuration 55
6.1 Cpipe configuration workflow 56
6.2 Access port configuration 57
6.3 Access port configuration: E1 unstructured (part 1) 58
6.4 Access port configuration: E1 unstructured (part 2) 59
6.5 Access port configuration: E1 unstructured (part 3) 60
6.6 Access port configuration: E1 unstructured (part 4) 61
6.7 Access port configuration: G.704 CRC (E1) [part 1/5] 62
6.8 Access port configuration: G.704 CRC (E1) [part 2/5] 63
6.9 Access port configuration: G.704 CRC (E1) [part 3/5] 64
6.10 Access port configuration: G.704 CRC (E1) [part 4/5] 65
6.11 Access port configuration: G.704 CRC (E1) [part 5/5] 66
6.12 Customer configuration 67
6.13 Cpipe service configuration 68
6.14 SDP bindings 71
6.15 Disabled SDP signaling 72
7 QoS 73
7.1 SAP ingress menu 74

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 5
 Table of Contents [cont.]

Page

7.2 SAP ingress policy—General 75

7.3 SAP ingress policy—General (Apply) 76
7.4 Dot1p 77
7.5 DSCP 78
7.6 IP Match Criteria 79
7.7 Queues 80
7.8 Forwarding classes (FC) 81
7.9 Relations 82
7.10 Tree view 83
7.11 SAP ingress policy 84
8 Policy distribution 85
8.1 Policy search 86
8.2 Local policy definitions 87
8.3 Policy distribution 88
8.4 Policy distribution verification 90
8.5 Policy distribution verification at the CLI 91
8.6 Policy audit 92
8.7 Policy Management93
8.8 Policy audit—General 94
8.9 Policy audit—Global Policy Selection 95
8.10 Policy audit—alarm information 96
8.11 Policy
10 — 1 — 6
synchronization preparation97
8.12 Policy
Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries
synchronization98
COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

8.13 Policy management99

8.14 Policy release 100
8.15 Policy distribution 101
8.16 Policy distribution verification in GUI 102
8.17 Policy distribution verification in CLI 103
9 Ethernet OAM tools 104
9.1 Ethernet OAM tools—general 105
10 Ethernet CFM OAM 106
10.1 Ethernet CFM test support 107
10.2 CFM OAM components 108
10.3 Configuring Ethernet CFM 109
10.4 Creating an Ethernet CFM test policy 110
10.5 Creating an Ethernet CFM test suite 111
10.6 Executing an Ethernet CFM test suite 112
10.7 Viewing results of an Ethernet CFM test suite 113
11 EFM OAM diagnostics 115
11.1 EFM OAM test support 116
11.2 EFM OAM diagnostic configuration—open 802.3ah form 117
11.3 EFM OAM diagnostic configuration parameters 118
11.4 EFM OAM diagnostics 119
11.5 EFM OAM diagnostic results—Statistics 120
11.6 EFM OAM diagnostic results—Peer Information 121

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 6
 1 Introduction

10 — 1 — 7 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This section introduces the 5620 Service Aware Manager and its management portfolio.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 7
 1 Introduction
1.1 Alcatel-Lucent 5620 Service Aware Manager (SAM)
Integrated Element, Network
and service
Management in one unified Device,
platform network and
routing
configuration

Accelerate Network Third-party

Service
device
& Service Provisioning integration
provisioning

Scalable and Secure

Architecture 5620
Service Aware
Open north- Manager (SAM) Fault
bound
management
interfaces

Scalability & Performance

Security management

10 — 1 — 8 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service
8 | Maximizing
Aware Manager
Operational
— 5620
Efficiency
SAM with 5620 SAM
7705 SAR — R6.0 Strategic Industries

The Alcatel-Lucent 5620 Service Aware Manager (SAM) allows network operators to perform integrated element,
network and service management in one unified platform.
 Accelerated Network & Service Provisioning
 Simplified point and click end-to-end Provisioning
 Wizards can guide operators step-by-step through complex tasks
 Automation reduces configuration steps and risk of errors
 Reliable Network & Service Assurance
 Proactive assurance identifies issues before they become customer-affecting
 Rapid problem detection, isolation and resolution
 Operational Fit & Flexibility
 Rapid, cost-effective integration with existing OSS systems and portals
 Scalable, secure Architecture
 Modular and redundant architecture supports the largest networks
 Comprehensive user security for command scope and span of control

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 · Module 1 · Page 8
Section 10 — Module 1 — Page 8
 1 Introduction
1.2 Alcatel-Lucent management
• Accelerated Network & Service Provisioning
5620 SAM • Reliable Network & Service Assurance
• Scalable, secure Architecture
• Operational Fit & Flexibility

10 — 1 — 9 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM is the Management solution for

 Core routers with the 7950 XRS family (eXtensible Routing System): core router for the
100G era and beyond
 Service routers with the 7750 SR family (Service Router)
 Optical Network element with the 1830 PSS Family (Photonic Service Switch)
 Microware equipment with 9x00 MPR/MSS family (Microwave Packet Radio/ Multi
Service Switch)
 Service access Switches with the 720 SAS family (Service Access Switch)
 Metro Ethernet Service Switches with 7450 ESS family (Ethernet Service switch)
 Backhaul and Aggregation equipment the the 7705 SAR family (Service Access Router)
 Enterprise Switches with OS family (Omni Switch)
 Wireless Packet Core including the 7750 SR MG (Media Gateway) 9471 WMM (acting as
MME/SGSN) and 5780 DSC
 Wireless LTE RAN with the various eNodeB

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 9
 1 Introduction
1.3 Alcatel-Lucent management architecture

Network Dynamic Application

OSS / BSS access control service control admission control
and service portals
OSS Connected Partner Program

Portal Development Service

5750 SSC / 5780 DSC
Policy-driven framework

5670 RAM Layer 4 to 7

Application Triple play/
intelligence services
Rapid residential
provisioning Layer 2 and 3
5650 CPAM Business
services
Control plane Reliable services
management
assurance
MPLS paths
Metro
and service tunnels
5620 SAM Operational aggregation
Service efficiency
management
IP routing protocols Enterprise
MPLS End-to-end
infrastructure
networks
scalability
Physical Physical network
infrastructure Mobile
infrastructure

10 — 1 — 10 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service
10 Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide describes the Alcatel-Lucent Management Architecture

 5620 SAM (Service Aware Manager) : The 5620 SAM enables operational efficiency for IP/MPLS networks by
providing comprehensive element, network, service-aware and application-aware management capabilities in
one unified platform.
 5650 CPAM (Control Plane Assurance Manager)
The 5650 CPAM is a route and path analytics tool that is tightly integrated with the 5620 SAM to provide highly
effective control plane assurance for Interior Gateway Protocol (IGP) and Border Gateway Protocol (BGP)
routing, Multi-Protocol Label Switching (MPLS), multicast, and layer 2 and layer 3 services.
 5670 RAM (Reporting and Analysis Manager)
The 5670 RAM gives service providers the query and analysis capabilities they need to explore IP/MPLS traffic
flows, application usage trends, and application performance. With this approach, service providers can ensure
a positive customer experience, sustained revenue growth and operational flexibility while increasing profits.
 5750 SSC (Subscriber Services Controller)
The Alcatel-Lucent 5750 SSC is a flexible, modular and pre-integrated subscriber and policy management
solution. As the controller for residential broadband services, the 5750 SSC enables service providers to deliver
innovative services such as enhanced high-speed Internet, bandwidth on -demand, metered services, IPTV,
video on-demand and VoIP to their existing customer base, as well as to attract new customers. It plays a key
role in three key areas of residential service delivery: network access control, dynamic service control and
service admission control.
 A web-based application, the Service Portal features a lightweight, framework architecture, enabling rapid,
cost-effective implementation. The framework-based design also makes the Service Portal easy-to-use and
allows the application to be tailored to the exact needs of customers by using their particular predefined rules,
network architecture and live-network information. Such an exceptional operational fit preserves investment in
existing service architectures, processes, systems and workflows while streamlining operations.
 The Service Portal can support an operator’s in-house OSS applications as well as third-party OSS solutions.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 10
 2 5620 SAM platform

10 — 1 — 11 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This section provides a high-level description of the 5620 SAM platform.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 11
 2 5620 SAM platform
2.1 Platform types
GUI Client Main Server Auxiliary Server

GUI Clients

IP

Client Delegate Database

10 — 1 — 12 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Five types of platforms can be present in a 5620 SAM Release deployment:

 5620 SAM Main Server

 5620 SAM Database

 5620 SAM Graphic User Interface (GUI) Client workstation(s)

 5620 SAM Client Delegate workstation(s)

 5620 SAM Auxiliary Server (Statistics Collector and Call Trace Collector)

The 5620 SAM supports co-location of the 5620 SAM Server and 5620 SAM Database software on a single
workstation.
5620 SAM also supports a distributed deployment, whereby the 5620 SAM Server and the 5620 SAM Database
software components are installed on two different workstations.
5620 SAM supports the distribution of statistics collection and the collection of call trace information. A 5620 SAM
Auxiliary can be configured for statistics collection or for call trace collection. It cannot be configured to perform
both functions.
5620 SAM supports redundancy of the 5620 SAM Server, 5620 SAM Database, and 5620 SAM Auxiliary workstations.
This can be achieved with the 5620 SAM Server and Database being in a collocated or distributed configuration.
The 5620 SAM Auxiliary can also be installed in a redundant configuration, but cannot be collocated on the same
workstation with a 5620 SAM Server or 5620 SAM Database.
A 5620 SAM Auxiliary Statistics Collector must be installed on an independent workstation to reduce the burden of
statistics handling from the 5620 SAM Server. The 5620 SAM Auxiliary Statistics Collector workstation can only be
configured in a 5620 SAM distributed deployment.
A 5620 SAM Auxiliary Call Trace Collector must be installed on an independent workstation to collect the call
trace information from eNodeB network elements.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 12
 2 5620 SAM platform
2.2 Main server

 Java-based network management

processing engine
 Includes:

application server

web server

protocol stack

database adaptor
 Supported on Solaris and RHEL (Red
5620 SAM Main Server Hat Enterprise Linux)

10 — 1 — 13 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM Main Server is a network management processing engine, which is written in Java and runs on the
Solaris platforms. The server includes several third-party components, such as an application server, web server,
protocol stack set, and database adaptor.
The 5620 SAM Main Server functionality can be distributed across multiple physical platforms in a standalone or
redundant 5620 SAM configuration. The 5620 SAM Main Server in a cluster is the network-management engine that
processes GUI and OSS client requests and monitors the network elements.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 13
 2 5620 SAM platform
2.3 Database

 Customized Oracle database

 Provides persistent storage of
network data
 Supported on Solaris and RHEL
5620 SAM database

10 — 1 — 14 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM Database is a customized Oracle relational database that provides persistent storage for the
network data.
5620 SAM Release supports a distributed deployment, whereby the 5620 SAM Main Server and the 5620 SAM
Database software components are installed on two different Solaris workstations. In such case, the database
must run on the same platform as the 5620 SAM Main Server software.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 14
 2 5620 SAM platform
2.4 GUI client

 Java-based client that provides a

graphical interface for network
operators
 May be installed on workstations
running different operating systems
from the 5620 SAM Main Server and
5620 SAM Database
 Supported on Solaris, RHEL, and
Windows
5620 SAM GUI Client

10 — 1 — 15 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM GUI Client Workstation (s) is a Java-based client that provides a graphical interface for network
operators.
The 5620 SAM GUI Client software may be installed on workstations running different operating systems from the
5620 SAM Main Server and 5620 SAM Database. For example, the 5620 SAM Main Server, 5620 SAM Auxiliary and
5620 SAM Database software can be installed on Solaris or RHEL workstations while the 5620 SAM Clients are
installed on a Windows platform. The 5620 SAM Client can be installed on Solaris, RHEL, or Windows.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 15
 2 5620 SAM platform
2.5 Redundancy overview

5620 SAM 5620 SAM

active server standby server

IP

Microwave Transport

9500 MPR 9500 MPR

7705 SAR 7705 SAR
IP / MPLS 7750 SR

Automatic transfer of
7450 ESS
7450 ESS
network data to Standby
1830 PSS 1830 PSS 7750 SR
Metro Optical Transport
Protects against:
Managed Network

software failure

hardware failure

connectivity problems

10 — 1 — 16 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

You can deploy a 5620 SAM system in a redundant configuration to provide greater fault tolerance by ensuring
that there is no single point of software failure in the 5620 SAM management network. A redundant 5620 SAM
deployment consists of the following components:
• primary and standby 5620 SAM main servers
• primary and standby 5620 SAM databases

The current state of a component defines the primary or standby role of the component. The primary main server
actively manages the network and the primary database is open in read/write mode. When a standby component
detects a primary component failure, it automatically changes roles from standby to primary. You can also
change the role of a component using the 5620 SAM client GUI or a CLI script. The 5620 SAM supports collocated
and distributed system redundancy. A collocated system requires two stations that each host a main server and
database. A distributed system requires four stations that each host a main server or database. Each main server
and database is logically independent, regardless of the deployment type.
The primary and standby main servers can communicate with the redundant databases, and periodically verify
server redundancy. If the standby server fails to reach the primary server within 60s, the standby server becomes
the primary server. A 5620 SAM database uses the Oracle DataGuard function to maintain redundancy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 16
 2 5620 SAM platform
2.6 Redundancy and auxiliary servers
5620 SAM GUI Clients

Geographic Location A Geographic Location B

5620 SAM Database 5620 SAM Database

Active Standby
Oracle DataGuard

5620 SAM Main Server 5620 SAM Main Server

Active Standby

5620 SAM Auxiliary 5620 SAM Auxiliary

Preferred for the Active Server Preferred for the Standby Server
Reserved for the Standby Server Reserved for the Active Server
Managed
Network

10 — 1 — 17 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

In customer networks where the statistics collection requirements exceed the scalability capabilities of a 5620
SAM Main Server, a 5620 SAM Auxiliary Server can be used. As with other high availability components, 5620 SAM
Auxiliary can be configured to be redundant. Each 5620 SAM Main Server can be configured to have one preferred
and one reserved 5620 SAM Auxiliary.
In the figure above, there are 2 workstations that are configured as 5620 SAM Auxiliary Servers. The role of the
5620 SAM Auxiliary is dependant and configured on the 5620 SAM Main Server that is active. In both geographic
locations, the 5620 SAM Main Server would consider the 5620 SAM Auxiliary in its geographic location to be the
preferred. The 5620 SAM Auxiliary in the opposite geographic location would be considered to be reserved. In the
this scenario, if the 5620 SAM Auxiliary for the active 5620 SAM Main Server were to no longer be available, the
active 5620 SAM Main Server would use the reserved 5620 SAM Auxiliary in the opposite geographic location to
collect statistics.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 17
 3 Modularity

10 — 1 — 18 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This section describes the 5620 SAM modular implementation.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 18
 3 Modularity
3.2 License Key File

10 — 1 — 20 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM functional software modules are enabled or disabled according to the 5620 SAM License Key file.
The image above shows an example of a SAM Licence form viewed using the SAM GUI.
As of R10.0 the 5620 SAM requires a license file, rather than a license key string value used in previous SAM
releases.

Alcatel-Lucent supports 5620 SAM license generation using the UUID or host ID as the system ID of
an x86-based station, or the host ID as the system ID of a SPARC-based station.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 20
 3 Modularity
3.3 SAM-E (Element Management)

CLI access to managed devices

Equipment Management
& Navigation

Alarm Policy
management

Real-time
equipment statistics

10 — 1 — 21 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The SAM-E module is the basic component of the 5620 SAM and is required for all other modules to function.
The SAM-E module provides:

 CLI access to managed devices

 device mediation, equipment management and navigation
 alarm policy management
 real-time equipment statistics
 security
 backup and restore, and
 inventory and reporting

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 21
 3 Modularity
3.4 SAM-P (Provisioning Management)

Protocol Management

Network Tunnel and

Path Management

Service Provisioning

Customer
Management

10 — 1 — 22 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The SAM-P module is an optional component of the 5620 SAM and provides functions that deal with service
provisioning.

Functions
The SAM-P module provides:

network protocol configuration and management

network tunnel and path management
subscriber management
policy management, and
templates

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 22
 3 Modularity
3.5 SAM-A (Assurance Management)

Fault Correlation
using alarms

Topology Views

P i ng OAM troubleshooting
tools

Statistics and Accounting

Policies & Data

10 — 1 — 23 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The SAM-A module is an optional module of the 5620 SAM and provides service assurance functions.
The SAM-A module provides the following functions:

topology views
fault correlation using alarms
OAM tools
statistics policies and data, and
accounting policies and data

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 23
 3 Modularity
3.6 SAM-O (Operating Support System OSS Interface)

OSS
Applications
XML interface

SOAP encoding

HTTP

5620 SAM Server

HTTPS

10 — 1 — 24 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM-O is a 5620 SAM module that provides an XML interface to the 5620 SAM through which an OSS
client application can perform the following tasks:
configure or retrieve 5620 SAM network management information
manipulate managed objects
receive event notifications from the 5620 SAM server using a persistent or non-persistent JMS connection

A 5620 SAM-O client sends an XML-encoded, SOAP-enabled message to a port on the HTTP or HTTPS server that
runs on a 5620 SAM main server. The default HTTP port for incoming messages is 8080. An XML application at port
8080 parses the SOAP XML message and sends the request to the 5620 SAM.

5620 SAM-O client

The 5620 SAM-O client implementation can range from a CLI to a third-party application. The format for the
client user interface varies with the function of the client application; for example, rolling up statistics into a
third-party billing application. The 5620 SAM-O clients function the same way regardless of the front-end
implementation: XML scripts are posted to the 5620 SAM server using an HTTP client.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 24
 3 Modularity
3.7 SAM-S (Supervision Module)

Web-based application
Summarized, at-a-glance view of NEs
and objects in the managed network

Configuration and
launch from GUI client

KPI history timers

Supervision Groups
Group and monitor
network resources Summary Views

Subtending network
Supervision Web Portal
management system interfaced
with the 5620 SAM

10 — 1 — 25 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM Supervision Module is a web-based application that provides a summarized, at-a-glance view of NEs
and objects in the 5620 SAM network. The 5620 SAM-E module includes five 5620 SAM-S licenses, with the option
to purchase additional licenses.

The Supervision module can be used to group and monitor network resources that are natively managed by the
5620 SAM or by a subtending network management system that is interfaced with the 5620 SAM for supervision
purposes.

In order to use the 5620 SAM Supervision Module, the following components must be configured on the 5620 SAM
client GUI from which the module will be launched:
1. Configure KPI history timers
2. Configure supervision groups
3. Configure summary views that include supervision groups

After configuration of the components, operators can launch the Supervision Portal from the 5620 SAM GUI client
by selecting the Application>Supervision Portal command.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 25
 3 Modularity
3.8 Mobile Services Package

5620 SAM LTE NEs components and EPS interfaces that are
managed in a typical LTE network
User Equipment

LTE RAN Evolved Packet Core (All-IP)

9471 WMM 5780 DSC

(PCRF)
7750 MG SGW 7750 MG PGW
eNode B

End-to-end IP management of 5620 SAM LTE

5620 SAM
10 — 1 — 26 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM LTE (Long Term Evolution) NE management solution focuses on the equipment, configuration, fault,
and state management of the ePC (Evolved Packet Core) NEs, LTE interfaces, and mobile services that are used
for mobile backhaul.

The 5620 SAM LTE NE management solution also supports the correlation of the LTE interfaces and mobile
services with the underlying network transport layer to provide enhanced multi-layer monitoring and
troubleshooting capabilities.

The 5620 SAM LTE NE management solution is comprised of the following components:
 5620 SAM
 5620 SAM LTE ePC
 7750 MG SGW
 7750 MG PGW
 9471 WMM
 5780 DSC
 5620 SAM LTE RAN (also known as the eUTRAN)
 eNodeB

The LTE RAN is the next generation of wireless broadband technology as outlined by the 3GPP and is the radio
access component of the LTE solution. The eNodeB is the key NE of the LTE RAN and is the physical radio link
between UE and the LTE ePC network. The eNodeB provides functions that include radio resource management,
interfaces between eNodeB devices and to ePC devices, IP header compression, and bearer level control. The
5620 SAM is the OAM system that manages the eNodeB.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 26
 Questions

?
10 — 1 — 27 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM-E is the base component of the 5620 SAM software.
a. True
b. False

Network protocol configuration and management is provided by which of the 5620 SAM software components?
a. 5620 SAM-E
b. 5620 SAM-P
c. 5620 SAM-A
d. 5620 SAM-O
e. 5620 SAM-S
f. 5620 SAM LTE

The 5620 SAM-A component of the 5620 SAM software provides which of the following functions?
a. Topology views
b. OAM troubleshooting tools
c. Statistics and accounting policies and data
d. All of the above

The 5620 SAM-O component of the 5620 SAM software provides open systems interface to the 5620 SAM managed
network?
a. True
b. False
Copyright © 2014 Alcatel-Lucent. All Rights Reserved.
TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 27
 Answers

Switch
The 5620 SAM-E is the to notesofview!
base component the 5620 SAM software.
a. True

b. False

Network protocol configuration and management is provided by which of the 5620 SAM software components?
a. 5620 SAM-E
b. 5620 SAM-P

c. 5620 SAM-A
d. 5620 SAM-O
e. 5620 SAM-S
f. 5620 SAM LTE

The 5620 SAM-A component of the 5620 SAM software provides which of the following functions?
a. Topology views
b. OAM troubleshooting tools
c. Statistics and accounting policies and data
d. All of the above

10 — 1 — 28 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM-O component of the 5620 SAM software provides open systems interface to the 5620 SAM managed
network?
a. True

b. False

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 28
 4 Launching the 5620 SAM GUI client

10 — 1 — 29 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 29
 4 Launching the 5620 SAM GUI client
4.1 GUI client overview

Provides access to the 5620 SAM main

server and to the managed network

GUI Client launch

Desktop Icon

Web Browser

5620 SAM GUI Client CLI

Supported on Unix and Microsoft

Windows platforms

A valid 5620 SAM user account is required to start a GUI client session

10 — 1 — 30 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM GUI clients provide a graphical interface for network operators. The SAM GUI Client is a Java-based
interface that provides access to the 5620 SAM main server and to the managed network. The GUI Client send
requests to the 5620 SAM main server to view and change data objects in the data model and to perform network
operations.
The 5620 SAM GUI client operation is supported on Unix and Microsoft Windows platforms.
The 5620 SAM GUI client can be launched:
•using a desktop shortcut icon created during the client software installation
•using a web browser
•or, using a command-line interface (CLI) from a Solaris machine

A valid 5620 SAM user account is required to start a 5620 SAM GUI client session.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 30
 4 Launching the 5620 SAM GUI client
4.2 Using a desktop icon

Double-click the 5620 SAM Client App icon

10 — 1 — 31 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

To start the 5620 SAM client GUI using a desktop icon:

1. Double-click on the shortcut icon that was created on your desktop when the software was installed. The 5620
SAM login window appears.
2. Enter the appropriate Login Name and Password, and click on the Login button.
The 5620 SAM client GUI opens.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 31
 4 Launching the 5620 SAM GUI client
4.3 Using a web browser

 Navigate to the URL:

http://server:8085/client

 Click on the Install or Launch

5620 SAM Client link

10 — 1 — 32 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

To start the 5620 SAM client GUI using a web browser:

1. Open the web browser on the 5620 SAM main server and Navigate to the following URL:
http://server:8085/client
where server is the IP address or hostname of the 5620 SAM main server

The web browser opens the 5620 SAM Client welcome page shown in the figure above.
2. Click on the Install or Launch 5620 SAM Client link.
If you did not use a web browser to install the client, a form opens and prompts you for the client installation
location. Use the form to specify the client installation directory, for example, C:\5620sam\client.
The 5620 SAM login window appears.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 32
 4 Launching the 5620 SAM GUI client
4.4 Using the CLI

CLI allows operators to specify one or more client startup options

Windows Solaris

See Alcatel-Lucent 5620 SAM User Guide – 5620 SAM GUI startup procedures
for a listing of startup options

10 — 1 — 33 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Using a CLI to start the client GUI allows operators to specify one or more client startup options.
To start the 5620 SAM client GUI from a Windows machine using a CLI:
1. Open a command window. At the CLI prompt navigate to the 5620 SAM client installation drive and directory,
entering the commands:
<drive id> ↵
cd /<sam client directory>/nms/bin ↵
where: <drive id> is the drive on which the 5620 SAM client is installed, for example, D:
<sam client directory> is the 5620 SAM client installation location, typically \5620sam\client
2. At the CLI prompt, start the 5620 SAM client by typing nmsclient.bat ↵ . The 5620 SAM login window appears.
Alternatively, at the CLI prompt operators can start the 5620 SAM client using one or more startup options.
For example, to force a client update, enter: nmsclient.bat update ↵
See Alcatel-Lucent 5620 SAM User Guide – 5620 SAM GUI startup procedures for a complete listing of 5620
SAM client startup options for Windows

To start the 5620 SAM client GUI from a Solaris machine using a CLI:
1. Open a bash console window on the client station. At the CLI prompt to navigate to the 5620 SAM client
installation directory, entering the command: /<sam client directory>/nms/bin ↵
where: <sam client directory> is the 5620 SAM client installation location, typically /opt/5620sam/client
2. Start the 5620 SAM client by typing ./nmsclient.bash ↵ . The 5620 SAM login window appears.
Alternatively, at the CLI prompt operators can start the 5620 SAM client using one or more startup options.
See Alcatel-Lucent 5620 SAM User Guide – 5620 SAM GUI startup procedures for a complete listing of 5620
SAM client startup options for Solaris

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 33
 4 Launching the 5620 SAM GUI client
4.5 Login window

Select a Server
Enter Login
Name and
Password

Click on the Login button

10 — 1 — 34 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The SAM login window allows to enter the SAM user account credentials in order to establish a session and
access the SAM GUI.
5620 SAM user accounts consist of a user name, password, and an associated user group and scope of command.
On the SAM Login Window the user name is used as the login name. All client sessions are protected by the
username and password for the session. Use the login name and password provided by the system administrator.
The user that starts a 5620 SAM Windows client must be one of the following:
• the user that installed the client software
• a user with sufficient permissions on the client files and directories, such as a local administrator
The user that starts a 5620 SAM in Solaris must be an user that has read, write, and execute permissions on the
client files and directories.

When a system administrator has configured the client to support the multiple server option, operators can use
the SAM Login form for selecting the one server to establish the session with from the multiple servers displayed
in the Server drop-down list. If the multiple server option has not been configured, the Server parameter in SAM
Login window displays only the server configured during the client installation process.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 34
 4 Launching the 5620 SAM GUI client
4.6 Client software update

10.0 R5

5620 SAM
GUI Client

5620 SAM
Server
10.0
11.0 R5
R1

10 — 1 — 35 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

During startup, the client software checks for available updates on a 5620 SAM main server. If a configuration
change is available, the client automatically applies it.
After a 5620 SAM main server is upgraded, a GUI client that connects to the server automatically detects the
release mismatch and attempts an upgrade to the server release level. If a client software upgrade is available,
the client displays a window indicationg the release mismatch and applies the upgrade in response to a user
prompt.
During a client software upgrade, a 5620 SAM client downloads and installs only the files required for the
upgrade. The upgrade process removes previously downloaded local 5620 SAM files that are not required by the
updated client software.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 35
 Questions

?
10 — 1 — 36 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.
Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The command “./nmsclient.bash” is used to:

a. start the 5620 SAM client GUI using a desktop icon.
b. start the 5620 SAM client GUI from a Solaris machine using a CLI.
c. start the 5620 SAM client GUI using a web browser
d. start the 5620 SAM database from a Solaris machine using a CLI.

Navigating to which URL will start the 5620 SAM client GUI using a web browser?
a. “C:\5620sam\client”
b. “/opt/5620sam/client/nms/bin”
c. “http://server/client” where server is the IP address or hostname of the 5620 SAM main server.
d. “http://server:8085/client” where server is the IP address or hostname of the 5620 SAM main server.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 36
 Answers

1. The command “./nmsclient.bash”

Switch to notesis view!
used to:
a. start the 5620 SAM client GUI using a desktop icon.
b. start the 5620 SAM client GUI from a Solaris machine using a CLI.

c. start the 5620 SAM client GUI using a web browser
d. start the 5620 SAM database from a Solaris machine using a CLI.

2. Navigating to which URL will start the 5620 SAM client GUI using a web browser?
a. “C:\5620sam\client”
b. “/opt/5620sam/client/nms/bin”
c. “http://server/client” where server is the IP address or hostname of the 5620 SAM main server.
d. “http://server:8085/client” where server is the IP address or hostname of the 5620 SAM main
server.

10 — 1 — 37 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 37
 5 Epipe configuration

10 — 1 — 38 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This section is intended to guide you through the steps required to configure an Epipe service:
a. Create an Epipe
b. Assign a port to SAP
c. Assign SDPs

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 38
 5 Epipe configuration
5.1 Access port configuration

10 — 1 — 39 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide describes the steps required to configure an access port:

1. From the Equipment tab, right-click on the equipment-facing port and choose Properties.
2. On the port properties General tan, change the Mode to Access, and the Encap Type to Dot1Q

Note: From the Port MTU will automatically increase from 1514 to 1518 when you click OK.

Technical Reference
For more details on the procedures to create an Epipe see Alcatel-Lucent 5620 SAM,
Release 10.0 R1 User Guide – 70.4 VLL service management procedures

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 39
 5 Epipe configuration
5.2 Epipe service creation

10 — 1 — 40 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Technical Reference
This slide describe the steps required to create an Epipe service:
For more details on the procedure to create an Epipe see Alcatel-Lucent 5620 SAM,
1. From the main menu, Create
choose10.0
Release
Service
R1 User VLL

Guide
– 70.4 Epipe.
VLL Epipe Serviceprocedures
Themanagement
service [Create] form
- opens with
Procedure 70-1 To create a VLL Epipe service
the General tab displayed
2. In the Customer panel, click the Select button to add the customer. Specify a Service Name and Description.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 40
 5 Epipe configuration
5.2 Epipe service creation [cont.]

10 — 1 — 41 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide provides the remaining steps required to configure an Epipe service:
3. From the Components Tree, right-click on Epipe Service and choose Create Site
- Select both nodes that will be included in the Epipe Service
4. Right-click the Access Interface and select the Access Port (From the Port Tab)
Note: When adding the access port, you need to specify a vlan tag: uncheck the box beside “Auto-Assign ID”
5. Right-click on Spoke SDP Bindings and select Create Spoke SDP Binding
1) When adding the Spoke SDPs (From the General Tab) after selecting the Tunnel Termination Site you
may Auto-Select the Tunnel or use the Select button to specify a SDP
2) From the Return Tab you can Auto-Select the Return Tunnel or once again use the Select button to
specify the return tunnel you created
6. Click on the Apply button.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 41
 5 Epipe configuration
5.4 View service topology

10 — 1 — 42 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Once the Epipe service is populated with the access port and spoke SDP, select the Topology View button to view
the service that you have created.

Note
If your network port MTUs are too small this is the stage you will see problems.
When you select View Topology your service will be painted red. Right click either
node and select Properties. You may see “SDP Binding Down”. If you right click the
SDP links and select Properties you may see “Tunnel MTU Too Small”. Simply adjust
your network port MTUs to an appropriate value on both ends and your service should
come up.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 42
 5 Epipe configuration
5.5 Adjust network port MTU value

Eth. Frame Null

IFG
Preamble
DA 6
SA 6
Type 2
VLAN
Tunnel 4
PW Header 4
CW (opt)
Payload 1514
FCS
Total MTU Required 1536

10 — 1 — 43 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Adjust your network port MTU to an appropriate value on both ends. This triggers your Epipe service to come up.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 43
 5 Epipe configuration
5.6 Verify operational state

10 — 1 — 44 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

To verify the service operational state, perform the following steps:

1. From the Tools Menu select Service Test Manager (STM). The Service Test Manager form opens.
2. Select Create
Service
Service Site Ping. The Service Site Ping [Create] form opens with the General
tab displayed.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 44
 5 Epipe configuration
5.6 Verify operational state [cont.]

3a

3b

4a
4b

10 — 1 — 45 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide provides the remaining steps required to verify the Epipe service operational state.
3. On the Service Site Ping [Create] form General tab configure the parameters:
a. Name and Description to name the Service Site Ping Test
b. System ID (Loopback IP Address) Click the Select button and specify the node the ping will originate from
4. Open the Test Parameters tab and configure the paramaters:
a. Target IP Address. Click the Select button and specify the “Target IP Address”
b. Service ID. Click the Select button and choose the service to be tested
5. Click on the Apply button.
1. Click Execute
6. From the Results Tab note the test results

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 45
 5 Epipe configuration
5.8 Epipe service creation—point-and-click method

10 — 1 — 46 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the first batch of steps required to create an Epipe service using the point-and-click provisioning
method:
1. Choose Create
Service
VLL
Epipe from the main menu. The Epipe Service [Create] form opens with
the General tab displayed
2. In the Customer panel, click the Select button to add the customer. Specify a Service Name and Description.
3. Click on the Apply button. The form refreshes into the Epipe Service - Name [Create] form opens displaying
additional tabs and with the General tab displayed.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 46
 5 Epipe configuration
5.8 Epipe service creation—point-and-click method [cont.]

10 — 1 — 47 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the remaining step that is part of the Epipe service creation through the point-and-click method:
4. On the Epipe Service - Name [Create] form, click on the More Actions and choose Topology View from the
contextual menu. The Service Topology map opens.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 47
 5 Epipe configuration
5.10 Epipe site creation—point-and-click method

10 — 1 — 48 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the first batch of steps required to create an Epipe site using the point-and-click provisioning
method:
1. Click on an empty portion of the Service Topology map. Choose Create→Epipe Site from the contextual
menu. The Select Network Elements form opens with a list of available sites.
2. Choose a site or multiple sites and click on the OK button. The Site (Create) form opens with the General tab
displayed.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 48
 5 Epipe configuration
5.10 Epipe site creation—point-and-click method [cont.]

10 — 1 — 49 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the remaining step that is part of the Epipe site creation through the point-and-click method:
3. On the Epipe Site (Create) form assign a Name and Description. Click on the OK button. The Epipe Site
(Create) form closes and the Service Topology map refreshes displaying the created Epipe sites.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 49
 5 Epipe configuration
5.12 Access interface creation—point-and-click

10 — 1 — 50 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the first batch of steps required to create an access interface sites using the point-and-click
provisioning method:
1. On Service Topology map, right-click on an Epipe site and choose Create→L2 Access Interface from the
contextual menu. The L2 Access Interface [Create] form opens with the General tab displayed
2. Click on the Port tab button and click on the Select button in the Terminating Port panel. The Select
Terminating Port form opens with a list of available access ports.
3. Choose a port from the list and click on the OK button. The Select Terminating Port form and the L2 Access
Interface [Create] form refreshes with selected port name is displayed in the Terminating Port panel.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 50
 5 Epipe configuration
5.12 Access interface creation—point-and-click [cont.]

Repeat steps 1 to 4 to create

access interfaces on other
Epipe sites

10 — 1 — 51 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the remaining step that is part of the access interface creation through the point-and-click
method:
4. Click on the OK button. The L2 Access Interface [Create] form closes and the Service Topology map
refreshes displaying the created access interfaces.

Repeat the access interface creation, as required, to create access interfaces on other Epipe sites.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 51
 5 Epipe configuration
5.13 Spoke SDP binding creation—point-and-click

10 — 1 — 52 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the first batch of steps required to create a Spoke SDP binding connection using the point-and-
click provisioning method:
1. On Service Topology map, right-click on an Epipe site and choose Connect→Create Spoke SDP Binding from
the contextual menu. The Spoke SDP Binding [Create] form opens with the General tab displayed
2. Click on the Select button to choose a Tunnel Termination Site. The Select Destination Network Element
form opens with a list of available tunnel termination sites.
3. Choose a tunnel destination site from the list and click on the OK button. The Select Destination Network
Element form and the Spoke SDP Binding [Create] form refreshes with the selected tunnel destination site is
displayed.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 52
 5 Epipe configuration
5.13 Spoke SDP binding creation—point-and-click [cont.]

10 — 1 — 53 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the next step required to create a Spoke SDP binding connection using the point-and-click
provisioning method:
4. Click on the OK button. The Spoke SDP Binding [Create] form closes and the Service Topology map refreshes
displaying the created spoke SDP binding.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 53
 5 Epipe configuration
5.13 Spoke SDP binding creation—point-and-click [cont.]

Repeat steps 1 to 4 to create

the Spoke SDP binding for the
returning tunnel

10 — 1 — 54 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Repeat steps 1 to 4 to create Spoke SDP binding connection the other Epipe site for the returning tunnel.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 54
 6 Cpipe configuration

10 — 1 — 55 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This section is intended to guide you through the steps required to configure a Cpipe service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 55
 6 Cpipe configuration
6.1 Cpipe configuration workflow

 Bind the service to

 Customer Configure a Create Service the customer at
Info. Bind service creation
Customer (Cpipe)
time
 Specify encapsulation

Configure port  Assign channel

 Configure
 Specify Bind Create SAPS group
Access Ports
Encapsulation type

Bind to a SDP
 Specify transport Create SDPs Bind Virtual Circuit
tunnels (service tunnel)

 Service Topology
Manage Service View
 Properties

10 — 1 — 56 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide describes the steps that a network administrator or operator needs to perform to configure a Virtual
Private LAN Service.
Customer - must be assigned to the service. Though the service can have only one Customer, that customer may
be assigned to more than one service.
Create Service - specify the service type (VLL) and add the appropriate service sites.
CreateService Access Points –Configure the port Mode for Access, define the Encapsulation Type, specify the
Encapsulation ID (as required) and specify the service MTU size.
Create SDP Bindings – Create the Spoke SDP or Mesh SDP Bindings by associating the service to service tunnels.
The VC Label may be assigned manually, by the network administrator or operator, or automatically, by the 5620
SAM.
Manage Service – through the Properties window and/ or by using the Service Topology View.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 56
 6 Cpipe configuration
6.2 Access port configuration

Full E1
TDM TDM

SAToP
CES IWF CES IWF

Dedicated timeslots
TDM TDM

CESoPSN
CES IWF CES IWF

10 — 1 — 57 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

First we need to prepare several access ports in different configurations:

•E1 Unstructured: the whole E1 will be sent transparently through the Cpipe.
•G.704 CRC: E1 timeslots are grouped together in one of many Channel Groups (CRC is included).
•G.704—no CRC: this configuration does not include CRC.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 57
 6 Cpipe configuration
6.3 Access port configuration: E1 unstructured (part 1)

1.Create channel
This allows to select the right
encapsulation. In order to modify
the subgroup parameters, the
Administative state must be
switched on first.

Important: click on Apply to go to

the next field.

10 — 1 — 58 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This is the first of 4 steps required to configure access ports in an E1 unstructured configuration: create a port
channel.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 58
 6 Cpipe configuration
6.4 Access port configuration: E1 unstructured (part 2)

Click OK after selecting E1-Unframed

10 — 1 — 59 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This is the second of the 4 steps required to configure access ports in an E1 unstructured configuration: select the
E1-unframed option for Channel Framing.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 59
 6 Cpipe configuration
6.5 Access port configuration: E1 unstructured (part 3)

The port will now contain a channel Group

In this channel, create a channel that will

represent the whole E1/T1

Fill in channel ID: for example, 1

Only one channel group can be created.

Select CEM as the VC type

(circuit emulation)

10 — 1 — 60 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This is the third of the 4 steps required to configure access ports in an E1 unstructured configuration: create a
channel that represents the whole E1/T1 link.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 60
 6 Cpipe configuration
6.6 Access port configuration: E1 unstructured (part 4)

Turn up the port.

Repeat the steps on the other side of the service.

10 — 1 — 61 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The last step is to turn up the access port.

Repeat the configuration steps on the other side of the service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 61
 6 Cpipe configuration
6.7 Access port configuration: G.704 CRC (E1) [part 1/5]

This configuration allows you to select dedicated timeslots.

10 — 1 — 62 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

As a prerequisite to the access port configuration with G.704 CRC (E1), create a channel and administratively
activate it.
Then on the Channel tab, select the option G.704 CRC from the Channel Framing box. This option means
synchronized frame with Cycle Redundancy Check.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 62
 6 Cpipe configuration
6.8 Access port configuration: G.704 CRC (E1) [part 2/5]

Use the Create Cha... button to create new

channel groups (subchannels), as required.

10 — 1 — 63 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

On the Subchannels tab, use the Create Cha... button to create new channel groups (subchannels).
Multiple channel groups can exist for each E1/T1.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 63
 6 Cpipe configuration
6.9 Access port configuration: G.704 CRC (E1) [part 3/5]

Configure the channel ID (for example, 1)

Select the encapsulation

type: CEM (Circuit Emulation)

10 — 1 — 64 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows how to:

•configure the channel ID
•select encapsulation type: CEM (Circuit Emulation)

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 64
 6 Cpipe configuration
6.10 Access port configuration: G.704 CRC (E1) [part 4/5]

Select the timeslots to add to the

channel group.

10 — 1 — 65 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

On the Channel Group tab, you can select the time slots that you need to add to the channel group.
The time slots do not need to be consecutive. The slide shows the selected time slots TS2 through TS8 and TS15.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 65
 6 Cpipe configuration
6.11 Access port configuration: G.704 CRC (E1) [part 5/5]

1
2
Select the channel group.
Cick on the Turn Up button.

The channel group is also available in Tree View.

10 — 1 — 66 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The configured channel group becomes available on the Subchannels tab. Select the channel group, and click on
the Turn Up button.
Repeat the steps on the port at the other site of the service.
The channel group is also available in Tree View.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 66
 6 Cpipe configuration
6.12 Customer configuration

1 Select Manage
Customers 2 Click Create.

3 Define the customer attributes.

10 — 1 — 67 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

A service needs to be associated with a customer. A service can have only one customer, but that customer can
be associated to more that one service.
To create a customer in the 5620 SAM, you need to perform these tasks:
•From the Main Menu, select Manage
Customers.
•In the new window, click on the Create button.
•Complete the customer details as provided in the configuration window.
•Click on the OK button.

To verify that the customer was created, or to edit customer configuration details, perform the following tasks:
•Select Manage
Customers from the Main Menu.
•Click on the Search button.
•Double-click on the appropriate entry or, select the appropriate customer and click on the Edit button.
•Review or modify the details, as required.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 67
 6 Cpipe configuration
6.13 Cpipe service configuration

10 — 1 — 68 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide describe the steps required to create and configure an Epipe service:
1. From the main menu, choose Create
Service
VLL
Cpipe. The Cpipe Service [Create] form opens with
the General tab displayed
2. In the Customer panel, click the Select button to add the customer. Specify a Service Name and Description.
3. Select the right encapsulation via the VC type:
1. Select SAToP for unframed (whole E1/T1).
2. Select CESoPSN for the dedicated time slots.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 68
 6 Cpipe configuration
6.13 Cpipe service configuration [cont.]

10 — 1 — 69 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Continue the configuration of the Cpipe service as follows:

1. Right-click on the Cpipe Service, and choose Create Cpipe Site. The Select Network Elements – Cpipe Service
window opens.
2. In the Select Network Elements – Cpipe Service window, select the network elements, as required.
3. Click on OK after selecting the network elements.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 69
 6 Cpipe configuration
6.13 Cpipe service configuration [cont.]

SDP selection
The selection of SDPs is just the same as in any other service.
The system uses T-LDP automatically as the signaling protocol for the creation
of the inner tunnels.

10 — 1 — 70 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Continue the configuration of the Cpipe service by creating an L2 access interface to add to the service.
• Find the unstructured port in case of SAToP.
• Find the channel group in case of CESoPSN.

The next configuration step is the addition of the SDP bindings—covered on the next slide.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 70
 6 Cpipe configuration
6.14 SDP bindings

2
1

4. Select a Service Tunnel

3
6

10 — 1 — 71 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The service requires SDPs (Service Distribution Paths) when SAPs (Service Access Points) are located on separate
network devices (distributed service). An SDP is created when a service is associated (bound) to a Service Tunnel.
The SDP bindings can be created manually or automatically. To manually create the SDP bindings, perform the
following tasks:
1. In the Components window for the service, Expand the Site listing, navigate to Spoke SDP Bindings, right-
click and select Create Spoke SDP Bindings. The Spoke SDP Binding [Create] window opens.
2. Click the Select button in the Termination Site section of the new window
3. Select the terminating Site ID from the list.
4. Click OK after selecting the appropriate site ID.
5. Select a Service Tunnel
6. Click OK after selecting the appropriate Service Tunnel.

Note
As of Release 5.0, pseudo-wire switching and redundancy are supported. Hence in an
Epipe, and other VLL services nodes can be terminating or endpoints. Because of these
features, the SAM allows for more than two nodes (sites) to be members of a VLL
service.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 71
 6 Cpipe configuration
6.15 Disabled SDP signaling

7705 SAR

7750 SR

In some interoperability cases, T-LDP cannot be used for signaling. In this

case, the signaling on an SDP is disabled (off). As a result, you need to
configure service labels (VC labels) manually on a service basis from the
service menu. The manually created VC labels have a reserved valid label
range: [2048..18431].

10 — 1 — 72 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

In some interoperability cases, T-LDP cannot be used for signaling. In this case, the signaling on an SDP is disabled
(off). As a result, you need to configure service labels (VC labels) manually on a service basis from the service
menu. The manually created VC labels have a reserved valid label range: [2048..18431].

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 72
 7 QoS

10 — 1 — 73 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This section covers quality of service topics.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 73
 7 QoS
7.1 SAP ingress menu

Search for
default/existing
QoS policies.

Create new QoS policy.

10 — 1 — 74 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The SAP ingress menu option has three functional segments:

•mapping traffic to forwarding classes
•mapping forwarding classes to queue
•queue declarations

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 74
 7 QoS
7.2 SAP ingress policy—General

Choose SAP ingress policy ID.

Default is Auto-AssignID.

The Displayed Name and

Description are optional.

The Scope can be

template (the policy can be applied
any number of times)

exclusive (the policy can be applied
only once)

Default priority

Default forwarding class

10 — 1 — 75 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Access ingress policies define ingress service forwarding class queues and map flows to those queues. When an
access ingress policy is created, it always has two queues defined that cannot be deleted: one for the default
unicast traffic and one for the default multipoint traffic. These queues exist within the definition of the policy.
The queues only get instantiated in hardware when the policy is applied to an access interface. In the case where
the service does not have multipoint traffic, the multipoint queue will not be instantiated.
In the simplest access ingress policy, all traffic is treated as a single flow and mapped to a single queue, and all
flooded traffic is treated with a single multipoint queue.
The required access ingress policy elements include:
• a unique access ingress policy ID
• an exclusive scope for one-time use, or a template scope for use with multiple SAPs and interfaces
• at least one default unicast forwarding class queue
• at least one multipoint forwarding class queue
Each queue can have unique queue parameters to allow individual policing and rate shaping of the flow mapped
to the forwarding class. Mapping flows to forwarding classes is controlled by comparing each packet to the match
criteria in the policy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 75
 7 QoS
7.3 SAP ingress policy—General (Apply)

Update send to node

Released

Get policy from node

View latest info released

Towards the nodes

Distribute policy to
specified nodes

10 — 1 — 76 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Policies are global or local. Global policies are policies that are created using the 5620 SAM. Local policies are
instances of global policies that are assigned to individual NEs. Depending on the distribution mode configuration of
a local policy,
when you modify a global policy using the 5620 SAM, all local instances of the policy on the associated NEs can be
updated. This ensures that all instances of the policy in the network are synchronized. If a local policy differs from
the
corresponding global policy because of changes to the global policy, a warning alarm is raised against the local
policy. After a global policy is updated and copied to all participating NEs, any mismatch alarms against local policies
are cleared.
To identify mismatches between local and global policies, you can perform a policy audit that compares the local
instances of a policy to the corresponding global policy and view the differences between them. Audits can be
performed on local policies of NEs that are within the user’s span of control and policies for which the user’s license
supports.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 76
 7 QoS
7.4 Dot1p

Dot1p value

FC mapping

10 — 1 — 77 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows how to configure the Dot1p and Forwarding Class parameters.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 77
 7 QoS
7.5 DSCP

DSCP value

FC mapping

10 — 1 — 78 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows how to configure the DSCP and Forwarding Class parameters.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 78
 7 QoS
7.6 IP Match Criteria

Different entries

FC mapping

IP Match
Criteria

10 — 1 — 79 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows how to configure the IP Match Criteria parameters.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 79
 7 QoS
7.7 Queues
Add queue

Define queue ID

Define queue name

and description

10 — 1 — 80 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows how to create and configure queues.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 80
 7 QoS
7.8 Forwarding classes (FC)

Choose the FC

Add FC
Queue to
FC mapping

10 — 1 — 81 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows how to create and configure forwarding classes.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 81
 7 QoS
7.9 Relations

Matching criteria

Forwarding classes

Queues

10 — 1 — 82 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the relations among IP matching criteria, forwarding classes, and queues.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 82
 7 QoS
7.10 Tree view

10 — 1 — 83 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the Tree View for a SAP policy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 83
 7 QoS
7.11 SAP ingress policy

Apply SAP ingress

policy ID

10 — 1 — 84 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide illustrates how to apply a SAP ingress policy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 84
 8 Policy distribution

10 — 1 — 85 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This section describes the policy distribution.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 85
 8 Policy distribution
8.1 Policy search

10 — 1 — 86 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Policies created with the 5620 SAM are of global significance, which makes them available to be applied to
network objects, as required. However, global policies hold no local significance (do not exist in NEs) unless they
have been applied to a network object. Therefore, a user logging into the node through CLI may not necessarily
have access to globally significant policies. A corporate policy may require that CLI users have access to policies.
The policy management feature permits personnel to create policies from the 5620 SAM and distribute them to
NEs, as required. Once distributed, a policy is able to maintain the association between the policies on the NE
(local policies) and policies in the 5620 SAM database (global policies).
To distribute a policy to NEs, perform the following tasks:
 Navigate to Tools
Statistics from the main menu.
 Select File Policies from the drop-down menu. The Manage File Policies window opens.
 Click on the Search button at the right side of the window to create a list of the available policies. Network
personnel may use the enhanced filter feature to reduce the number of entries in the list and more quickly
identify the policy or policies desired.
 Select the appropriate policy from the list.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 86
 8 Policy distribution
8.2 Local policy definitions

10 — 1 — 87 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

In the previous slide, the Policy Scope from within the Manage File Policies window was set to Global. This
permits personnel access to all of the policies available in the 5620 SAM database. Should they wish to determine
what policies exits on any particular network element:

From the drop-down menu next to the Policy Scope attribute, perform the following tasks:
 Select Local;
Click on the Select button next to the Local Node IP Address. The Select a Network Element window opens
with a list of all managed nodes within the network. Again, personnel may use the enhanced filter feature to
more quickly identify nodes by reducing the number of entries, as required;
Select the appropriate node from the list and click OK. The node system address appears in the Manage File
Policies window, as shown above;
Click on the Search button at the right side of the window. All available policies (file policies in this example)
will be listed.
 Select an entry and click on the Properties button at the right side of the window to manage the policy entry,
as required.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 87
 8 Policy distribution
8.3 Policy distribution

10 — 1 — 88 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Policy distribution serves to permit network personnel the ability to make global policies available to CLI users on
any node. The advantage is that policies are created from the center (the 5620 SAM) and then distributed to any
number of managed elements in the network. This process will eliminate misconfiguration and is particularly
useful dealing with complex policies (QoS and routing policies) across large networks.

To distribute a policy, perform the following tasks:

 Select the appropriate policy to be distributed (in this example, a file policy) from within the Global Policy
Scope;
 Click on the Distribute button at the lower right side of the window. The Distribute – File window opens;
 Under the section labeled Available Nodes, select the node or nodes to which the policy will be distributed.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 88
 8 Policy distribution
8.3 Policy distribution [cont.]

Distributing instance
 Policy to be distributed

Available nodes Selected nodes

 Nodes to which the  Nodes to which the
policy can be applied policy will be applied

10 — 1 — 89 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

In the Distribute – File window, you can find the following information:
•Distributing Instance – this identifies the policy to be distributed;
•Available Nodes – provides a list of all managed nodes to which the policy may be applied;
•Selected Nodes – provides a list of nodes to which the policy will be applied. The Distribute button at the
bottom of the window is greyed out until at least one node has been selected.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 89
 8 Policy distribution
8.4 Policy distribution verification

10 — 1 — 90 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

To distribute the policy to a single node or to multiple nodes, perform the following tasks:
 Select the nodes or nodes from the Available Nodes list at the left side of the window;
 Click on the right arrow head between the two sections. The nodes will appear in the Selected Nodes column.
Network personnel may modify the list from either column and click on the right or left arrow head located
between them, as required;
 Once the list has been created, click on the Distribute button at the bottom of the window;
 Close the Distribute – File window.

Once distributed, a policy will have a local significance. To verify the local significance of a policy, do the
following:
 Select the node from the list and specify the Local Policy Scope from within the Manage File Policy window;
 Click on the Search button at the right side of the window to view the list of policies (file policies, in this
example). Personnel may use the enhanced filter feature to reduce the number of entries in the list so as to
more quickly identify the appropriate entry;
 Click on the Properties button at the right side of the window to view or modify the current configuration of
the policy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 90
 8 Policy distribution
8.5 Policy distribution verification at the CLI

View local policy.

#show log file-id x

10 — 1 — 91 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

You can also verify that a policy has been distributed to the node using CLI:
 Launch a Telnet or SSH session to the appropriate network element from the 5620 SAM GUI;
 Log in to the node;
 From the command prompt, type show log file-id x, where x is the file ID assigned from within the 5620 SAM;
 Compare the configuration output to that from the 5620 SAM. Check to ensure that they are both identical.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 91
 8 Policy distribution
8.6 Policy audit

Local user makes change to Global

policy

View local policy changes.

#show log file-id x

10 — 1 — 92 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Depending upon the user security set within the network, network personnel may be able to access network
elements via CLI. As such, they may also be able to make configuration changes to policy statements. These
changes may cause disruption in the network which may be difficult for personnel to isolate. To assist in isolating
such configuration changes, the 5620 SAM provides a mechanism to flag changes in the local policy and its
corresponding global policy known as the Policy Audit.

In the example shown on the slide, a user has accessed a network element through CLI and made changes to the
existing file policy: Rollover has been set to 2880 and Retention to 24 vice the original 1440 and 12, respectively.

Use the following syntax to configure a file policy through CLI:

configure log file-id x rollover yyyy retention zzzz

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 92
 8 Policy distribution
8.7 Policy Management

10 — 1 — 93 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

A Policy Audit is launched manually in accordance with corporate policy or during network troubleshooting.
To launch a Policy Audit, perform the following tasks:
 Navigate to the policy from the main menu, Tools
Statistics
File Policy in this example;
 List the policies (Global Policy scope) and select the policy or policies, as required;
 Click on the Policy Audit button at the right side of the Manage File Policies window.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 93
 8 Policy distribution
8.8 Policy audit—General

Alarm All Differences

 Generate alarm for any difference
between Global and local policies.

Distribution Mode
 Local Edit Only—does not allow
synchronization with global policy
 Sync with Global—allows
synchronization with global policy

10 — 1 — 94 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The Policy Audit – audit-status [Edit] window opens to the Global Policy Selection tab. Click on the General
tab. This tab provides basic configuration information about the Policy Audit.
• Date and time information is provided to indicate the last time the audit was completed, as well as, last failure
and if the audit was interrupted.
•By default, the 5620 SAM is set to provide an alarm for all differences between the local and global policies. The
Distribution Mode parameters are also disabled.

You can set the Distribution Mode as follows:

•Set to „Local Edit Only“ upon finding differences indicates that the policy will not be sychronized with the
global policy if a difference is found. This ensures that unique policies are not modified when a global policy is
updated; useful where some instances of the local policy have been deliberatley modified for a specific
application and synchronizing to the global policy is not desired;
•Set to „Sync with Global“ upon finding of no differences is used when network personnel wish to be able to set
the global and local instances of the policy to a common setting through synchronization.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 94
 8 Policy distribution
8.9 Policy audit—Global Policy Selection

10 — 1 — 95 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The Global Policy Selection tab provides access to the list of policies from within the selected context. The
example in this slide shows only one entry, but there can be multiple entries as well.
Start the audit as follows:
 Create a list of the policies. Personnel may apply filters from the drop down menus along the list columns to
reduce the number of entries and more quickly identify the policy or policies to be audited;
 Select the appropriate policy or policies. Network personnel may select any combination of the entries for
auditing by using Shift+Click or Shift+Ctrl.
 Click on the Start Audit button at the bottom of the window.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 95
 8 Policy distribution
8.10 Policy audit—alarm information

10 — 1 — 96 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The 5620 SAM performs the policy audit as defined in the previous slide. In this example, the policy audit feature
has been configured to provide an alarm for any differences between global and local policies. Additionally, the
system assumes that the differences are deliberate and will assume that the policy is set to „Local Edit Only“
which maintains the unique configurations of the local policy.

In this example, there has been a change to File Policy ID 1 which should generate an alarm in the Dynamic Alarm
list, as shown above. To view the alarm details, do the following:
 Select the alarm from within the Dynamic Alarm List;
 Right click and select Show Alarms from the contextual menu. The Alarm Info window opens;
 Specific information about the alarm is provided under the General tab. Notably:
 Application Domain defines the alarm to be File Policy;
 Site ID defines the site from which the difference was detected;
 Alarmed Object ID indicates File ID 1;
 Alarm Name specifies TemplateInconsistency.

From this information, you can determine that File Policy ID 1 on site Node158 has inconsistencies with the
global policy.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 96
 8 Policy distribution
8.11 Policy synchronization preparation

10 — 1 — 97 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Once you determined that a policy configuration mismatch exists, it becomes a matter of corporate policy as to
whether the inconsistency is acceptable or not. If it has been determined that the inconsistency is to be
corrected, the 5620 SAM can be used to sychronize the global and local policies.
To synchronize policies, do the following:
 Determine which policy instance (global or local) is valid. In this example, the local instance (on Node158) will
be synchronized to the global instance (from the 5620 SAM database);
 Navigate to the Global Policy Scope of the policy. In this example, from the main menu, select Tools >
Statistics > File Policy;
Select the appropriate policy (File Policy ID #1) and click on the Synchronize button on the right side of the
window. The Synchronize – File window opens. The next slide describes the Synchronize – File window.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 97
 8 Policy distribution
8.12 Policy synchronization

10 — 1 — 98 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the Synchronize – File window. This window contains the following sections:
 Synchronization Instance(s) indicates the file to be used as the source for synchronization. This is the same
policy selected in the previous step;
 Available Nodes lists all nodes on which the selected policy currently exists;
 Selected Nodes identifies the node from which network personnel have decided to use the policy as the source
for sychronizing the policy.

To trigger the policy sychronization, perform the following tasks:

 Ensure that the correct policy has been selected as the Synchronizing Instance;
 Select the node from which the polciy will be synchronized from the Available Nodes list;
 Click on the right arrowhead. The selected node will appear in the Selected Node cloumn within the window;
 Click on the Synchronize button.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 98
 8 Policy distribution
8.13 Policy management

10 — 1 — 99 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Once the 5620 SAM has completed the policy synchronization process, ensure that the change has taken place by
verifying the policy properties. To verify policy properties, perform the following tasks:
 Navigate to the Manage xxx Policies (where File stands for xxx in the example shown on this slide) window. In
this example, select Tools
Statistics
File Policies from the main menu;
 Select the appropriate Policy Scope (Global in this example). Use the filter feature in each column, and click
on the Search button to reduce the number of list entries;
 Click on the Properties button at the right side of the window. Review the configuration parameters to ensure
that they are set as required.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 99
 8 Policy distribution
8.14 Policy release

10 — 1 — 100 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

During the synchronization process, the policy sets the Configuration Mode to Draft. This ensures that the policy
does not overwrite existing instances until you confirmed the policy validity. The policy Configuration Mode
needs to be set to Released before the policy can be distributed to network elements.
To set the policy Configuration Mode to Released, perform the following tasks:
 Navigate to the General configuration tab of the Policy to be released. The Configuration Mode attribute is
currently set to Draft, as shown on the slide;
 Click on the Switch Mode button. The Confirm window opens asking you to acknowledge that you want to
proceed. This window be suppressed under File
User Preferences;
Once the server has finished processing the change request, the 5620 SAM sets the Configuration Mode to
Released.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 100
 8 Policy distribution
8.15 Policy distribution

10 — 1 — 101 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

After verifying the validity of the policy configuration and setting the Configuration Mode to Released, you need
to distribute the policy to the appropriate node or nodes. In the example shown on the slide, File Policy 1 is
distributed to site Node158.

To distribute a policy, perform the following tasks:

 Select the appropriate policy to be distributed (in this example, a file policy) in the Global Policy Scope;
 Click on the Distribute button. The Distribute – File window opens;
 In section Available Nodes, select the node or nodes to which the policy is to be distributed;
 Click on the right arrowhead to move the node in the Selected Node column;
 Click on the Distribute button.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 101
 8 Policy distribution
8.16 Policy distribution verification in GUI

10 — 1 — 102 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

You can verify that the policy has been distributed and that changes have been made. To verify policy
distribution in the 5620 SAM GUI, perform the following tasks:
 Click on the Local Definitions tab in the File Policy Properties window;
 Click on the Search button. Use the filter feature provided for each cloumn to reduce the number of list
entries, as required;
 Verify that the network element to which the policy was distributed is in the list, and then click on the
Properties button.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 102
 8 Policy distribution
8.17 Policy distribution verification in CLI

Before Synchronization:
•Rollover 2880
•Retention 24

After Synchronization:
•Rollover 1440
•Retention 12

10 — 1 — 103 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

You can also verify in the CLI that the policy changes have been sent to the network.

To verify the policy distribution in the CLI, perform the following tasks:
 Log in to the node using the CLI;
 Type show log file-id x (where x is the File Policy ID; this is 1 in the example shown on this slide);
 Review the command output. The configuration changes (Rollover and Retention parameters) need to show as
configured within the policy from the 5620 SAM.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 103
 9 Ethernet OAM tools

10 — 1 — 104 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This section describes the Ethernet OAM tools available in the 5620 SAM. For details about the Ethernet CFM and
EFM OAM tools, see the Ethernet OAM module in this course.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 104
 9 Ethernet OAM tools
9.1 Ethernet OAM tools—general

Ethernet Connectivity Fault Management (CFM) OAM tool kit

The CFM OAM supports end-to-end service management in a Layer 2 network
and provides for consistent service monitoring and tools to isolate faults and
to verify connectivity between two points. Specifies protocols, procedures,
and managed objects to support transport fault management, including
discovery and verification of a path, detection and isolation of connectivity
faults for each Ethernet service instance

5620 SAM Ethernet

OAM tools

Ethernet in the First Mile (EFM) OAM mechanism

The EFM OAM provides tools for monitoring link operations such as remote
fault indication and remote loopback control. The EFM OAM gives operators
the ability to monitor the health of the network and to quickly determine the
location of failing links or fault conditions. The 5620 SAM supports EFM OAM
diagnostic configuration on Ethernet ports in network mode on the 7705 SAR.

10 — 1 — 105 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The Alcatel-Lucent Service Routing Portfolio implements the following Ethernet OAM tools kits:
•The CFM OAM tool kit, as defined by the concepts and principles of the IEEE 802.1ag standard, also referred to as
the Ethernet Continuity Fault Management (CFM) standard, the ITU-T Y.1731 recommendation and MEF
specifications. For more information, see the Ethernet OAM module in this course.
•The Ethernet in the First Mile (EFM) OAM sublayer, as defined in the IEEE 802.3ah standard, Clause 57.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 105
 10 Ethernet CFM OAM

10 — 1 — 106 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 106
 10 Ethernet CFM OAM
10.1 Ethernet CFM test support

CFM loopback CFM linktrace

CFM Continuity Check

CFM One-Way Delay

5620 SAM Ethernet CFM CFM Two-Way Delay

CFM Ethernet OAM tests

CFM Two-Way SLM CFM Single-Ended Loss

CFM Dual-Ended Loss

10 — 1 — 107 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The CFM tools provide path discovery and fault detection, isolation, and notification. This slide shows the Ethernet CFM tests supported by the
5620 SAM:
•The CFM continuity check monitors path connectivity between pre-defined MEPs.
•The CFM loopback test verifies connectivity to a specific MEP or MIP.
•The CFM linktrace test verifies the hop-by-hop connectivity to a targeted MEP.
•The CFM one-way delay test measures the one-way trip time between the source and destination sites.
•The CFM two-way delay test measures the round-trip time between the source and destination sites.
•The CFM single-ended loss test calculates the rate of frame loss in each direction for Ethernet packets sent between two MEPs.
•The CFM dual-ended loss test calculates the rate of frame loss in each direction for Ethernet packets sent between two MEPs.
•The CFM two-way SLM test provides Synthetic Loss Measurement and it is used to check packet loss.
•The CFM Ethernet performs one-way in-service diagnostics that include verifying bandwidth throughput, frame loss, and bit errors.

See the release notice for your 7705 SAR for information about the support of a specific Ethernet test on your chassis.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 107
 10 Ethernet CFM OAM
10.2 CFM OAM components

IEEE 802.1ag name ITU-T Y.1731 name Function

Maintenance Domain Maintenance Entity (ME) Administrative scope and reach

(MD)

Maintenance Domain MEG Level Numerical identifier of the domain

Level

Maintenance Association Maintenance Entity Group Grouping of service endpoints

(MA) (MEG)

Maintenance Association MEG Endpoint (MEP) Terminating and origination

Endpoint (MEP) endpoints

Maintenance Association MEG Intermediate Point Management points between

Intermediate (MIP) endpoints
Point (MIP)

10 — 1 — 108 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide describes the service OAM components, as defined in the IEEE, ITU-T and MEF contributions to the
service OAM architecture and functionality. These components have been already discussed in the Ethernet OAM
module of this course.
Note that the 5620 SAM CFM implementation uses the Maintenance Entity Group (MEG) term. A MEG represents
one service and consists of a group of MEPs. Only one MEG can be associated with a service, but one service can
be associated with multiple MEGs. The 5620 SAM distributes MDs and MEGs through policies.
Within a MEG, MEPs can be sorted into logical groupings called MEG subgroups. A MEG that contains subgroups is
called a Global MEG. By default, a Global MEG has one subgroup. MEG subgroups allow you to group managed
MEPs and unmanaged remote MEPs so that Ethernet CFM can be directed to a specific area of a system rather
than to the entire system.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 108
 10 Ethernet CFM OAM
10.3 Configuring Ethernet CFM

Create an MD. You perform this task, as well as the following steps, in the
1 Maintenance Domain Policies form. Choose Tools → Ethernet CFM → Maintenance
Domain Policies from the 5620 SAM main menu.

Create one or more global MEGs in the MD. Each MEG must be associated with
2 one service or Ethernet path. Creating a Global MEG generates a CFM
continuity check test.

3 Associate a service with the Global MEG.

4 Add an Ethernet path to the Global MEG, as required.

5 Add a remote MEP to the MEG, as required.

6 Add an unmanaged remote MEP to the Global MEG, as required.

7 Add a MEG sub-group to a Global MEG, as required.

10 — 1 — 109 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide outlines the Ethernet CFM configuration in the 5620 SAM GUI. To configure the Ethernet CFM, you need
to create an Ethernet CFM MD and the subordinate objects associated with the MD such as a Global MEG, MEG,
and MEPs for each level at which Ethernet connectivity needs to be monitored.
The following slides provide high-level instructions about creating test policies and test suites, executing a test
suite, and viewing test results.
For detailed procedures about these tasks, see the 5620 SAM User Guide for your release.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 109
 10 Ethernet CFM OAM
10.4 Creating an Ethernet CFM test policy

Create a test policy. You perform this task in the Service Test Manager form.
Choose Tools → Service Test Manager (STM) from the 5620 SAM main menu.
1 Click on the Create button, choose Test Policy, and configure policy parameters.
You need to enable the NE Schedulable parameter, and select VLL Service,
VPLS, or Composite Service for the Entity Type parameter.

Add a test definition to the policy. Click on the Test Definition tab, and then click
on the Add button. A cascading submenu with test categories and options opens.
The Ethernet CFM category provides the following test definition options: Add
2 CFM Loopback, Add CFM Link Trace, Add CFM Two Way Delay Test, Add CFM
Two Way SLM.
Choose an Ethernet CFM test definition option and configure its parameters. You
can continue choosing additional options, as required.

Associate the Ethernet CFM test policy with an MD. Click on the CFM Details tab,
3
and choose and MD.

Save your Ethernet test policy by clicking on all the applicable Apply and OK
4
buttons on the Test Policy form tabs.

10 — 1 — 110 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide provides high-level instructions for creating an Ethernet CFM test policy. You create a CFM test policy
the same way you create a regular 5620 SAM test policy. When you add a test definition to the test policy, you
need to choose an Ethernet CFM test definition options from a cascading submenu. The options that are available
for selection depend on the on the Entity Type and NE Schedulable parameter values that you specified when
configuring the test policy parameters. The Ethernet CFM test definition options appear only if you selected
either the VLL Service or the VPLS option as the Entity Type, and if you also enabled the NE Schedulable
parameter.
For detailed information about creating an Ethernet CFM test policy, see the 5620 SAM User Guide for your
release.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 110
 10 Ethernet CFM OAM
10.5 Creating an Ethernet CFM test suite

Create a test suite. You perform this task in the Service Test Manager form.
Choose Tools → Service Test Manager (STM) from the 5620 SAM main menu.
1
Click on the Create button, choose Test Suite, and configure suite parameters.
You need to enable the NE Schedulable parameter.

Add a test policy to the test suite. Click on the Test Policy tab and perform the steps
2
required to search for test policies and add them to the test suite, as required.

Click on the tested Entities tab, and then click on the Add button to choose a
3
service, transport element, or device as the object on which the test suite is run.

Click on the First Run Tests tab, and then click on the Add button to choose a
4
predefined test to execute before the generated tests in the suite.

Click on the Last Run Tests tab, and then click on the Add button to choose a
5
predefined test to execute after the other tests in the suite have completed.

Click on the Generated Tests tab. Click on the Generate Tests button. The
6
5620 SAM begins generating tests for the test suite based on the test policy.

Click on the Generation Logs tab to view the log file that the 5620 SAM creates
7
during test generation, as required.

10 — 1 — 111 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide provides high-level instructions for creating an configuring an Ethernet CFM test suite. You create and
configure a CFM test suite the same way you create and configure a regular test suite. However, for Ethernet CFM
test suites, the NE Schedulable parameter needs to be enabled.
For detailed information about creating and configuring an Ethernet CFM test suite, see the 5620 SAM User Guide
for your release.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 111
 10 Ethernet CFM OAM
10.6 Executing an Ethernet CFM test suite
Choose Tools → Service Test Manager (STM) from the 5620 SAM main menu.
1
The Service Test Manager (STM) form opens.

2 Choose Test Suite (Edit) from the object drop-down list.

Configure the filter criteria., and click on the Search button. A list of test
3
suites appears.

Select an Ethernet CFM test suite, and click on the Properties button. The
4
Test Suite (Edit) form opens with the General tab displayed.

Click on the Execute button. Execution of the test suite begins. You can view the
5
test results when the test execution is complete.

Click on the Generated Tests tab. Click on the Generate Tests button. The
6
5620 SAM begins generating tests for the test suite based on the test policy.

Click on the Generation Logs tab to view the log file that the 5620 SAM creates
7
during test generation, as required.

You can also schedule the execution of an Ethernet CFM test suite.

10 — 1 — 112 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide provides high-level instructions for executing an Ethernet CFM test suite. You execute an Ethernet CFM
test suite the same way you execute any other test suite.
For detailed information about executing an Ethernet CFM test suite, see the 5620 SAM User Guide for your
release.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 112
 10 Ethernet CFM OAM
10.7 Viewing results of an Ethernet CFM test suite

Choose Tools → Service Test Manager (STM) from the 5620 SAM main menu.
1
The Service Test Manager (STM) form opens.

2 Choose Test Suite Result (Assurance) from the object drop-down list.

3 Click on the Search button. A list of test suite results appears.

Select an Ethernet CFM test suite result and click on the Properties button.
4
The Test Suite Result (View) form opens with the General tab displayed..

5 View the general information and statistics on the General tab.

6 Click on the Results tab to list the test results from the tests in the test suite.

Use the horizontal scroll bar at the bottom of the list to view the tabular
7 Information on the listed tests. To view information about a specific test, select
the test entry from the list and click the Properties button.

10 — 1 — 113 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide provides high-level instructions for viewing the results of an Ethernet CFM test suite. You view the
results of an Ethernet CFM test suite the same way you view the results of any other test suite.
For detailed information about viewing and analyzing the results of an Ethernet CFM test suite, see the 5620 SAM
User Guide for your release.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 113
 Knowledge check

The IEEE 802.1ag standard uses Maintenance Association (MA) and the ITU-T
Y.1731 recommendation uses Maintenance Entity Group (MEG) to designate the
same concept: a group of MEPs. What is the term used by the 5620 SAM
implementation?
a) MA
b) MEG
c) MA-MEG

The 5620 SAM Tools → Service Test Manager (STM) menu option gives you access
to some of the following tasks—select all that apply:
a) Viewing results of an Ethernet CFM test suite
b) Executing an Ethernet CFM test suite
c) Configuring Ethernet CFM
d) Creating an Ethernet CFM test policy

10 — 1 — 114 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

The IEEE 802.1ag standard uses Maintenance Association (MA) and the ITU-T Y.1731 recommendation uses
Maintenance Entity Group (MEG) to designate the same concept: a group of MEPs. What is the term used by the
5620 SAM implementation?
a) MA
b) MEG

The 5620 SAM Tools → Service Test Manager (STM) menu option gives you access to some of the following tasks—
select all that apply:
a) Viewing results of an Ethernet CFM test suite

b) Executing an Ethernet CFM test suite

c) Configuring Ethernet CFM
d) Creating an Ethernet CFM test policy

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 114
 11 EFM OAM diagnostics

10 — 1 — 115 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 115
 11 EFM OAM diagnostics
11.1 EFM OAM test support

Active and passive modes

EFM OAM capability discovery

Remote failure indication

5620 SAM EFM Local loopback

OAM tests

High-resolution EFM OAM timers

Remote loopback
EFM OAMPDU tunneling

10 — 1 — 116 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the EFM OAM tests supported by the 5620 SAM:
•EFM OAM capability discovery
•active and passive modes
•remote failure indication
•local loopback
•remote loopback
•EFM OAMPDU tunneling
•high-resolution EFM OAM timers

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 116
 11 EFM OAM diagnostics
11.2 EFM OAM diagnostic configuration—open 802.3ah form

In the navigation tree view selector, Choose Equipment. The Equipment

1
view opens.

Right-click on the device on which you need to configure an 802.3ah

2 EFM OAM diagnostic, and choose Properties from the contextual menu.
The Network Element (Edit) form opens with the General tab displayed.

3 In the Network Element (Edit) form navigation tree, expand the Shelf icon.

Navigate to the port level, and click on a port object. The Physical Port (Edit)
4
form opens with the General tab displayed.

Click on the Ethernet tab. The Ethernet port configuration form opens
5
with the General tab displayed.

6 Click on the 802.3ah tab. The 802.3ah form opens.

10 — 1 — 117 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Before using the EFM OAM tests, you need to configure them in the 802.3ah EFM OAM form. This slide provides
the steps required to navigate to the 802.3ah EFM OAM configuration form in the 5620 SAM GUI.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 117
 11 EFM OAM diagnostics
11.3 EFM OAM diagnostic configuration parameters

10 — 1 — 118 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide shows the 802.3ah form. Configure the EFM OAM parameters on the 802.3ah form, as required:

Administrative State

Tunneling

Mode

Transmit Interval

Multiplier (Intervals)

Received Remote Loopback Requests

Set Remote Loopback

Set Local Loopback

Hold Time (s)

Ignore EFM State

Grace Tx State Enable

To save the EFM OAM configuration and run the EFM OAM diagnostics, you need to use the buttons at the bottom
of the 802.3ah form. The next slide provides the steps to perform these tasks.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 118
 11 EFM OAM diagnostics
11.4 EFM OAM diagnostics

Save the 802.3ah configuration

1 Click on the Apply button. The Confirm window opens.

Click on Yes to confirm the configuration changes.

2
Now you are ready to run the EFM OAM diagnostics.

Run the 802.3ah diagnostics

3 Click on the Resync button. The Confirmation window opens.

Click on Yes to confirm the resynchronization. The 5620 SAM

4
updates the form with the results of the 802.3ah diagnostic.

3 4 1 2

10 — 1 — 119 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Before running the EFM OAM diagnostics, you need to save the 802.3ah configuration. Follow the steps provided
on the slide.
After saving the diagnostic configuration, run the EFM OAM diagnostics as shown on the slide. The 5620 SAM
updates the form with the results of the 802.3ah diagnostic. The values that are displayed on the form depend on
the configuration of the local and peer ports.
The 5620 SAM also populates the Statistics and Peer Information panels with information collected by the EFM
OAM diagnostic. The next slide provides details about the content of the Statistics and Peer Information panels.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 119
 11 EFM OAM diagnostics
11.5 EFM OAM diagnostic results—Statistics
Statistics Displayed Value Description

Information Tx Number of OAMPDUs The number of information OAMPDUs transmitted on

(dot3OamInformation Tx) this interface.

Loopback Control Tx Number of OAMPDUs The number of loopback control OAMPDUs transmitted
(dot3OamLoopbackConrolTx) on this interface.

Unsupported Codes Tx Number of OAMPDUs The number of OAMPDUs transmitted on this interface
(dot3OamUnsupportedCodesTx) with an unsupported opcode.

Frames Lost Due to OAM Number of frames The number of frames that were dropped by the OAM
(dot3OamFramesLostDueToOam) multiplexer.

Information Rx Number of OAMPDUs The number of information OAMPDUs received on this

(dot3OamInformationRx) interface.

Loopback Control Rx Number of OAMPDUs The number of loopback control OAMPDUs received on
(dot3OamLoopbackControlRx) this interface

Unsupported Codes Rx Number of OAMPDUs The number of OAMPDUs received on this interface with
(dot3OamUnsupportedCodesRx) an unsupported opcode

10 — 1 — 120 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide describes the EFM OAM diagnostic results displayed in the Statistics panel of the 803.2ah form.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 120
 11 EFM OAM diagnostics
11.6 EFM OAM diagnostic results—Peer Information
Peer information item Value Description

Peer MAC Address MAC address The MAC address of the peer port. The MAC address is
(dot3OamPeerMacAddress) contained in the received OAMPDU.

Peer Vendor OUI Organization Unique The OUI of the OAM peer: part of the peer MAC address
(dot3OamPeerVendorOui) Identifier contained in the received OAMPDU. The OUI can be used to
identify the vendor of the remote OAM device.

Peer Vendor Info Vendor information The vendor information field is in the local information TLV, and
(dot3OamPeerVendorInfo) text can be used to determine additional information about the peer
device.

Peer Mode (dot3OamPeerMode) Active or Passive See Mode.

Peer Max PDU Size PDU size The largest OAMPDU value, in bytes, that is supported by the
(dot3OamPeerMaxOamPduSize) peer port. The default is 1514.

Peer Configuration Revision 0 to 65 535 The configuration revision of the OAM device as identified in the
(dot3OamPeerConfigRevision) latest OAMPDU sent by the OAM peer.

Peer Functions Supported Event Support The peer port can send and receive Event Notification OAMPDUs
(dot3OamPeerFunctSupported) Loopback Support The peer port can initiate and respond to loopback commands
Unidirectional Support The peer port supports the OAMPDUs Tx on unidirectional links
Variable Support The peer port can send and receive Variable Request and
Response OAMPDUs

10 — 1 — 121 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

This slide describes the EFM OAM diagnostic results displayed in the Peer Information panel of the 803.2ah form.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 121
 Knowledge check

What is the name of the EFM OAM diagnostic configuration form in the 5620 SAM?
a) 802.1ag
b) 802.3ah
c) Y.1731

Which of the following tests are EFM OAM tests? Select all that apply.
a) linktrace
b) local loopback
c) remote loopback
d) continuity check
e) remote failure indication

10 — 1 — 122 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

What is the name of the EFM OAM diagnostic configuration form in the 5620 SAM?
a) 802.1ag
b) 802.3ah

c) Y.1731

Which of the following tests are EFM OAM tests? Select all that apply.
a) linktrace
b) local loopback

c) remote loopback

d) continuity check
e) remote failure indication

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 122
 Module summary

In this module, you have learned:

What are the major components of the 5620 SAM.

What are the 5620 SAM modules.

How to configure Cpipe and Epipe services in the 5620 SAM.

How to make and distribute policies.

What are the Ethernet OAM tools supported by the 5620 SAM.

10 — 1 — 123 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

In this module, you have learned:

What are the major components of the 5620 SAM.

What are the 5620 SAM modules.

How to configure Cpipe and Epipe services in the 5620 SAM.

How to make and distribute policies.

What are the Ethernet OAM tools supported by the 5620 SAM.

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 123
End of module
5620 SAM

10 — 1 — 124 COPYRIGHT © ALCATEL-LUCENT 2014. ALL RIGHTS RESERVED.

Service Aware Manager — 5620 SAM
7705 SAR — R6.0 Strategic Industries

Copyright © 2014 Alcatel-Lucent. All Rights Reserved.

TER36055_V3.0-SG-R6.0-Ed1 Module 10.1 Edition N/A
Section 10 — Module 1 — Page 124
Last but one page

Congratulations
You have finished the training

Your feedback is appreciated!

Please feel free to Email your comments to:

[email protected]

Please include the training reference in your email (see cover page)

Thank you!

1 All Rights Reserved © Alcatel-Lucent @@YEAR

@@PRODUCT
@@COURSENAME

All Rights Reserved © Alcatel-Lucent @@YEAR

@@COURSENAME - Page 1
All rights reserved © Alcatel-Lucent
Passing on and copying of this document, use and communication of its contents
not permitted without written authorization from Alcatel-Lucent

All Rights Reserved © Alcatel-Lucent @@YEAR

@@COURSENAME - Page 2