4_1_ason_mgt

Section 4 · Module 1 ·

All Rights Reserved © Alcatel-Lucent 2008Issue 02

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 2008

Module 1Management

Issue 02

Section 41354 RM ASON

Alcatel-Lucent GMRE+ASONOperation Rel.3.2

3FL35093AAAAZZZZZ Issue Ed02




Alcatel-Lucent GMRE+ASON · Operation Rel.3.21354 RM ASON · Management4 · 1 · 2

Blank Page

This page is left blank intentionally

First editionBelgard, Steffen2006-06-0101

RemarksAuthorDateEdition

Document History





Module Objectives

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

Create Shared Risk Groups

Create ASON NPAs

Create HO-Trails / Paths crossing an ASON





Module Objectives [cont.]






Table of Contents

Switch to notes view! Page

1 Introduction 71.1 From IP to GMPLS 81.2 Plane model 111.3 GMRE architecture overview 131.4 Management of an ASON: Architecture 14

2 ASON Management in RM 152.1 Terminology 162.2 Steps 18

3 Shared Risk Group Management 193.1 Introduction 203.2 Create SRG 223.3 Correlate physical connections to SRGs 24

4 ASON NPA Management 254.1 Bundling rule 264.2 Create ASON NPA 274.3 Getting relevant information - ASON NPA Highlight 284.4 Getting relevant information - ASON NPA view 294.5 Getting relevant information - internal physical connections 304.6 Getting relevant information - SDH ports 314.7 Getting relevant information - TE-Links 32

5 Physical Connection Management 345.1 Unlock physical connections 35

6 HO-Trail / Path Management 376.1 Introduction - node roles 386.2 Introduction - SNC 396.3 Introduction - protection and restoration 416.4 Path setup from RM 456.5 Getting relevant information - ASON NPA view 486.6 Getting relevant information - examples 496.7 Getting relevant information - NPA boundary CTPs 54





Table of Contents [cont.]

Switch to notes view!






1 Introduction





1 Introduction

1.1 From IP to GMPLS

IP packet communication:

4localBc

1cBb

3bBa

PortNext Routerto use

DestinationRouter

Routing table:

AB

ad

c

b

12

3

2 31

4

123

4

4

IP packet communication:

Information is transmitted in packets.

Each packet contains source and destination address.

Packets are routed according the routing tables in each router of the network.





1 Introduction

1.1 From IP to GMPLS [cont.]

MPLS (Multi-Protocol-Label-Switching):

LSP setup

AB

ad

c

b

Port 1 Port 2IP 25

IP 19

MPLS Label

Port 3 Port 4Swap(4, 19)(1, 25)

Swap(3, 12)(2, 23)

Swap(3, 17)(1, 24)

Swap(2, 17)(1, 22)

Label Operation

Out(port,label)

In(port,label)

Connection Table

2 31 4

MPLS (Multi-Protocol-Label-Switching):

A label is assigned to each IP packet. Packets are forwarded according the label.

Each router has a connection table mapping input port and label to output port and label.

A Label Switching Path (LSP) can be setup providing fast restoration and quality of service.





#1STM

#2STM

Time Slot

Port 1 Port 2

Port 3 Port 4

NE a

ASON Domain

NE cconnection setup

1 Introduction

1.1 From IP to GMPLS [cont.]

GMPLS (Generalized MPLS):

Swap4, 21, 1

Swap3, 32, 1

Swap3, 21, 3

Swap2, 41, 4

Label Operation

Out(port, TS)

In(port, TS)

Connection Table

NE d

NE b

2 3

1 4

GMPLS (Generalized MPLS):

Extends MPLS to support multiple switching types including SDH / SONET.

ASON: Automatic Switched Optical Network

Main advantages:

Path routing is performed at NE level (not via the Network Management System). This allows very fast connection provisioning and distributed restoration.

It is standardized, this means it can work in a multi-vendor environment.

It is designed to work in a multi-technology environment: IP, ATM, SDH and OTH networks.





1 Introduction

1.2 Plane model

Management Plane

E.g.Q3 or CO

RBA or TL-1

Already widely developedbut we need now to manage the control plane

Transport/Data PlaneE.g. SD

H/SO

NET, O

TH, Ethernet

Control Plane

SignalingPlane

Adapted from IP such

asRSVP-TE

RoutingPlane

Adaptedfrom IP such

asOSPF-TE

GM

PLS

Example:

Broken path:

Alarm in Transport plane.

Routing plane shows a new root.

Signaling plane prepares this route.

New path arrangement in Transport plane.

The GMPLS work per plane:

OSPF-TE: Open Shortest Path First with Traffic Engineering extension for GMPLS (Routing Protocol)

RSVP-TE: Reservation Protocol with Traffic Engineering extension for GMPLS (Signaling Protocol)

A Control Plane shall provide: interworking, auto discovery of resources, resilience against failures.

Current SDH protocols for ring protection (K1/K2) should be considered as Control Plane predecessor.

GMPLS based Control Plane can be considered as protection protocol for meshed networks.

Control Plane is a set of protocols running between Network Elements to provide ION features.

Routing Plane:

Used to find a way through the network.

Routing Protocol:

to collect network topology information (always distributed)

to compute the route across the network (centralized or distributed)

Signaling Plane:

tells the nodes which connections to make (any mix of centralized and distributed).





1 Introduction

1.2 Plane model [cont.]

Policy managementAccountingEnd-to-end path managementAlarm correlation & supervisionPerformance managementVisualization

Real time actions:Recovery (restoration)Multi-vendor path establishmentDiscovery

Traffic engineeringRoute optimizationRestoration preparation

Combined Tasks

NM

S

Cont

rol P

lane

Work split between NMS and Control Plane:

There are tasks which can be realized by Control Plane and/or NMS (Network Management System).

Other tasks are clearly assigned to Control Plane or NMS, respectively.

Therefore, Control Plane and NMS is necessary!





1 Introduction

1.3 GMRE architecture overview

TransportPlane

ControlPlane

ManagementPlane

NE

CLITerminal

NetworkManagementSystem

MIB

nativemanagementinterface to

Q3 MIB of NE

GMRE

CLI: Command Line Interface

GMRE (GMPLS Routing Engine):

software package installed on top of the NE software

supported by Alcatel 1678MCC and Alcatel 1674LG

coordination of the various actions, necessary for providing dynamic path setup and release in a decentralized way

controls the resources (entirely or partially) of the underlying NE

can be managed from a craft terminal or a network management system

controls the underlying NE via the conventional management interface Q3





1 Introduction

1.4 Management of an ASON: Architecture

SDH NE with GMRE

ASON

1354RMASON Manager

SDH NE

SDH Network

MTNM

Q3

MTNM: Multi Technology Network Management based on CORBA





2 ASON Management in RM






2.1 Terminology

ASON

SDH NetworkSDH NE

SDH NE with GMRE

2F MS-SPRing

shared port (drop port)

interworking physical connection

internal physical connectionI-NNI port

I-NNI: Interior Network to Network Interface

The TPs on a shared port can either be:

Completely managed by RM:

Example:The shared port terminates a interworking physical connection, which is part of a 2F MS-SPRing, and as such completely managed by RM.

Managed by both RM and GMRE:

Both managers operate on the TP:

RM will be in charge of all the normal operations on the TP, apart from the set-up of the cross-connections, which are set-up by GMRE and dynamically changed according to GMRE’s restoration strategies.

RM, for maintenance purposes, manages the physical and the Multiplex Section Layers (MSP included).






2.1 Terminology [cont.]

Traffic Engineering Link (TE-Link):It is a bundle of physical connections seen by the GMPLS as equivalent from the routing point of view.

• •

• •

physical connection

physical connection

TE-Link #1

TE-Link #2NE A

STM-1

STM-4

STM-16

STM-64

STM-16

STM-16

NE B

STM-1

STM-4

STM-16

STM-64

STM-16

STM-16






2.2 Steps

To manage an ASON with RM the following actions are necessary in RM:Step 1: network construction

synchronize EML domains containing NEs with GMREcreate nodescreate/upload and implement internal and interworking physical connectionsmodify the allocation cost of the physical connections

Step 2: Shared Risk Groups (SRGs) management create SRGscorrelate physical connections to SRGs

Step 3: ASON NPA managementcreate and implement ASON NPA

Step 4: physical connection managementunlock internal and interworking physical connections

Afterwards HO-trails / Paths crossing the ASON can be created from RM.





3 Shared Risk Group Management






3.1 Introduction

NE2NE1

Fibers

Physical connections

Conduit

Cable

A physical connection is the logical representation of a pair of fibers connecting two SDH ports of two different nodes.

The fibers are part of a fiber cable.

Fiber cables are part of a fiber conduit.

Fiber conduits can cross the same or different Right of Ways (land where the network operator has the right to install conduit or cable).






3.1 Introduction [cont.]

Example for Shared Risk Groups (SRGs):

Cable

Physical Connection

NE 1 NE 2

NE 3

12

3

4

5

6

7

A B

CD E

E7

E6

B + C5

A + B4

A + C3

D2

D1

SRGPhys. Conn.

A SRG is a set of physical connections that share a common risk (common cable, common WDM server layer, etc.) whose failure can cause the failure of all the elements in the group.

A single physical connection may belong to several SRGs in different sections.






3.2 Create SRG

1. From the Domain icon, use the right mouse button menu:

2. Select Create

To remove a SRG, no physical connection must be associated to it.






3.2 Create SRG [cont.]

3. Select the SRG type

4. Only the User Label field is mandatory.

5. Click on 'Finish' to start the action.

SRG type:

physical connection: it can represent a WDM OTS physical connection supporting an SDH one

cable: it is a set of fibers

conduit: it is a set of cables

right of way: it is a land where the network operator has the right to install conduit or cable

The SRG type is not relevant for the further handling of SRGs.

SRG Probability:

Can be seen as comment. It is not relevant for the further handling of SRGs.






3.3 Correlate physical connections to SRGs

Starting from the physical connection: use the right mouse button menu: Shared Risk Group Correlate/Modify

2. Select the SRGs

3. Click on 'Finish' to start the action.

1. Select the operation

The actions shown to correlate a physical connection to a set of SRGs must also be used to modify the correlations:

remove a SRG

remove all SRGs in one shot

add one or more new SRGs

The correlations cannot be modified if the physical connection belongs already to a TE-Link. In this case the TE-Link must be updated.





4 ASON NPA Management






4.1 Bundling rule

With an ASON NPA the related TE-Links are automatically created.A rule must be given to bundle physical connections in TE-Links:

AB

C

D

NE 1 NE 2

phys. conn.

SRG

TE-Link

one-to-one

A B

A B

D

CANE 1 NE 2

with same risks and cost

A B

D

CANE 1 NE 2

When an ASON NPA is built, the related TE-Links are automatically created in RM and in the involvedGMREs.

Bundling rule:

with same risks and cost:

The physical connections having the same type, cost, protection and belonging to the same Shared Risk Groups are grouped in the same TE-Link.

one to one:

For each physical connection a different TE-Link is created.

The user labels of the TE-Links are automatically created by RM and forwarded to the GMREs.






4.2 Create ASON NPA

1. Starting from the network or a subnetwork: use the right mouse button menu: Create NPA

Bundling Rule:• with same risks

and cost• one to one• all together

NPA Type = ASON

Select internal and interworking physical connections

2. Implement the NPA: the communication between RM and GMRE is started and the Control Plane of each NE becomes reachable.

'Bundling Rule' = 'all together' is not supported.

The value of the 'Allocation cost' of the physical connections is used as value for the 'link metric' of the TE-Link.






4.3 Getting relevant information - ASON NPA Highlight

Starting from the ASON NPA the NPA can be highlighted in the map:

interworking physical connections are highlighted in grey

internal physical connections are highlighted in white






4.4 Getting relevant information - ASON NPA view

Starting from the ASON NPA the NPA view can be displayed:

Control planes = GMRE of the NEs

TE-Links

Internal and interworkingphysical connections.

A SNC (Sub-Network Connection) is the part of a path/trail that belongs to the ASON. It is the connection between GMRE head and tail nodes.






4.5 Getting relevant information - internal physical connections

Physical connection structure:

ASON NPA the physical connection belongs to.

TE-Link the physical connection belongs to.






4.6 Getting relevant information - SDH ports

Port inside ASON terminating a internal physical connection.

Shared port terminating a interworking physical connection in ASON.

'Miscellaneous' attributes of a SDH port:

Port outside ASON.






4.7 Getting relevant information - TE-Links

Navigation from TE-Link

to:SNPPlinks (Subnetwork Point Pool Links) = a bundle of ports terminating a TE-Link in one GMRE node.

For a selected SNPPlink the details on GMRE can be displayed using the right mouse button menu

Show Details on GMRE.






4.7 Getting relevant information - TE-Links [cont.]

Navigation from TE-Link

to:SRGs:

physical connections:





5 Physical Connection Management






5.1 Unlock physical connections

New links cannot be used immediately by ASON to carry traffic.Explicit authorization of the operator is requested in order to be able to use a new link.This is done by changing the 'ASON Administrative State' of the internal and interworking physical connections from 'locked' to 'unlocked'.






5.1 Unlock physical connections [cont.]

Starting from the physical connection(s): use the right mouse button menu: Ason Maintenance

1. Select the new ASON Administrative State.

2. Click on 'SET' to start the action.

ASON Administrative State:

locked: no new traffic can be routed over the physical connection. All existing SNCs are deactivated.

unlocked: the traffic can be routed over the physical connection.

ShuttingDown: no new traffic can be routed over the physical connection. All existing SNCs are kept; they can be moved on an alternative route by the GMRE before locking the physical connection.

CHECK: retrieves the physical connection status from GMRE (typically after a ShuttingDown operation).

To de-implement an ASON NPA all internal and interworking physical connections must be in ASON administrative state 'locked'.





6 HO-Trail / Path Management






6.1 Introduction - node roles

headnode

transitnode

tailnode

transitnode

transitnode

connection setup ASON

Head node:responsible for keeping the connection intacthas the full LSP informationmaintains the state of each connectionknows all routes (nominal and backup routes)notifies the NMS about connection (state) changes

Transit and tail nodes:only know the connection-ID and head node

to be used when querying the head node to retrieve the full connection informationreport failures to the head node

head node then triggers restoration actions

An ASON is usually a core network used for the transit of HO-Trails / Paths which are terminated in the SDH access rings.

In this case, the RM provides the information to create the connection between the GMRE head and tail nodes.






6.2 Introduction - SNC

ASON

HO-Trail / Path Subnetwork Connection (SNC)

SDH Network

As a consequence of the connection setup request from RM, the GMRE create a transport entity belonging to the ASON which is called SNC (SubNetwork Connection).





Routes of a Subnetwork Connection:


6.2 Introduction - SNC [cont.]

ASON

Nominal RouteCurrent RouteBackup Route

A SNC has the following routing attributes:

Nominal Route: It is the route allocated by the RM inside the ASON. GMRE will always try to revert to this original route.

Current Route: It is the route set-up and implemented by the GMRE inside the ASON. It is where the traffic is really routed and can be different from the Nominal Route.

Backup Route: If during the trail/path creation a backup route is requested to the ASON, it is the routing of this calculated backup route. Until no failure exists a backup route is inactive. After switching the nominal to the backup route the backup is called active.

When the RM operator sets up a trail/path crossing (or terminating in) the ASON, RM will provide the SNCNominal Route to the GMRE. GMRE will be in charge of the provisioning of the single cross-connections to the NEs.






6.3 Introduction - protection and restoration

Restoration modes:Upon Failure (Source Based Restoration):

The GMRE calculates (and uses) a backup route only in case of failure.Pre-calculated (Guaranteed Restoration):

The GMRE calculates a priori a backup route to be used in case of failure.No Restoration:

No restoration requested for the SNC.

Protection Restoration Combined:SNCP protection + restoration 'Upon Failure'






6.3 Introduction - protection and restoration [cont.]

Upon Failure (Source Based Restoration):Nominal Route

?

Backup Route

ASON

Functionality:

Upon a failure in the network the GMRE head node calculates a new route.

Contention is solved by priority mechanism.

The new route will use old route resources as much as possible.

If other restoration mechanism fails 'upon failure' restoration is applied to save the traffic.







Pre-calculated (Guaranteed Restoration):

Nominal Route

ASON

Backup Route (predefined)

Functionality:

Each working route has a pre-reserved backup route which can be shared with other backups of disjointSNCs.

Restoration mechanism activates the backup route after failure.

The backup route will be restored after failure and provides fully protected status of the restored SNC.

If the backup fails, a minor error will occur.

Benefits

Recovery of backup route using 'upon failure' restoration (fallback).

Multiple failure recovery without manual intervention.







Protection Restoration Combined:Main routeSpare route

?

ASON

Functionality:

Restoration mechanism creates a new SNCP main route after failure recovery, i.e. provides fully protected status of the restored SNC using 'upon failure' restoration.






6.4 Path setup from RM

1. Create the path:Step 1 and Step 2 of the 'Path Creation Wizard' are filled out as usual.In Step 3 the details about the 'CP Restoration' are defined:

Preferred Restoration Mode:

• No Restoration• Upon Failure• Pre-calculated

Default Reversion Mode:• Automatic• Manual

Default Priority:1: highest priority5: lowest priority

Default Priority:

Specifies the priority of the SNC within the ASON.

High priority connections can preempt low priority connections in case no resources are available for restoration.

Default value: 4

Default Reversion Mode:

'Automatic': the reversion of the SNC to the nominal route is done automatically after the route becomes available again.

'Manual': the reversion of the SNC to the nominal route must be started by the operator.

In the 'Trail Creation Wizard' similar possibilities exist to define the CP Restoration attributes for HO-Trails.






6.4 Path setup from RM [cont.]

2. Allocate the path:The routing algorithm of RM chooses to cross the ASON.A SNC is created.






6.4 Path setup from RM [cont.]

3. Implement the path:

ASONSDH Network

1354RM

3. implement SNC (current route and backup route if necessary)

MTNM

2. create SNC (nominal route)

headnode

Path Q3

1. create cross-connection

1. create cross-connections

Implement the path:

RM, via Q3 interface, implements the cross connections belonging only to the non-ASON part of the network.

RM provides to the GMRE head node the command to implement the SNC and the (nominal) routing of the SNC.

Each GMRE takes care to create the cross connection of each managed NE belonging to the SNC routing.

If required, the GMRE head node determines also a backup route. In case of failure the GMRE head node automatically switches the SNC on the backup route taking care of the all operations.





Soft Permanent Connection (SPC):The set-up of the SNC is requested to the GMRE by RM.


6.5 Getting relevant information - ASON NPA view

Paths crossing the ASON.

SNCs in the ASON.






6.6 Getting relevant information - examples

Example 1 - unprotected path, 'restoration mode' = 'Pre-calculated':Highlight path in map:

current route = nominal route

(inactive) backup route

Select the type of route that has to be highlighted (all, current, nominal, backup).

The following colors are used for the highlight:

Each route is shown with the related background color as previously described.In case of resource containing different routes, Current has priority over Nominal, and Nominal over Backup

Spare

Each route is shown with the related background color as previously described.In case of resource containing different routes, Current has priority over Nominal, and Nominal over Backup

MainAll

WhiteBackup (inactive)

Light PinkSpare

Light BlueMainNominal

PinkSpare

BlueMainCurrent

Background colorResource TypeRoute






6.6 Getting relevant information - examples [cont.]

Example 1 cont.: Routing display:

Select the SNC to display the current route and the backup route.

nominal route

current route = nominal route







Example 2 - unprotected path, 'restoration mode' = 'Pre-calculated':A physical connection used by the current route failed.The current route switched to the pre-calculated backup route and a new backup route was calculated.

current route = pre-calculated backup route

nominal route







Example 3 - SNCP protected path (SNCP switches inside ASON), 'restoration mode' = 'Upon Failure':Highlight path in map: current route (main) =

nominal route (main)

current route (spare) = nominal route (spare)







Example 3 cont.: One SNC is created in the ASON. The 'current route' has a main and spare route.






6.7 Getting relevant information - NPA boundary CTPs

PM cannot be started inside ASON, only on NPA boundary CTPs.

Miscellaneous attributes of CTPs:

PM cannot be started inside ASON, only on NPA boundary CTPs.





End of ModuleManagement

4_1_ason_mgt

Documents

rights reserved alcatellucent

rm ason management4

ason npas

ason npa management

relevant information

blank pagethis page

module objectives cont

gmre architecture overview