gmplscookbook ts-workshop issue01

7/29/2019 GMPLSCookbook TS-Workshop Issue01

1/35

Cookbook

for

GMPLS configuration

on hiT7300 R4.30


2/35

GMPLS cookbook TS-Workshop

Page 2 /35

GMPLSCookBook_TS-Workshop_Issue01.doc

Copyright 2010 Nokia Siemens Networks GmbH & Co KG

Issued by NWS Product Management TS PS DWDMSt.-Martin-Str. 76D-81541 Mnchen

Document History

Revision Issue Date Remarks

Issue 01 2011-01-18 1st release for R4.30.01


3/35


Page 3 /35


1 Planning of equipment for a new GMPLS serviceBefore a new service is can be created, the related equipment needs to beinstalled and make sure, that the used hardware provides sufficient opticalperformance to bridge the distance without regeneration.

A GMPLS control plane offers some degree of photonic constraint aware routing,taking OSNR and non linear effect into account. This is sufficient for most Metroor Regional networks. More demanding long haul networks however are betteraddressed by a dedicated wavelength planning tool like TransConnect.

This means that two options exist for the planning of new equipment:

1. Either supported by a planning tool (solid lines). The planning tool alsoprovides a detailed list of a equipment which needs to be installed (of courseTransponders, but potentially also filters, regenerators, cables), a cabling

plan, and an optical performance analysis report. In case GMPLS restorationmechanisms are used, the planning tool can also define and pre-plandedicated restoration routes => Recommended way

2. Alternatively skipping the planning tool (dotted line) and relying either onphotonic constraint based routing in the GMPLS plane, or some manualrouting tables.

Planning of equipment for a

new GMPLS service

Planning of equipment for a

new GMPLS service

PCEPCE

PCE

Network

Operator

Planning Tool

TransConnect

Optical Perf. Report

Cabling Plan

List of Material

For simple networks:

Skip TransConnect


4/35


Page 4 /35


1.1 Introduction

The first implementation of GMPLS into the SURPASS hiT 7300 was done withthe software version 4.30.01 v3.

GMPLS doesn't support any control plane recovery scheme, in particular, RSVPrestart is not supported. The only persistent information concerns protocol andinterface parameters, as well as call configuration at ingress.

1.1.1 Requirements for GMPLS

To operate GMPLS on the SURPASS hiT 7300 prerequisites according to thehardware and the planning process must be considered.

1.1.1.1 Hardware requirements

In the current version of SURPASS hiT 7300 GMPLS runs only on following typeof network elements:

ONN-X

ONN-X80

On these NEs it the switching of wavelengths is the only supported configuration.Configuration of transponder cards is not supported up to now by the GMPLS.

Next to the limitation of network element types there is also a newer controller

card and CF card to be installed necessary.

CCMP-2

CCEP-2

CF with 8GB capacity

1.1.1.2 DCN requirements

Only one DCN / GMPLS are supported in the actually release


5/35


Page 5 /35


1.1.1.3 Planning requirements

When GMPLS should be used certain configurations must be done in theTransNet planning tool. Following settings are necessary:

Service Provisioning via NMS must be enabled

To double-check this setting on the NEs, complete the following steps:1. In the EM main menu, select the Configuration > NE-Configuration... menu

item.The Network Element Configuration window is opened.

This example shows a NE with Service Provisioning enabled.


6/35


Page 6 /35


This example shows a NE with Service Provisioning looked.

WARNING

IF SERVICES ARE CREATED WITH GMPLS THERE IS NO POSSIBILITY TOIMPORT THESE SERVICES INTO THE TRANSNET TOOL AT THE MOMENT.

Requirements for GMPLS

Hardware Requirement:

Network Element Type:

ONN-X

ONN-X80

Controller card:

CCMP-2 + CF with 8GB capacity

CCEP-2 + CF with 8GB capacity

DCN Requirement:Only one DCN / GMPLS domain

Software Requirement:

APS version:

4.30.1

Planning Requirement:

TransNet settings:

Service Provisioning via NMSmust be enabled


7/35


Page 7 /35


1.1.2 Calculating Router ID

Each GMPLS activated network element has a unique identifier. This identifier iscalled Router ID. It's used for internal communication between the GMPLSnodes.

For calculating the Router ID, it is necessary to know the internal IP address. Theinternal IP address can be found e.g. on the primary DHCP serverCommunication > Reachable Systems.

To the internal IP address 0.0.128.0 will be added.

The Router ID will be calculated like this example:

DHCP IP address:

172.16.1.31

Calulation:

172.16.1.31 + 0.0.128.0 172.16.129.31

Router ID:

172.16.129.31

WARNING

If GMPLS should be used the DHCP pool basis address must be lower than172.X.127.X. Otherwise there will be a conflict to calculate the Router ID.


8/35


Page 8 /35


Calculate Router IDCalculate Router ID

e.g.

ONN-X NE3

Internal IP: 172.16.1.128

Router ID:

Internal IP + 0.0.128.0 Router ID172.16.1.128 + 0.0.128.0 172.16.129.128 Router ID: 172.16.129.128


9/35


Page 9 /35


1.2 Init ial configuration of GMPLS

Before creating services with GMPLS an initial configuration must be performedon all NEs that will participate in the GMPLS service creation.

TIPAfter every action related to the GMPLS configuration it is necessary up to now toupdate the GUI.

1.2.1 Enabling GMPLS service

If all hardware and planning requirements received attention, the GMPLSprocesses must be started on the CCxP card of all PXC nodes you are using forGMPLS.

To enable the GMPLS features following steps must be performed:1. In the EM main menu, select the Configuration > NE > Configuration ...

menu item.The Network Element Configuration window is opened.

2. Select the Management tab and check the GMPLS enabled checkbox.

3. Click the Apply button make the changes effective.


10/35


Page 10 /35


Enable GMPLS processEnable GMPLS process

2

3

1


11/35


Page 11 /35


1.2.2 GMPLS general settings

The GMPLS configuration window provides several information and settingsregarding the running GMPLS of the NE. Most of the settings are not userconfigurable however; a limited number of parameters can be configured by theuser if necessary.

WARNINGIt is recommended that all the default GMPLS configuration settings areused. Only execute the following procedure in exceptional circumstances.

To configure the GMPLS of an NE, complete the following steps:

4. In the EM main menu, select the Communication > GMPLS >Configuration... menu item.

The GMPLS Configuration window is opened.5. In the RSVPtab configure the following settings as desired: Sender TTL: Enter the Time-To-Live value of the sender.

Min peer restart: Enter the minimum peer restart time.

Setup priority: Enter the LSP setup priority value.

Holding priority: Enter the LSP holding priority value.

6. In the RRtab configure the following settings as desired:

Interval: Enter the Route Reflector notification interval.

7. In the TE tab configure the following settings as desired:

Allow graceful deletion: Select/Clear the checkbox to enable/disable thedeletion of a TE link without traffic disruption.

Show transit tunnel: Select/Clear the checkbox to show/hide the transittunnel.

Maximum attempts: Enter the maximum number of attempts for a tunnelretry.

8. In the CMS tab enable the IPS Tracing to get more service information.

For this checkbox you have to enable the Service Mode first!

9. Click Applyto confirm the settings.The GMPLS of the NE is configured. Please repeat his setting for the other NEs.


12/35


Page 12 /35


GMPLS general configurationGMPLS general configuration

GMPLS general configuration


13/35


Page 13 /35


1.2.3 GMPLS interface conf iguration

It is important to enable the GMPLS process on the dedicated line interfaces ofthe ONN-X network element. If the interface is configured and up the RSVPprotocol will start working on this dedicated interface.

For the GMPLS configuration is only the Booster port important. The relatedPreamp port is known by the system itself. To identify an interface, the shelf-slot-port values for the booster are required.

WARNINGIf the interface is not configured correctly, GMPLS calls via this interfaceare not possible. There will be no warnings or alarm created by a wrongconfiguration.

Each interface which is a part of a GMPLS call has a remote interface. Exceptthe interfaces which are a pure ingress or a pure egress interface in a GMPLSdomain, it means these interfaces are connected to nodes outside the GMPLSdomain. The interface configuration take place in each node which is involved ina GMPLS call for the by GMPLS used interfaces.


14/35


Page 14 /35


Example for a useful overview of the available GMPLS nodes (PXC only)

2-7-2

1-7-2

3-7-2

2-7-2

1-7-2

3-7-2

2-7-21-7-2 2-7-21-7-2

1-7-22-7-2

GMPLS Call

Protec. Hop1 Protec. Hop2

Worker Hop1 Worker Hop2 Worker Hop3

194.0194.0

NE1

NE2 NE3

NE4

NE5

GMPLS CCWorker

GMPLS CCWorker

GMPLS CCWorker

GMPLS CCWorker

GMPLS CCProt.

GMPLS CCProt.

GMPLS CCProt.

NE1 NE2 NE3 NE4 NE5Int. DHCP IP Addr. (Example) 172.16.1.2 172.16.1.54 172.16.1.39 172.16.1.3 172.16.1.78GMPLS IP Addr. 172.16.129.2 172.16.129.54 172.16.129.39 172.16.129.3 172.16.129.78


15/35


Page 15 /35


To configure GMPLS interfaces, complete the following steps:

1. In the EM main menu, select Communication > GMPLS > Interfaces...menu item.The Interfaces Configuration window is opened.

2. Select the first wanted interface and press Interface Management. Enter theremote interface (in this case the same value as the local interface seeexample) and the remote router ID (GMPLS Control Plane IP address) forNE2.

GMPLS Interface configuration

3

4

2

5

GMPLS Interface configuration see example NE2

3. In the General tab, configure the following settings:

Name: Enter the GMPLS interface name. This parameter is only possible tochange if the Administrative Status is down.

Administrative Status: Select the administrative status from the drop-downmenu. A warning message is opened. Click the Continue button to confirmthe setting.

Remote Router ID: Enter the remote router ID. This parameter is onlypossible to change if the Administrative Status is down.


16/35


Page 16 /35


4. Click Apply to confirm the settings.5. Click Update to update the window information.6. Click Close to close the Interface Management window.7. Repeat the steps 2 up to 6 for all interfaces dedicated for GMPLS on this

network element.

Follow the comments in the next steps to complete the example

The Interface 3-7-2 NE1 is the interface as pointing to the starting point of the opticalchannel (for example a I01T10G card in a neighbor NE (ONN-I)). He has no a remoteGMPLS interface. So the remote router ID and the remote Tx index is zero (see nextpicture)

Apply this configuration and select the last Interface in this node.

For the third interface in NE1 (Tx index 2-7-2): the remote Tx is 2-7-2 and the remoterouter ID is 172.16.129.78 (NE5)

Apply also these settings; you will get back to the Interface Configurationswindow.


17/35


Page 17 /35


Set the Administrative Status to UP on all configured Interfaces.Check the Operational Status (press F5 - window update). It must switch to Up.

8. Click Close to close the Interfaces Configuration window.

9. Repeat the steps 1 up to 8 for all other NEs dedicated to run GMPLS.

The GMPLS interface configuration is completed.


18/35


Page 18 /35


1.3 Create Services via GMPLS

A service created through GMPLS is call "Call". The Call describes the paths(worker/protection) of a communication channel though the network. It must

reflect its real topology. The Call configuration take place in the Ingress Nodeand is only there necessary.

1.3.1 Create Call

The contents of a Call are the Ingress Interface, Source Router, EgressInterface, Destination Router and the Hop List. Regarding this informations,the GMPLS will create the needed cross connections.

To add a call list entry to the NE, complete the following steps:

Our example call is staring in NE1. So this NE is the Ingress-NE and here is the Callto configure. All other involved NEs will informed by NE1.

1. In the EM main menu, select the Communication > GMPLS > Call List...menu item. The Call List window is opened.

2. Click the Add... button. The Call Add window is opened.3. In the General tab configure the following settings for our example: Administrative status: Select the administrative status of the call. DOWN Description: Enter a description for the new call. Deletion mode: Select the deletion mode of the call. Graceful Call event history size: Enter the size of the call event history. 10 Source Router ID: Enter the IP address of the source router. 172.16.129.2

(ingress NE)

Destination Router ID: Enter the IP address of the destination router. 172.168.129.3 (egress NE)

Name: Enter the call list name (appears in the CC list column Trail identifier).


19/35


Page 19 /35


Create GMPLS call (1)Create GMPLS call (1)

2 3

4. In the Traffic tab configure the following settings as desired: Protection class: Select the type of traffic protection for the call.

Restoration

This open the possibility to configure a protection hop list. Otherwise only theworker hop list is selectable.

Auto reversion: Select/Clear the checkbox to enable/disable the reversion tothe initial working and protecting LSPs. Wait restore timer: Enter the waiting time to restore traffic on the working

path. Restoring traffic will cause a traffic hit!

Signal type: Select the type of traffic signal of the call (2,5G / 10G / 40G).


20/35


Page 20 /35



4

5. In the Routing tab configure the following settings as desired: Port: Select the routing ingress shelf/slot/card/port. 3-7-2 in our example Frequency: Select the routing ingress frequency. 194.000 in our example Shelf: Enter the routing egress shelf number. Shelf1

Slot: Enter the routing egress slot number. Slot 7 Port: Enter the routing egress port number. Port 2in our example


21/35


Page 21 /35



6

5

16

When we are starting from the beginning, all the hop lists are empty. So it isnecessary to create it.

6. Click the Select Working Hop List... button. The - GMPLSCurrent Working Hop List Config is opened.


22/35


Page 22 /35


Create GMPLS call (4)

8

7

7. Click the Add List... button. The - Hop List Add window isopened.

8. Configure the following settings:

Router ID: Enter the IP address of the router. Should be filled automatically withthe source router ID entered in step 3.

TE Link ID: Select the hop list card shelf/slot/card/port.

For our example:

If it is the first hop for the hop list of this call, the Router ID of the ingress NE isset by default.

The TE Link ID is the interface in NE1, which is pointing to the next element inthe worker path chain. For this example the interface which is connected to NE2(1-7-2).

Click the Add button to create a working hop list.

9. Click the Add Hop... button. The - Hop Add window is opened.

10. Configure the following settings:


23/35


Page 23 /35


Router ID: Enter the IP address of the router. Should be filled automaticallywith the source router ID entered in step 3.

Shelf: Enter the hop card shelf number.

Slot: Enter the hop card slot number.

Port: Enter the hop card port number.

For our example:

Now the first hop in the Hop List #4 is created (the list index #4 is caused bythree other attempts to create a hop list). For add the second hop into this listselect a row with the list index #4 and press Add Hop. Enter the router ID for thesecond NE of the worker path chain and select the interface which is pointing tothe third part of this path

Click the Apply to add a working hop to the hop list.

Create GMPLS call (5)

10

9

The next hops for the example are available in the next pictures.


24/35


Page 24 /35


The hop list #4 is now reserved for the working path of this GMPLS Call.

Repeat these steps to create the Protecting Hop List. Of course use the right values forthe protection path.

11. Select the working hop list entry from the table and click the Select button.

Click Apply to confirm the settings.12. Close the - GMPLS Current Working Hop List Config

window. Return to the Call Add window, Routing tab.

13. Click the Select Protecting Hop List... button. The - GMPLSCurrent Protecting Hop List Config is opened.


25/35


Page 25 /35


14. Select the protecting hop list entry from the table and click the Select button.Click Apply to confirm the settings.

15. Close the - GMPLS Current Protecting Hop List Configwindow. Return to the Call Add window, Routing tab.

16. Click the Add button to create the call list.


26/35


Page 26 /35


17. To dial the prepared GMPLS connection setAdministrative Status to up.

18. Click the Apply button to activate the call.

19. Use the Update button to verify the operational status. If the operational

status is Up the call is set up.

A new call list entry is added.

IMPORTEND TIPThe activation time between of a GMPLS call:

Datarate 10Gbit/s Activation time up to 90 seconds

Datarate > 10 Gbit/s Activation time up to 6 minutes

If the call activation takes longer there is possible a mistake.

Check all the settings and whether required resources (TPs for CrossConnections) are already in use.

END of our example!


27/35


Page 27 /35


1.3.2 Verify Call result

After a call was added to the call list and the operational status was set to up, theresult of the new created service should be verified.

On following places the call result is checked:

Transponder cards line interfaces

GMPLS Call List

GMPLS Call List > Modifiy > Events

Cross Connections

Verify Call resultsVerify Call results


28/35


Page 28 /35


Verify Call resultsVerify Call results


29/35


Page 29 /35


1.4 Modification or Service tasks

GENERALLY WARNING!

ALL MODIFICATIONS ON A RUNNING GMPLS CALL, HAS DIRECTLY

AFFECTS TO THE RUNNING TRAFFIC AND HIT THE TRAFFIC IN THE MOSTCASES!

1.4.1 Modify Call

To modify a call list entry of the NE, complete the following steps:

WARNINGModifications of a GMPLS Call are always traffic affecting! In this case alCross Connections for this Call will deleted automatically. This always the

case if the Administrator status will be set from UP to DOWN!

1. In the EM main menu, select the Communication > GMPLS > Call List...menu item. The Call List window is opened.

2. Select the entry to modify from the table and click the Modify... button. The - Call Modify window is opened.3. In the General tab configure the following settings as desired: Administrative status: Select the administrative status of the call. Destination Router ID: Enter a description for the new call. Description: Enter a description for the new call. Deletion mode: Select the deletion mode of the call. External switch requests: Enter a description for the new call. Call event history size: Enter the size of the call event history.4. In the Traffic tab configure the following settings as desired: Protection class: Select the type of traffic protection for the call. Auto reversion: Select/Clear the checkbox to enable/disable the reversion to

the initial working and protecting LSPs. Wait restore timer: Enter the waiting time to restore traffic. Signal type: Select the type of traffic signal of the call.5. In the Routing tab configure the following settings as desired: Port: Select the connection ingress port.


30/35


Page 30 /35


Frequency: Select the connection ingress frequency. Shelf: Enter the connection egress shelf number. Slot: Enter the connection egress slot number. Port: Enter the connection egress port number.6. If the working/protecting hop lists need to be modified complete steps 6 to 25

from the Adding a call entryprocedure. Click Apply to confirm all thechanges.

The call list is modified as desired.

Now it will take time to create the CC for the call again in the system and to bringthe status to UP.


31/35


Page 31 /35


Modify GMPLS callModify GMPLS call

34

2

Modify GMPLS callModify GMPLS call

5

6


32/35


Page 32 /35


1.4.2 Delete Call

To delete a call list entry from the NE, complete the following steps:

In the EM main menu, select the Communication > GMPLS > Call List... menuitem. The Call List window is opened.2. Set the Administrative Status to Down to remove the cross connections.

3. Select the desired call list entry from the table and click theDelete button.The call list entry is deleted.

WARNING

If the Administrator status will be set to DOWN, the system will delete theCC for this Call in the GMPLS network. In this case you have always trafficaffecting!


33/35


Page 33 /35


Delete GMPLS callDelete GMPLS call

23


34/35


Page 34 /35


1.4.3 Manual swi tching between working and protectionGMPLS path

To modify a call list entry of the NE, complete the following steps:In the EM main menu, select the Communication > GMPLS > Call List... menuitem. The Call List window is opened.2. Select the entry to modify from the table and click the Modify... button. The - Call Modify window is opened.3. In the General tab change the External switch request field according to the

needs.

4. Click Apply to confirm all the changes.

WARNINGSwitching between working and protection GMPLS path is always trafficaffecting!

TIPSwitching time between working and protection GMPLS path:

Datarate 10Gbit/s Switching time up to 90 seconds

Datarate > 10 Gbit/s Switching time up to 6 minutes


35/35


Manual Protection switchManual Protection switch

2

3

4

gmplscookbook ts-workshop issue01

Documents