3_3_LabelSwitchedPaths.pdf

7/21/2019 3_3_LabelSwitchedPaths.pdf

1/22

Section 3 Module 3 Page 1

All Rights Reserved Alcatel-Lucent 2008

Issue 02

Do not delete this graphic elements in here:


Module 3Label Switched Paths

Issue 02

Section 3Operation

Alcatel-Lucent GMRE+ASONOperation Rel.3.2

3FL35093AAAAZZZZZ Issue Ed02


2/22



Issue 02


Alcatel-Lucent GMRE+ASON Operation Rel.3.2Operation Label Switched Paths

3 3 2

Blank Page

This page is left blank intentionally

First editionBelgard, Steffen2006-06-0101

RemarksAuthorDateEdition

Document History


3/22



Issue 02



3 3 3

Module Objectives

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

Learn how to setup LSPs

Get to know the management


4/22



Issue 02



3 3 4

Module Objectives [cont.]



5/22



Issue 02



3 3 5

Table of Contents

Switch to notes view!Page

1 LSP Setup 71.1 Introduction 81.2 Mandatory Parameters 9

1.3 Optional parameters 101.4 Example 111.5 Exercise 13

2 LSP Management 142.1 Priority Changing 152.2 Nominal Route 162.3 Move current route 182.4 Shutdown and deletion 202.5 Exercise 21


6/22



Issue 02



3 3 6

Table of Contents [cont.]

Switch to notes view!



7/22



Issue 02



3 3 7

1 LSP Setup


8/22



Issue 02



3 3 8

1 LSP Setup

1.1 Introduction

VC4

VC4

VC4 Label Switched Path

Cross connection with label switch



ASON

Note: Label Switched Paths are always bi-directional in GMPLS. Whereas MPLS defines LSP as uni-

directional.


9/22



Issue 02



3 3 9

1 LSP Setup

1.2 Mandatory Parameters

Mandatory parameters to setup LSPs:

InLink

- denotes local ingress interface address or index (e.g. drop port)

InLabel

n-0-0-0-0 - the GMPLS label (S-U-K-L-M) position at ingress interface

DestLSR

- the IP address of NNI session destination LSR

DestLink

- denotes egress interface address or index at the DestLSR (e.g. drop port)

DestLabel

n-0-0-0-0 - the GMPLS label (S-U-K-L-M) position at egress interface of the DestLSR

LspTraffic

VC4, VC4-4c, VC4-16c or VC4-64c

ProtRestType

GUARANTEED - Guaranteed

PRC - Protection Restoration Combined

SBR - Source Based Restoration

SNCP Subnetwork Connection Protection

UNPROTECTED - Unprotected


10/22



Issue 02



3 3 10

1 LSP Setup

1.3 Optional parameters

Optional following parameters can be configured

SourceTNA, DestTNA

Can be used on UNI links instead of specifying InLink+InLabel and DestLink+DestLabel

The GMRE will automatically select the Links and Labels from the TNA addresses

Priority

- the GMRE supports by default 5 priority levels (1..5, where 1 is the highest priority)

ReversionMode:

< Automatic | Manual > - Automatic reversion will try to revert the nominal route after 5 minutes

without alarm on it.

NominalRoute, BackupRoute

Hop = #//

Allows the operator to specify the explicit route the LSP should take for (SNCP Main) nominal and(SNCP Main) backup paths

If provided, all Hops must be provided

Only NodeAddr & TeLink are mandatory

BackupRoute is optional

SpareNominalRoute, SpareBackupRoute

Hop = #//

Similar to the definition of the NominalRoute and Backup Route for specifying the SNCP Spare routes.

LinkDiversity


11/22



Issue 02



3 3 11

1 LSP Setup

1.4 Example

LSP index

LSP setup configuration is always accepted, if there is no syntax error or no errors on the Ingress (current)

node.

To check if the LSP is physically setup in the network, use the show lsp commands or the CLI notification

feature.

If the setup fails, GMRE will try to setup the path later on.


12/22



Issue 02



3 3 12

1 LSP Setup

1.4 Example [cont.]

Node Role

Actual Route


13/22



Issue 02



3 3 13

1 LSP Setup

1.5 Exercise

Setup of Label Switched Paths

Please set up a path to a remote node

Configure it according the training manual

Watch the results


14/22



Issue 02



3 3 14

2 LSP Management


15/22



Issue 02



3 3 15

2 LSP Management

2.1 Priority Changing

Standard Priority 5

Priority 1

The Priority attributes can be changed at any time, even while the LSP is active.

Priority

The GMRE will not make any immediate consequent action

However in the network, there could be indirect consequent actions if some protection or restoration

events take place due to the new priority distribution


16/22



Issue 02



3 3 16

2 LSP Management

2.2 Nominal Route

Label Switched Path=Subnetwork Connection

1

2

TE-Link 100001

Databearer

Databearer 13050201

TE-Link 100002

Tail side interface

To determine routes the "addresses" of the tail interfaces have to be used as follows.

#//

Example:

config ... 10.10.255.1/100001/13050101/1-0-0-0-0, 10.10.255.2/100002/13050201/1-0-0-0-0


17/22



Issue 02



3 3 17

2 LSP Management

2.2 Nominal Route [cont.]

New nominal route

Old nominal route

The configured nominal route can be modified permanently for maintenance actions, e.g. resolve

deadlocks, re-arrange the network manually, etc.

The Nominal Route can be modified at any time without causing a traffic hit

hitless move of nominal traffic

Based on the current status of the Nominal route, the following sequences should follow:

Nominal path is active:

A temporary SNCP is created with the new Nominal route, switched to the new, then the old Nominal

route is torn down

Nominal path is inactive:

The new Nominal path is immediately taken over and the usual reversion attempts to nominal take

placeThe Spare Nominal Route for SNCP can also be modified


18/22



Issue 02



3 3 18

2 LSP Management

2.3 Move current route

MaintenanceMove traffic

The current route can be modified at any time without causing a traffic hit

This can be applied to the nominal or backup paths and is temporary

Used in maintenance scenarios to do with Locking and Freeing ports

First the port which needs to be freed must be Locked by setting the Databearer AdminState=Down. In this

state:

Existing LSPs on the Databearer are unaffected

New LSPs will not be able to use the Locked port

Once all LSPs have been moved away from it, the Databearer will automatically become

AdminState=Down

The move from command is used to move traffic away from the corresponding TE-Link(s)

On completion of the maintenance actions, when the Databearer AdminState is set to UP, the LSPsautomatically revert back to their original routes.

Attention: If protection and/or restoration is defined for LPSs running on this databearer,

AdminState=down will cause restoration.


19/22



Issue 02



3 3 19

2 LSP Management

2.3 Move current route [cont.]

Adminstate SHUTTINGDOWN

By setting the adminstate of the databearer to 'SHUTTINGDOWN', it will remain 'UP until all traffic is

moved from. Up on this it will go DOWN automatically.


20/22



Issue 02



3 3 20

2 LSP Management

2.4 Shutdown and deletion

LSPs are gracefully deleted simply by setting the LSP AdminState=DOWN

The LSP configuration will remain in the GMRE ingress node and in persistency. This allows the LSP to be

setup again by simply setting AdminState=UP

While LSPs are in AdminState=DOWN, network resources are not used or reserved.

To completely delete the LSP configuration and from persistency, the delete lsp command can be used.


21/22



Issue 02



3 3 21

2 LSP Management

2.5 Exercise

Try out the LSP management

Change priority

Change the nominal route

Change the current route Tear down your created LSPs


22/22



3 3 22

End of ModuleLabel Switched Paths

Documents

3_3_LabelSwitchedPaths.pdf