Sei sulla pagina 1di 973

Operators Handbook

Alcatel 1300NM
Network Management

1354RM Rel.7.2
Regional Network Manager for SDH and Optical Networks

Volume 1/1

3AL 61348 AAAA Ed.01

3AL 61348 AAAA Ed.01

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM REL.7.2 OPERATORS HANDBOOK

TABLE OF CONTENTS
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3
3
3

2 PRODUCT-RELEASE HANDBOOKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Handbooks related to the products software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Handbooks related to the products hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Handbook configuration check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Handbooks related to the products hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5
5
5
7
8

3 1354RM OPERATORS HANDBOOK DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


3.1 Contents of Volume 1/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9
9

4 LIST OF ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


5.1 Products, product-releases, versions and Customer Documentation . . . . . . . . . . . . . .
5.2 Handbook supply to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Aims of standard Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Handbook Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Changes introduced in the same product-release (same handbook P/N) . . . . . . . . . . . .
5.4.2 Changes due to a new product-release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Customer documentation supply on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 Contents, creation and production of a CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.2 Use of the CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.3 CDROM identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.4 CDROM updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15
15
15
15
16
16
16
17
17
18
18
18

01

050207

ED

DATE

CHANGE NOTE

M.RAGNI ITAVE

V.PORRO ITAVE

APPRAISAL AUTHORITY

ORIGINATOR

1354RM REL.7.2
OPERATORS HANDBOOK

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

1 / 18

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.1:HANDBOOK GUIDE

3AL 61348 AA AA

18

2 / 18
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK


1.1 General information
WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims the
implied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liable
for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or special, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied, reproduced or disclosed to a third party without written consent.

1.2 Handbook applicability


This handbook applies to the following product-releases:

1AA 00014 0004 (9007) A4 ALICE 04.10

ANV P/N

1354RM

3AL 61328 ABAA

PRODUCT

RELEASE

VERSION (N.B.)

ANV P/N

1354RM

7.2

3AL 61328 ACAA

KERNEL

For NR7

N.B.

ED

PRODUCT

see NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS in para.5.4.1


on page 16.

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

3 / 18

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.1:HANDBOOK GUIDE

3AL 61348 AA AA

18

4 / 18
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2 PRODUCT-RELEASE HANDBOOKS
The list of handbooks given here below is valid on the issue date of this Handbook and
can be changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available on the issue date of this
Handbook.
The standard Customer Documentation in the English language for the equipment whose product-release-version is stated in para.1.2 on page 3 consists of the following handbooks:

2.1 Handbooks related to the products software


Table 1. Handbooks related to the specific software application

REF

HANDBOOK

ANV Part No.

[1]

1354RM Rel.7.2 Administration Guide

3AL 61348 BAAA

[2]

1354RM Rel.7.2 Operators Handbook

3AL 61348 AAAA

THIS
HANDBOOK

Table 2. NR Related Handbooks

2.2 Handbooks related to the products hardware


Refer to WS supplier handbooks.
In particular refer to such handbooks to obtain the following information (where applicable):

COMPLIANCE WITH EUROPEAN NORMS

SAFETY RULES

General rules
Harmful optical signals
Risk of explosion
Moving mechanical parts
Heatradiating Mechanical Parts

ELECTROMAGNETIC COMPATIBILITY
ELECTROSTATIC DISCHARGERS (ESD)
EQUIPMENT LABELS

1AA 00014 0004 (9007) A4 ALICE 04.10

2.3 History
Ed.01

Creation on January 2005

This handbook applies to Network Release 7.2.

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

5 / 18

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.1:HANDBOOK GUIDE

3AL 61348 AA AA

18

6 / 18
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.4 Handbook configuration check

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This handbook is a collection of documents (each contained in a specific section) that can have
editions different from one another.
The Edition of the whole handbook is that of section 1 (HANDBOOK GUIDE).
The edition of the enclosed documents indicated in the following table is that of the corresponding original internal document.
HANDBOOK EDITION

01

REGISTER AND SECTION TITLE

ED

03

04

05

SECTION EDITION

HANDBOOK GUIDE

01

GETTING STARTED

01

OPERATION

01

MAINTENANCE

01

TECHNICAL ANNEXES

01

WDM NETWORK MANAGEMENT

01

RMNP INTERWORKING

01

RMGMRE INTERWORKING

01

01

02

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

7 / 18

2.5 Handbooks related to the products hardware

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Refer to WS supplier handbooks.

1AA 00014 0004 (9007) A4 ALICE 04.10

In particular refer to such handbooks to obtain the following information (where applicable):

COMPLIANCE WITH EUROPEAN NORMS

SAFETY RULES

General rules

Harmful optical signals

Risk of explosion

Moving mechanical parts

Heatradiating Mechanical Parts

ELECTROMAGNETIC COMPATIBILITY

ELECTROSTATIC DISCHARGERS (ESD)

EQUIPMENT LABELS

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

8 / 18

3 1354RM OPERATORS HANDBOOK DESCRIPTION

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This handbook is composed of the following volumes and sections:

3.1 Contents of Volume 1/1


SECTION 1: HANDBOOK GUIDE (This document)
The Handbook Guide gives general information on the application and use of the Handbook.
SECTION 2. GETTING STARTED
This document aims at introducing the 1354RM working environment, to the users of the system, in
terms of getting access to the system, the environment utilities, the existing 1354RM functionalities
and navigation through the system.
SECTION 3. OPERATION
This document is intended for people who are in charge of the construction of the network.
SECTION 4. MAINTENANCE
The aim of this document is to describe the operations related to the maintenance of the protection
network controlled by the 1354RM.
SECTION 5. TECHNICAL ANNEXES
This section details technical characteristics of the system
SECTION 6. WDM NETWORK MANAGEMENT
The aim of this document is to describe the operations related to the operation and maintenance of
the WDM Network
SECTION 7. RMNP INTERWORKING
The aim of this document is to describe the operations related to the RMNP INTERWORKING
SECTION 8. RMGMRE INTERWORKING

1AA 00014 0004 (9007) A4 ALICE 04.10

The aim of this document is to describe the operations related to the RMGMRE INTERWORKING

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

9 / 18

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.1:HANDBOOK GUIDE

3AL 61348 AA AA

18

10 / 18
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4 LIST OF ABBREVIATIONS
ADM

Add Drop Multiplexer

AIS

Alarm Indication Signal

ALMIM

Generic Alarm Info Model

ALMAP

Alcatel Common Platform

AP

Access Point

APS

Automatic Protection Switching

AS

Alarm Surveillance

AU

Administrative Unit

BN

Backbone Network

BR & SW

Bridge & Switch

Browser

Application which allows to browse all RM-MIB objects

CAP

Client Access Point. It represents a point where a client layer can access a server layer
( i.e. a VC4 that is configured to carry lower order signals is a HOCAP)

CI

Communication Infrastructure

CMISE

Common Management Information Service ( ISO/OSI protocol )

CMOT

Common Management Info Protocol on TCP/IP

CTP

Connection Termination Point

DB

Data Base

DBMS

Data Base Management System

DCI

Drop & Continue Interconnection

DCN

Data Communication Network

D&C

Drop & Continue

DWDM

Dense Wavelenght Division Multiplexing

ECC

Embedded Communication Channel

EM

Element Manager

EML

Element Manager Layer

EML domain

A set of NEs that are maintained by the same EMLOS.

EMOS

Element ManagerOperation System

EMS

Event Management Services

EPS

Equipment Protection System

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

11 / 18

Elementary Subnetwork

ET

Elementary Topology. It is a grouping of some nodes connected according to specific


rules.
A typical ET is a ring.

FAD

Functional Access Domain

FM

Fault Management

FOX

Fiber Optic Extender

HOAP

High Order Access Points

HOPLN

High Order Path Layer Network

HOPL

Higher Order Path Layer

HP

Higher Path Traffic

HPOV

Hewlett Packard Open View

HP-OVw

Hewlett Packard Open View Windows

IAP

Inventory Application

ISA

Integrated SDH ATM

Isn

Interface between NML and SML

Link
Connection
(lc )

A transport entity provided by the client/server association.It is formed by a nearend


adaptation function,a server trail and a farend adaptation function between connection
points. It can be configured as part of the trail management process in the associated
server layer.

LOAP

Low Order Access Point

LOF

Loss of Frame alignment

LOP

Loss of Pointer

LP

Lower Path traffic

LSP

Link single fault protection index (LSP). The LSP index is determined (in a way similar
to NSP for nodes) taking into account of both the number (C) of archs belonging to the
main route and the number (D) of archs belonging to the main and spare routes.

Map

Set of related objects , backgrounds,symbols and submaps that provides a graphical


and hierarchical representation of the network.

MIB

Management Information Base

MSAP

Multiplex Section Access Point

1AA 00014 0004 (9007) A4 ALICE 04.10

MSCTPCAP Multiplex Section Termination Point


MSEXBER

Multiplex Section Excessive BER

MSRDI

Multiplex Section Remote Defect Indication

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

12 / 18

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ESN

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

MSL

Multiplex Section Layer

MS Spring

Multiplex Section Shared Protection Ring

MS SIGDEG

Multiplex Section Signal Degrade

MSLN

Multiplex Section Layer Network

NAP

Network Access Point (it is a HO/LO-TTP related to a PDH port)

NE

Network Element . It is a telecommunication equipment.

NetView

Application based on OVW, used to display, create, keep updated view of the SDH
Network Through maps.

NM

Network Manager

NML

Network Manager Layer

Node

It is the view of the NE at NML level

NSP

Node single fault protection index (NSP). The NSP index is determined taking into
account of both the number (A) of Nodes belonging to the main route and the number
(B) of Nodes belonging to the main and spare routes, except the end nodes.

OS

Operations System

PCMAP

Payload Configuration Management Application

PDH

Plesiochronous Digital Hierarchy

Physical
Connection

A Physical Connection connects two SDH ports in the network. These two ports belong
to different NEs and must have the same transmission rate.

PM

Performance Monitoring

POH

Path Overhead

Port

Physical Interface of a Node. A port can be SDH or PDH.

PRC

Protection and restoration combined

Q3

OSI Interface based on CMISE

Qnn

Q3 Interface between 1354RM and 1354NN

sbn

Subnetwork. It is a grouping of nodes and ETs.

SDH

Synchronous Digital Hierarchy

SENIM

Simple Element Network Information Model

SD

Signal Degrade

SF

Signal Failure

SMF

System Management Features

SNML

Subnetwork Management Layer

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

13 / 18

1AA 00014 0004 (9007) A4 ALICE 04.10

Subnetwork Connection Protection

SONET

Synchronous Optical Network

STM

Synchronous Transport Module

TCA

Threshold Crossing Alarm

TM

Terminal Mode

TN

Transport Network

TP

Termination Point

Trail

A transport entity in a server layer responsible for the integrity of transfer of


characteristic information from one or more client network layers between server layer
access points.It defines the association between access points in the same transport
network layer. It is formed by combining a nearend trail termination function, a
netwrwork connection and a farend trailtermination function.

Trail
termination

A transport processing function which generates the characteristic information of a layer


network and ensures integrity of that characteristic information. The trail termination
defines the association between the access point and termination connection point and
these points thereofore delimit the trail termination.

TSDIM

Same as QB3 protocol. Information Model for interworking between Network Managers
and Network Elements.

TTP

Trail Termination Point

TU

Transport Unit

UPA

Unavailable path alarm

URU

Underlying Resource Unavailable

VC

Virtual Container

WTR

Wait Time to Restore

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

14 / 18

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SNCP

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION


5.1 Products, product-releases, versions and Customer Documentation
A product is defined by the network hierarchical level where it can be inserted and by the whole of performance and services for which it is meant.
A product evolves through successive product-releases which are the real products marketed for
their delivery at a certain product-release availability date.
So, a productrelease defines a set of hardware components and a software package which, as a whole,
identify the possible network applications and the equipment performance which the specific product-release has been designed, engineered and marketed for.
In some cases a product-release has further development steps, named versions, that are born to
improve or add some performance (mainly software) with respect to the previous version, or for bug fixing
purposes.
A product-release has its own standard Customer Documentation, composed by one or more handbooks.
A new version of a product-release may or may not produce a change in the status of the Customer
Documentation set, as described in para.5.4 on page 16.

5.2 Handbook supply to Customers


Handbooks are not automatically delivered together with the equipment they refer to.
The number of handbooks per type to be supplied must be decided at contract level.

5.3 Aims of standard Customer Documentation


Standard Customer Documentation, referred to hereafter, must be always meant as plant-independent.
Plant-dependent documentation, if envisaged by the contract, is subjected to commercial criteria as far
as contents, formats and supply conditions are concerned (plant-dependent documentation is not
described here).
Standard hardware and software documentation is meant to give the Customer personnel the possibility
and the information necessary for installing, commissioning, operating and maintaining the equipment according to AlcatelTelecom Laboratory design choices.
In particular the contents of the handbooks associated to the software applications focus on the
explanation of the man-machine interface and of the operating procedures allowed by it.

1AA 00014 0004 (9007) A4 ALICE 04.10

Consequently, no supply to the Customers of design documentation (like software source programs, programming tools, etc.) is envisaged.

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

15 / 18

5.4 Handbook Updating

Each handbook is identified by:

the name of the product-release (and version when the handbook is applicable to the versions
starting from it, but not to the previous ones),

the handbook name,

the handbook P/N,

the handbook edition (usually first edition=01),

the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
5.4.1 Changes introduced in the same product-release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:

only the date changes (pointed out in the Table of Contents) when modifications are made to the editorial system not changing the technical contents of the handbook.

the edition, hence the date, is changed because modifications made concern technical contents. In
this case:

the table in para. 1.2 on page 3 indicates the section(s) edition change;
in each section, the main changes with respect to the previous edition are listed;
in affected chapters of each section, revision bars on the left of the page indicate modifications
in text and drawings (this is done after the first officially released and validated version).

Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of
a version character (e.g. from Ed.02 to Ed.02A).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications (typically the Operators Handbooks) are not modified unless the new software version distributed to Customers implies manmachine interface
changes or in case of slight modifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product-releases version marking, they are not replaced in the handbooks related to a subsequent version, if the
screen contents are unchanged.
5.4.1.1 Supplying updated handbooks to Customers

1AA 00014 0004 (9007) A4 ALICE 04.10

Supplying updated handbooks to Customers who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue
(supplying erratacorrige sheets is not envisaged).
5.4.2 Changes due to a new product-release
A new product-release changes the handbook P/N and the edition starts from 01.
In this case the modified parts of the handbook are not listed.

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

16 / 18

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The handbooks associated to the productrelease are listed in para.1.2 on page 3

5.5 Customer documentation supply on CDROM

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In the following CDROM means Customer Documentation on CDROM


5.5.1 Contents, creation and production of a CDROM
In most cases, a CDROM contains the documentation of one productrelease(version) and for a certain
language.
In some other cases, the same CDROM can contain the documentation of different
productrelease(version)s for a certain language.
As a general rule:

CDROMs for Network Management products do not contain:

the Installation Guides

the documentation of system optional features that Customers could not buy from Alcatel together with the main applicative SW.

CDROMs for Network Elements products do not contain:

the documentation of system optional features (e.g. System Installation Handbooks related to
racks that Customers could not buy from Alcatel together with the main equipment).

the Installation and Turnup & Commissioning handbooks

A CDROM is obtained collecting various handbooks and processing them by InterleafWorldView


Press after the manual addition of some hyperlinks which make the navigation through the various handbooks easier. No additional information is added to each handbook, so that the documentation present
in the CDROMs is exactly the same the Customer would receive on paper.
The files processed in this way are then transferred on a PC where the viewer (InterleafWorldView) is
added and a master CDROM is recorded.
Suitable checks are made in order to have a virusfree product.

1AA 00014 0004 (9007) A4 ALICE 04.10

After a complete functional check, the CDROM image is electronically transferred to the archive of the
Production Department, so that the CDROM can be produced and delivered to Customers.

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

17 / 18

5.5.2 Use of the CDROM

The minimum configuration and the setup procedure are present in the README.TXT file included in
the CDROM.
After the setup procedure, which installs the viewer in the PC or Unix WS environment, the Customer
is allowed to read the handbooks on the PC/WS screen, using the navigation and zooming tools included
in the viewer, and to print selected parts of the documentation through a local printer.
N.B.

Copyright notification

WorldView:

Copyright 19811996
INTERLEAF Inc.
All rights reserved.
The use of WorldView is permitted only in association with the files contained
in the CDROMs officially supplied by Alcatel.

Alcatel documents:

All rights reserved.


Passing and copying of documents and files contained in the CDROMs
officially supplied by Alcatel, use and communication of its contents are not
permitted without written authorization from Alcatel.

5.5.3 CDROM identification


Each CDROM is identified:
1)

by the following external identifiers, that are printed both on the booklet and the CDROM upper
surface:

the name of the productrelease(s) (and version when the CDROM is applicable to
the versions starting from it, but not to the previous ones),

a writing indicating the language(s),

the CDROM P/N (Factory P/N 417.xxx.xxx x and ANV P/N),

the CDROM edition (usually first edition=01)

2)

and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose
collection and processing the CDROM itself has been created.

5.5.4 CDROM updating


The list of source handbook/document P/Nseditions indicated in previous para.5.5.3 point 2 ) , in
association with the CDROMs own P/Nedition, is also loaded in the AlcatelInformationSystem as a
structured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system,
a check in the AlcatelInformationSystem is made to identify the list of CDROMs that must be updated
to include the new editions of these handbooks/documents.
This causes the planning and creation of a new edition of the CDROM.

1AA 00014 0004 (9007) A4 ALICE 04.10

Updating of CDROMs always follows, with a certain delay, the updating of the single handbooks
composing the collection.

END OF DOCUMENT

ED

01

SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18

18 / 18

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The CDROM can be used both in PC and Unix WS environments.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM REL.7.2 OPERATORS HANDBOOK

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7
7
7
7

2 1354RM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 The Regional Manager in the controlled network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Topological Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Transport Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 1330AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4 System Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.6 Performance Monitoring Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9
9
9
10
12
12
12
15

3 REGIONAL MANAGER GRAPHICAL USER INTERFACE PRINCIPLES . . . . . . . . . . . . . . . . . .


3.1 Generalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 Location and insertion cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Dimensions and layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 Client area and Window titles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 Window menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 Scroll bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.5 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.6 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.7 Entry boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.8 Dialogue boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17
17
17
17
18
20
20
20
21
21
22
25
29
32

4 GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

37

5 PRELIMINARY OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Logging in to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Workspace description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

45
45
46

01

050207

ED

DATE

CHANGE NOTE

M.RAGNI ITAVE

V.PORRO ITAVE

APPRAISAL AUTHORITY

ORIGINATOR

1354RM REL.7.2
OPERATORS HANDBOOK

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

1 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

47
48

6 ACCESS TO THE MAIN FUNCTIONALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 The TMNOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Task Subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Active task subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.1 System Menus started from the logo icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.2 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.3 Create new panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.4 Task bar popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.5 This Panel Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.6 Global Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.7 Utility popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.8 Customize panel procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.9 Add this menu as drawer to panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

49
49
50
52
54
55
56
56
60
61
62
63
66
67
69

7 VIEWS DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Management Tools windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

71
71
72
72

8 SDH NETVIEW : MAP NAVIGATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1 Usage of zoom tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.2 EXAMPLE of SDH submap navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

73
73
74
76

9 BROWSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Browser main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 Counters area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5 Object filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.6 DEFINE QUERY FOR (the selection/filter window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.7 Show/Set Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.8 Items selection in the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.9 Generic Browser pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.10 Actions: Search: Main Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.11 Actions: Search: All Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.12 Actions: Search: Parent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.13 Actions: Select: Related Items.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.14 Actions: Select: All related Items.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.15 Actions: Select: Unselect All.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.16 Actions: Close: Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.17 Actions: Close: Item by Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.18 Actions: Close: All related items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.19 Actions: Align item(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.20 Actions: Details: Show/set attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.21 Actions: Details: Displayed info... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.22 View:Displayed info.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.23 View:Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.24 Options: Filtered presentation / Not filtered presentation . . . . . . . . . . . . . . . . . . . . . . . . .

85
85
87
88
89
90
90
92
93
94
95
95
96
96
96
96
97
97
97
97
97
98
98
99
99
101

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

2 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.3 Locking the screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


5.4 Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

102
102
102
102
102
103
103
104
104
105
106
106
107
108
109
113
119
120
121

10 BROWSER: DRAWING WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.1 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.2 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

123
123
124
124

11 BROWSER MULTICOLUMN WINDOWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1 Pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.2 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.3 Title area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.4 Counters area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.5 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.6 Counters and graphs on Browser MultiColumn Lists . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.7 Multicolumn list window configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Available Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

125
125
126
127
128
128
128
129
129
131

12 BROWSER: LOCATE ITEMS IN NETVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


12.1 Locate topological objects on Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

135
135

13 ZERO INSTALLATION READ ONLY BROWSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


13.1 Application Requirements & Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 RM MIB Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3 Print and Export table view data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

137
137
140
140
140

14 ONLINE DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

141
141

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

142

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.1.25 Options: Overlay windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


9.1.26 Options: Enable AS link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.27 Options: Task bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.28 Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.29 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.30 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.31 Navigations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Active Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.2 Metaclasses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.3 How it works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.2 NAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.3 FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5 Definition and Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.1 Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.2 Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.3 List visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

3 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

FIGURES
Figure 1. Path configuration status states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Alarm navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Mouse pointer representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Example of a window layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Window menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Scroll bar components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Examples of push buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Examples of radio buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Window view showing the menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Window view with Pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Window view with Cascading menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Unselectable menu items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Highlighted menu item indicating selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Example of a dialogue box having Entry Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Multiple List box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Error dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Question dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Information dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Confirmation Dialogue Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Login panel view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. The SDH Manager workspace Front Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Locking the screen using a manual lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Screen lock Password: entry box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Logging out using the front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. HPCDE Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. TMNOS manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. Selfhiding vertical palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Active task subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. System Menus started from the logo icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Panel Close confirmation window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. System menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. System Menus: Path Provisioning menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. System Menus: Network Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. System Menus: Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. System Menus: OS Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Create New Panel submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Create: New Corner Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Create: New Edge Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Task bar popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Panel Properties: Edge Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Panel Properties: Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Global Panel Configuration: Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Global Panel Configuration: Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Utility popup menu on each system menu item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Utility buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Utility button: Add this as menu to panel for a group of commands . . . . . . . . . . . . . . . . .
Figure 48. Customized user menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. System menus: Path Provisioning: Path Creation Wizard: Add this to launcher panel .
Figure 50. Window icon popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

11
14
19
20
21
22
23
24
25
26
27
28
29
30
33
34
34
35
35
45
46
47
47
48
49
50
54
55
56
57
57
58
58
59
59
60
60
61
61
61
62
63
64
65
67
68
68
69
70
70

SC.2:GETTING STARTED
3AL 61348 AA AA
142

4 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LIST OF FIGURES AND TABLES

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 51. Map window: Pulldown menu and tool buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 52. Zoom tool interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 53. Area to magnificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. Zoomed area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. RM domain map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. Available Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. Domain submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. Objects belonging to a subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. Objects belonging to a 2nd level Subnetw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. Physical Connection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. Physical Connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. Popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. Browser main window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. Browser work area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. Object filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. Define query window for Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. Show/Set Attributes dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. Actions: Details: Displayed Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. View:Report full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. View:Report short . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. Options:Deferred Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. Active Counters tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 73. Browser: Tools: Active Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 74. Status window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 75. Status window menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 76. Active Counter Creation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 77. Entering data in Active Counter Creation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 78. Monitored Class selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 79. Condition Modification dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 80. Condition Modification: Attribute selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 81. Condition Modification: attribute (enumerated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 82. Condition Modification: attribute modification (label) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 83. Split button enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 84. Counter: Modify popup menu item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 85. Active Counter: Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 86. Condition Visualization ( Show) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 88. Example of Multicolumn window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 89. Ordering items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 90. Sorting items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 91. Node list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 92. Highlighted node in Netview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 93. Application warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 94. Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

73
74
75
76
77
78
79
80
81
81
82
83
87
90
91
92
94
99
100
101
102
103
109
110
111
113
114
115
116
116
117
117
118
119
120
121
128
129
130
135
136
138
139

TABLES
Table 1. Items selection in the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

95

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

5 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

6 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1 INTRODUCTION
1.1 Introduction
This document aims at introducing the 1354RM working environment, to the users of the system, in terms
of getting access to the system, the environment utilities, the existing 1354RM functionalities and
navigation through the system.

1.2 Target audience


The Introduction Manual is intended for all 1354RM users.

1.3 Document structure


This section covers the following topics:

ED

1354RM Overview

User Interface Principles

Windows

Glossary

Logging Operation

Workspace description

Locking the screen

Logout

Access to the Main Functionalities

View Description/Wizards

Map Navigation

Browser Main Window

Drawing Introduction

Browser List

Locate

Help System

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

7 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

8 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2 1354RM OVERVIEW
2.1 The Regional Manager in the controlled network
Main Product are: (please refer to the relevant documentation for further info).
1353NM is the Common Element Management Layer OS which can manage more than 100 NE versions
and types.
1354BM is the NML application for managing ATM services available in OMSNs.
1354SN is the NML application for managing Submarine Line Systems.
1354NP is the Fast Restoration NML application for controlling DXC meshed backbone networks.
1355VPN permits to manage Optical Virtual Private Networks at the end Customer premises.
1355ONE (Optical Network Engineering) is a network analyser.
1354RM provides the management of SDH/SONET and DWDM subnetworks. Via the 1353NM 1354RM
controls the Network Elements.

1AA 00014 0004 (9007) A4 ALICE 04.10

2.1.1 Topological Components

Network:
A path that crosses two Networks cannot be managed by 1354RM as a single transport entity (i.e.
it will be represented with two paths)

Subnetwork:
A Network can be composed by more than one subnetworks)

2nd level Subnetwork:


It represents a partitioning of a subnetwork.

Node:
It represents the image of a Network Element.

Physical Connection:
It is the logical representation of fibers and coaxial cables, between network ports

EML Domain:
It represents one EMLIM component of 1353NM.

NE:
It represents a physical NE.

Network port:
It represents the physical port where e.g. the fiber is connected.
Example:
A STM16 port of a SDH NE.
An OTS port of a DWDM NE.

Access port:
It represents the physical port where the client signal is added/dropped.
Example:
a PDH port of a SDH NE.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

9 / 142

Section:
It is a trail at Multiplex Section Layer.
Example:
MSTrail between two STMn ports of two adjacent SDH NEs.
OMSTrail between two OTS ports of two adjacent DWDM NEs.

HO (Higher Order) Trail:


An HO Trail is a HO route (e.g. infrastructure pipe) between two (either adjacent or not) SDH NEs.
It is delimited by two CAPs (Client Access Points) and it can be configured to carry LO traffic.

Path:
A path (can be at either HO or LO path layer) is a route established in the SDH/SONET network. It
is delimited by NAPs (Network Access Points).
Example:
A VC12 path delimited by two VC12 NAPs

Link Connection:
It is an arc delimited by the two CTPs with the same timeslot and it is supported by the same server
Trail
Example:
An Au4 Link Connection is delimited by two corresponding AU4 CTPs and it supported by a MS
Trail.

2.1.2.1 Network Construction


The operator can:

Define the submaps according to the preferred network partitioning

Define the physical connections

Define the Network Protection Architectures one per each 2nd level subnetwork
To each access port the related Network Access Point is available.
Moreover the following feature is available:

Add/Remove Network Element in Subnetwork and in Elementary Topology including Join/Split


Physical Link Connection management.

The map provides a network view partitioned in subnetworks, which can be partitioned in 2nd
level subnetworks, and nodes (submaps may have a geographical background). This map
representation is created during the network construction process.

The different views are organized in hierarchical trees. Zooming operations allow the user to navigate
through a tree of hierarchical views.
2.1.2.2 Path Management

1AA 00014 0004 (9007) A4 ALICE 04.10

1354RM can manage the following path categories:

ED

Terminated, non terminated


Unidirectional, bidirectional
Pointtopoint, pointtomultipoint
Unprotected, endtoend protected, enhanced protected by means of drop and continue facilities,

With automatic/semiautomatic protected or not protected route selection.

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

10 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.1.2 Transport Entities

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

A path can be in the defined, allocated, implemented, and commissioned state. The picture describes the
admitted state transitions.
Create

Allocate

Defined

Delete

Implement

Allocated

DeAllocate

Commission

Implemented

DeImplement

Commissioned

DeCommission

Figure 1. Path configuration status states


In the next paragraphs the description of management of these phases is provided.
2.1.2.3 Path Definition
During this phase the path description is stored in the data base; in the following the main information are
listed:

Path name
Path type (i.e. unidirectional, bidirectional or point to multipoint)
Protection type
Rate
AEnd and ZEnd points
Allocation/implementation rules
Alarm enable/disable for the involved path up to the commissioning state.

2.1.2.4 Path Allocation


The path allocation can be performed either automatically (i.e. immediately after the creation) or manually
on user request.
During this phase the idle resources (link connections, crossconnections) are selected in order to assign
them to the path.
The routing search is performed on a lower cost basis applying the Dijkstra cost model, which assigns a
cost value to all relevant resources. The cost model is dynamic and it is influenced by the presence of
protections.
Upon operator request the cost values can be:

modified by the operator himself or


automatically modified, in order to provide a balanced load of the network when resources become
scarcer.

When this activity is successfully terminated, the selected resources are locked; please notice that at the
end of this phase the path does not yet exist in the network.

1AA 00014 0004 (9007) A4 ALICE 04.10

2.1.2.5 Path Implementation


The path implementation can be performed either automatically after allocation or later, on user request.
During this phase, 1354RM sends the proper crossconnection (identified at allocation time) messages
to the relevant NEs via 1353SH/GEM.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

11 / 142

2.1.2.6 Path Commissioning


When test activities are terminated, the path is ready for service and the operator can declare it commissioned. The alarm reporting related to the path is enabled, just in case it was inhibited before.
2.1.3 1330AS
1330AS is an ALMAP Generic Component, which is in charge to manage the network alarms generated
by 1354RM as soon as an elementary alarm affects a network resource (e.g. path, trail).
1330AS is the entry point for the operator to perform fault management and fault localization and it provide
capabilities for define alarm synthesis, alarm acknowledge, alarm archiving etc.
2.1.4 System Management Features
Main system utilities are:

Operator Administration functions: Add Operator, Remove Operator, List Operators, Change
Password, List Current Login, List Successful Login and List Unsuccessful Login.

Console Administration functions: Add Operator Console, Remove Operator Console, List Operator Consoles, Lock Operator Console and Unlock Operator Console.

System Log functions: List System Messages, List Archived Messages and List restored Messages.

Periodic Actions functions: Show Scheduling Time, Set Scheduling Time and Cancel Scheduling
Time, bearing in mind that the term periodic actions here refers to System Management Functions.
Also, the communication between the 1354RM and the registered Element Managers is tested periodically, being an alarm generated when a communication test fails.

Backup & Restore functions: It is possible to automatically backup data periodically, since online
full backup is supported. It is possible to do a complete full backup on Operator request and to get
information on planned actions. It is possible to disable automatic operation and restore a full or an
incremental backup. Restore is offline and 1354RM shall be previously shutdown.

System Start/Stop functions: Start System, Stop System, Show System State, Autostart Enable/
Disable and Show Autostart State.

1AA 00014 0004 (9007) A4 ALICE 04.10

2.1.5 Fault Management


Incoming NE elementary alarms are managed by 1354RM in order to detect which network entities (e.g.
paths, trails) are impacted and to notify, if any, to the operator the resulting network alarm(s).
The elementary alarms are processed prioritizing, root problems against the effects. In case of alarm flooding, 1354RM continues to process the primary alarms, discarding, if necessary, the secondary ones. When
this abnormal condition is finished, 1354RM can execute the alarm resynchronization.
The network alarms are generated by the system for physical connections, trails, and paths.
The severity of this type of alarms can be modified relying on the alarm severity assignment profile management available in 1354RM.
For the path and HOtrail alarms, the alarm is generated when the traffic is affected.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

12 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Only if this scenario is successfully completed, the path becomes implemented, i.e. a real connection between the selected endpoints exists in the network.
In this state it is possible to activate loopbacks on ports, in order to validate the path itself.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Each network alarm (X.733 compliant) provides information about the affected resource, alarm type, probable cause, severity, timestamp and so on.
All the current network alarm information is shown to the operator in the current alarms list. The alarm fields
are customizable by the user. After the operator acknowledgement and alarm clearing the network alarm
is moved into the historical alarm log. As default, the system provides alarms counters related the total
alarms in the domain and to each managed alarm severity (critical, major, minor, warning, indeterminate),
and cleared alarms. The user can define other type counters according his needs.
Starting from the alarm list it is possible for a specific network alarm to retrieve information about the elementary alarms correlated to it.
Network management topological objects (NE, ring, subnetwork,...) containing the alarmed object (TP,
port, ...) are graphically displayed according the color of the highest alarm severity.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

13 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 2. Alarm navigation


Log consultation and report generation are allowed by the system.
The alarm information can be made available to external system (via Ioo).

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

14 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.1.6 Performance Monitoring Management


In order to manage PM Data for Quality Of Service (QoS) and maintenance correlated to services (e.g.
paths), 1354RM provides a dedicated application.
By means of it the operator can manage PM measures, which can group together a set of transport entities
(paths or trails) having a common performance goal.
A measure (with 15 minutes and/or 24 hours periodicity) allows to collect the PM counters belonging to
specific Termination Point (TP) in order to control the performance of the related transport entities.
After the selection of a transport entity, 1354RM selects, as monitored points, the termination points of the
transport entity, e.g. for a path will select NAPs or border CTPs depending it is terminated or not.
Intermediate CTPs of a transport entity can be monitored as well.
Depending on the capability offered by the NEs, the operator can define and activate the Threshold Crossing Alarm profiles for NAPs and CTPs.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

15 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

16 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3 REGIONAL MANAGER GRAPHICAL USER INTERFACE PRINCIPLES


3.1 Generalities
The Regional Manager user interface is based on the Hewlett Packard Open View Windows (HPOVW)
standard customized by Alcatel and on normal X windows. This section will describe the different elements
composing the interface as well as the users general environment.
The users work environment can be partitioned into the following utilities:

Keyboards: the different keys and the actions they induce will be defined.
Mouse: the operation of the different buttons will be explained.
Workspace: A workspace is the screen area where you bring the applications needed for your work,
arrange them to suit your preferences, and put them away after finishing your job. Each workspace
occupies the entire display, and you switch from one workspace to another using a control.
Icon: A small, graphic representation of an object on the workspace. Objects can be iconified
(turned into icons) to clear a cluttered workspace and normalized (returned to their original
appearance) as needed. Processes executing in an object continue to execute when the object is
iconified.
Windows: the windows general layout, menu and configuration (size) will be described.
Dialogue Boxes: the different types of boxes and their aspect is defined so that the user will be
familiar with them.

The above utilities are detailed in the following paragraphs.


3.1.1 Keyboard
A workstation keyboard has the following types of keys:

Alphabetic Keys:
They represent the letters of the alphabet, the punctuation marks and textformatting functions such
as Tab, Return and the Space bar.
Numeric Keys:
They represent the numbers from 0 to 9. They are located near the top of the keyboard and in a
numeric keypad on the right side of the keyboard.
Modifier Keys:
Used in conjunction with other keys to modify the meaning of these keys. They are Ctrl, Shift or Alt keys.
In particular the Control button, used in conjunction with the Selection button ( left mouse button )
is used to extend the object selection.
Function Keys:
They provide extra or general functions. They are labelled F1, F2, F3..etc... and are located across
the top of the keyboard. They can be used as accelerator keys, giving the possibility to select menu
options rapidly using the keyboard. For example, under certain conditions, the F1 key generates a
HELP dialogue box.

1AA 00014 0004 (9007) A4 ALICE 04.10

3.1.2 Location and insertion cursor


This cursor takes the form of an Ibeam pointer (see Figure 3. ). It indicates where the text is going to be
entered. This cursor is frequently met when using Entry boxes (see chapter 3.2.7). The cursor can be
moved horizontally and vertically using the Navigation keys.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

17 / 142

The mouse is associated with a mouse pointer. This pointer represents the current position of the mouse
on the screen. Any movement of the mouse, on the mouse pad, moves the pointer on the screen in an
identical way. The mouse can be moved anywhere on the workspace.
3.1.3.1 Mouse buttons
There are 3 Mouse buttons. The actions that are undertaken using the different mouse buttons depends
on their configuration.

Select button: enables you to select objects (mouse button 1).


Drag button: enables you to drag objects (mouse button 2).
Custom button: enables you to generate popup menus (mouse button 3).

With a left handed mouse configuration, button 3 becomes the select button.
3.1.3.2 Select/Deselect/DragandDrop functionalities

Selecting an object: first move the mouse pointer to the object. Then select the object by clicking
on it with the Select mouse button. The object appearance changes indicating that it has been
selected.
Draganddrop mouse functionality: used for displacing objects or icons on the workspace. To
use it, first move the mouse pointer to the object you wish to move. Then press, and hold down, the
Drag mouse button and drag the object to the chosen area using the mouse. When the object has
reached the chosen area, release the mouse button.

3.1.3.3 Mouse pointer signification

1AA 00014 0004 (9007) A4 ALICE 04.10

The shape of the mouse pointer gives an indication of what actions can be undertaken in that particular
mouse position. The user will soon understand the different functionalities related to the mouse pointer
form. To help him, a list of the mouse pointer forms is given in the figure below.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

18 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.1.3 Mouse

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This arrow pointer indicates that in the actual mouse position an action can
be undertaken. For example, open a menu, resize or move a window...

This arrow pointer is usually associated with menus. It indicates that a menu
is open and that a menu item can now be selected by clicking.
This Ibeam pointer is usually associated with windows and entry boxes.
They indicate that a written entry can be performed here.
The X pointer shape indicates that the mouse is outside an application area
(for example a window).
The work in progress pointer symbol indicates that some action is in progress.
The cross pointer is used to select a window to be printed as part of a screen
hardcopy process.
The 4directional arrow pointer indicates a move operation or a resizing operation can be undertaken on a window.
The hand sign means that the pointer is over the object ( browser context)
The Caution sign indicates that the graphical object under the mouse is not
selectable. For example, during a logout process, this pointer appears when
the mouse pointer is outside the confirmation dialogue box.

Figure 3. Mouse pointer representations


3.1.3.4 Double clicking

1AA 00014 0004 (9007) A4 ALICE 04.10

Numerous actions can be undertaken by double clicking using the mouse. For example, opening windows
related to objects (this is of importance during the construction of the Network Topology as shall be seen
in the Operation Manual) and opening iconified windows.
a)

To open an object (file, directory..).

Place the mouse pointer over the object you wish to open.
Click twice, rapidly, using the Select mouse button on the object.
The mouse pointer will take the work in progress representation until the object should open.

b)

To open a symbol submap or the object view (this refers to the Operation Construction manual).

Place the mouse pointer over the symbol whose submap you wish to open.
Click twice, rapidly, using the Select mouse button on the object.
The mouse pointer will take the work in progress representation until the symbols submap should open.

c)

To select from a list of selectable feature or function and confirm by pressing OK ( SMF context )

d)

To get the selectable list of the object related items (browser context)

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

19 / 142

3.2 Windows

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This section defines the attributes of windows and describes their general aspects.
3.2.1 Dimensions and layout
The figure below indicates the standard window layout.
Window menu button

Window title

Maximize
button

Menu Bar

Client area
Resize borders

Figure 4. Example of a window layout

3.2.2 Client area and Window titles

1AA 00014 0004 (9007) A4 ALICE 04.10

The Client area is the area in which you work. You can write text, insert or construct images or display
Network views. The window title gives the name of the window.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

20 / 142

3.2.3 Window menu

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Enables operations to be undertaken on the window.


To open the window menu, click on the window menu button using the Select mouse button. You can
then select an item from the pull down menu that appears. The window menu options are shown in the
figure below.
Window menu button

Figure 5. Window menu options

Restore: restores the window from the iconified state to its normal size (in this case the window is
already opened so this menu option is greyed. Greyed menu options are explained in chapter
3.2.6.5).
Move: displaces the window around the workspace,
Size: changes the size of the window,
Minimize: iconifies the window,
Maximize: gives the window the full screen size,
Lower: places the window at the back of the workspace (this is helpful if many windows are opened
and overlap on the workspace),
Occupy Workspace...: gives you the possibility of selecting the workspace on which the window is
shown,
Occupy All Workspaces: places the window on all the workspaces,
Unoccupy Workspace: removes the window from the workspace from which this option is selected,

3.2.4 Scroll bars


If the window size does not enable all the information contained in the client area to be visible, scroll bars
enable you to move up, down, right or left in the client area.

1AA 00014 0004 (9007) A4 ALICE 04.10

There are vertical and horizontal scroll bars as shown in the figure below.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

21 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Slider

Stepper
arrows

Scroll Region
Figure 6. Scroll bar components
There are three ways to use scroll bars:

Using the stepper arrows.


Place the mouse pointer on the stepper arrow and click on it using the Select mouse button. The
contents in the client area are displaced only one unit in the direction indicated by the stepper arrow.

Using the scroll regions.


Place the mouse pointer in the scroll region outside the sliders. Click, using the Select mouse button. The contents in the client area are displaced one window length.

Using the sliders.


Place the mouse pointer on the slider. Drag, using the Select mouse button, the slider in the direction desired. The contents in the client area are displaced as long as the slider moves.

3.2.5 Buttons

1AA 00014 0004 (9007) A4 ALICE 04.10

In any working application related to the SDH Manager, the operator will have to confirm, cancel, select
options or ask for help using buttons. Different types of buttons exist and are described in this section.
3.2.5.1 Push buttons
Push buttons are identified by two characteristics:

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

22 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The graphical image representing the button. The buttons are generally of rectangular or square shape.
The label identifying the action associated with the button. The label is placed on the button.

Examples of the different types of push buttons are described in the figure below.

: Confirms an operation or action.

: Gives access to help on context.

: Cancels an operation or action.

: Exits from the application

Figure 7. Examples of push buttons.

1AA 00014 0004 (9007) A4 ALICE 04.10

To apply the action related to a push button, position the mouse pointer over the button you wish to select
and click using the Select mouse button.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

23 / 142

Each radio button represents a single choice selection. Selecting one radio button automatically deselects
the others in the set.
To select a radio button, place the mouse pointer over the button needed and click on it using the Select
mouse button.

Selected radio button

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 8. Examples of radio buttons.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

24 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.2.5.2 Radio buttons

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.2.6 Menus
In this section we describe an important aspect of the user interface. The user constantly has to open windows, select icons and navigate through the different functionalities of the SDH Manager. To do this he
will use menus.
A menu consists of a title, that usually identifies the nature of the actions that can be undertaken, and a
list of options associated with actions.
There are different menu types that can be classed as follows:

menu bars,
pull down menus,
cascading menus,
tear_off menus,
popup menus.

These types of menus are described in detail below. The details concern a view of the menu types on real
windows.
3.2.6.1 Menu bars
They are present at the top of a window, under the title of the window. They appear automatically along
with the window. An example is given in the figure below. They contain the titles from which pull down menus and cascading menus are opened.
Window title

Menu Bar

1AA 00014 0004 (9007) A4 ALICE 04.10

Tool bar

Figure 9. Window view showing the menu bar

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

25 / 142

A pull down menu is pulled down from a menu item present in a menu bar. To open a pull down menu, click
on the title of the menu you need to open with the Select mouse button.
Pulldown menu

Selected menu item

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 10. Window view with Pull down menu


N.B.

A menu option followed by ... means that selecting this option opens another view.

N.B.

A menu option followed by a sequence of keys signifies accelerators.


Accelerators are used as shortcuts to access functions. For example, the annotation Shift+F1
in Figure 10. can be used as a shortcut for accessing the Get Parent option.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

26 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.2.6.2 Pull down menus

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.2.6.3 Cascading menus


Cascading menus are derived from pull down menus and represent additional options for the pull down
menu item selected. Cascading menus are indicated if the > sign follows an option in a pull down menu.
To open a cascading menu, click on the menu option with the > sign in the pull down menu.

Pull down menu selected

Selected menu item

Cascading menu

Figure 11. Window view with Cascading menu.


3.2.6.4 Popup menus
Popup menus appear when you click, using the Custom mouse button, in the following cases:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

Clicking on a symbol in a view.


In this case, once the symbol is selected, click on the symbol using the Custom mouse button. The
popup menu opens. Select an item from the menu by clicking on it using the Custom mouse buttons.

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

27 / 142

In an opened menu (pull down or cascading), any item that is greyed indicates that you do not have access
to the menu item. Clicking on it will not activate it. You have access to all the items that are not greyed.
An example of an inaccessible or greyed menu item is shown below.

Greyed menu
option showing
non selectability

Figure 12. Unselectable menu items.

1AA 00014 0004 (9007) A4 ALICE 04.10

To select an item from a menu (any type of menu) place the mouse pointer over the item and click using
the Select mouse button. The item will appear highlighted.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

28 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.2.6.5 Unavailable menu items and Menu item Selection

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Selected menu
item highlighted

Figure 13. Highlighted menu item indicating selection.


3.2.6.6 Mnemonics
A mnemonic is a single letter that is underlined in a menu (in Menu bars, Pull down menus or Cascading
menus). For example, in Figure 11. every item of the menu bar has a single letter underlined. That letter
is the mnemonic. It enables you, via the keyboard, to undertake the selection of the corresponding menu
item.
To open a pull down menu press, simultaneously, the ALT key and the mnemonic of the pull down
menu you wish to open. The pull down menu opens immediately.
To select an option from the opened pull down menu, press on the keyboard the character corresponding to the mnemonic of the option.
3.2.7 Entry boxes
3.2.7.1 Description and Definition

1AA 00014 0004 (9007) A4 ALICE 04.10

Entry boxes are windows in which you can consult, add or modify information or data. Figure 14. gives
you examples of the general representation of an Entry Box.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

29 / 142

Entry box
(text entry
area)

Figure 14. Example of a dialogue box having Entry Boxes


Each Entry Box has two parts:

Entry Box Label: Indicates what is entered or what is to be entered in the entry area concerned.
Entry Box: When selected, enables you to enter a text.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

The text entry areas may not be accessible for entering text. In this case they have a different
colour than other entry areas in which text can be entered. In the example above, the Name of
Open Map entry box may not be used for text entry. Its colour is lighter than the other entry areas.
Furthermore the text cursor is dotted, indicating that text cannot be entered.

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

30 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Title of the window


Label of the Entry box

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

To access an entry box and enter text, click on the text entry area. The text cursor begins to blink. The text
cursor has an Ibeam shape. The following keys are useful when entering text.
Key

Function

Back Space

Deletes to the left.

Del

Deletes to the right.

, , ,

Displace the cursor along the text.

To access another entry box, you can either click in the entry box using the Select mouse button or use
the Tab key on the keyboard.
Selecting the Tab key, on the keyboard, enables you to pass to an entry box situated beneath the one from
which the Tab key is pressed. Selecting the Shift+Tab keys gives you access to an entry box situated
above the one from which the action is launched.
N.B.

The Tab key does not give you access to those entry boxes that are read only and in which you
cannot write. Therefore, when a dialogue box containing entry boxes opens, the Tab key takes
you directly to the first entry box in which you can write.

3.2.7.2 Syntactic guidelines

1AA 00014 0004 (9007) A4 ALICE 04.10

This concerns the use of upper case and lower case characters when entering text.
The text entered is redisplayed in its original form.
This means that if upper case characters are given to a Log file name, the name will appear in upper case
characters in the save directory.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

31 / 142

3.2.8 Dialogue boxes

Dialogue boxes provide an interface between the SDH Manager and the user. They enable to confirm operations or consult information, displayed by the system, following an action of the user.
There are many types of dialogue boxes. They generally combine several of the graphical controls described previously (scroll bars, push buttons...). The principal dialogue boxes are described below.
3.2.8.2 List dialogue boxes
A list dialogue box is generally a window that enables you to consult and select items from an existing list.
They have a Title heading indicating the purpose or contents of the List box. Depending on the size of the
List box, scroll bars are present or not.
Different types of List boxes can be distinguished.
a)

Single column lists.


As the name suggests, they enable you to select elements from a single list.
They contain:

b)

Title: specifying the context of the List box.


List: from which an item or items are selected.
Pulldown menu
Tool bar which contains selectable icons

Multiple columns lists.

1AA 00014 0004 (9007) A4 ALICE 04.10

They display the data in the form of multiple columns. An example is given below.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

32 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.2.8.1 Generalities

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 15. Multiple List box


You can choose from the list the item you wish, and if possible, using the menu bar options undertake
certain operations concerning the item.
3.2.8.3 Message and Confirmation dialogue boxes
They display messages and information. They require a confirmation of the action you wish to undertake.
Generally, work is suspended till the dialogue box is closed. This means that you first have to click on the
corresponding button (OK, Cancel, Help or other options) before resuming operations.

1AA 00014 0004 (9007) A4 ALICE 04.10

Different types are shown in the figures below:

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

33 / 142

These dialogue boxes inform you of an illegal command or action.


Warning dialogue boxes are displayed to warn you about future events pertaining to the action you have
launched.
Work in progress dialogue boxes indicate that work is in progress and that you may resume operations only
when the work is over. The dialogue box may close automatically or you may have to click on a push button
to close it.

Figure 17. Question dialogue box

1AA 00014 0004 (9007) A4 ALICE 04.10

A question dialogue box requests additional confirmation following a command previously launched. The
Cancel push button cancels the operation.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

34 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 16. Error dialog box

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 18. Information dialogue box


They inform you on the action you have undertaken. In Figure 18. a particular printer was not configured
and could not be used for printing. Sending a print command to this printer generates this dialogue box.

Figure 19. Confirmation Dialogue Box

1AA 00014 0004 (9007) A4 ALICE 04.10

They enable you to confirm or cancel an action previously launched.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

35 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

36 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4 GLOSSARY OF TERMS
Add and Drop Multiplexer:
Equipment used to combine several signals to produce one signal at a higher rate and to decompose it
back to the original lower rate signals.
Administrator:
A user who has access rights to all the Management Domains of the SDH Manager product. He has access
to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the OS. An alarm is characterized by an alarm begin and an alarm end.
Alarm Indication Signal:
Alarm linked to the physical interface, associated with a probable alarm occurrence in the normal
transmission of the signal.
Automatic laser Shutdown:
Functionality provided by the SDH Manager to cut the laser source automatically in case of system failure.
Automatic Protection Switching:
Functionality related to Network Elements that automatically switches from the degraded resources to the
redundant or spare resources. This assures the best quality of transmission service.
Alarm Severity Assignment Profile:
Function allowing the assignment of severities to the alarms depending on their probable causes.
Alarm Status:
Identifies the type and severity of an occurring alarm.
Administrative Unit:
Entity composed of a high order virtual container (VC4) to which is added a pointer indicating the position
of the virtual container in the STMN frame.
Administrative Unit pointer Justification Counter:
Counter indicating whether positive, negative or null justification is undertaken in the administrative unit.
This counter enables the management of the synchronization and the coherence of the transmitted signal.
Bit Error Rate:
This determines the number of errored bits in a signal frame. If the value exceeds a certain threshold then
an alarm is generated.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.

1AA 00014 0004 (9007) A4 ALICE 04.10

Compact Disk Read Only Memory:


Data saving support from which the information can only be read. Is useful for stocking data due to its
available memory space.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

37 / 142

Crossconnect (XC)
CrossConnects provide the network with the Routing Capabilities, this is the possibility of routing one
signal to a particular destination.
Digital Communication network:
Communication Network in which the transmission of data is done in a digitized format.
Degraded Signal:
Alarm sent when the number of errors detected in a received signal frame exceeds a certain threshold.
Embedded Communication Channel:
Communication channel used in conjunction with packet commuting networks (X25) to manage distant
SDH networks. These communication channels are related to the QECC* protocols.
Element Management Layer:
This apllication is responsible for the configuration and management of Network Elements.
Equipment Protection Switching:
Used to provide protection for cards within the ADM to protect traffic in the event of card failure.
Filter:
They are related to the alarms or events generated on an NE or internally within the OS itself. They can
be configured by an operator to reject specified types of notifications and limit the processing that is applied
to them.
Flushing:
This deals with logs. When a log is flushed, all its records are deleted.
Functional Access Domain:
It defines the range of functions which are available to a specified user.
Far End Receive Failure:
Alarm linked to the multiplex section termination functional block, indicating that a receiving problem is
occurring at the far end of a communication link.
Gigabits per second:
Unit that corresponds to the transmission of 109 bits every second.
Gateway Network Element:
It is a Network Element devoted to the control, from the OS, of those NEs providing a QECC* interface.
High Order Assembler:
Function of the SDH Manager that is composed of the Higher Order Path Adaptation and the Higher Order
Path termination functions.

1AA 00014 0004 (9007) A4 ALICE 04.10

High Order Matrix:


Defines the ports of an NE handling transmission rates greater than 140 Mbit/s.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

38 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Craft Terminal:
Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used to
configure or perform monitoring tasks on the NE.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

High Order Path Adaptation:


Function used to assemble the low order virtual containers (VC12 and VC3) into the high order virtual
container (VC4).
High Order Path Connection:
Function dealing with the establishment of high order connections (cross connections and pass through
connections) in boards.
High Order Path Termination:
Function used to complete the high order virtual container path overheads and vice versa extract the path
overhead from these virtual containers.
High Order Virtual Container:
A virtual container associated with a 140 Mbit/s signal (VC4).
History Report:
This function enables operators to get information concerning performances, security or alarms on entities
composing the network, or on the network itself. The operator specifies the time period for which he
requires the report.
Information Manager:
Processes used by the SDH Manger that are the functional part of the SDH Manager applications.
International Telegraph and Telephone Consultative Committee:
Standard organization for telecommunications. Now called the ITUT (International Telecommunication
Union).
Kilobits per second:
Unit that corresponds to the transmission of 103 bits every second.
Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or
multiplexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Loss Of Frame:
Alarm linked to the regenerator section termination functional block, associated with the loss of signal
frame.
Low Order Matrix:
Defines the ports of an NE handling transmission rates less than 140 Mbit/s.
Loss Of Pointer:
Alarm linked to the section adaptation functional block, associated with the loss of a pointer in an
administrative unit.

1AA 00014 0004 (9007) A4 ALICE 04.10

Loss Of Signal:
Alarm linked to the physical interfaces, associated with the absence of a received signal.
Loss Of Tributary Signal:
Alarm linked to the PDH physical interface, indicating the loss of a tributary signal.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

39 / 142

Low Order Path Connection:


Function of the 21x2Mbit/s, 3x34Mbit/s and the 140 Mbit/s tributary boards that routes the lower order
signals to the STMN frame.
Low Order Path Termination:
Function of the 21x2Mbit/s, 3x34Mbit/s tributary boards that completes the signal by adding the path
overhead.
Low Order Virtual Container:
A virtual container associated with a 2 Mbit/s (VC12) or a 34 Mbit/s (VC3).
Management Domain:
The SDH Manager product is partitioned into management domains for functional proposes. Each
management domain is associated with functionalities that enable the operators to manage the NEs.
Media Access Control Address:
Represents the Level 2 address for Local Area Networks.
Megabits per second:
Unit that corresponds to the transmission of 106 bits every second.
Management Information Base:
Describes all the managed objects controlled by the system. An OS MIB and an NE MIB exist.
Multiplexer:
Equipment used to combine several signals to produce a single signal at a higher transmission rate and
to decompose it back to the smaller rate signals.
Multiplex Section:
In general, represents the section containing the multiplexed signals.
Multiplex Section Protection:
Provides protection for an STMN signal in case of channel failure or low transmission quality.
Multiplex Section Termination:
Function of the 140 Mbit/s and the STM1 tributary boards and aggregate boards that completes the
section overhead of the signal frame and checks the coherence of the transmitted signal. This functional
block also manages alarms linked to the multiplex section.
Network Access Domain:
NADs are used to define the set of resources a user can manage.
Network Element:
Either a telecommunication equipment or groups parts of a Telecommunication Network. Have
characteristics compliant with CCITT recommendations.

1AA 00014 0004 (9007) A4 ALICE 04.10

Network Management Level:


Designates the management functions performed on networks elements assembled in a network.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

40 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Low Order Path Adaptation:


Function of the 21x2Mbit/s, 3x34Mbit/s and the 140 Mbit/s tributary boards that maps (or demaps) the
tributary signal to (or from) the virtual containers used in the synchronous transport domain.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Network Service Access Point:


This refers to the access point in layer 3 (network layer) of the OSI stack which provides services to the
transport layer (layer 4). This access point is identified by a unique NSAP address which is constructed
according to international standards. On the 1353NM an NSAP address must be provided to uniquely
identify the NE to be supervised.
Notification:
Spontaneous data received by the system concerning an NE.
Operation System:
A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to
the operator a set of functions necessary to supervise the NEs. The SDH Manager is an Operation System.
Operator:
The enduser of the SDH Manager. He supervises a part of the network that is dependant on his user profile.
Plesiochronous Digital Hierarchy:
Represents the standard of signals having transmission rates less than 155 Mbit/s. The synchronization
signals for PDH networks are derived from different sources.
Physical Interface:
Electrical transformers that decouple the line signals and adapt the form of signal for further transmission.
This functional block also manages clock extraction, signal loss monitoring and loopback functions.
PDH Physical Interface:
As above but restricted to the PDH signals (140Mbit/s, 34Mbit/s and 2Mbit/s).
Path Trace Mismatch:
Alarm linked to the lower order path termination functional block in the 21x2Mbit/s and 3x34Mbit/s tributary
boards, indicating that a mismatch of the signal path trace has occurred.
Port:
A physical point at which the Network Element can be attached to a transmission medium. A port is either
a termination point or an origination point.
Regeneration Section:
When there is at least one repeater between two interconnected equipments, each part of the line section
between two repeaters or between a repeater and an line system is called a regenerator section.
Regeneration Section Termination:
Functional part of the 140 Mbit/s and STM1 tributary boards and aggregate boards that completes the
section overhead and checks the level of the incoming signal to determine the correctness of the frame
pattern.
Repeater:
Equipment used to regenerate a signal when it has travelled a long distance.
Section Adaptation:
Synchronizes the incoming higher order virtual container (VC 4) or the incoming STM1 signal to the
outgoing STM1 frame or the outgoing high order virtual container.

1AA 00014 0004 (9007) A4 ALICE 04.10

Severity:
Linked to alarms, severities indicate the magnitude related to the failure.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

41 / 142

Synchronous Digital Hierarchy:


Represents a standard of signals having transmission rates greater than, or equal to, 155 Mbit/s. They
are derived from PDH signals. the term synchronous indicates that the synchronization signal for SDH
networks are derived from incoming transmitted information signals.
SDH Physical Interface:
Physical interface linked to the SDH signals that converts the electrical signal to the optical signal and
detects the loss of signal during reception.
Session:
A session is a temporary association between an operator and the SDH Manager. A session always begins
with the identification and authentication of the operator (the login phase) and ends with the exit of the
operator from the SDH Manager (the logout phase). A session generally lasts a few hours.
Synchronous Transport Module level N:
Indicates the type of SDH signals that exist. N is an integer (either 1,4 or 16) representing the transmission
rate of the SDH signal. For example, an STM1 signal has a transmission rate of 155 Mbit/s while an
STM16 signal has a transmission rate of 2.5 Gbit/s.
Transmit Fail:
Alarm that indicate a dysfunction in the transmission of the signal.
Telecommunication Management Network:
Defines the concept of interoperable management of TNs. They provide an organized network structure
to achieve the interconnection of the different components of the TN and the services to process the
information.
Telecommunication Network:
Describes the network to be managed. Provides the transmission, the transport and the switching
supports to the interconnected Network Elements.
Terminal Point:
Describes either the origin or the termination of a signal in an equipment. Is related to a port.
Thresholding:
This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that,
when exceeded, generate trouble indications.
Tributary Unit:
Entity composed of a virtual container to which is added a pointer that indicates the position of the container
in the STMN frame.

1AA 00014 0004 (9007) A4 ALICE 04.10

Tributary Unit Pointer Justification Counter:


Counter indicating wether positive, negative or null justification is undertaken in the tributary unit. This
counter enables the management of the synchronization and the coherence of the transmitted signal.
User Profile:
Identifies the functionalities of the SDH Manager to which a user has access. A finite number of predefined
user profiles is determined by a fixed set of FADs.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

42 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Small Computer Serial Interface:


The Small Computer System Interface is an American National Standard for interconnecting computers
and peripheral devices. The SCSI standard includes specifications for a variety of device types.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

User Service Manager:


These are presentation processes used by the SDH Manager to manage the Human Machine Interface
and facilitate the interaction with the product.
Virtual Container:
Virtual Containers are managed by the SDH Manager. Entity composed of an information signal to which
a path overhead has been added. The path overhead is used in the management of the information signal.
Different types of virtual containers exist depending on the rate of the information signal. Lower and Higher
order virtual containers exist. The SDH norm identifies VC11, VC12, VC2, VC3 and VC4 virtual containers
named from the lowest (VC11) to the highest (VC4) container capacity.
Wrapping:
Wrapping is the technique that enables the most recent entries in a file to replace the oldest when a file
is full.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

43 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

44 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5 PRELIMINARY OPERATIONS
5.1 Logging in to the System
This is the first operation you will have to undertake to access the Regional Manager system. The view
that will greet you, called the Login panel is presented below.

Figure 20. Login panel view


To correctly access the Regional Manager:

Enter your login name.

N.B.

You are assigned the login name by the Regional Manager administrator.
Enter your password.

1AA 00014 0004 (9007) A4 ALICE 04.10

After a correct login, the login view is replaced by a transition view giving certain software copyright
indications. This view is automatically replaced by the normal workspace view containing the Front Panel
from which you will be able to access the SDH Manager functionalities.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

45 / 142

Your workspace is described as the functionalities that appear on your workstation screen after login.
The workspace Front Panel is described below.
WS
activity

Clock
Date

Padlock

Text
Editor

Workspaces

Exit

Printer

Letter

Terminal

File
Manager

TMNOS
Manager

Figure 21. The SDH Manager workspace Front Panel.


The components of this front panel are:

The Clock icon displays the current time on your workstation.


The Date display indicates the day and the date.
The WS activity icon indicates the activity of the workstation.
The Padlock icon enables you to lock your workstation screen.
The EXIT icon launches the logout procedure.
The Workspaces icons enable you to access different workspaces. There are six available
workspaces (workspaces One to Six)
The Printer icon enables you to access the printing facilities. You can drag a file to the printer
icon to print it or simply access printer information.
The Letter icon gives access to the electronic mail service.
The File Manager icon gives you access to the files in your home directory.
The Terminal icon launches a hpterm command shell on your workspace.
The Text Editor icon launches the hp text editor application.
The TMNOS icon gives you access to the functionalities offered by the Regional Manager
product for the management of the network.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

46 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.2 Workspace description

5.3 Locking the screen

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This utility enables you to lock the screen to prevent other users from using your working environment.

Padlock
icon

Figure 22. Locking the screen using a manual lock


To lock the screen simply click on the small Padlock icon situated on the Front Panel described above.
The screen will lock immediately. The following figure will appear on the screen.

Figure 23. Screen lock Password: entry box

1AA 00014 0004 (9007) A4 ALICE 04.10

To resume work type in your password in the Password: entry box.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

47 / 142

Logging out from the workstation will automatically quit all the Regional Manager graphical applications
that you opened and give place to the Login panel. Notice the the Regional Manager processes are still
running.
Using the Front Panel.
Click on the EXIT icon on the front panel, using the Select mouse button, as shown in the figure
below.

EXIT icon

Figure 24. Logging out using the front panel

1AA 00014 0004 (9007) A4 ALICE 04.10

A dialogue box opens from which you can confirm or cancel the Logout operation.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

48 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.4 Logging Out

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6 ACCESS TO THE MAIN FUNCTIONALITIES


A more detailed description concerning the Regional Manager management domains is given in the
Regional Manager Introduction Manual.
Access to the Regional Manager functionalities is provided through the workspace front panel as
described in the following sections.

6.1 Introduction
The 1354RM graphical interface is based on:

HP Common Desktop Environment (HP-CDE)

OSF Motif applications (Browser, RM aplications, etc.).

Task subpanel.

The HP_CDE Tool panel ( See Figure 25. ) has been customized to contain the TMNOS Manager
(righthand side).
WS
activity

Clock
Date

Padlock

Text
Editor

Workspaces

Exit

Printer

Letter

Terminal

File
Manager

TMNOS
Manager

Figure 25. HPCDE Panel

1AA 00014 0004 (9007) A4 ALICE 04.10

Clicking on the Manager icon you can open the TMNOS Management. ( See Figure 26. )

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

49 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.2 The TMNOS

Figure 26. TMNOS manager


By clicking on the TMNOSs icon opens a window containing all the OSs icons, i.e. all the systems resident
on the server/ws. The colour of each icon depends on the OS process state:

green

all the processes are running

red

at least one process is not running

blue

all the processes are stopped

yellow

the process state is unknown. It may be due to a isolation condition.

The window contains a pulldown menu bar comprising the following menus:

File

containing the only option Close to close the window

Edit

containing the only option Clear Message area

View

It allows to show/hide OS area orMessage area

OS
Start System. This submenu is present both for RM and SH. The Start option is available
if the selected OS is in the Stop state.
Stop System. This submenu is present both for RM and SH. The Stop option is available
if the selected OS is in the running state.
Both options are provided if the selected OS is in the Wrong state (partially stopped).

1AA 00014 0004 (9007) A4 ALICE 04.10

System Config. This submenu is available both for RM and SH. It allows to configure the
system in terms of processes
Process Monitoring. This submenu is available both for RM and SH. It opens the Process
Monitor window.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

50 / 142

System Information. It gives information on the product actually installed.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Actions
(active only for resident Manager) containing a list of menus that vary
depending on the OS type (RM or SH) and on its actual status. The relevant OS icon must be
selected. The available submenus are:
User Interface. This submenu is present both for RM and SH. It permits to launch the user
interface
Performance Monitoring. This submenu is present both for RM and SH. It permits to
launch the Performance Monitoring display window.
Alarms. This submenu is only available for SH. It permits to launch the AS application.
SMF. This submenu is present both for RM and SH. It contains the following options:
Operator
Log
Trace
Failure
Scheduler
Backup
Restore
Cleanup
Initiator

Global Actions
(active only for resident Manager) It permits to launch the entire
system actions. It contains the following submenus:
Operator. It contains the following options:
Global Operator Actions
Change Password
Session management
Max Operator Logged Administration
Set Personal Printer
Synchronize Systems
Alarm Federations

The window contains a tool bar (active only for resident Manager) which allows to launch the most
frequently used applications. They are:

ALARM
SURVEILLANCE
1AA 00014 0004 (9007) A4 ALICE 04.10

SYSTEM
EXIT

CONFIG
PROCESS
MONITORING

ED

01

PERFORMANCE
HELP

MONITORING

BROWSER

SC.2:GETTING STARTED
3AL 61348 AA AA
142

51 / 142

Exit

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

System Config
Process Monitoring
Help
1354RM Browser
Performance Monitoring
Alarm Surveillance

6.3 Alarm management


From your workspace front panel click on the Alarm icon shown in Figure 26. on page 50.
The Counter summary window is opened from which the operations on alarms can be carried out.

1AA 00014 0004 (9007) A4 ALICE 04.10

A customized sublist is presented. This sublist contains the following rows:

ED

1)

PHYSICAL LINK IN SERVICE ( IMPLEMENTED )

2)

OMS TRAIL IN SERVICE ( IF IMPLEMENTED ITS SUPERORDINATE PHYSICAL


CONNECTION )

3)

HO TRAIL IN SERVICE ( IMPLEMENTED OR PARTIALLY IMPLEMENTED )

4)

MS TRAIL IN SERVICE
CONNECTION )

5)

OCH TRAIL IN SERVICE ( IMPLEMENTED OR PARTIALLY IMPLEMENTED )

6)

PATH IN SERVICE
COMMISSIONED)

7)

CLIENT PATH IN SERVICE


COMMISSIONED)

8)

EML

9)

NE

1)

ALL PHYSICAL LINKs

2)

ALL OMS TRAILs

3)

ALL HO TRAILs

4)

ALL MS TRAILs

5)

ALL OCH TRAILs

6)

ALL PATHs

7)

ALL CLIENT PATHs

01

( IF IMPLEMENTED ITS SUPERORDINATE PHYSICAL

( IMPLEMENTED OR PARTIALLY

( IMPLEMENTED OR PARTIALLY

IMPLEMENTED OR

IMPLEMENTED OR

SC.2:GETTING STARTED
3AL 61348 AA AA
142

52 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

8)

PRC

9)

BACKBONE NETWORK

10 ) MAIN ALARM LIST


11 ) DEFAULT ALARM LIST
Alarms on NOT_ IN_ SERVICE entities are automatically acknowledged by AS.
The not in service declaration is done:

by the user for physical connections, OCH/HOtrail and (client)path

automatically by the system for physical connections, OCH/HOtrail and (client)path at


deimplementation time

If an alarmed entity is declared in service, a warning is given to the user.


Each row of the above sublist has been created, activated and saved; each row of the default sublist
has been deactivated and deleted. (The default sublist contains one row per each alarm severity).
6.3.1 Alarm Navigation
The following sequence briefly describes the alarm navigation.
a)

From the Counter summary window open the Alarm sublist clicking twice on the relevant row of the
Counter summary window. As an alternative select the row and issue the Sublist: Open pulldown
menu item.
The Alarm sublist is presented.

b)

Select the alarm from the sublist and navigate it by selecting the Navigation: 1354RM pulldown
menu item. A confirmation dialog box appears. Click on OK to confirm.
The following cases are possible:

for PATH object the napView window is presented

for PHYSICAL CONNECTION object the physical connection structure window is


presented

for O/MS TRAIL object the physical connection structure window is presented

for HO TRAIL object the path in trail window is presented

for EML object only the navigated object is presented

1AA 00014 0004 (9007) A4 ALICE 04.10

Notice that in each view the alarmed object is marked by an alarm icon. By clicking on this icon a window
is presented, which gives details on the selected alarm.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

53 / 142

6.4 Task Subpanel

Alcatel logo

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The task subpanel (see Figure 28. ).starts automatically at browser startup.

upper arrow

Create connection

Create SDH Trail

Create Path

task buttons
Active counters

Netview
Browser

lower arrow

Figure 27. Selfhiding vertical palette

1AA 00014 0004 (9007) A4 ALICE 04.10

The selfhiding vertical palette contains:

upper arrow. If you click with the left mouse button on it, the icons contained in the layered icon area
will shift to the top side of the area itself.

lower arrow. Same as upper arrow, except for the direction.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

54 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

TASK BAR. It contains the Alcatel logo and the icons of the tasks customized by the user. If you click
with the left mouse button on the icon of task, this causes the task to start. The task bar is customizable by the user, i.e. the user can add task buttons of the most frequently used applications by means
of the utility popup menu, available on each system menu item. See example in the following pages.
On the other hand the user can remove a less frequently used application icon by means of the task
bar popup menu ( Remove item ). The user can drag these icons by pressing the middle mouse
button.

6.5 Active task subpanel


The active task subpanel is an horizontal panel located on the bottom of the screen.

Left arrow

Right arrow

TASK BAR
LAYERED ICON AREA

iconified windows

Figure 28. Active task subpanel

1AA 00014 0004 (9007) A4 ALICE 04.10

It contains:

left arrow. If you click with the left mouse button on it, the icons contained in the layered icon area
will shift to the lefthand side of the area itself.

right arrow. Same as left arrow, except for the direction.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

55 / 142

TASK BAR. It contains the Alcatel logo and the icons of the tasks customized by the user. If you click
with the left mouse button on the icon of task, this causes the task to start. The task bar is customizable by the user, i.e. the user can add task buttons of the most frequently used applications by means
of the utility popup menu, available on each system menu item. See example in the following pages.
On the other hand the user can remove a less frequently used application icon by means of the task
bar popup menu ( Remove item ). The user can drag these icons by pressing the middle mouse
button.

layered icon area. This area contains the icons of the browser windows actually opened. If you click
with the left mouse button on the icon of a browser window, this causes the window to open.

6.5.1 System Menus started from the logo icon


System Menus can be started from the logo icon. See para 6.5.2.1 on page 57.for details.

Figure 29. System Menus started from the logo icon

6.5.2 Menus
INTRODUCTION
To lauch the application/function associated to a single item, select the item with the left mouse button
MENU DESCRIPTION

1AA 00014 0004 (9007) A4 ALICE 04.10

Point with the right mouse button to an empty area of the horizontal task bars.The main popup menu is
displayed. See below figure.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

56 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 30. Popup menu


The main menu contais the following submenus:

System menus. System menus contains a cascode menu of the main system applications.

User menus. This menu is customizable by the user by means of the utility popup menu, available
on each system menu item. See example in the following pages.

Close main panel. This menu item closes the panel. The panel opens automatically at browser startup.

Figure 31. Panel Close confirmation window.


6.5.2.1 System menus

1AA 00014 0004 (9007) A4 ALICE 04.10

System menus ( see following figure ), include:

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

57 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 32. System menu

Path Provisioning. The cascode menu is shown in Figure 33.

Network Configuration. The cascode menu is shown in Figure 34.

Maintenance. The cascode menu is shown in Figure 35.

OS Supervision. The cascode menu is shown in Figure 36.

Browser. This menu starts the browser application.

Netview. This menu starts the Netview application.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 33. System Menus: Path Provisioning menu

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

58 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 34. System Menus: Network Configuration menu

Figure 35. System Menus: Maintenance

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

59 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 36. System Menus: OS Supervision

6.5.3 Create new panel


This option allows to create a new panel: edge panel (horizontal) or corner panel (vertical)

Figure 37. Create New Panel submenu

1AA 00014 0004 (9007) A4 ALICE 04.10

Figures which follow show the icons of the corner and edge panel

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

60 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

NEW CORNER PANEL


Figure 38. Create: New Corner Panel
.

NEW EDGE PANEL


.
Figure 39. Create: New Edge Panel

6.5.4 Task bar popup menu


The task bar popup menu contains the following options:

Remove from panel

Move applet. If you click on this menu, you will be able to move the involved icon by dragging it by
means of the left mouse button. It is the same as using the middle mous button ( pressed ) to drag
icons

Properties...

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 40. Task bar popup menu

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

61 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.5.5 This Panel Properties

Figure 41. Panel Properties: Edge Panel


Edge panel:
Position ( Top, Bottom, Left, Right )
Minimize Options ( Auto Hide, Enable hidebuttons, Enable hidebutton arrows )

1AA 00014 0004 (9007) A4 ALICE 04.10

Background:

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

62 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 42. Panel Properties: Background

6.5.6 Global Properties

1AA 00014 0004 (9007) A4 ALICE 04.10

The Global Properties menu item, if selected, allows to display/modify panel configuration. Figure which
follows shows the Global Panel Configuration first dialog box: Animation.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

63 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 43. Global Panel Configuration: Animation


Parameters managed by this dialog box are:
Animation

1AA 00014 0004 (9007) A4 ALICE 04.10

Auto hide animation speed ( in ms ) = delay to disappear of the panel when you move the pointer outside
the panel. This modality is in effect if you previously selected AutoHide in the Panel Properties: Edge
Panel view. ( see previous paragraph.)
Explicit hide animation speed ( in ms ) = delay to disappear of the panel when you move the pointer
outside the panel and a window overlaps the panel. This modality is in effect if you previously selected
AutoHide in the Panel Properties: Edge Panel view. ( see previous paragraph.)
Drawer animation speed= N.A.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

64 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Auto Hide minimize delay ( in ms. )=delay to appear of the panel when you move the pointer inside the
panel. This modality is in effect if you previously selected AutoHide in the Panel Properties: Edge Panel
view. ( see previous paragraph.)
Auto Hide minimized size ( pixels )=size of the remaining bar when the most part is hidden ( the survivor,
look carefully...)

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 44. Global Panel Configuration: Miscellaneous


Miscellaneous
If you click on Miscellaneous button, a different set of parameters is displayed. They are:

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

65 / 142

Show popup menus outside of panel N.A.


Show buttons. If this option is enabled, the last submenus of the panel is is not available and is replaced
by a button ( see below figure). If you click on a button, the utility popup menu is provided, allowing to
customize groups of commands.

keep menus in memory. This option can be used to speedup panel performance.
Remaining options are not applicable.
.
BUTTONS...

6.5.7 Utility popup menu


The user can add task buttons of the most frequently used applications by means of the utility popup
menu, available on each system menu item ( see figure below ). This menu, opened via the right mouse
button, contains the following options:
Add this as drawer to panel
Add this as menu to panel
Add this to personal menu

1AA 00014 0004 (9007) A4 ALICE 04.10

On the other hand the user can remove a less frequently used application icon by means of the task bar
popup menu ( Remove item )

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

66 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Tooltips enabled=enables the display of the icon help textstrigs which appear when you move the mouse
pointer over the icon

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 45. Utility popup menu on each system menu item

6.5.8 Customize panel procedure


a)

Point with the mouse to an empty region of the panel, press the right mouse button to open the
popup menu. Select Global Properties menu item.

b)

From the Global Panel Configuration window click on Miscellaneous button. The Miscellaneous
dialog box page is displayed. Select option Show...buttons. Click on OK button to confirm and close
the dialog box. If you click on Apply to confirm, the dialog box remains open.

c)

Select the command or the group of commands you want to customize, marked by the button shown
in the figure below.

In the following we are giving two examples:


1)

Managing a group of commands, e.g. Path Provisioning.


Select with the left mouse button the button placed on the right side of the command group line.

1AA 00014 0004 (9007) A4 ALICE 04.10

The utility menu is displayed. Possible actions are:

ED

01

Add this as drawer to panel

Add this as menu to panel

Add this to personal menu

a)

If you select Add this as drawer to panel, the Path Provisioning icon will be added to the
panel, as in Figure 46. herebelow. Clicking on the icon a vertical panel is raised, containing
the icons of the commands included in the subgroup of commands.

SC.2:GETTING STARTED
3AL 61348 AA AA
142

67 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

BUTTON for the group of commands

Button for the single command belonging to the group of commands

Figure 46. Utility buttons


b)

If you select Add this to personal menu, the Path Provisioning icon will be added to the
panel, as in figure herebelow. Clicking on the icon a vertical panel is raised, containing the
icons and the textstrings of the commands included in the subgroup.

Figure 47. Utility button: Add this as menu to panel for a group of commands

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

01

If you select Add this as menu to panel, the Path Provisioning icon will be added to the
personal menu. Clicking on the icon a vertical panel is raised, containing the icons and the
textstrings of the commands included in the subgroup.

SC.2:GETTING STARTED
3AL 61348 AA AA
142

68 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 48. Customized user menu.


2)

Managing a single command i.e. Path Creation wizard


Select with the left mouse button the button placed on the right side of the command group line.
The utility menu is displayed. Possible actions are:

Add this launcher to panel

Add this to personal menu

a)

If you select Add this launcher to panel, the Path Creation wizard icon will be added to the
panel. Clicking on the icon with the left mouse button, the application starts.

b)

If you select Add this to personal menu, the Path Creation wizard icon will be added to the
panel.

6.5.9 Add this menu as drawer to panel

1AA 00014 0004 (9007) A4 ALICE 04.10

With reference to Figure 49. , if you want to add the icon of the path create to the task bar, select System
menus: Path Provisioning: Path Creation Wizard: Add this to launcher panel

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

69 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 49. System menus: Path Provisioning: Path Creation Wizard: Add this to launcher panel
NOTE
The window icon popup menu allows to close or restore the window

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 50. Window icon popup menu

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

70 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7 VIEWS DESCRIPTION
7.1 Overview
The User Interface of the 1354RM is the Browser. It allows to open many applications.
Netview allows to create and display the topological objects (Network, Subnetwork, Ring, Node, SDH
Port) and the physical connections involved.
In any submap, by clicking twice on an object, the submap associated to the object proper opens.
The different submaps are described in next Chapter Navigation. It describes the Navigation procedures
among the Netview submaps.
The available submaps are:

Network Domain submap

Network submap.

Subnetwork submap.

2nd level Subnetwork submap

Link submap.

The physical connections are grouped in links.

1AA 00014 0004 (9007) A4 ALICE 04.10

The Browser application includes:

a main view which allows to navigate among all the topological and connectivity objects;

several views named:

Netview, mentioned above

Payload configuration of a Physical connection

Port payload structure

HOTRAIL configuration (LO lc in HOtrail)

LO Paths in a HOTRAIL

Payload Configuration of a SDH port

MSSPRING protection block view

Single MSSPRING Protection Block

Path Routing view

Node view

Nap view

several lists. They are:

ED

Path List
Trail List
01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

71 / 142

NAP List
CTP List
CAP List
Port List
Performance Measure List
Alarmed Object List
Alarm Profile List

7.2 Management Tools windows


Several windows associated to the Management Tools are also available. In the following are listed the
main ones:
Payload Configuration

It is used to create or modify a physical connection or a ring


payload structure

Trail Creation (WIZARD)

It is used to create a trail.

Path Create (WIZARD )

It is used to create a path (endtoend connection) between


two or more NAPs.

Path Constraints

It is used to assign the constraints to a path or trail

PM Measure Create

It permits to create a Performance Monitoring measure.

PM Measure Correlate

It is used to assign the objects involved to a measure:

transports (trail/path)

termination points (tp)

Event logger

It allows to display the events.

Node create ( WIZARD )

It allows to create a node.

Connection Create ( WIZARD )

It allows to create a connection

7.2.1 Wizard
Wizards make use of a driven approach to better help the user in executing the requested procedures.
In the fact each wizard is constituted by a fixed sequence of dialog boxes. Per each dialog box the user
is requested to enter some parameters or names or values, and after filling the box the user passes to the
subsequent box by clicking on Next button.
Each box ( with the exception of the first one ) contains also the button Previous, which allows the user
to check / change the previously entered values.

1AA 00014 0004 (9007) A4 ALICE 04.10

The last dialog box contains the button Finish, which launches the execution of the procedure concerned.
Wizards are easy and friendly to the user, since they do not require to navigate through the browser to
select objects to be dropped: namely they contain dedicated selection buttons, which provide lists of the
objects suitable to be inserted to fill the wizard dialog boxes. Notice that these lists are filtered according
to the parameters entered in the previous dialog boxes.
It is also possible to navigate through Netview map to select the objects to insert into the dialog boxes.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

72 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

8 SDH NETVIEW : MAP NAVIGATION


8.1 Introduction
It is possible to start The Netview applicationfrom browser, pointing to the Network domain icon and issuing
the popup menu Display: All Related Items.
Select item Network Domain view and click on No Filter. Netview opens, showing the Network icon(s).

PULL_DOWN MENU

GENERAL TOOL BUTTONS

SHOW/SET
ATTRIBUTES
GET PARENT

GET PARENT
OBJECT

EXIT
POPDOWN

GET RELATED OBJECTs

ALIGN ITEMs

SHOW USER

ACTIVATE WINDOW ZOOM


SHOW EQUIPMENT

ZOOM TOOLS

HIGHLIGHT

CREATE TOOLS

SAVE
COORDINATES

MOVE NODE

HIDE BACKGROUND
RESIZE OBJECT

SAVE
BACKGROUND

OPEN
SECONDARY VIEW

SET VISIBLE LAYER


HIDE ISOLATED NODES

1AA 00014 0004 (9007) A4 ALICE 04.10

SPECIFIC TOOL BUTTONS

Figure 51. Map window: Pulldown menu and tool buttons

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

73 / 142

Menus and tool buttons change according to the selected object. By moving the mouse over
the tool button icon, a ballon help is shown, explaining the operation invoked by the button itself.

8.1.1 Usage of zoom tool


The zoom pulldown menu includes:
Zoom In to enlarge the working area of the map view. This item allows the operator to increase the
current scale factor. The view center point does not change.
Zoom Out . This item allows the operator to reduce the scale of the current scale factor. The view center
point does not change.
Fit. This item allows the operator to return to the original size and center of the view.

Figure 52. Zoom tool interface


Window Zoom

1AA 00014 0004 (9007) A4 ALICE 04.10

This item allows the operator to zoom into a defined view rectangle. Click on Activate Window Zoom
button. Click on the first corner of the area to zoom and drag to the second corner of the area to zoom,
thus drawing a rectangle on the map. See following figure.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

74 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

N.B.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 53. Area to magnificate

Release mouse button. The selected rectangle fits the working area. See following figure.

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

75 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 54. Zoomed area.

8.1.2 EXAMPLE of SDH submap navigation


An example of submap navigation is shown in the figures that follow.

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

Figure 55. shows the RM submap.

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

76 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 55. RM domain map

1AA 00014 0004 (9007) A4 ALICE 04.10

The display of the physical connections can be filtered by means of the Available Layers button, present
on the tool button palette, which allows to display separately the map connectivity.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

77 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 56. Available Layers

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

78 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 57. Domain submap

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

Clicking twice on the network icon, the network map is opened. It contains the subnetwork symbols
along with their physical connections (see example in Figure 57. )

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

79 / 142

Clicking twice on the subnetwork icon, the submap of the objects belonging to that subnetwork is
opened (see example in Figure 58. )
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

c)

Figure 58. Objects belonging to a subnetwork

1AA 00014 0004 (9007) A4 ALICE 04.10

d)

ED

Clicking twice on the icon of the 2nd level Subnetw, the submap of the objects belonging to it is
presented (see example in Figure 59. on page 81)

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

80 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 59. Objects belonging to a 2nd level Subnetw

1AA 00014 0004 (9007) A4 ALICE 04.10

Clicking on the Physical Connection group, the Physical Connection list opens.

Figure 60. Physical Connection list

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

81 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Select the Physical Connection and click on icon Physical Connection structure. The Physical Connection
structure opens.

Figure 61. Physical Connection structure

1AA 00014 0004 (9007) A4 ALICE 04.10

On each object represented in the map, the object popup menu can be opened. See Figure 62.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

82 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 62. Popup menu

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

83 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

84 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9 BROWSER
9.1 Introduction
The Browser is a Motif based application which provides multiple navigation views. It supports full view
of MIB data objects or tailored views. The commands available in the browser depend on users profile.
The Browser supports:

Single/multiple selection operations

Pulldown menu with generic and/or object specific commands

Popup menus with generic and/or object specific commands

Drag and drop operation for interworking between applications

Help on item (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button/object.

Contextsensitive help. If you select the object and the pulldown menu Help on selected
object, the Worldview application starts and displays automatically the description of the
selected object class.

The Browser is based on the approach to enable navigation into all, a portion or a view of the containment
tree.
Objects are presented with:

An icon related to the class (a bitmap) that can be related to one or more attribute values.
Example:

class NE with bitmap depending on Type

A color relevant to an attribute value (e.g. implementationStatus)

A label related to one or more attribute values

Additional labels/option buttons/texts or multicolor icon (pixmaps) displaying attribute values

An alarm icon that appears only when the object is alarmed, whose color is related to the alarm
status value.

1AA 00014 0004 (9007) A4 ALICE 04.10

Object containment is represented using:

ED

Recursive object grouping into frames

Indentation

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

85 / 142

The basic operations on objects are:

Related items ...


All related items
Unselect all

Details

1AA 00014 0004 (9007) A4 ALICE 04.10

Main related items ...


All related items ...
Align item(s)
Parent

Select

ED

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Search (Display)

Show/Set attributes ...


Displayed info ...

Class specific actions (executed as separate processes)

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

86 / 142

9.1.1 Browser main window

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

After launching the Browser application, the Browser window is opened.


This window contains:
icon bar

pulldown menu

window title
counters

item

balloon
help

area
info

work area

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 63. Browser main window.

ED

window title : 1354RM: Browser

pulldown menu bar.

icon bar. Refer to paragraph 10.2.1

title : 1354 RM Viewer [ drop to view ]


You can drop here an item dragged from browser or other RM applications.

counters area. It contains three counters:


01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

87 / 142

Total. It is the total number of objects actually retrieved by the Browser.

Visible. It is the total number of objects visible in the window.

Selected. It is the total number of objects selected (should be always 1)

work area. It contains the retrieved objects.

info area containing:

logo

help area providing the following information:

values of displayed attributes.You get this information moving the mouse to the
involved object in the work area.

function button description. You get this information moving the mouse to the
involved button in the button box.

events flag indicator (Create not processed, Delete and Update processed).

Balloon help are present on widgets (buttons, items, attributes, ...).

9.1.2 Icon bar


The first row of icon bar contains the following buttons:

Exit. It corresponds to the pulldown command File: Exit.

Display: Main Related Items. It corresponds to the pulldown command Actions:Search:Main


related items and/or to the popup command Search:Main related items

Display parent item. It corresponds to the pulldown command Actions:Search:Parent and/or to the
popup command Search:Parent.

Show/Set attributes. It corresponds to the pulldown command Actions:Details:Show/Set Attributes


and/or to the popup command Details:Show/Set Attributes.

Align item(s). It corresponds to the pulldown command Actions::Align item(s) and/or to the popup
command Align item(s).

User info. It provides the help information of the logged user.

The second row of icon bar contains the following buttons:

Highlight button. It allows locate/display object

Open Map. It opens the map view

Topology tools. If you click on this button a submenu is opened. It includes the following buttons:

1AA 00014 0004 (9007) A4 ALICE 04.10

go to parent menu
go to home menu
Create Node
Create Physical Connection
Shared Risk Group Management

Configuration Tools (CFG). It shows the configuration tools. If you click on this button a submenu
is opened. It includes the following buttons:

ED

go to parent menu
01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

88 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

go to home menu
Payload configuration
Concatenated rates setup
create HO trail
add/remove protection

Path tools. If you click on this button a submenu is opened. It includes the following buttons:

go to parent menu
go to home menu
Create path
Add Constraints to a path/trail
Add leg to a path
Show scheduled operations
WDM Connectivity Tool
Add/Remove protection

Alarms tool. If you click on this button a cascode submenu is opened. It includes the following
buttons:

show alarms at server layer

Report elementary alarm correlation

Show active alarms

Create Alarm profile

Alarm Management wizard

PM. It shows the performance monitoring tools. If you click on this button a submenu is opened. It
includes the following buttons:

Create Measure
Correlate transport to a measure
Merge measure
Show PM Data

Tools

go to parent menu
go to home menu
Active counters
Event Log. It starts the Event Log application.

Show Equipment. It opens the Equipment view of the selected NE

9.1.3 Counters area

1AA 00014 0004 (9007) A4 ALICE 04.10

In the Total, Visible and Selected field are shown respectively the total number of displayed items, the
number of visible items and the number of selected items.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

89 / 142

9.1.4 Work area


Attribute (Working State)

Label

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Item

Figure 64. Browser work area.


In the Browser main window work area are displayed the retrieved items that are configured to be shown
in that window (eg. Nodes in topology from the ET). Retrieved items can be also displayed in Drawing
Windows and in Multicolumn Windows (eg. All nodes from Network, Network Domain and Root Domain)
and will be detailed in the next paragraphs; in these cases a group icon that refer to the relative window
is displayed in Browser Main Window work area.
9.1.5 Object filtering

1AA 00014 0004 (9007) A4 ALICE 04.10

Object filtering and scoping is supported throught the Search:Main related items and Search:All related
items.Filtering can be performed with:

Conditions entered by the user

User defaults presaved conditions

Class related predefined conditions (e.g. customerName=xyy)

Using the popup Search:Main related items or Search:All related items, or selecting one or more items
and using the icon button Display Related Items or the pulldown Actions:Search:Main related items or
Actions:Search:All related items a Chooser window of available navigation is shown:

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

90 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 65. Object filtering.

Clicking on the Options ... button the Define Query For window is shown (see next paragraph)

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

91 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.1.6 DEFINE QUERY FOR (the selection/filter window)

Figure 66. Define query window for Node


The DEFINE QUERY window is used to display a list of attributes of the selected object. This window has
a standard structure, described in the following:

Window label

The window label is: DEFINE QUERY FOR <object class name >

Parameter group buttons


The parameters are divided in groups. Each button activates the
display of the parameters belonging to that group

Selection parameters

The selection parameters are structured in three columns:


attributes, filtercriterion , value.

Control buttons

Three control buttons are provided: Apply, Cancel and Help

1AA 00014 0004 (9007) A4 ALICE 04.10

The lefthand column contains the list of all the attributes of the selected object
The central column (option button) specifies the filter condition. A popup menu can be opened, which
allows to select among the options.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

92 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

If attribute is of type string the popup menu which can be opened is the following:

None.

No filtering is specified.

Start with.

This filter condition provides the instances which start with the speci
fied string in the relevant MIB data.

Match exactly.

This filter condition applies an exactly match between the field


specified and the relevant MIB data.

Contains.

This filter condition provides the instances which contain the speci
fied string in the relevant MIB data.

End with.

This filter condition provides the instances which ends with the speci
fied string in the relevant MIB data.

Doesnt contain.

This filter condition provides the instances which do not contain the
specified string in the relevant MIB data.

If the attribute is of the type enumerated, the popup menu which can be opened is the following:

None

Equal to

Not Equal to
If the attribute type is date, the popup menu is:

None

Before

Since

Exactly
If the attribute type is integer the popup menu is:

None

Greater equal than

Less equal than

Equal to

Not equal to
The righthand column contains the attribute values. The value can be entered in text field, for the types
integer, date and string. The value can be entered as option for the type enumerated.
The function of the filter is an AND of all the previously specified conditions.
In case the selection is handled by pointers instead of containment tree, the filter is disabled.
9.1.7 Show/Set Attribute

1AA 00014 0004 (9007) A4 ALICE 04.10

The Show attribute operation is startable from popup Details:Show/Set attributes, from the pulldown
Actions:Details:Show/Set attributes and from Show/Set attributes icon and allows to display the
ATTRIBUTE VALUES FOR window that shown the item attributes retrieved.
The ATTRIBUTE VALUES FOR window is quite similar to the DEFINE QUERY window and is used to
display or change value in MIB of the selected objects attributes. This window has a standard structure,
( see Figure 67. ) described in the following:

ED

Window label

01

The window label is: ATTRIBUTE VALUE FOR <class> <item label>

SC.2:GETTING STARTED
3AL 61348 AA AA
142

93 / 142

Parameter group buttons


The parameters are divided in groups. Each button activates the
display of the parameters belonging to that group

Parameters

The parameters are structured in three columns:


attributes name, set buttons (set and set to default) present only if the
attribute is modifiable, fields or option buttons.

Control buttons

Three control buttons are provided: Apply, Cancel and Help

group
buttons
non modifiable attribute

set button

Figure 67. Show/Set Attributes dialog box.

9.1.8 Items selection in the Browser


A possible use of this feature is, for example:

select within a path list already displayed in the browser, all the paths where the configuration state
is allocated and the customer name matches a given value or pattern. After the selection, the
configuration action required can be issued.

1AA 00014 0004 (9007) A4 ALICE 04.10

The available commands and the behavior result from the following table:

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

94 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Table 1. Items selection in the Browser

Command

Select All

Browser
Main Window
Not available

Browser
Multi Column Lists

Browser
Graphical Views

All the items in the current Not available


multi column list are selected

Select
All the children of the given Not available
All related items selected object are selected
Unselect All

Not available

All the selected objects All the selected objects All the selected objects
are unselected
are unselected
are unselected

Select
related A mask with the possible Not available
items ....
children classes for the selected object is presented.
From this mask, the user
can select a class and, optionally, the detailed filter
to be applied (see description for multicolumn
view)
Select ....

N.B.

Not available

A mask with the possible


classes displayed in the
view is presented.From
this mask, the user can select a class and, optionally,
the detailed filter to be applied (see description for
multicolumn view).

A mask with the attributes Not available


of class displayed in the
list is presented. The user
can define a sequence of
conditions in order to perform the needed selection.

The command Select All allows to select a maximum of 65 lines.

9.1.9 Generic Browser pulldown menu

9.1.10 Actions: Search: Main Related items...


The purpose of this procedure is to retrieve from the MIB data base the main information related to the
selected object. The relationship between the selected object and its related items is described in the
object containment tree. In detail, this relationship can be though as a fatherchild relationship or a pointer
relationship.

1AA 00014 0004 (9007) A4 ALICE 04.10

This operation can be executed either from the Actions pulldown menu, that starts the get operation of
all selected objects (they MUST belong to the same class) or from the object popup menu that starts the
get operation only on that object.
This operation can also be launched by doubleclicking the object or clicking on the Get object from MIB
icon of the icon bar.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

95 / 142

SEQUENCE
Select (left click) one or more object to browse and Actions: Search: Main Related items....
The related item selection window is displayed. This window contains the list of child classes of the
selected object.
b)

Select the class to display and the search mode (Filter/No Filter). If you select No Filter the related
objects (children) of the selected object are displayed below the father icon.
If you select Filter the Define Query window is displayed (See Figure 66. ).
The box containing the available related objects is indentated with respect to the symbol of the father.

c)

You can continue displaying related items for an object selecting again Search: Main related items
popup or pulldown menu item, according to the database hierarchical tree.

NOTE
The output of the Search Main Related items operation can be in normal format, i.e. displayed indentated
in graphical way, or in multicolumn format or by means of dedicated views, i.e. giving a compacted list
of the browsed objects.
9.1.11 Actions: Search: All Related items...
This command is analog to the command Actions: Search: Main Related items... (see paragraph
9.1.10)The only difference is that all related items are available to be displayed.
9.1.12 Actions: Search: Parent.
The purpose of this procedure is to retrieve from the MIB data base information related to objects that
contains the selected one. The relationship between the selected object and its parent is described in the
object containment tree. More in detail, this relationship can be though as a fatherchild relationship or
a pointer relationship.
This operation can also be launched by clicking on the Get parent object from MIB icon of the icon bar or
from the object popup menu.
a)
b)

Select (left click) one/more object/s to browse or popup.


Select Actions: Search: Parent.

The Parent object is displayed in the Browser window below the icon of the child object.
9.1.13 Actions: Select: Related Items....
This menu, if selected, provides a mask with the possible children classes for the selected object.
From this mask the user can select a class and, optionally, the detailed filter to be applied.
This operation can be executed also from the object popup menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

9.1.14 Actions: Select: All related Items....


All children of the given selected object are selected.
This operation can be executed also from the object popup menu.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

96 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

a)

9.1.15 Actions: Select: Unselect All....

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All selected objects are unselected.


This operation can be executed also from the object popup menu.
9.1.16 Actions: Close: Item
The purpose of this procedure is to remove the selected object and its opened children from the window.
This operation can be executed also from the object popup menu.
a)

Select (left click) one or more object/s to close.

b)

Select Close: Item.

The selected object/s is/are removed from the screen.


9.1.17 Actions: Close: Item by Class
The purpose of this procedure is to remove from the window the specific child class of the selected object.
This operation can be executed only from the Actions pulldown menu.
a)

Select (left click) one/ more object/s whose child class has to be forgotten.

b)

Make use of the Actions pulldown menu. Select Close: Items by Class.

c)

The child selection window is displayed. One/more child class can be selected (left click).

d)

Pressing the OK button the select classes are removed from the screen.

9.1.18 Actions: Close: All related items


This command removes from the window all displayed children of the selected object.
This operation can be executed also from the object popup menu.
a)

Select (left click) one/more object/s whose related items have to be removed.

b)

Select Action: Close: All related items.

9.1.19 Actions: Align item(s)


The purpose of this procedure is to align the data displayed on the screen to MIB data.

1AA 00014 0004 (9007) A4 ALICE 04.10

This operation can be executed from the object popup menu and the pulldown menu.
a)

Select (left click) one / more object/s to be aligned.

b)

Select Actions: Align item(s) or by using the right mouse button, select Align item(s)

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

97 / 142

This allows to show attributes of an object or modify the value of the simple attributes (Modifiable at UI)
in the MIB data base.
This operation can also be executed by clicking on the Show/Set attributes icon of the icon bar or from
the object popup menu.
a)

Select (left click) the object whose attributes have to be set/shown.

b)

Select Show/Set attributes. A dialog box is presented. It contains the objects attributes.
The attribute that cannot be modified is displayed without any
If the user selects the option Set, will enter the new value in the area of the field (string, integer and
date type) or set the new enumeration value.
If the user selects the option Set to default, the attribute will be set to the default value.

c)

After entering the modifications, select Apply. The attribute will be modified.
The Show/Set dialog box also contains the Cancel button, which causes to abort the procedure and
close the window and the button Help providing the relevant Help information.

9.1.21 Actions: Details: Displayed info...


The purpose of this procedure is to display the information relative to the selected object class.
This operation can also be executed by clicking on the Details on the displayed information icon of the icon
bar or from the object popup menu (Details: Displayed info..).
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)
b)

ED

Select (left click) one/more objects or right mouse...


Select View:Displayed info...
A dialog box is presented. It contains the information relative to class name, color of the icon,
displayed attributes.

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

98 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.1.20 Actions: Details: Show/set attributes

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 68. Actions: Details: Displayed Info.

9.1.22 View:Displayed info....


Same as 9.1.21
9.1.23 View:Report

1AA 00014 0004 (9007) A4 ALICE 04.10

The View:Report item allows to select one of the following submenus:

Report full...

Report full only selected...

Report short...

Report short only selected...

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

99 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 69. View:Report full

ED

Report short...(See Figure 70. )

Report short only selected...

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

100 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 70. View:Report short

9.1.24 Options: Filtered presentation / Not filtered presentation


These options specify if the pulldown Search Related Items action is filtered or not when exists only one
child class.
9.1.24.1 Options:Deferred Operations (only for path and trail)
The purpose of this procedure is to enable the scheduling of the subsequent actions on paths.

1AA 00014 0004 (9007) A4 ALICE 04.10

PROCEDURE
a)

Select Options:Deferred Actions. Select the action to schedule. A dialog box is displayed (lefthand
side of Figure 71. ).

b)
c)
d)

Click on the scrollbar. A selectable list is displayed (rigthhand side of Figure 71. )
Select the time value and click on OK. The selected value is copied into the lefthand side box.
Selecting OK the action on path will be executed at the specified time.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

101 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 71. Options:Deferred Actions

9.1.25 Options: Overlay windows


The purpose of this option is to overlay or not the opened browser windows.
9.1.26 Options: Enable AS link
The purpose of this option is to break off the talking between browser and AS application.
9.1.27 Options: Task bar
The purpose of this option is enable/disable the task bar to contain iconified browser windows. The
following selections are allowed: Vertical / Horizontal / Show / Hide.
On each browser window icon the following popup menu is available:

popup ( or double click ). This menu, if selected, causes the redisplay of the iconified window on
the screen.
popdown. This menu, if selected, iconifies in the browser working area the relevant window.
close. This menu closes the window.

9.1.28 Specific
It contains menus which depends on the selected item (typically specific actions).
9.1.29 Windows

1AA 00014 0004 (9007) A4 ALICE 04.10

It contains the list of opened windows (views and multi column lists). Iconified windows can be deiconified,
deiconified windows can be iconified.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

102 / 142

9.1.30 Tools

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

It allows to open the Active Counters tool. See following figure.

Figure 72. Active Counters tool

9.1.31 Navigations
It allows to open views containing items built after AS navigation and navigation from external tools
(eg: setup trail, path creation). The menu has following submenus:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

from AS. It opens a browser instance containing objects navigated from the Alarm Surveillance
application.
from Others. It opens a browser instance containing objects navigated from the Netview application.

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

103 / 142

The Active Counters feature offers a way to monitor objects that match a given condition (defined on the
objects attributes) and to detect objects matching the condition
A simple but complete GUI allows the user to perform these tasks (creating/modifying/deleting counters
(with their conditions) and monitoring objects) easily and quickly.
9.2.1 Overview
This section briefly describes how Active Counters feature works while illustrating the structure of this document.
Every counter is defined by a name (its identifier), a description (generally longer than the name and useful
to understand/remember the meaning/use of the counter) and a condition.
A counters condition is defined by the class to which is applied (route, high order CTP, TMLSTrail, etc.)
and a list of terms that represents the subconditions to apply to the single attributes of the class elements (see 3.1 Conditions).
In addition to schema classes, metaclasses (see 2 Metaclasses) can be used to define conditions
Given the counters condition, if we define a time origin that we call epoch, at a given time (equal or subsequent to the epoch) we can calculate four values:

the absolute number of objects that match the condition (total)

the number of objects losing the condition since the epoch (out)

the number of objects taking the condition since the epoch (in)

the objects repeatedly losing and taking the condition since the epoch (upsanddowns)

These four values are called subcounters (of the counter) and are the values that the user will monitor.
The Active Counters feature uses as an epoch the time at which the user activated it. While the feature
is active the user can reset the epoch of any of the counters (or all of them) to the current time, so to restart
the count.

1AA 00014 0004 (9007) A4 ALICE 04.10

Counters are fully explained in paragraph Counters.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

104 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.2 Active Counters

9.2.2 Metaclasses

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Metaclasses are virtual groups of classes, in order to handle counters defined on more than one class
Metaclasses have no real disadvantages over multiple classes while having two main advantages:

the logic of the feature is simpler, thus keeping the design simple and, therefore, lowering the cost
of implementation and maintenance;

from a user perspective, conditions that spawns multiple classes behave exactly as singleclass conditions. Moreover the user doesnt need to know whether hes dealing with a single class or a metaclass.

Metaclasses are configured on a per USM machine basis, so they are stored in the file system of the machine that hosts the USM. This means, amongst other things, that, if there is more than one USM machine,
is to the administrator to supply every machine with its own copy of the metaclasses configuration file.
Metaclasses can only be defined/modified/removed by the administrator while other users can only use
them.
In this document we will talk of simple classes when we wish to refer to schema classes, we will talk of
metaclasses when we wish to refer to metaclasses and we will talk of classes referring to both schema
classes and metaclasses.
9.2.2.1 Structure of a metaclass
A metaclass is made of the following components:

name: a string identifier

metaattributes: a set of virtual attributes that group the attributes of the joining classes;

joining classes: a set of simple classes that join the metaclass and, for each simple class, the attributes of that class that join the metaattributes.
A metaclass is subject to the following constraints:

the name of the metaclass must be unique among class name, i.e. it cant have the same name of
an existing simple class or of another metaclass;

1AA 00014 0004 (9007) A4 ALICE 04.10

a metaclass must have at least one metaattribute

two metaattributes (of the same metaclass) cant have the same name: while two metaattributes of
different metaclass can;

only countable simple classes may join metaclasses: metaclasses and noncountable simple
classes cant;

a simple class may join a metaclass almost once

a joining class associates one (and only one) of its attributes to each metaattribute, if a joining class
does not associate any attribute to one or more metaattributes, we say that the joining class does
not handle the metaattribute;

a metaattribute must be supported by at least one joining class

the simple attributes joining a metaattribute must be of compatible, i.e. one of the following condition
must be true:

ED

all joining attributes are of string type

all joining attributes are the same simple attribute

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

105 / 142

As already told, metaclasses have been designed to minimize their impact on design, while needing some
support at implementation level.
In practice, a counter based on a metaclass is implemented creating one counter for each joining class.
Each derived counter has a condition obtained converting the original (meta)condition, in this way:

the class of the derived condition is the joining class

the terms of the derived condition are the original terms, except that:

if the metaattribute of the original condition is handled by the joining class, the attribute of the
derived condition is the joining attribute for that joining class;

if the joining class does not handle the metaattribute of the original condition, the term is not
included in the derived condition.

In spite of all this deriving/translating work, the end user only sees the original counter, while the derived
counters are invisible to him.

9.3 Counters
Every counter is defined by:

a name: a unique string identifier

a description: generally longer than the name and useful for the user to understand/remember the
meaning/use of the counter;

a condition: a counters condition is defined by the class to which is applied (route, high order CTP,
TMLSTrail, etc.) and a list of terms that represents the subconditions to apply to the single attributes of the class elements

Given the counters condition, if we define a time origin that we call epoch, at a given time (equal to the
epoch or after it) we can calculate four values:

the absolute number of objects that match the condition (total)

the number of objects losing the condition since the epoch (out)

the number of objects taking the condition since the epoch (in)

the objects repeatedly losing and taking the condition since the epoch (upsanddowns)

1AA 00014 0004 (9007) A4 ALICE 04.10

These four values are called subcounters (of the counter) and are the values that the user will monitor.
The epoch is the time at which the user activated the Active Counters feature. While the feature is active
the user can reset the epoch of any of the counters (or all of them) to the current time, so to restart the
count.
In addition to the concise view of subcounters, the user can inspect the situation with greater detail displaying the list of the items that are counted by a specific subcounter. These lists are implemented using the
standard Browsers list, with the notable exception of lists opened for counters base on metaclasses. In
this case, in fact, we have implemented a special multilist widget that, visually similar to a standard browsers list, is capable of displaying multiple lists of items in the same window.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

106 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.2.3 How it works

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Active Counters are defined and used on a per user basis, so that every user will have/will be able to create
its own counters independently from other users. Note that different Unix logins, even impersonating the
same operator, are considered different users.
A requirement for Active Counters is persistency for different sessions of the same user.
This current implementation supplies a per USM machine persistency, i.e. the counter definitions are
stored in the file system of the machine that hosts the USM. This means that different machines hosting
the USM will have different counter definitions. Moreover, because of the per user nature of the counters
a unique configuration file in the users configuration directory will store its definitions.
9.3.1 Conditions
A condition is defined by the class to which is applied (route, high order CTP, TMLSTrail, etc.) and a list
of terms that represents the subconditions to apply to the single attributes of the class elements.
Classes that can make part of conditions can either be simple classes or metaclasses. But non all simple
classes can make part of conditions: in fact, not all simple classes are suitable/sensible to be counted (e.g.
classes that are never instantiated, but serves only as base classes to derive from). The subset of countable classes is not configurable by the end user.
The conditions are generic and are based on AND/OR of terms.
A condition is of the form:
(term1 OR term2) AND term3 OR Term4
(term1 OR term2) AND term3 OR Term4...AND termn
where termi (for i=1,...,n) is of the form:
termi = attri opi value

so, termi is true if applying opi to attri and valuei returns true.
Not all attributes of countable classes are allowed to make part of terms, in fact, only enumerated or string
attributes are allowed and only if they are primitive attributes (so IATTR and XATTR are excluded).
For what regards the operators:

if the terms attribute is an enumerated one, the possible operators are: equal and not equal;

if the terms attribute is of string type, the possible operators are: starts with, matches exactly, contains, ends with, doesnt contain and differs from.
Finally the value must be compatible with the attribute, so:

if the attribute is of enumerated type, the value must be one of the enumerated values;

if the attribute if of string type, the value must be a string.

1AA 00014 0004 (9007) A4 ALICE 04.10

9.3.2 NAD
From an NAD point of view, active counters created by a certain user take into account only objects that
such user can access (or at least objects on which it has some visibility). Then:

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

107 / 142

every objects security label is known: i.e. AVC events (and also other events) must bring security
label;

a function that, knowing the users rights, filters incoming events basing on the users access rules.

Currently these two requirements cant be achieved, therefore, at least for this first release, the active
counters feature will behave differently, depending on user type:

for administrators: objects handled by the feature will be all the object accessible by the operator (i.e.
all);

for nonadministrators: each counter will count every object satisfying its condition (also those not
visible/accessible by the user), but only accessible objects will be displayed by lists.

9.3.3 FAD
As for NAD, there is a different access/use of functions whether the operator is an administrator or not:
if the operator is an administrator:

operator will be able to define new metaclasses and/or modify existing ones , to be used by all the
operators;

all the lists opened through the Status Window will update in realtime, thus reflecting the respective
counters status ;

1AA 00014 0004 (9007) A4 ALICE 04.10

if the operator is not an administrator:

operator will be able to use the metaclasses defined by administrators;

any lists opened through the Status Window will not update, unless the user requests a refresh.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

108 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.4 User Interface

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Two windows have been defined to support Active Counters:

the Status window: a flying window that allows the user to display and manage the counters;

the Create/Modify/Show Counter widget: a widget that will allow the user to create, show and/or
modify existing active counters;

the Multilist widget: a modified Browsers list that displays items from different classes.

9.4.1 Monitoring
The Status Window is a standard window provided with its own menu, its own toolbar and the list of active
counters defined by the user.
The user will open the Status Window through the Tools menu of the Browsers main window .
Each counter can be selected by the user to perform a specific action on it. The selection is single, so only
one by one actions can be performed on active counters (e.g. is not possible to delete multiple counters
with a single action).
The counters are presented in a tablelike layout, showing for each active counter the following items:

the Counter name: a user defined label used to identify the counter

the Tot (Total) count: the absolute number of objects that match the condition;

the In count: the number of objects taking the condition from the last reset command;

the Out count: the number of objects losing the condition from the last reset command

the Up&Dw (Upsanddowns) count: the number of objects doubleflipping the condition from the
last reset command.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 73. Browser: Tools: Active Counters

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

109 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 74. Status window

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

110 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

PULLDOWN MENUS

POPUP MENU
Figure 75. Status window menus

1AA 00014 0004 (9007) A4 ALICE 04.10

The monitor window displays all the active counters defined by the user and allows him to:

show an existing counter definition either via the Actions menu (that will show the selected counter),
via the popup menu (that will show the active counter on which the right click has been performed)
or using the toolbar;

modify an existing counter definition either via the Actions menu, via the popup menu or using the
toolbar;

remove an existing active counter either via the Actions menu, via the popup menu or using the toolbar;

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

111 / 142

reset an existing active counter (resetting In, Out and Upsanddowns values) (via the Actions
menu, via the popup menu or using the associated toolbar icon);

reset all existing counters (via the Actions menu, via the popup menu or using the associated toolbar
icon), after a user confirmation;

create a new active counter (via the File menu or using the associated toolbar icon)

counter save (via the File menu or using the associated toolbar icon); If a counter is changed and
the operator doesnt use this save, when he will close the Status Window a popup will point out the
loss of modification if the save is not invoked and the confirm of the exit operation.

show the list of counted items via the Actions/Lists menu, via the Lists submenu of the popup menu
or as follows:

double clicking on the In value will open the list of objects taking the condition of the active
counter from the last reset;

double clicking on the Out value will open the list of objects losing the condition of the active
counter from the last reset;

double clicking on the Tot (Total) value will open the list of objects that match the condition of
the active counter;

double clicking on the Up&Dw (Upsanddowns ) value will open the list of objects doubleflipping the condition of the active counter from the last reset.

The lists opened are not uptodate, they can be uptodate using the refresh function.

1AA 00014 0004 (9007) A4 ALICE 04.10

Even if not shown in the above figures, the columns for the four subcounters have different background
colors, in order to quickly recognize them. In addition, when a subcounter leaves the reset state its cell
is highlighted to capture the attention of the user.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

112 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.5 Definition and Activation


The creation of a new Active Counter is performed from the status window, either choosing New counter
from the File menu or using the proper toolbar icon. The user action will invoke the Create Counter widget.
The approach proposed is the bottomup type and consists to create before the terms of condition and
When opened, the Create Counter form is:

Figure 76. Active Counter Creation window

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

113 / 142

When the class is chosen, more elements of the window are enabled and is possible to create the condition terms.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 77. Entering data in Active Counter Creation window

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

114 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In this form all is disabled but the two text fields (name and description of counter), the option box for the
choice of the class to monitor and the cancel button to annul the counter creation.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 78. Monitored Class selection.

Clicking on Add New, the term creation form is opened:

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

115 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 79. Condition Modification dialog box

Figure 80. Condition Modification: Attribute selection


After attribute selection, the window changes to allow the selection of the operator and the value(s), so
that:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

if the attribute is an enumerated one, an option box with the two foreseen operators (equals, not
equals) is followed by a list box with the attribute possible values:

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

116 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 81. Condition Modification: attribute (enumerated)

if the attribute is of type string, an option box with the string operators (Starts with, Matches exactly,
Contains, Ends with, Doesnt contain and Differs from) is followed by a text box in which the
user will type the string to compare to the attribute:

Figure 82. Condition Modification: attribute modification (label)


When the first term is created, the option box Monitored Class is disabled and it is not possible to change
the class. If all terms are removed the option box is enabled again.

1AA 00014 0004 (9007) A4 ALICE 04.10

Each object on the form has an its specific function:

the list with the multiple selection Subconditions, lists all terms created by user and all partial condition created joining two or more terms;

in every moment, it is possible to create new terms clicking on Add new up to the maximum limit of
six terms;

if a term is selected in Subconditions and you click on Modify, the term modify form is opened.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

117 / 142

if one or more elements (simple terms or partial condition) are selected, it is possible to delete clicking
on Remove (with a confirm by the user);

if two or more elements (simple terms or partial condition) are selected, it is possible aggregate them
using AND Join or OR Join, so a new partial condition with the selected elements joined by AND
or OR (according to the push button selected) is obtained. Moreover, the original elements are eliminated. If, for example, we select the fist two terms and clicking on AND Join we obtain:

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 83. Split button enabled

ED

if one or more elements that represent partial condition are selected, it is possible to decompose
them using the Split button. See above figure. Split cancels the previous aggregation operation. So,
selecting on the first row of the above figure and clicking on Split, the following arises:
01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

118 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

since the partial condition can became long, can be difficult for the user examine a partial condition
only using the Subconditions list, so the last partial condition selected is displayed completely in
Selected subcondition field;

the Overall condition shows as would be the final condition if all partial conditions were aggregated
using the function button (AND or OR) ;

the OK button confirms the counter creation with the condition shown in condition

9.5.1 Modification
The form of counter modification is equal to the creation one but the differences described below:

The form shows counter data (name, description, class and condition);

The class is not modifiable.

Modifications that involve attributes and values (i.e. all except renaming), if successfully completed, reset
the counter (i.e. the Total counter is recomputed and the In, Out and Upsanddowns counters are reset).
To modify the active counter, first select the counter and the issue the Modify popup menu. See
Figure 84. herebelow.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 85. shows the Active Counter Modify window.

Figure 84. Counter: Modify popup menu item

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

119 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 85. Active Counter: Modify

1AA 00014 0004 (9007) A4 ALICE 04.10

9.5.2 Visualization
For the visualization of Active Counters, issue the popup item Show. The same form of modification is
used except that user cannot modify values. See figure which follows.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

120 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 86. Condition Visualization ( Show)

9.5.3 List visualization

1AA 00014 0004 (9007) A4 ALICE 04.10

Lists are displayed using the standard Browsers lists, sole exception are lists for metaclasses that are
displayed using the special Browsers multilists that allow to display multiple list of objects of different
classes into the same window.
The lists opened from Status Window (with double click on the column chosen) have as title the column
name (In, Out, Tot, Up&Dw) followed by the counter name.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

121 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

122 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10 BROWSER: DRAWING WINDOWS


The Browser application includes the possibility to display several drawing windows, which are helpful in
managing the controlled network.

10.1 Introduction
Drawing windows support:

Single/multiple selection operations

Pulldown menu with generic and/or object specific commands

Icon Bar generic commands

Dynamic Icon Bar depending on selected class

Popup menus with generic and/or object specific commands

Help on item (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button/object.

Contextsensitive help. If you select the object and the pulldown menu Help on selected
object, the Worldview application starts and displays automatically the description of the
selected object class.

1AA 00014 0004 (9007) A4 ALICE 04.10

Drawing windows have the following look (see Figure 87. )

ED

window title : 1354RM: Browser

pulldown menu bar. Refer to paragraph 9.1.9 .

Icon bar

title : eg. Physical connection structure

work area: It contains the retrieved objects.

info area (Refer to paragraph 9.1.1 )

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

123 / 142

10.1.1 Icon bar

Close window. It forget the window and all its opened ones. This operation can also be executed
from the pulldown menu (File:Close).

Hide window. It hides the window. It can be redisplay without any reget. This operation can also
be executed from the pulldown menu (File:Popdown).

Go to the parent window. It goes to window from which this one has been opened. The current
drawing is hidden or not, depending the status of Options:Close window going to parent on browser
main window (see paragraph 9.1.27)

Display Main Related Items. It navigates the selected object(s) on browser main window. The
children chooser is automatically proposed (Main related items). This operation can also be executed
by double click on object or from the object popup menu (Search:Main related items)

Show/set attributes. This allows to show attributes of an object or modify the value of the simple
attributes (Modifiable at UI) in the MIB data base. This operation can also be executed from the object
popup menu (Details:show/Set attributes) or from pulldown menu (Actions:Details:show/Set
attributes)

Align items (s). It alignes the data displayed on the screen to MIB data. Almost one object must be
selected. This operation can also be executed from the object popup menu (Display:Align items(s))
or from pulldown menu (Actions::Align item(s))

Refresh this window. It deletes all items and regets all data. Note that all children
views/multicolumns lists are closed.

Order Items. It allows to manage the order and size of the table columns

Sort Items. It allows to set in ascending/descending order the columns.

Hide/Show attribute counter. It allows to display the attribute counters referred to the displayed
list

The second row depends on the specific view. It typically allows to open an application (eg. Setup trail,
Payload configuration, Path/Trail constraints) or views to create instances or to correlate objects to each
others).
The third row depends on selected class. It dynamically shows icons to open view/multicolumn list
associated to selected object.
10.1.2 Work area

1AA 00014 0004 (9007) A4 ALICE 04.10

In the Drawing window, the work area displays the retrieved items typically located on graphic background
to show the relation to each other. Inside the work area are often displayed particularly items (named
group) from which other view/multicolumn lists can be opened).

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

124 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The Icon bar area is subdivided in three rows. The first one contains the following buttons:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11 BROWSER MULTICOLUMN WINDOWS


The Browser application includes the possibility to display several multicolumn lists, which can be iconified
to the main Browser window.

11.1 Introduction
Multicolumn lists windows support:

popup menu, which can be opened from the sinle row

Single/multiple selection operations

Pulldown menu with generic and/or object specific commands

Icon Bar generic commands

Dynamic Icon Bar depending on selected class

Help on icons (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button

Contextsensitive help. If you select the object and the pulldown menu Help on selected
object, the Worldview application starts and displays automatically the description of the
selected object class

Statistical counters related to displayed attributes

Counters graphs which displays the changes of some attributes value

1AA 00014 0004 (9007) A4 ALICE 04.10

Multicolumn lists windows have the following look (see Figure 88. on page 128 )

ED

window title : it is composed by parent class and name of list

pulldown menu bar

Icon bar

Title area

Counters area

work area: It contains the retrieved objects.

info area (Refer to paragraph 9.1.1 ).

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

125 / 142

11.1.1 Pulldown menu

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The following pulldown menu item is available:


File
Actions
View
Options
Windows
Help

The menu File allows to further select among:

Save all as. This command saves the lists content on specified file

Save selected as. This command saves the selected items on specified file

Print all. This command prints all lists content

Print selected. This command prints the selected lists content

Views: Save. It allows to save the view. To redisplay the saved view, issue from the task bar
the menu Saved Views selecting the desired view from the item list.

Hide. This command hides the multicolumn list window

Close. This command closes the multicolumn list window. The group icon displayed on Browser
main disappears, the one displayed on drawing window change its colour.

The menu Actions allows to further select among:

a menu common to all lists: (path list, nap list...):

Search
Select
Details
Align item(s)
Align view
Remove from RM

a menu of Actions specific to the object class being retrieved.

1AA 00014 0004 (9007) A4 ALICE 04.10

The menu View allows to further select among:

ED

Columns.This option allows to perform a column reordering. If you select this option, a column
reordering window is presented, containing the fields which allow to move the columns, perform
text string justification and change the column width. After executing the changes you can select
Apply, to apply the changes to the list, OK to apply the changes while closing the column
reordering window or Cancel, to close the window without any change.

Sorting. This option allows to perform a list sorting. If you select this option, the Sorting window
is displayed, containing the fields Priority and Condition.The priority field allows to assign a
sorting priority among the object attributes. The field Condition allows to assign an increasing
or decreasing sorting condition. After executing the changes you can select Apply, to apply the
changes to the list, OK to apply the changes while closing the sorting window or Cancel, to close
the window without any change.

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

126 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Report. For Path/Trail is available the Report: Route and the command file generator used to
save the list of path/trail that can be reused to rebuild the circuit.

11.1.2 Icon bar


The Icon bar area is subdivided in three rows. The first one contains the following buttons:

Close window. see description of menu File:Close in paragraph 11.1.1

Hide window. see description of menu File:Hide in paragraph 15.1.1

Go to the parent window. It goes to window from which this one has been opened. The current
multicolumn lists window is hidden or not, depending the status of Options:Close window going to
parent on browser main window (see paragraph 13.1.28)

Display related items. It navigates the selected object(s) on browser main window. The children
chooser is automatically proposed (Main related items). This operation can also be executed from
pulldown menu (Actions:Search:Main related items)

Display Parent item. It navigates the selected object(s) on browser main window.

Show/set attributes. This allows to show attributes of an object or modify the value of the simple
attributes (Modifiable at UI) in the MIB data base. This operation can also be executed from the
pulldownmenu (Actions:Details:show/Set attributes)

Align items (s). It alignes the data displayed on the screen to MIB data. Almost one object must be
selected. This operation can also be executed from the pulldown menu (Actions:Align item(s))

Change filter criteria. It allows to change the filter criteria and retrieve again the list using the new
criteria

Refresh window. It deletes all items and regets all data. Note that all children views/multicolumns
lists are closed. This operation can also be executed from the pull down menu(Actions:Align view)

Ordering items. see description of View:Columns menu in paragraph 15.1.1

Sorting items. see description of View:Sorting menu in paragraph 15.1.1

Hide/Show counters. It hides/shows the counters displayed in counters area.

The second row depends on the specific multicolumn list. It typically allows to open external
application (eg. Setup trail, Payload configuration, Path/Trail constraints) or views to create
particularly instances or to correlate objects to each others).

The third row depends on selected class. It dynamically shows icons to open view/multicolumn list
associated to selected object.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

127 / 142

It contains icons related to parent class and the displayed class (with their names), the title of list, the total
number of displayed items and the number of selected ones.
11.1.4 Counters area
It contains counters related to most significant attributes with their values. To change displayed attributes
please open Ordering items window.
11.1.5 Work area
In the multicolumn list window, the work area displays the retrieved items in according to selected order
and sorting criteria, and to specified filter criteria (if any).

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 88. Example of Multicolumn window


The associated group icon is displayed under the parent object in the Browser Main window or inside the
drawing windows. On group icon a popupmenu allows to iconify/deiconify/close the associated list. When
lists has been opened from other list, the group icon is not displayed but the related item in Windows menu
is present to iconify/deiconify list.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

128 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.1.3 Title area

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Double clicking on the single row, the relevant browser window is opened.
On the selected object it is also possible to start all the objects specific actions (e.g. for Path:
Allocate/Implement, Protect/ Unprotect, Delete, ect...)
11.1.6 Counters and graphs on Browser MultiColumn Lists
A dedicated button is available (see Figure 88. on page 128 ).
Clicking on Hide/Show counters, defined counters are displayed. For each displayed attribute a set of
counters is presented.
11.1.7 Multicolumn list window configuration
11.1.7.1 Ordering items
Open the relevant view following procedure described in paragraph 11.1.1 or paragraph 11.1.2

Figure 89. Ordering items

1AA 00014 0004 (9007) A4 ALICE 04.10

The view contains in the upper area an option button that allows to read/save user configuration file (active
after Apply button pressing)

ED

User defaults. Reads saved user configuration file


Save user default. Saves the user configuration file
User default from. Reads the specified user configuration file
Save user default as. Saves the specified user configuration file

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

129 / 142

The scale Fixed columns allows to set the number of fixed columns on multicolumn (to have partial
horizontal scrolling)
The Multicolumn counters and Browser counters buttons allow to display/hide specified counters on
multicolumn or browser
For each attibute of displayed class, it is possible to define the position (to hide attribute choose Ignore),
the justify and the displayed size of name (width).
To change the list, press OK button (the interface will be closed) or Apply button, to abort press Cancel
11.1.7.2 Sorting items
Open the relevant view following procedure described in paragraph 11.1.1 or paragraph 11.1.2.

Figure 90. Sorting items


The upper area has already been described in paragraph 11.1.7.1.

1AA 00014 0004 (9007) A4 ALICE 04.10

For each attibute of displayed class, it is possible to define the priority used in sort (Ignore value doesnt
take in account the attribute) and the Condition (Ascending or Descending)
To change the list, press OK button (the interface will be closed) or Apply button, to abort press Cancel

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

130 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The button System default read the system configuration file.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.2 Available Lists


All lists have the same look already described. Main differences among list are the dynamic Action menu
(depending on retrieved class) and the specific toolbar (second row inside the icon bar area).
Possible getting multicolumn windows are following lists:

All nodes
available from Root Domain (for MultiRM), Network Domain, Network, Subnetwork

Trails at all sublevels


available from Network, Subnetwork, ET

Used defined HOTRAIL at all sublevels


available from Network, Subnetwork, ET

All physical connection in network

Ports
available from ne

SDH Ports
available from ne

PDH Ports
available from ne

Payloadable HOTTP
available from node

CTPs
available from node

High Order CTPs


available from node

Low Order CTPs


available from node

Client Link Connection


available from trail

Measures
available from pm domain

Monitored NEs
available from pm domain

TCA profiles
available from pm domain

Counter reports
available from pm domain

Threshold reports
available from pm domain

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

131 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

Archive session
available from pm domain

PM Transports
available from measure

Paths in Topology
available from root domain, network domain, network, subnetwork, et, node

Alarmed objects
available from network, subnetwork, et, node

Paths in Topology (with Source/Sink)


available from network, subnetwork, et, node

Paths starting(ending) from (in) node

HO Trail starting(ending) from (in) node

Ports in node

Paths starting(ending) from (in) node (with Source/Sink)

Naps (with Path label)


available from node

monitoring Measures
available from path, trail

Alarms in route
available from path, trail

LCs in routing link


available from routing link.

Paths in physical connection

HO Trail
available from physical connection

Link Connection in physical connection

Active paths in physical connection

Paths in physical connection (with Source/Sink)

Active paths in physical connection (with Source/Sink)

Path in Trail

Path at the same layer


available from link connection

Path at the same layer (with Source/Sink)


available from link connection

ED

01

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SC.2:GETTING STARTED
3AL 61348 AA AA
142

132 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Counter reports
available from measure

Related NE
available from pm NE

Restoration rule
available from restoration Domain

Asap correlated objects


available from restoration Domain

Eml domain
available from network Domain

Related NE
available from Eml Domain

NMLEML misaligned objects


available from Network, Subnetwork, ET, Node.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

133 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

134 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

12 BROWSER: LOCATE ITEMS IN NETVIEW


12.1 Locate topological objects on Map
It is possible to locate toplogical objects from browser to Netview. In the following an example of locating
a node is given.
a)

From the Node list ( see Figure 91. ) select the node and click on Navigation button. The Node icon
is displayed in the Browser main window. ( already selected ).

HIGHLIGHT BUTTON

Figure 91. Node list.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

With the node already selected click on button Highlight ( see NO TAG). The node is highlighted in
the Netview submaps as in Figure 92.

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

135 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 92. Highlighted node in Netview.

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

136 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

13 ZERO INSTALLATION READ ONLY BROWSER


The Zero installation browser is a new Java based GUI that enables the user to browse all information
inside the RM MIB. The application uses the same views of the unix browser (same displaying characteristics e.g. the objects and attributes are displayed using the same icons & colors). The application can be
started using both Internet Explorer and Netscape.
All views are sensitive to IM events except for the cases listed in the Restrictions section.
All RM unix browser Navigations are available except the following (that will be available in the next release):

Topology views

Navigations towards external applications

Routing displays of transport entities

The navigations cannot be filtered.

13.1 Application Requirements & Download


The applications can be started using either Internet Explorer or Netscape configured with the Java Sun
plugin 1.4.x. To test if your Internet browser is configured properly please use the following link
http://www.java.com/en/download/help/testvm.jsp. The JRE Version displayed should be 1.4.x. If the
JRE version is less than 1.4.x or the JRE is not installed please follow the instructions at the bottom of the
page to download and install the plugin.

1AA 00014 0004 (9007) A4 ALICE 04.10

Once the correct plugin is installed, you can load the application pointing your browser to the following
URL http://hostname:10 where hostname is the name of the 1354 RM server or alternatively its IP number.
When the Java applet has been completely loaded a security warning appears asking to acknowledge the
necessary permission to the application.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

137 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 93. Application warning

1AA 00014 0004 (9007) A4 ALICE 04.10

Clicking yes the application starts and shows an input box asking for username and password to login.
Please insert a username and password registered in the 1354 RM server. If the login is accepted you
should see in the application client area, a window with the server you are connecting to. Right clicking
on this server will present you all the possible starting navigations inside the RM MIB.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

138 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 94. Login window

ED

01

SC.2:GETTING STARTED

3AL 61348 AA AA

142

139 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The navigation mechanism is quite similar to the unix browsers one. Starting from one of the displayed
views, the element to browse must be selected. Clicking the right mouse button, a popup menu appears
containing all possible navigation that can be required to RM Server. Selecting a navigation, after a while
(there is a progress bar in the right bottom corner of the applet), the new requested view is opened.
The browsed objects and the related (performed) navigations are inserted in the application tree (on the
left side of the applet).

13.3 Print and Export table view data


Data displayed inside table views can be printed using a local printer.
Data can also be exported in the following formats:

PDF

Excel

CSV

1AA 00014 0004 (9007) A4 ALICE 04.10

13.4 Restrictions

There are the following restrictions on the events management:

the create and delete events are not yet managed

the attribute icons of the graphic views are not yet updated

Views cannot be refreshed.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

140 / 142

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

13.2 RM MIB Browsing

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

14 ONLINE DOCUMENTATION
14.1 Overview
The help is based on world wide web technologies. The topics are written in html. Netscape Gold is the
browser used to navigate through the html pages and it is also used to edit the user personal pages.
Navigation through the help is also possible using a customized navigation bar permanently displayed in
the left of the help screen

The menu options are in fact entry points to the main help system. Once you have entered the help system
via one of these menu options, hyperlinks enable you to navigate to other parts of the help system and
to view other help topics.

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

141 / 142

INDEX

Browser Main, 85
Buttons
Push buttons, 22
Radio buttons, 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Actions, 18, 19
Buttons, 18
Pointer, 18
Multicolumn Windows, 125, 135

N
Navigation to/from, Alarms, 52

C
Cascading menus, 27

P
Path List, 131
Popup menus, 27
Pull down menus, 26

D
Drawing Windows, 123

List dialogue boxes, 32


Login, 45
Logout, Front panel, 48

Screen, Lock, 47
SDH Manager, Main functionalities, 49

U
M
Upper case/Lower case characters, 31
User Interface, Standard elements, 17

Menu bar, 25
Menus
Cascading menu, 27
item, 28
Menu bar, 25
Mnemonics, 29
Popup menu, 27
Pull down menu, 26
Mnemonics, 29
Mouse

W
Windows
Layout, 20
Menu, 21
Scroll bars, 21
Workspace, Types of, 46

1AA 00014 0004 (9007) A4 ALICE 04.10

END OF DOCUMENT

ED

01

SC.2:GETTING STARTED
3AL 61348 AA AA
142

142 / 142

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM REL.7.2 OPERATORS HANDBOOK

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Interrelationships with 1353NM during Network Construction . . . . . . . . . . . . . . . . . . . . .
1.5 System Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9
9
9
9
12
12

2 NETWORK CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Network Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Start the Netview application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Save Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Create the network objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 Creating the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 Creating the Subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3 Creating the 2nd level Subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.4 Creating Nodes and ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 External Network Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Create the External Network Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Create Connection to External network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Create Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.1 Example of SDH create connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6 Introduction to NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.1 Topology definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.2 Network Protection Architecture Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.3 NPA display & Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.4 NPA modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.5 NPA Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.6 NPA: Specify Ring Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.7 NPA Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7 Create a 4F STM16 NPE Ring with 1664SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.1 Creating the Connections between Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8 Takeover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9 Create a 4Fibre STM64 NPE Ring with 1670SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13
13
14
14
16
16
18
20
22
27
27
27
30
35
40
40
41
51
57
59
61
62
63
63
64
65

01

050207

ED

DATE

CHANGE NOTE

M.RAGNI ITAVE

V.PORRO ITAVE

APPRAISAL AUTHORITY

ORIGINATOR

1354RM REL.7.2
OPERATORS HANDBOOK

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

1 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

67
68
68
68
69
70
70
70
70
72
78
79
84
86
86
88
88
90
90
92
93
95
95
95
103
107

3 TRANSPORT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Path Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Path Create management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Path Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 10/100Mbits Ethernet management (point to point) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 Multi Path Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.5 Path Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 1 Gigabit path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 1 Gigabit transparent path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 1 Gbit/s Ethernet Rate Adaptive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 LCAS Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Path creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Optimized diverse routing of server trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Path removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4 Add/remove bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.5 Activation/deactivation of an intermediate server trail . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.6 LCAS enabling/disabling on an already defined path . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Compatibility tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1 Path creation using 16xGbE boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2 Rate adaptive path : Modification: Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3 Path: Ethernet mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Path Allocate,Implement, Commissioning and Display . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.1 Path Allocate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.2 Path Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.3 Path Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

109
109
109
112
112
122
124
125
126
127
127
132
135
135
137
138
138
138
138
141
148
149
156
157
157
158
158

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

2 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.10 Takeover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2.11 Setting up linear MSP in Q3 NEs with RM/NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.1 Linear 1+1 MSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.2 Linear 1:1 MSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.3 Alarm Behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12 Upload Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.1 JO SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.2 Upload Physical Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.3 Upload of Protection Schema (MSP linear) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.13 Move node from/to RM topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.14 Internal Physical Connection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.15 2Mb/s retiming management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.16 Network implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.17 Payload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.17.1 Configuring the Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.17.2 Payload Configuration monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.17.3 Payload Configuration supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.18 AU4 Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.18.1 AU4 Concatenation SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.18.2 AU4 Concatenation Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.18.3 AU4 Concatenation Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.19 Trail Creation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.19.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.19.2 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.20 Upload NAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.21 Takeover of retiming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

159
167
169
173
177
178
180
180
185
190
191
192
192
196
204
204
206
209
209
213
215
215
218
221
221
230
231
231
231
232
233
233
233
237
237
238
239
239

4 NETWORK MODIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Adding a Network Element in a SCNP network, case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Adding a Network Element (NE) to a SNCP ring case 2 . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 Removing a Network Element (NE) from a SNCP ring . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.4 Add Q3 NE to a 2F MS Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.5 Add QB3 STAR NE to 2F MS Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.6 Remove Q3 NE / Remove QB3 STAR NE from a 2F MS Spring . . . . . . . . . . . . . . . . . .
4.1.7 Add NE to a 4Fiber NPE ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.8 Remove NE from a 4Fiber NPE ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Add/Remove Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Remove a PDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Removing an SDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Adding a PDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 Adding an SDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

241
241
242
243
244
244
245
246
247
247
249
249
249
249
249

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.6.4 Displaying the path route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


3.7 Service state modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8 Path /TrailConstraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9 Adding /Removing a leg to a path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10 Path in NPE ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10.1 Examples of path crossing mixed rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11 Drop and Continue path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11.1 4Node Drop and Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11.2 D & C path in a 2Node SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11.3 Path Constraints in a 2Node SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11.4 D & C path in a 1Node Enhanced SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11.5 D & C path create in a 2Node SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11.6 D & C path allocate in a 2Node SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.12 Add / Remove Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.13 OS driven restoration for HO paths & trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.13.1 Create a restoration rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.13.2 Display a restoration rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.14 Join/Split Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.14.1 Join Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.14.2 Split path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.15 JoinSplit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.15.1 Split a HOTrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.15.2 Join two HOTrails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.16 JoinSplit Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.16.1 Split Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.16.2 Join physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.16.3 Fail to join working state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.16.4 Fail to split working state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.16.5 Fail to disconnect working state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.16.6 Fail to connect working state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.17 ISDN primary access management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.17.2 ISDNPRA Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.18 4 x ANY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.18.2 Upload of the Data ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.18.3 Create Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.18.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

3 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

251
251
251

5 EXPORT OF RESOURCES ON ISN INTERFACE FOR 1355VPN . . . . . . . . . . . . . . . . . . . . . . . . .


5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Adding a VPN initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 Add Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.3 VPN assignment of the end points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.4 Assignment of the link connection within an RM domain . . . . . . . . . . . . . . . . . . . . . . . . . .

253
253
254
255
256
257

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

258

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

4 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.3 Configuration of a Transmux board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


4.3.1 Payload Structure Configuration of a Transmux board . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Payload Structure Remove of a Transmux board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LIST OF FIGURES AND TABLES


FIGURES
Figure 1. Netview domain submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Add background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Create Network dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Create: Network popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Network Domain submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Create: Subnetwork. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Create 1st lev. Subnetwork dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Network map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Subnetwork: Create: 2nd level Subnetwork popup menu . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Create 2nd level Subnetwork dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. New Object Holding Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Objects belonging to a subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Subnetwork: Actions: Create: Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Node creation wizard: step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Node creation wizard: step 1: NE selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Node just created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Node drag to the working area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. External Network Creation wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Create Connection step 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Create Connection step2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Physical Connection: Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Actions: Create: Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Create Connectionstep 1Type SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Create Connectionstep 1Type WDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Create Connectionstep 1Type SDHCBR/WDM interworking . . . . . . . . . . . . . . . . . . . .
Figure 26. Create Connectionstep 1Type Generic Digital Client/WDM interworking . . . . . . . . . .
Figure 27. Create Connectionstep 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Port selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Physical Connection Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Physical Connection: Configuration: Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Physical connection structure implemented. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Actions: Create: Npa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Create: Npa: Step 1: SNCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Create: Npa: Step 1: 1 + 1 protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Create: Npa: Step 1: 1 to N protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Create: Npa: Step 1: ASON protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Create: Npa: Step 1: NPOS protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Selection of the Physical connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. 1 to N NPA: physical connection selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Network: Display: All Related Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Item selection: NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. NPA list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. 2F MS Spring NPA view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. 4F MS Spring NPA view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. 1 to 1 protection NPA view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. NPA: Actions: Configuration: Modify NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. NPA: Modify: step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. NPA: Modify: step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. NPA: Actions: Configuration: Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. NPA: Specify ring map: step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 51. NPA: Specify ring map: step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

14
15
16
17
17
18
19
19
20
21
21
22
23
24
25
26
26
27
28
28
29
30
31
32
33
34
35
36
37
38
39
42
44
45
45
46
46
47
48
51
52
52
54
55
56
57
58
59
60
61
62

SC.3:OPERATION
3AL 61348 AA AA
258

5 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

63
65
66
67
71
72
73
74
74
75
75
76
76
77
77
80
81
82
83
85
86
87
88
90
90
91
91
92
93
93
95
96
98
99
100
101
102
103
104
105
105
106
110
111
113
114
114
115
116
116
117
118
119
120
122

SC.3:OPERATION
3AL 61348 AA AA
258

6 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 52. Physical view of the aggregates of 1664SMNPE ( from 1353NM ) . . . . . . . . . . . . . . . . .


Figure 53. Example of NPE ring with 1670SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. 1670SM equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. 4Fibre NPE ring 1353NM main dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. Upload Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. Node: Modification: Move Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. Move dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. Network Domain map opened in selection modality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. Network map opened in selection modality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. 2nd level subnetwork map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. Selection of the Destination topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. Move dialog box: command launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. Moved node in the New Object holding area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. Destination submap after the move operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. Multiple move operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. Path: Configuration: 2Mbit/s Retiming management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. Path Retiming; step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. Path: retiming: port selectionstep 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. Port: Retiming state=enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. All Protection Blocks in MSSPRING 4 F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. Payload Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 73. Payload Configuration dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 74. Physical connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 75. Physical Conn.:display related items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 76. Selection of the Physical Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 77. Physical Connection Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 78. MS trail: AU4 concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 79. Payload configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 80. MS Trail Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 81. AU4 Concatenation Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 82. Actions: Create: Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 83. Setup Trail: step 1: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 84. Setup Trail: step 1: Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 85. Setup Trail: step 1: Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 86. Trail Creation wizard step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 87. Trail structure: warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 88. Trail structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 89. Topological object: Configuration: Upload NAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 90. NAP upload monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 91. Node: Search: Main related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 92. Selection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 93. NAP list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 94. Actions: Create: Path pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 95. Node: Create: Path popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 96. Path Create step1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 97. Service type PDH: Service rate selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 98. Service type DATA: Service rate selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 99. Path type selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 100. Path SNCP type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 101. Protection selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 102. MS Protection Usage Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 103. Path Create: step2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 104. Example of NAP selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 105. Path Create: step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 106. Path just created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 107. Fast Ethernet board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123


Figure 108. Fast Ethernet board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 109. Fast Ethernet board: Port view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 110. Objects on browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 111. Multiple path creation button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 112. Multi path creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 113. 1 Gigabit connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 114. GB Eth path create step1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 115. Path create step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 116. 1 Gigabit path routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 117. Trail list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 118. Path: Modify Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 119. 1 Gbit/s Ethernet Rate Adaptive path attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 120. 1 Gbit/s Ethernet Rate Adaptive path routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 121. 1 Gbit/s Ethernet Rate Adaptive path trail list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 122. Server trail routing modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 123. Path create:ethadapt:es:step 3: LCAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 124. Path: Modification: Lcas control menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 125. Path: Modification: Lcas control dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 126. Modification: Bandwidth: Increase bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 127. Action report: Increase bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 128. Display server trails button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 129. Server trail list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 130. Modification: Bandwidth: Activate Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 131. Modification: Bandwidth: Deactivate Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 132. GFP Protocol Modification wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 133. Path list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 134. Route report example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 135. Actual route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 136. Path Routing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 137. Highlight button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 138. Symbols used by Hyghlight feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 139. Path Locate button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 140. Example of Path locate on subnetwork map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Figure 141. Example of protected Path locate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 142. Locate path: protected on the same link group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 143. Service State Modification box and dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 144. Path Constraints dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 145. CTP as constraint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 146. Use Service Forward/Backward for Dual Node SNCP network . . . . . . . . . . . . . . . . . . . . 172
Figure 147. Add Leg menu item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 148. Add Leg dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 149. Drag from browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 150. Add Leg button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 151. Routing display of a broadcast path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Figure 152. Bidir. Path, 1664SM, RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 153. Bidir path, 1670SM, RIW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 154. Drop and Continue D/C W INS W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 155. Drop and Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Figure 156. Drop and Continue 1st failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 157. Drop and Continue 2nd failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 158. Network submaps of the 3 2nd level subnetworks (ET1 , ET2, ET3) for 2 Node D & C .
185
Figure 159. Example Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Figure 160. Routing view for 2N D & C path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

7 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

188
189
190
191
192
193
194
196
197
198
199
200
201
202
204
205
206
207
208
209
210
210
211
211
212
212
213
214
214
215
216
216
217
219
220
222
223
224
224
225
226
227
228
230
231
233
234
235
236
239
242
243

SC.3:OPERATION
3AL 61348 AA AA
258

8 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 161. Status switch subwindows for 2N D & C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 162. Main route connection view detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 163. CTP name detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 164. Use Service Forward/Backward for Dual Node SNCP network . . . . . . . . . . . . . . . . . . . .
Figure 165. Double failure for a SNCP path (w/o enhanced) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 166. Path routing view ( one node D & C ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 167. Enhanced SNCPone node connection detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 168. Add/Remove Protection Tool button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 169. Add/Remove Protection wizard step1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 170. Add/Remove Protection wizard step 2: selection of the switch . . . . . . . . . . . . . . . . . . . .
Figure 171. Add/Remove Protection wizard step 2: switches selected . . . . . . . . . . . . . . . . . . . . . . . .
Figure 172. Add/Remove Protection report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 173. Path routing view after protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 174. Path routing report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 175. Restoration:Create Restoration Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 176. Create: Restoration Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 177. Browser: restoration domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 178. Restoration Rule list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 179. Restoration Rule attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 180. Rings to be merged. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 181. Submaps of ET Meshed and ET_2F_QB3* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 182. Path List containing paths P1 and P2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 183. P2+P3 Join path pulldown menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 184. Join path dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 185. Joint Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 186. Path list after join operation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 187. Actions: Manage path: Split path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 188. Split path dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 189. Node selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 190. Trail: Modification: Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 191. Split trail dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 192. Common node selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 193. Split trail report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 194. Actions: Modifications: Join. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 195. Trail: Modification: Join dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 196. Topology Management popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 197. Split wizard: step1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 198. Node list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 199. Node inserted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 200. Step 2. First port to use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 201. Port list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 202. Step 2. First port to use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 203. Split connection summary dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 204. Join Physical Connections dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 205. Join Physical Connection report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 206. Path: Alarms: Operations: On Clients: PDH framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 207. ISDNPRA step 1 dialog box ( alarm monitoring type) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 208. ISDNPRA step 2 dialog box (Port role assignment) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 209. ISDNPRA: NT Ports selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 210. Ports in node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 211. Adding a new Network Element, case 1CONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 212. Adding a new Network Element to a SNCP ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1 INTRODUCTION
1.1 Purpose of the document
This document describes al the procedures usually executed by the operator. It refers to a no faults
environment.

1.2 Target audience


This document is intended for people who are in charge of the construction of the network.
The documents that should be read before starting this document are:

1353NM Operators Handbook

Regional Manager Introduction Manual

Regional Manager Getting started Manual

1.3 Document description


This section covers the following topics:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

NETWORK CREATE

Introduction

Network Construction

Start the Netview application

Create the network objects

External Network Reference

Create Connection

Introduction to NPA

Network Protection Architecture Create

NPA display & Views

NPA modify

Create a 4F STM16 NPE Ring with 1664SM

Takeover procedure

Create a 4Fibre STM64 NPE Ring with 1670SM

Takeover procedure

Setting up linear MSP in Q3 NEs with RM/NM

Upload Connectivity
01

SC.3:OPERATION
3AL 61348 AA AA
258

9 / 258

MOVE NODE

Internal Physical Connection Management

2Mb/s retiming management

NETWORK IMPLEMENTATION

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Network implementation

CONFIGURATION

Payload Configuration

AU4 Concatenation

Trail Creation Wizard

Upload NAPs

Takeover of retiming

TRANSPORT MANAGEMENT

Introduction

Path Provisioning

Path Create management

1 Gigabit path

LCAS Management

Compatibility tables

Rate adaptive path : Modification: Bandwidth

Path Allocate,Implement, Commissioning and Display

Service state modification

Path /Trail Constraints

Adding /Removing a leg to a path

Path in NPE ring

Drop and Continue path

Add / Remove Protection

OS driven restoration for HO paths & trails

Join/Split Path

JoinSplit Trail

JoinSplit Physical Connection

01

SC.3:OPERATION
3AL 61348 AA AA
258

10 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ISDN primary access management

4 x ANY

NETWORK MODIFICATIONS

Introduction

Add/Remove Tributary Board

Configuration of a Transmux board

EXPORT OF RESOURCES ON ISN INTERFACE FOR 1355VPN

Introduction

The paragraphs which follow briefly describe the Interrelationships with 1353NM during Network
Construction and System startup.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

11 / 258

This paragraph summarizes the macroactivities to be executed at NM and RM side during Network
Construction. The detailed description of the operations to be carried out at NM side is contained in the
1353NM Operators Handbook, while the paragraphs which follow describe the operations at RM side.
The macroactivities to be executed at NM and RM side are:

On 1353NM: Create Map

On 1353NM: Create NE Directory: Create NE. The NE which has been just created appears
browncolored in the map window

On 1353NM: Select the NE and then NE: NE Address

On 1353NM: Select the NE and Start: Supervision: Align Up. The NE is uploaded and assumes the
alarm synthesis color in the map. Check the uploaded hardware with Supervision: Show Equipment.
If needed, complete the hardware provisioning ( command Equipment:Board: Set Board )

On 1353NM: Select : OS : Process Monitoring.

On 1353NM: Execute Stop and Start of the emlim processes.

On 1354RM: the EML identifiers are automatically created in the RM.

On 1354RM: create the data base. See chapter NETWORK

CONFIGURATION.

1AA 00014 0004 (9007) A4 ALICE 04.10

1.5 System Startup


a)

Execute a login by entering username and password.

b)

Select TMNOS Manager icon from the horizontal palette: the TMNOS window opens.

c)

Select the RM icon, then menu OS: Start System.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

12 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1.4 Interrelationships with 1353NM during Network Construction

2 NETWORK CONFIGURATION

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The main procedures described in this Chapter are:

Network Construction

Payload Configuration

Upload NAPs

2.1 Network Construction


It is assumed that the controlled network has been correctly installed and tested and the 1354RM has been
properly installed.
The network construction consists in representing the whole managed network with the necessary
submaps and creating all the required objects in the RMMIB data bases.
The macroactivities are:

Create the network objects

Implement the network.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

13 / 258

a)

Start the Netview application. From the browser point to the Network domain icon and issue the
popup menu Search: Related Items. Select Network Map. The Netview opens.

Figure 1. Netview domain submap

2.2.1 Save Background

1AA 00014 0004 (9007) A4 ALICE 04.10

For each submap you can add a background. Select Save Background, select the suitable background
and click on OK.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

14 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.2 Start the Netview application

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SELECT BACKGROUND

SAVE

BACKGROUND

Figure 2. Add background

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

15 / 258

During this activity, the operator has to create all the submaps according to the network partitioning levels
and insert inside them all the objects (network, subnetworks, 2nd level subnetworks, nodes, ports and connections).
The following steps have to be executed:
2.3.1 Creating the Network
SEQUENCE
a)

From browser, point to the 1354RM network domain and issue the Create: Network popup menu.
See Figure 4. on page 17

b)

In the Create dialog box enter the Network name and click on Create button. See Figure 3. The Network icon appears in the New Object Holding Area. Drag ( holding the middle mouse button) the icon
into the window.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 3. Create Network dialog box.


N.B.

Many networks can be created. It is not possible to interconnect the networks to each other

N.B.

Alternatively, from browser, point to the 1354RM network domain and issue the Create: Network popup menu. See Figure 4. on page 17

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

16 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.3 Create the network objects

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 4. Create: Network popup menu

Figure 5. Network Domain submap

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

17 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.3.2 Creating the Subnetwork

a)

The subnetwork objects are created in the Network submap pointing to the network icon and issuing
the Create: Subnetwork popup menu.

b)

In the Create:Subnetwork dialog box ( see Figure 7. ) enter the Subnetwork name and click on Create
button. The Subnetwork icon appears in the New Object Holding Area

c)

Drag the icon to the window work area. See Figure 8.

N.B.

Alternatively, from browser, point to the network icon and issue the Create: Subnetwork popup
menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 6. Create: Subnetwork.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

18 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 7. Create 1st lev. Subnetwork dialog box.

Figure 8. Network map

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

19 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.3.3 Creating the 2nd level Subnetwork

a)

The 2nd level Subnetwork objects are created in a Subnetwork submap pointing to the subnetwork
icon and issuing the Create: 2nd level Subnetwork popup menu. See below figure.

Figure 9. Subnetwork: Create: 2nd level Subnetwork popup menu

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

The Create dialog box is presented. See Figure 10. Enter the following values:

name

comments (if any)

01

SC.3:OPERATION
3AL 61348 AA AA
258

20 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 10. Create 2nd level Subnetwork dialog box.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

Click on Create button. The 2nd level Subnetwork icon appears in the New Object Holding Area

Figure 11. New Object Holding Area

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

21 / 258

Drag the icon to the center of the window. See following figure. Double click on the icon to open the
submap.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

c)

Figure 12. Objects belonging to a subnetwork

2.3.4 Creating Nodes and ports


SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

The Node object is the representation of the network element in the 1354RM map. A node can be inserted
either in the Subnetwork submap or in the 2nd level submap.
a)

ED

Select the Subnetwork or the ET where the new node has to be inserted and issue the menu Actions:
Create: Node. See Figure 13. The Node Creation wizard is displayed. See Figure 14. Notice that
NAP automatic upload is the default.

01

SC.3:OPERATION
3AL 61348 AA AA
258

22 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 13. Subnetwork: Actions: Create: Node

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

23 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 14. Node creation wizard: step 1


b)

Click on NE list button. The list of the available NEs is displayed. Select the NE and click on Apply
button. The selected NE icon is now present in the list of the wizard.

c)

Click on Finish button to confirm the node creation.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

24 / 258

available NE list

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

NE list button

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 15. Node creation wizard: step 1: NE selection.

the NE is pasted to the map in the new object holding area( See Figure 16. ) and its related node is
created in the data base. At this time NE SDH ports are automatically uploaded from the controlled network.

d)

Drag the node/s just created to the map working area. See Figure 17. on page 26

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

25 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

map working area

new object
holding area

Figure 16. Node just created

Figure 17. Node drag to the working area.

SC.3:OPERATION

3AL 61348 AA AA

258

26 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.4 External Network Reference


External Networks are used to describe a connection between various 1354RMs or to create a path terminated to a node non controlled by 1354RM. A path is defined as non terminated if either one of the NAPs
or both are not in the 1354RM domain. A nonterminated path describes a path between a Trail Termination Point (TTP) associated to a PDH port and a Connection Termination Point ( CTP).
2.4.1 Create the External Network Reference
SEQUENCE
a)

Select from the map the topology ( subnetwork or ET ), which will contain the new External Network
and issue: Create : External Network.

b)

The Create External Network wizard is displayed. Enter userlabel and location and click on Finish
button. See below figure.

Figure 18. External Network Creation wizard.


c)

The External Network Reference is created and displayed in the New Object Holding area. You can
drag the object to the center of the map.

1AA 00014 0004 (9007) A4 ALICE 04.10

2.4.2 Create Connection to External network


a)

From the map select the external network/s to connect and issue Actions: Create: Physical Connection.

b)

The Create connection wizard is presented. See below figure.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

27 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 19. Create Connection step 1.

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

Select the connection type, enter the connection name and click on next button

Figure 20. Create Connection step2

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

28 / 258

Select the real node from the node list and enter the external network name. Click on Finish button.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

d)

Figure 21. Physical Connection: Implement


NOTE
After creating the virtual objects, you could follow the usual procedures:

Create the Connection

Implement the objects and the connection ( see above figure )

Create the Path

NOTE

1AA 00014 0004 (9007) A4 ALICE 04.10

The user can modify, by means of the Show/Set Attributes window, the userlabel of an external network
and the userlabel of a port belonging to an external network.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

29 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.5 Create Connection

Figure 22. Actions: Create: Physical Connection


The Create Connection can be started from the map by selecting source node / destination node and issuing the command Actions: Create: Connection.

1AA 00014 0004 (9007) A4 ALICE 04.10

The Create Connection wizard allows to select the connection type among:

SDH. See Figure 23.

WDM. See Figure 24.

SDHCBR/WDM interworking, where CBR=constant bit rate. See Figure 25. on page 33

Generic Digital Client/WDM interworking. See Figure 26. on page 34

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

30 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 23. Create Connectionstep 1Type SDH

If you select connection type=SDH, you will further select the STM type

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

31 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 24. Create Connectionstep 1Type WDM


If you select connection type=WDM, you will further select the WDM connection type between OPS and
OTS, where:
OTS ( Optical Transmission Section ) is used for connections between different WDM nodes.

1AA 00014 0004 (9007) A4 ALICE 04.10

OPS ( Optical Physical Section ) is used for connections within the same WDM node, originated and terminated to the same node.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

32 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 25. Create Connectionstep 1Type SDHCBR/WDM interworking

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

33 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 26. Create Connectionstep 1Type Generic Digital Client/WDM interworking

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

34 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.5.1 Example of SDH create connection

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE
a)

From the create connection wizard, select connection type=SDH, STM type and enter the connection name. Click on Next button.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 27. Create Connectionstep 2

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

35 / 258

ATERM NODE LIST

PORT
LIST

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

BTERM NODE LIST

PORT
LIST

BTERM PORT LIST

ATERM PORT LIST

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 28. Port selection.


b)

Click on ATerm Node List. From the Atermination Node list ( upperright part of ), select the node
to connect and click on Apply button. The icon of the selected Node is now present in the Create connection dialog box.

c)

Click on ATerm Port List. From the Atermination Port list select the port to connect and click on
Apply button. The icon of the selected Port is now present in the Create connection dialog box.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

36 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

d)

Execute the selection of the terminating node/port following the modality explained at above points
b) and c). Click on Next button.

e)

The Finish button, if selected, completes the connection create.


The Cancel button, if selected, aborts the connection create.
The Previous button allows to revert to the previous screen, in order to modify node/port selection,
connection name...

f)

Wait... After the connection create the physical connection structure view, if required, is displayed.
See below figure.

Figure 29. Physical Connection Structure

1AA 00014 0004 (9007) A4 ALICE 04.10

g)

ED

Physical connections are implemented during network implementation; however it is possible to implement individually a certain physical connection by means of the command Configuration: Implement. See below figure.

01

SC.3:OPERATION
3AL 61348 AA AA
258

37 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 30. Physical Connection: Configuration: Implement

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

38 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 31. Physical connection structure implemented.

Having created the connection, an external connection symbol is created in the submaps which
contain the connected objects. The external connection symbol label contains the name of the
object connected at the other end plus the connection name.

The physical connection is created in the map and the parent link is also created, if no other connections between the involved nodes were present. The link label indicates the number of present physical connections.
h)

Create all the remaining connections

1AA 00014 0004 (9007) A4 ALICE 04.10

Linear MSP schemes need to be carefully managed by the operator. For detail see paragraph
which follows.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

39 / 258

A NPA is a set of NEs, protections blocks, physical connections working together to create a dedicated
protection mechanism or grouped together to establish path layer protections
NPAs are:
SNCP, 2f MSSPRings, 4f MSSPRings, Linear MSPs (e.g. 1:n, 1+1), ASON /Fast Restoration
SNCP rings do not use any dedicated protection mechanism related to the ring itself, but, RM treat them
in a special mode for the path routing and protection.
2.6.1 Topology definition
The RM operator builds the network defining:
The partitioning topologies (i.e. network, first / second level subnetworks)
The placement of NEs into the subnetworks (> Nodes)
The interconnections between the Nodes (physical connections) entered manually or using the autodiscovery function (based on J0 or on NE cables)
As a further, independent step, the operator needs to build the NPAs.
No strict relation exist anymore in RM between topologies (used for partitioning) and protections. In previous RM, ET topologies were used to represent both a protection and partitioning of the network

1AA 00014 0004 (9007) A4 ALICE 04.10

The ET (Elementary topology) can be considered a second level subnetwork removing the payload configuration capability and the statistics related to the configuration

N.B.

For the scenario adding a DXC NE in an MSSPRing (with split operation), the workaround
is to configure the MSSPRing on SH before enabling the download on DXC NE.

N.B.

For the scenario removing a DXC NE from an MSSPRing (with join operation) the work
around is to deconcatenate the concerned AU4s from CT before enabling the download on
DXC NE.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

40 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.6 Introduction to NPA

2.6.2 Network Protection Architecture Create

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to create a Network Protection Architecture ( NPA )
The NPA creation tool allows to specify:
the type,
the involved physical connections and, if applicable, their associated role (e.g. Working or Protection for
4fMSSPRing, and Linear MSP).
For ASON NPA, the user must specify also the physical connections used for the interworking with the rest
of the network
A NPA can be defined independently from the Topologies used for the partitioning of the Network. This
means that a NPA can belong to different Topologies of different levels and that Topology can have NEs
and links involved in multiple NPAs
The creation tool can be started from :
A topology: Network, Subnetwork (lev.1 or lev.2)
Within the tool, the involved physical connections can be retrieved browsing from the initial topology(*) or
from a different one reached through up & down navigations.
The NPA definition ends with the creation in RM of a NPA and its visualization on the user Interface
The NPA can be created even if not valid (e.g. a ring can be open or even empty) but RM always provides
to the users the proper warnings.
Dependently from the type of NPA to be created, the creation activity requires different information and
performs different checks:
A SDH physical connection can only belong to one NPA with the following exceptions:
ASON internal / linear MSP
ASON interworking / any other NPA
SNCP / linear MSP (To Be Confirmed )
A SDH physical connection is present in RM also when supported by a WDM network. The server OTS
or OPS physical conn. Are, in RM, not part of any NPA
SNCP rings must have the same uniform rate and east/west sequence is checked for first gen. NEs
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From the browser select Actions: Create: Npa

01

SC.3:OPERATION
3AL 61348 AA AA
258

41 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 32. Actions: Create: Npa


b)

The Create: Npa: Step 1: dialog box opens. The following cases may arise:
1)

selection of NPA type=SNCP ( generic ).

NPA Reduction Cost Factor

NPA Usage Cost

NPA Usage Cost:


It is an extra cost to pay for the usage of a NPA. It has the target to make costly to enter and to exit from
a Network Protection.
As bigger is set as more the routing in the current NPA will be preferred compared to a less expensive
detour outside the NPA in the meshed network or in another NPA.
It is not considered for the spare that uses the same ring of the main.

1AA 00014 0004 (9007) A4 ALICE 04.10

If set to 0, the routing is done not considering the NPAs.


If set to more than half of the cost of a physical link (Default value TBC), the routing is done as it would
be having only not stacked protections and an internal route is preferred to an external one even if has
a double cost

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

42 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

By default the NPA Usage Cost cost is set to an RM installation default value but can be modified by the
user. For example if L is the default cost of a physical connection, a meaningful default value for the NPA
Usage Cost can be L/2+1 ( i.e. (L/2+1)*2 )
Applications of the NPA Usage Cost
With the proposed NPA Usage Cost, the routing algorithm behaves for stacked and not stacked ring configuration in a similar way (i.e. for the routing, it is like to have a physical link between two stacked rings)
An additional example of the stability effect of the NPA Usage Cost is the behaviour in case of stacked and
unbalanced rings.
NPA Cost Factor:
The NPA cost factor is an additional parameter of each NPA, enabling a percentage cost reduction for its
links. This cost reduction has the target to balance the NPA Usage cost and makes more attractive the
routing inside a NPA compared to the one outside at least for route longer than a given number of arcs.
In the fact, it is an indicator on how much a Main/Spare routing in a NPA has to be preferred compared
to an external route. It works together with the NPA Usage Cost making more attractive long routes in a
NPA.
If equal 0 it has no effect.
As bigger is set as more the cost of NPA internal route is reduced and as more the NPA attracts the routing.
Changing the default physical conn. cost
In case of particular unbalanced configurations, if the NPA Usage Cost is not enough to avoid the ring
changing, the user needs to properly set the costs of physical connections
RM Rules for Main & Spare in 2f MSSpring
These routing rules are used by RM in order to fulfil the requirements:
The NPA Usage Cost for the rings used by the main is set to 0 and the cost of all its routing resources
(e.g. physical conn). is reduced by a parametric cost factor k (the Main & Spare cost gravity factor)
This is equivalent to say that it is preferred a routing in the ring compared to the best route if its nominal
cost is no more that k times the external optimal route
If the spare uses the same links and passthrough connection of the main, the cost is considered zero.
This tries to prefer main and spare overlapped and finally gives more priority to a D&C configuration
The overlapping on Drop/Insert connections between main and spare is forbidden.This is the driver to differentiate main and spare and has its effect mainly forcing a diversity outside the ring

1AA 00014 0004 (9007) A4 ALICE 04.10

The cost of using the ring for the spare in opposite direction compared to the main is increased of a cost
n. In the previous versions of RM this opposite direction was totally disabled.

Enter NPA name and click on Apply

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

43 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 33. Create: Npa: Step 1: SNCPU


2)

Selection of NPA type=2 F MS Spring or 4 F MS Spring. Enter NPA name and click on Apply

3)

Selection of NPA type=Linear plus, i.e. 1 + 1 protection. In this case the user must enter:

NPA name ( userlabel )

Protection Switch Mode

Switch upon SD ( ssignal Degrade )

Mode of operation

Plus APS Mode

Enter NPA name and click on Apply

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

44 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 34. Create: Npa: Step 1: 1 + 1 protection


4)

Selection of NPA type=Linear colon, i.e. 1 to N protection. Enter NPA name and click on Apply

Figure 35. Create: Npa: Step 1: 1 to N protection

1AA 00014 0004 (9007) A4 ALICE 04.10

5)

ED

01

Selection of NPA type=ASON. Enter NPA name and click on Apply

SC.3:OPERATION
3AL 61348 AA AA
258

45 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 36. Create: Npa: Step 1: ASON protection


6)

Selection of NPA type=Fast restoration. Enter NPA name and click on Apply

Figure 37. Create: Npa: Step 1: NPOS protection

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

The NPA Create step 2 dialog box is presented, asking to specify the physical connections to include
in the NPA. Click on Physical connection list button. The Physical connection list opens.

01

SC.3:OPERATION
3AL 61348 AA AA
258

46 / 258

PHYSCON List

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

PHYSCON List button

APPLY button
Figure 38. Selection of the Physical connections
Select the relevant Physical connections and click on Apply button. The icon(s) of the Physical connections are now present inthe main window. Click on Finish button to launch the creation.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

In case of 1 to 1 NPA or 1 to N NPA the selection dialog box contains two subwindows, one to
select the main Physical connection (s), one for the protecting one. See example of 1 to N NPA
in the following figure

01

SC.3:OPERATION
3AL 61348 AA AA
258

47 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 39. 1 to N NPA: physical connection selection

Figures which follow show the action creation report and the NPA highlight on the map.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

48 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Actions after NPA create

Actions available after NPA create are Modify NPA, Modify Ring Map, Implement and Unlock physical connections

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

49 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

NPA highlight

NPA highlight shows on the map the nodes connected by physical connections involved in the NPA.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

50 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.6.3 NPA display & Views

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.6.3.1 NPA display


SCOPE
NPAs can be retrieved from:
The containing network (list of all the existing NPAs)
The subnetworks (level 1 & 2) containing at least a Node (not a physical connection) involved in a NPA.
The map view of network and subnetworks
A physical connection involved in a NPA. A specific graphical flag shows that a Phys.Conn. belongs to
a NPA. This flag is represented on the payload structure view
The routing display of a path crossing one or more NPAs (LIN MSP is under analysis). See specific information on Routing.
A map of a topology containing at least a Node involved in a NPA (different from linear MSP) visualizes
a flag with the type and the name of the NPA :
The flag placement is in charge of the user (e.g. close to the right Nodes)
From the flag it is possible to retrieve the NPA and its view.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

From the browser select Network: Search: All Related Items

Figure 40. Network: Display: All Related Items

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

51 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

b)

c)

ED
Select option NPA

Figure 41. Item selection: NPA

The NPA list is displayed, as in the following figure

Figure 42. NPA list

01

SC.3:OPERATION

3AL 61348 AA AA

258

52 / 258

2.6.3.2 NPA views

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

From a NPA is possible to produce the following views:


Protection blocks (not available for ASON and SNCP).This view displays protection blocks and involved
physical connections and trails.For MSSPRings please refer to the previous ET views. For Lin. MSP
this is a new view.
Node view circularly placed in the case of SNCP
A NPA can be highlighted on a map:
The involved physical connection, links, sublinks, Nodes, topologies and NPA flags are highlighted.
Example of NPA views are shown in the following figures

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

53 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 43. 2F MS Spring NPA view

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

54 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 44. 4F MS Spring NPA view

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

55 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 45. 1 to 1 protection NPA view

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

56 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.6.4 NPA modify

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SNCP Rings, 2f MSSPRings, 4f MSSPRings can be modified adding or removing physical links
Linear MSPs can only be modified adding and removing members of the linear 1:n protection.
The command is performed using a tool similar to the creation/modification wizard
ASON NPA can be modified adding and removing internal or interworking physical links
The command is performed using a tool similar to the creation/modification wizard
ASON NPA can not be modified by splitting / Joining existing internal physical links. This is due to limitation
on the interface between RM and GMRE.
As a specific tool for MSSPRings, the user can also visualize and modify the NE sequence numbers in
the NPA ring to allow a hitless takeover.
The form display the current sequence of the NE protection blocks and allows the definition of a new consistent one.
NOTE: Only a defined NPA can be modified.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 46. NPA: Actions: Configuration: Modify NPA

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

57 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 47. NPA: Modify: step 1

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

58 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 48. NPA: Modify: step 2

2.6.5 NPA Implementation


Once a NPA has been defined, it can be implemented. This is accepted by RM only if the NPA is valid.
This produces the creation of the needed structures / protection blocks in the NEs.
Checks are performed during the implementation and the deimplementation:
Involved physical connections must be implemented (only for NPA implementation )
No path must be present in case of Rings with the exception of SNCP Rings.
No paths must be present on the spare in case of 1+1 Linear MSP or 1:n Linear MSP with noextra
traffic. In case of extra traffic, the relation with the path attribute named MS Protection profile, needs to
considered (To be committed).
The implementation and deimplementation operations also modifies the number of HO LCs according
to the presence or not of low priority traffic.

1AA 00014 0004 (9007) A4 ALICE 04.10

This limitation can be removed in future RM versions allowing a simple migration of protections. In the current release, it simplify the implementation since no path related information (e.g. squelching tables) are
sent to the NEs during NPA implementation

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

59 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 49. NPA: Actions: Configuration: Implement

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

60 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.6.6 NPA: Specify Ring Map

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

NPA: Specify ring map allows to change/display the Node position in NPA ring and the Node Id in NPA.
The user can change these attributes, according to the NPA ring.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 50. NPA: Specify ring map: step 1

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

61 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 51. NPA: Specify ring map: step 2

2.6.7 NPA Remove

1AA 00014 0004 (9007) A4 ALICE 04.10

The NPA can be removed only if not implemented


Implement / deimplement, remove of physical connections and topologies:
In case of ASON NPAs, RM still requires to perform a payload configuration on internal links even if this
activity is only internal and not required by GMREs.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

62 / 258

2.7 Create a 4F STM16 NPE Ring with 1664SM

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to create a 4Fibre NPE ring with 1664SM equipment.
SEQUENCE
a)

The ring (Elementary Topology) objects are created in a Subnetwork submap using the command
Construction:Create:

b)

Create Nodes and ports

2.7.1 Creating the Connections between Nodes


The Creating of the Connections is described in the previous paragraph Create Connection. Notice that:
East Working Ports must be connected to West Working Ports
East Protection Ports must be connected to West Protection Ports

TX
RX

SLOT 17
AGGR. WEST 1
WORKING

SLOT 19
AGGR. WEST 2
PROTECTION

SLOT 18
AGGR. EAST 1
WORKING

SLOT 20
AGGR. EAST 2
PROTECTION

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 52. Physical view of the aggregates of 1664SMNPE ( from 1353NM )


N.B.

The 1644SM network element, when inserted in a NPE ring is equipped with 4 STM16
aggregate boards, as shown in Figure 52. This figure is part of the 1353NM equipment view.

N.B.

West 1 and East 1 aggregate ports support the working capacity, West 2 and East 2 aggregate
ports support the protection capacity.

c)

Create NPA=4fMS Spring

d)

Implement NPA

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

63 / 258

2.8 Takeover procedure

The 4F ring is already configured at 1353NM ( EML ) layer.


No path crosses the ring

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

Create the NPA 4f for the topology which represents the existing ring

b)

At the NE/EML layer read the information of Node Id and Node Position per each node of the ring
and move these information to 1354RM map.

c)

Issue NPA: Specify Ring map setting Node Position and Node Id.

d)

Issue Download Disable

e)

Implement the ring

f)

Execute the Mark Audit and verify differencies, if any

g)

Enable download

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

64 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONDITIONS

2.9 Create a 4Fibre STM64 NPE Ring with 1670SM

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope is to create and implement a STM64 4Fibre NPE ring with 1670SM equipment.
SEQUENCE
a)

Create the Nodes. See below figure.

b)

Create all the connections main (clockwise). The following assignment is suggested:
1)

Create the connection main A to B, selecting board 24 on node A and board 32 on node B

2)

Create the connection main B to C, selecting board 24 on node B and board 32 on node C

3)

Create the connection main C to D, selecting board 24 on node C and board 32 on node D

4)

Create the connection main D to A, selecting board 24 on node D and board 32 on node A

Figure 53. Example of NPE ring with 1670SM


c)

d)

Create all the connections spare (clockwise). The following assignment is suggested:
1)

Create the connection spare A to B, selecting board 28 on node A and board 36 on node B

2)

Create the connection spare B to C, selecting board 28 on node B and board 36 on node C

3)

Create the connection spare C to D, selecting board 28 on node C and board 36 on node D

4)

Create the connection spare D to A, selecting board 28 on node D and board 36 on node A

Implement the Ring.


The attribute Nodeid of Node A is Nodeid=1
The attribute Nodeid of Node D is Nodeid=2

1AA 00014 0004 (9007) A4 ALICE 04.10

The attribute Nodeid of Node C is Nodeid=3


The attribute Nodeid of Node B is Nodeid=0

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

65 / 258

The first port, which has been selected while creating the A to B connection ( board 28 on node A
) is now distinguished by the attribute SDHPORTROLE=EAST MAIN. The second port, which has
been selected while creating the A to B spare connection ( board 36 on node B ) has now the attribute
SDHPORTROLE=EAST MAIN. The remaining ports of the NPE ring are marked accordingly.

WEST SPARE
EAST SPARE
slot b28
slot b36
WEST MAIN
EAST MAIN
slot b24
slot b32

Figure 54. 1670SM equipment view

1AA 00014 0004 (9007) A4 ALICE 04.10

Assignments are visible only at 1353NM interface ( 4Fibre NPE ring main dialog box ). See below
figure

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

66 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The first port, which has been selected while creating the A to B main connection ( board 24 on node
A ) is now distinguished by the attribute SDHPORTROLE=WEST MAIN. The second port, which has
been selected while creating the A to B main connection ( board 32 on node B ) has now the attribute
SDHPORTROLE=EAST MAIN. The remaining ports of the NPE ring are marked accordingly.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 55. 4Fibre NPE ring 1353NM main dialog box


e)
f)

Create NPA=4fMS Spring


Implement NPA

2.10 Takeover procedure


CONDITIONS
The 4F ring is already configured at 1353NM ( EML ) layer.
No path crosses the ring

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

Create the NPA 4f for the topology which represents the existing ring

b)

At the NE/EML layer read the information of Node Id and Node Position per each node of the ring
and move these information to 1354RM map.

c)

Issue NPA: Specify Ring map setting Node Position and Node Id.

d)

Issue Download Disable

e)

Implement the ring

f)

Execute the Mark Audit and verify differencies, if any

g)

Enable download

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

67 / 258

This paragraph summarizes the main guidelines for the correct set up of linear MSP schemes, 1+1 and
1:1, in SDH Q3 NEs in NR5.0x, NR5.1A and 5.1B, i.e. in all the NRs where, according to the current planning of 1354RM, the creation of the linear MSP scheme is provided only via 1353SH. The paragraph describes also the undesired behaviours (in any case, without loss of traffic) that may occur if those guidelines are not followed.
The procedures described in this document apply especially for the Q3 NEs where it is possible to explicitly
setup/dismiss linear MSP schemes, namely ADMs
2.11.1 Linear 1+1 MSP
Step 1: SH operator shall set up the protection scheme before RM establishes any physical connection
between the ports of the main and of spare sections. This operation shall be performed before RM takes
into charge the involved resources, or after a temporary deassignment by RM of the involved resources,
or within a privileged operator session.
Step 2: RM operator shall create the physical connection between the ports of the main section only. It has
to be noted that in this situation RM application prevents the creation of a physical connection between
the ports of the spare section.

What happens if this procedure is not followed: if RM operator sets up a physical connection
between the ports of the spare section before establishing the MSP scheme, there are two possibilities, both critical
a) If also paths are defined over the spare section before the MSP scheme is set up via SH, the establishment of the MSP scheme will fail.
b) If no paths are defined on the spare section, the establishment of the MSP scheme will succeed but
there will be an inconsistency between RM representation and the actual configuration. Moreover, if RM
operator tries setting up a path over the spare section after the MSP scheme is established, the path implementation will succeed but the new path will be immediately alarmed. As a further side effect, there will
be an inconsistent representation of connectivity in SH (the path connections over the spare section are
shown in the crossconnection view but not on the corresponding port view, which will only display the
main section). The final result is that it will be difficult for an operator to understand that the path over the
spare section is alarmed because of a wrong configuration sequence.
2.11.2 Linear 1:1 MSP
Step 1: RM operator shall create in advance the physical connections both between the ports of the main
section and between the ports of the spare section. This operation is necessary to allow the set up of extra
traffic paths on the spare section.

1AA 00014 0004 (9007) A4 ALICE 04.10

Step 2: NM operator (administrator) shall set up the protection scheme. This operation shall be performed
within a privileged operator session because the physical connections shall be left assigned to RM.
Once the protection scheme is established as described above, RM can set up paths, i.e. traffic, on both
the main (protected) and spare (extratraffic) sections. It has to be noted that RM does not characterize
as low priority traffic the spare section.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

68 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.11 Setting up linear MSP in Q3 NEs with RM/NM

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

What happens if this procedure is not followed: if steps 1 and 2 of the sequence are reversed, after the
MSP is established the RM application will prevent to set up a physical connection between the ports of
the spare section. As a result, it will not be possible to set up extra traffic.
2.11.3 Alarm Behaviour
2.11.3.1 Linear 1+1 MSP
By convention, RM represents the protected multiplex section as a single section between the main ports.
The spare resources are not shown. A MSP switch does not affect the supported paths provided there are
no failures in the protecting multiplex section.
The supported paths will be affected in case both the protected and protecting multiplex sections are failed
and there are no further protection schemes on a different layer (e.g. SNCP). It has to be noted that for
this situation RM affects the paths relying on SSF that should be generated autonomously by the NEs on
the impacted path layer TPs.
2.11.3.2 Linear 1:1 MSP
On RM, the main and the spare sections are handled as if they were independent. In case of MSP switch,
the low priority traffic will be lost and the related paths will then be alarmed. It is up to the human operator
to correlate this situation with a MSP switch.
KNOWN ISSUES
Failure on consistency audit
It has to be noted that, even if the above procedures are followed, in case RM performs a consistency audit
after the linear MSP scheme has been established, the spare ports will be marked as failed (anyway,
without impacts on the traffic).
Degraded protection indication on RM
RM can not perform any realtime correlation between failures in the main/spare sections and the position
of the switch inside the NE to deduce the degree of availability of the protection.
When the linear MSP is set up on a QB3* NE, the realtime correlation is performed inside NM MIB to
generate a degraded protection alarm on the port of the main (protected) section in case of a failure in
the spare (protecting) section. This alarm is then emitted by NM and represented at RM.
When the linear MSP is set up on a Q3 NE, neither NM (MIBless for Q3 NEs ) nor the NE perform such
a correlation. As a consequence, the degraded protection alarm is not generated.
Proper provisioning of low priority traffic in 1:1 MSP

1AA 00014 0004 (9007) A4 ALICE 04.10

RM does not characterize the traffic priority for the physical connections at MS level. It is the responsibility
of the human operator to define properly the highpriority traffic paths over the main (protected) multiplex
section and the lowpriority ones over the spare section.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

69 / 258

2.12.1 JO SETUP
J0 setup can be entered from the Network, Subnetwork or Node, issuing the command Actions: Configuration: Upload Tools.
From the Upload Tools dialog box ( see following Figure 56. ), select option Automatic Generation of Trace
Identifier, which means J0 definition and click on Finish button to confirm. The following string is automatically entered:
R$NDMPORTIDENTI
where NDM=Network Domain Id ( 3 characters) , PORTIDENTI=port identifier (10 characters)
As an alternative, sent and expected J0 can be entered by the operator by using the CT/NM when the
fiber pair in put in service.
2.12.2 Upload Physical Connectivity
SCOPE
The scope of this procedure is to upload the physical media adjacency of the network. This means that
SDH/SONET physical links are automatically created in RM, when a fiber pair is connecting two ports.
The discovery is performed by using the trace identifier J0
SEQUENCE
a)

The upload command is performed on one of the two NEs. Issue Configuration: Upload Tools. Select
option Upload Physical Connectivity
It is possible to issue this command on the whole network or on a subnetwork.

b)

Click on Finish button to confirm

2.12.3 Upload of Protection Schema (MSP linear)


SCOPE
The scope of this procedure is to upload the Protection Schemas. This means that the MSP linear protection schemas are discovered and the relevant NPA is automatically created in RM.
NPA user label is: AutoDiscporId
where portId is the identifier of the port marked with channel number 0 (main)
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

The upload command is performed on one of the two NEs. Issue Configuration: Upload Tools. Select
option Upload of Protection Schema
It is possible to issue this command on the whole network or on a subnetwork.

b)

ED

Click on Finish button to confirm

01

SC.3:OPERATION
3AL 61348 AA AA
258

70 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.12 Upload Connectivity

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 56. Upload Tool

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

71 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.13 Move node from/to RM topologies

To move nodes from the source topology to a destination topology.


CONDITIONS

no activities have to be in progress on the node to be moved.


the working state of the node must be normal
the working state of the source topologies in which the node is contained (ntw, sbn and et) must be
normal
the working state of the destination topology in which the node has to be moved (ntw, sbn and et)
must be normal
the working state of the involved physical connections must be NORMAL

N.B.

Alternatively,the user can move nodes using dedicated scripts and an offline tool, such as
Excel program, without interaction with the User Interface. See details in the 1354RM
Administrators Guide.

SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

From the source map point to the node to move and issue Node: Modification: Move Node. The Move
node dialog box opens. See Figure 58. on page 73.

Figure 57. Node: Modification: Move Node

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

72 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SELECTION OF
DESTINATION
TOPOLOGY

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 58. Move dialog box


b)

From the Move dialog box click on button Selection of the Destination topology. The map opens in
selection modality.

c)

Click twice on the network icon. The Network map opens.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

73 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 59. Network Domain map opened in selection modality

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 60. Network map opened in selection modality


d)

ED

Click twice on the target subnetwork. The 2nd level subnetwork map opens.

01

SC.3:OPERATION
3AL 61348 AA AA
258

74 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 61. 2nd level subnetwork map


e)

Select the Destination topology and confirm by pressing button selection. The Destination topology
icon is present in the Move dialog box. See Figure 63. on page 76

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 62. Selection of the Destination topology

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

75 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 63. Move dialog box: command launch

1AA 00014 0004 (9007) A4 ALICE 04.10

f)

Issue the Move command by clicking on Finish button. The moved node is present in the destination
submap in the New Object holding area.

Figure 64. Moved node in the New Object holding area

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

76 / 258

Drag the moved node from the New Object holding area to the center of the window. The connections
are drawn automatically.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

g)

Figure 65. Destination submap after the move operation

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

Multiple move operation is allowed. See below figure.

Figure 66. Multiple move operation

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

77 / 258

RM allows to manage a Physical Connections between ports of the same NE: this is mainly for WDM NE
management but it can be used in particular SDH application.
The following commands/actions are available:

Creation of an internal physical connection


The user can specify an internal physical connection by entering twice the Node to be interconnected.
Implementation of an internal physical connection
Removal of an internal physical connection
Display of an internal physical connection

Note that Physical Connection(s) between ports of the same Node are not displayed on the maps.

1AA 00014 0004 (9007) A4 ALICE 04.10

Internal Physical Connections can be retrieved through inventories requiring all Physical Connections that
are present in the topology where the Node is included, or that are startingending in the Node.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

78 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.14 Internal Physical Connection Management

2.15 2Mb/s retiming management

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to enable/disable the retiming functionality, i.e. to manage a 2Mb/s synchronous timing source going out from a certain NE port, used to synchronize the PDH network, in order to
reduce the pointer justification wander.
This procedure includes also the configuration of the action to perform in case of loss of synchronization.
The consequent actions that can be configured are:

timingPDH (default) . Timing of the outgoing signal is synchronized by the incoming signal

AIS. All ones are inserted in the 2Mbit/s outgoing signal

CONDITIONS
The functionality is applied at path level. The functionality can be enabled/disabled on the ports related
to the path. The retiming can be defined only for an already implemented or partially implemented path.
The retiming functionality is applicable only for 2Mbit/s signals and on ports belonging to Q3 NEs
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

Point to the path whose port is to be used as synchronization source and open the popup menu.
Select Configuration: 2Mbit/s Retiming management. See Figure 67. The Path Retiming wizard
step 1 is displayed. See Figure 68.

01

SC.3:OPERATION
3AL 61348 AA AA
258

79 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 67. Path: Configuration: 2Mbit/s Retiming management

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

80 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 68. Path Retiming; step 1


b)

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Click on Next button. The Path Retiming wizardstep 2 is displayed. See Figure 69. You can enter
the following:

retiming supported (retiming/notsupported)

retiming state (Disabled/Enabled)

Enter the suitable selection

01

SC.3:OPERATION
3AL 61348 AA AA
258

81 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 69. Path: retiming: port selectionstep 2

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

82 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 70. Port: Retiming state=enabled

1AA 00014 0004 (9007) A4 ALICE 04.10

The Operator can modify the retiming and the related consequent action on the displayed ports. For unidirectional or broadcast path, only the sink ports supporting the retiming functionality are presented to the
Operator. In addition it is possible to navigate on the 1353NM in order to get further information.
The consequent actions are applicable only for ISDNPRA or Leased Line signals and can be configured
only for bidirectional paths and only if the retiming functionality has been enabled.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

83 / 258

By network implementation it is meant putting the previously tested network in service .


The NEs are reset and a default configuration is sent for the NE which includes only higher order
CTPs.

In case of NPE MSSpring the Topology Implementation process performs the following steps:
a)

starting from the sequence number in et node attribute (it provides the position of each node in the
et), it builds the string corresponding to the ring map info attribute of the 4f MS Protection Block MOC

b)

for each node of the et:

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

1)

it creates, contained in the node, the MS Protection Block MOC filling the Configuration State
attribute with the virtual value

2)

it submits to the proper TSDIM Front End Processor (in charge of the node) the request to
change on the MS Protection Block (contained in the node and related to the et) the
Configuration State attribute to the active value and the ring map info attribute to the string set
up at step a ). In case the topology is modified adding/removing a node and the et is requested
to be implemented again, the topology implementation process submits the request to change
the ring map info attribute only.

To execute the network implementation select the Network/Subnetwork/Ring icon in the


Root/Network/Subnetwork window and issue the command Actions: Configuration: Implement.

01

SC.3:OPERATION
3AL 61348 AA AA
258

84 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.16 Network implementation

N.B.

In case of NPE MSSPRING the operator can excute the following checks:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1)

From the Subnetwork map point with the mouse at the NPE ring and issue the popup menu
Main Items: All Protection Blocks in MSSPRING 4 F. The relevant graphical window is
displayed, including all protection blocks.

Figure 71. All Protection Blocks in MSSPRING 4 F


2)

From 1353 NM equipment view select menu MSSpring:Manage Ring Map.


This map lists Ring Position and Node Id of each node and describes the connections with the
other nodes, in terms of Ring Position, Node Id and side (West/East)

1AA 00014 0004 (9007) A4 ALICE 04.10

3)

ED

01

From 1354RM 4 FMS Spring window select a node and click on the Show/Set Attributes icon
( lens ). The Ring Map Info Attribute lists the sequence of the connected Node IDs in ET. The
Show/Set Attributes window contains also the values of the attributes Node Position in ET and
Node Id in ET. Notice that:
VALUE at NM interface = VALUE at RM interface + 1

SC.3:OPERATION
3AL 61348 AA AA
258

85 / 258

At the end of the network implementation the network is automatically configured at higher order, i.e. the
MIB contains all the HOLCs with the HOCTPs.
Payload configuration consists of:

creating the LO objects starting from HO objects

modifying the existing payload configuration (e.g. from 63 x 2 Mb/s to 3 x 34 Mb/s payload structure)

The configurable objects are:

Physical connection
Higher order link connection
Higher order trail

N.B.

The payload configuration is not required for NPE Ring, since the 1664SM network element can
implement only connections at VC4 level.

2.17.1 Configuring the Payload


The payload configuration procedure consists in:

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

FROM THE MAP


1)

Select the object to configure.

2)

Click on Payload Configuration tool button. The Payload Configuration window is presented.

Figure 72. Payload Configuration window

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

86 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.17 Payload Configuration

b)

FROM BROWSER

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1)

Select the object from the Browser window and launch the Configure Payload application by
selecting the appropriate Tool button.

The virtual container fields are shown on the Payload Configuration window. The operator can write
the new configuration into these fields or can choose it using the selection box on the right of the
VC fields (Dictionary). Enter the configuration and click on OK.

Figure 73. Payload Configuration dictionaries

1AA 00014 0004 (9007) A4 ALICE 04.10

If the object to be payloaded is an HO trail or an HOLC, the list of configurable TUG is presented.
Choose the TUG combination and click on OK. For example the TU12, TU12, TU3 combination
means 21 TU12+ 21 TU12+ 1 TU3.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

87 / 258

When the payload configuration is in progress, the operator can supervise the operations performed by
the process. It mainly means:
a)

Verify in the Browser that the working state of the object (e.g. a ring) changes to Configuring.

b)

If the object to configure is a ring, the working state of all the contained physical connections must
be configuring. To do this enter command: Display:Related items:Physical Connections, starting
from a ring.

c)

If the operator wants to supervise the other objects involved in payload configuration, he can issue
a Display:All Related items command on mstrails, Client Link Connections, HOtrails, Low Order Link
Connections, etc.

At the end of the configuration process the working state of the configured objects must return to normal;
otherwise the working state becomes Fail to Configure.
2.17.3 Payload Configuration supervision
When the payload configuration is successfully completed, the user can supervise it in the following ways:

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

From the map select the Physical Connection and use the popup menu Payload Configuration. The
relevant drawing window is opened; the Payload Configuration is represented graphically.

Figure 74. Physical connection structure

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

88 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.17.2 Payload Configuration monitoring

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

b)

From the browser display the ring or the physical connection: both objects have dedicated fields
displaying the actual configuration of the Physical Connection. You can also use the Display: Related
items: Physical Connection Structure option to display the relevant drawing window. In addition, you
can select an HO trail and issue the Actions: Display Related Items to display the views and/or the
lists of the children objects: Paths in trail, Client link connections, ...

c)

From the browser or from the Physical Connection drawing window you can also open the graphical
window on the SDH Port, which displays the payload configuration supported by the port.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

89 / 258

2.18.1 AU4 Concatenation SETUP


SEQUENCE
a)

From the map select the physical connection to configure and issue Browse: Object(s). The browser
opens on the selected object. See Figure 75.

b)

Point with the mouse at the physical connection and issue Display: Related Items: physical
connection structure. See Figure 76. The relevant view is displayed. See Figure 77. on page 91.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 75. Physical Conn.:display related items

Figure 76. Selection of the Physical Connection.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

90 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.18 AU4 Concatenation

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 77. Physical Connection Structure.

Figure 78. MS trail: AU4 concatenation

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

91 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 79. Payload configuration window.


c)

From the view select the MS trail and click on Payload Configuration button. The Payload
Configuration window opens. The actual payload structure is displayed in the bottom section of the
window.

d)

Click on the AU4 which will be the first AU4 of the concatenated stream. A subwindow is displayed
( see Figure 79. ), which allows to select the payload structure. If the operator selects AU44C and
presses OK, the concatenated configuration is set up in the Payload Configuration window.

e)

Click on SETUP button to confirm. The configuration is sent to the Network Elements and a Report
Log is displayed.

2.18.2 AU4 Concatenation Display

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

Select the relevant Physical Connection and issue Display: Related Items: Physical Connection
Structure. The graphical window is displayed in Figure 80. herebelow.

01

SC.3:OPERATION
3AL 61348 AA AA
258

92 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 80. MS Trail Structure

1AA 00014 0004 (9007) A4 ALICE 04.10

2.18.3 AU4 Concatenation Remove


a)

From the browser select the MS trail to configure and click on Payload Configuration button. The
Payload Configuration window is presented. See Figure 81.

b)

The actual payload structure is displayed in the bottom section of the window.

c)

Click on the first AU4 of the concatenated stream. A subwindow is displayed ( see Figure 81. on
page 93 ), which allows to select the payload structure. If the operator selects AU4 and presses OK,
the concatenated configuration is removed from the Payload Configuration window.

Figure 81. AU4 Concatenation Remove

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

93 / 258

Click on SETUP button to confirm. The configuration is sent to the Network Elements and a Report
Log is displayed.

1AA 00014 0004 (9007) A4 ALICE 04.10

Notice that the operation of physical connection remove comprises the removal of the physical
connection, MS trail and link connections. The involved ports are deassigned. No action is made
on the AU4s at NE level, which hold the last setting ( concatenated or not concatenated ).

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

94 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

d)

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.19 Trail Creation Wizard


2.19.1 Introduction
A HOTrail can be created only between nodes external to the NPE MSSpring.
The Trail creation wizard function is used to create, allocate, implement and configure an HOTrail within
the SDH Network. A HOTrail is a transport connection between HOTTPs ( HOCAPs) related to SDH
ports. A HO Trail provides LO resources ( LOLCs) to carry LO traffic (i.e. LO paths).
Beeing a wizard, the user is driven by a series of steps to execute the procedure; subsequent boxes are
to be filled with requested parameters or values; in the first part of the boxes some comment helps the user
fillingin the fields; the Next button go to the next step/box and the Prev button allows to change previously
entered values; the Finish button gives the execution of the procedure.
N.B.

The user creates a network with different subnetworks.The user tries to select simultaneously
two NEs between two subnetworks and it is possible. But, once opened the trail window, only
one element is present, the first one selected. This is due to the structure of ilog maps. Namely,
it is possible to select a couple of nodes only if they belong to the same map view.

2.19.2 Operation
a)

Select the Trail Termination points to be created on the map and then on the menu Actions: Create:
Trail. A sequence of boxes will openup together with a browser window (if not already open).

1AA 00014 0004 (9007) A4 ALICE 04.10

On the upper part of Step1 box figure, there are helpfull notes about choosing/selecting the parameters
and values.

Figure 82. Actions: Create: Trail

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

95 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 83. Setup Trail: step 1: Configuration


Note that the number of trails can be specified only for trails between nodes.

1AA 00014 0004 (9007) A4 ALICE 04.10

The User Label can be:

not specified
specified

Configuration subwindow. See Figure 83. It contains:

ED

it is created according to Rec. M1400.


if you create more trails an ordinal number is added to the User Label.

Setup mode: a question button asks the user if he wants to proceed with automatic allocation,
implementation and payload ( Yes / No )

Payload structure. Select the suitable configuration.

01

SC.3:OPERATION
3AL 61348 AA AA
258

96 / 258

Protection subwindow. See Figure 84. It contains:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Protection. You can select:

None

SNCP

D&C SNCP

SNCP type

SNCP/I preferred with alarms

SNCP/I preferred no alarms

SNCP/N preferred
This feature allows the managing of different type of SNCP protection schemes for a path/
trail. The allowed schemes are:
SNCP/I (Inherent)
SNCP/N (Notintrusive)
The two schemes are related to the switch criteria. In particular:
SNCP/I switch criteria: AIS and LOP
SNCP/N switch criteria: Server Signal Failure, Signal Degraded, Trace Identifier Mismatch, Excessive BER and Unequipped
The user can specify the preferred type of SNCP protection using the Path Creation (for
paths) and Set up Trail (for trails) commands. Anyway, the type of SNCP protection can
be modified, in a second step, even if the path/trail is implemented.
If the user wants to add the protection to an unprotected path/trail, he has to use the Add
Protection command. The preferred type of SNCP protection has to be previously chosen
by the user modifying the related attribute of the path.
Since this feature is not supported by all the NEs, a path/trail may have SNCP/I and SNCP/
N protections.

1AA 00014 0004 (9007) A4 ALICE 04.10

RM does not provide provisioning of SNCP/N switching criteria (i.e. Excessive BER, Signal
Degraded).

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

97 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 84. Setup Trail: step 1: Protection

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

Routing subwindow. See below figure, which contains the explanation of:

NPA Main & Spare factor

MS Spring D & C factor

CP Restoration subwindow. It contains the following fields:

Restoration Mode ( No Restoration / On Control Plane )

Priority of the trail in the ASON network

01

SC.3:OPERATION
3AL 61348 AA AA
258

98 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 85. Setup Trail: step 1: Routing

b)

ED

Click on Next button. On Step 2 box there is the source/sink selection of Node/Ctp.

01

SC.3:OPERATION

3AL 61348 AA AA

258

99 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 86. Trail Creation wizard step 2


Click on CTP list button (source). From the list select the CTP and confirm with Apply button. The icon of
the CTP is displayed in the lefthand part of above figure.

1AA 00014 0004 (9007) A4 ALICE 04.10

Note that the CTP selection can be avoided; the system selects the first idle CTP. If the user
wants to select manually the CTP, the possible CTP names can be individuated from the Physical Connection Structure.
Note that the selection of only one ctp is sufficient: in this case the same tp will be chosen on the far end.
c)

ED

Click on Finish button to confirm the creation.

01

SC.3:OPERATION
3AL 61348 AA AA
258

100 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

d)

ED

A warning alerts to refresh manually the window, as per Figure 87. . The trail structure is shown in
Figure 88.

Figure 87. Trail structure: warning

01

SC.3:OPERATION

3AL 61348 AA AA

258

101 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 88. Trail structure

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

102 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.20 Upload NAPs


The Upload NAPs operation is required to take in charge the NAPs ( Network Access Points ) at RM side.
NAPs are Lower Order Trail Termination Points for 2 Mb and 34 Mb tributary ports or Higher Order Trail
Termination Points for 140 Mb tributary ports. In practice a NAP coincides with a VC12, or VC3, or VC4.
As a result of this command, PDH ports are assigned to the Regional Manager and the related TTPs are
created in the RM database.

This command can be issued for the whole network, for a subnetwork only, an Elementary Topology (ring)
or a single Node.
It can be launched from Browser or Netview.
2.20.1 Upload NAPs
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

From the browser window point with the mouse at the topological object whose NAPs are to be
uploaded and open the popup menu. Select menu item Configuration: Upload NAPs. See
Figure 89. A dialog box alerts that the action has been correctly started.

Figure 89. Topological object: Configuration: Upload NAPs.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

103 / 258

The operator can monitor in real time the upload in progress by means of the browser, which displays the
working state=uploading of the involved topological object. See Figure 90.

Working state=

uploading

Figure 90. NAP upload monitoring.


2.20.1.2 Verify the Upload of NAPs

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

Verify from the browser


1)

From the browser point the mouse at the topological object to verify and open the popup menu.
Select menu option Display: Main related items...

2)

From the selection dialog box of Figure 92. on page 105 click on option NAPs and click on No
Filter. The NAP list is displayed. See Figure 93. on page 106

01

SC.3:OPERATION
3AL 61348 AA AA
258

104 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.20.1.1 NAP upload monitoring

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 91. Node: Search: Main related items...

Figure 92. Selection dialog box.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

105 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 93. NAP list.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

106 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.21 Takeover of retiming

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
This feature allows to upload the retiming configuration from an existing network.
CONDITIONS
This feature is useful when the retiming has already been configured in the network (e.g. from SH) and
RM has to take in charge this configuration
SEQUENCE
a)

the Synchronize NE command has to be executed on all the NEs that can support 2Mbs ports. As
a consequence, the retimingSupported attribute of the port is aligned

b)

the NE has to be put in Download disabled mode

c)

a dedicated script has to be executed. This script contains the following steps:

the Consistency Audit (notify modality) has to be performed on all the ports involved in a path and with
the retimingSupported attribute different from notSupported. (through a dedicated script). As a consequence, the consistency status of all the ports with the retiming enabled in the NE is set to consistencyMismatch.
the retimingStatus attribute of the paths involving ports with the consistencyStatus attribute equal to consistencyMismatch is aligned (set to enabled. As a consequence, the retiming attribute of the involved ports
is aligned (set to enabled)
N.B. As the NE is in Download disabled mode, the consistencyStatus attribute of the involved ports is equal
to notAligned. Performing a new Consistency Audit (notify modality), the consistencyStatus attribute will
be set to normal. At the end, the NE has to be put in Download enabled mode. the batch file has to be
executedPM on regenerator section monitoring function (WDM/PM/B1)This feature deals with the Performance monitoring of client path (B1 monitoring).
2.21.1 Measurement types
The supported types of PM measurements are:
PM 15 minutes for Maintenance (unidirectional)
PM 24 hours for Maintenance (unidirectional)
2.21.1.1 Creation of PM TPs
When a raw connection is transformed in a client path, RM automatically creates, for each end point of
the created client path, the following PM TPs:
24 hour / 15 minutes ingressing unidirectional for the boundary CTP
24 hoursminutes ingressing unidirectional for the adjacentBoundary CTP

1AA 00014 0004 (9007) A4 ALICE 04.10

PM TPs are created taking into account NE restriction. For example, in case of 1696MS, only the PM TP
for the adjacentBoundary CTP can be created.
N.B. The automatic creation of PM TPs can be disabled thought an environment variable set at installationtimeManual Management of OADM Connectivity

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

107 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

108 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

3 TRANSPORT MANAGEMENT

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The main procedures described in this Chapter are:

Path Provisioning and path visualization

Path Constraints

Add Leg

OS driven restoration

Join/Split path

Join/Split trail

Join/Split Physical Connection

N.B.

After a 1354RM merge operation the Join/Split procedures will be used in the following order:
1join path 2join trail 3join physical connection
ISDN management

3.1 Path Provisioning


3.1.1 Introduction
The path creation can be executed only in an implemented network with already uploaded NAPs.
Path Provisioning is composed by:

path create. define a connection by making a reservation of its end points

path allocate. make reservation of the route within the network. The route includes all relevant
elementary connections ( connections in topology ). Path deallocate is the reverse operation
The allocation algorithm chooses the less costly route by appliyng the Dijkstra algorithm

path implement. transmit to the network the commands to activate all included connections in
topology, thus implementing ( i.e. activating ) the whole path. Path deimplement is the reverse
operation

path Commission, Decommission is only a lock which can be set / removed to / from an implemented
path

path constraints. Used by the allocation algorithm, which is forced to follow users preferencies in
selecting the path route

It is possible to execute the allocation, deallocation, implementation, deimplementation, commission,


decommission on several paths at the same time.

1AA 00014 0004 (9007) A4 ALICE 04.10

You can then display the path route using the SDH netview or browser application.
Examples of path create commands (pulldown and popup, respectively), are shown in Figure 94. and
Figure 95.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

109 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 94. Actions: Create: Path pulldown menu

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

110 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 95. Node: Create: Path popup menu

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

111 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.2 Path Create management

Path management consists in:

path create. define a connection by making a reservation of its end points

path allocate. make reservation of the route within the network. The route includes all relevant elementary connections ( connections in topology )

path implement. transmit to the network the commands to activate all included connections in topology, thus implementing ( i.e. activating ) the whole path

path constraints. Used by the allocation algorithm, which is forced to follow users preferencies in
selecting the path route

3.2.1 Path Create


SEQUENCE
a)

Launch the path create application. The path create wizard is displayed. See Figure 96.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

The user creates a network with different subnetworks. On these subnetworks, the user creates
some Ets with many adms. The user tries to select simultaneously two adms between two Ets
and it is possible. But, once opened the path window, only one element is present, the first one
selected. This is due to the structure of ilog maps. Namely, it is possible to select a couple of
nodes only if they belong to the same map view.

01

SC.3:OPERATION
3AL 61348 AA AA
258

112 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 96. Path Create step1


b)

Enter the following values:

Service type ( PDH/ATM/ETHERNET /DATA/CBR)

1AA 00014 0004 (9007) A4 ALICE 04.10

1)

ED

01

If you select PDH, selectable service rates are those shown in Figure 97.

SC.3:OPERATION
3AL 61348 AA AA
258

113 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 97. Service type PDH: Service rate selection


2)

If you select ATM, selectable service rates are the same as for PDH service type

3)

If you select Service type=Ethernet, selectable service rates are summarized in the below
table.

SERVICE TYPE

SERVICE RATE

TRANSPORT RATE

ETHERNET

1 Gbit/s Ethernet transparent

AU4nV
(concLevel=8)

1 Gbit/s Ethernet Rate adaptive

AU4nV
(concLevel=17)

10/100 Mbit/s Ethernet Rate TU12 / TU12 nV


adaptive
TU3 / TU3 nV
AU4

4)

If you select Service type=DATA, selectable service rates are shown in figure which follows:

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 98. Service type DATA: Service rate selection

ED

01

a)

For a 10100Mb path enter:

Service Rate=10100 Mb Rate Adaptive

SC.3:OPERATION
3AL 61348 AA AA
258

114 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Transport Rate: any

Service type=Ethernet

Service Rate=10100 Mb Rate Adaptive

Transport Rate: any

Configuration rate: Automatic 10 Mb / Automatic 100 Mb / Manual 10 Mb / Manual 100 Mb


Automatic means that the path adapts the rate to the ethernet port rate
Manual means that the path does not adapt the rate to the ethernet port rate

path name

b)

For a 1 Gb transp see description at paragraph

Path type. For details see explanation at section Technical Annexes.

Figure 99. Path type selection

SNCP type

it describes different types of SNCP protection schemes for a path/trail. Allowed schemes are:
SNCP/I (Inherent)
SNCP/N (Notintrusive)
The two schemes are related to the switch criteria. In particular:
SNCP/I switch criteria: AIS and LOP
SNCP/N switch criteria: Server Signal Failure, Signal Degraded, Trace Identifier Mismatch,
ExcessiveBER and Unequipped
The user can specify the preferred type of SNCP protection using the Path Creation (for paths) and Set
up Trail (for trails) commands. Anyway, the type of SNCP protection can be modified, in a second step,
even if the path/trail is implemented.
If the user wants to add the protection to an unprotected path/trail, he has to use the Add Protection
command. The preferred type of SNCP protection has to be previously chosen by the user modifying the
related attribute of the path.
Since this feature is not supported by all the NEs, a path/trail may have SNCP/I and SNCP/N protections.

1AA 00014 0004 (9007) A4 ALICE 04.10

RM does not provide provisioning of SNCP/N switching criteria (i.e. Excessive BER, Signal Degraded).

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

115 / 258

NOTE: For a path/trail, the management of this feature foresees the introduction of the following new
attributes:
sncpType: it specifies the type of the protection of the path/trail. The allowed values are:
sncpIpreferredNoAlr: the SNCP/I type has to be preferred for all the protected connections of the
path/trail
sncpIpreferredAlr: the SNCP/I type has to be preferred for all the protected connections of the
path/trail.The alarms have to be enabled on the unreliable CTPs involved in the protection
(default
value)
sncpNpref: the SNCP/N type has to be preferred for all the protected connections of the path/trail

Protection. For details see explanation at section Technical Annexes.


Specifying SNCP, the user requests to find the best protection by minimizing the number
of overlapping NEs and physical connections. Select SNCP type

Figure 101. Protection selection


D&C
For paths and trails with the protection type set to D&C, RM should be able to perform the automatic adding
of drop & continue connections when the main and the spare cross the same SNCP NPA ring.
In previous RMs, D&C was added considering ETs and Subnetworks.
In case of unsatisfactory results of the automatic algorithm, D&C can now be added or removed manually
specifying the start and end points.

The following rules are also used:

1AA 00014 0004 (9007) A4 ALICE 04.10

The D&C must use only the resources of the NPA and protects only one direction.
D&C related to adjacent NPAs are merged together producing dual node crossconnections in the involved NEs
Unneeded changes of rings is one of the possible source of wrong D&C protections
The NPA can be used as a type of constraint for paths & trails. The constraint types are:

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

116 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 100. Path SNCP type

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Use main. The main route of the path must use at least one of the physical links belonging to the NPA.
At Lower Order the LC satisfying this constraint must be completely contained in the NPA (i.e. its server
trail must use only physical connections internal to the NPA)
Use spare. (as before changing main with spare)
Dont use main
Dont use spare

The add protection and D&C can now be performed without any limitation related to the partitioning (i.e.
to the involved topologies):
any Node of the main can be selected as a starting or ending point of an added spare protection.
No constraint exists anymore on the way to perform the network construction in order to allow path/trail
protections
The add/remove protection and add/remove D&C is performed from a wizard that allows to select the right
TPs or Nodes for the specified operation (protection in a NPA to be confirmed)

MS Protection Usage Profile. For details see explanation at section Technical Annexes.

Figure 102. MS Protection Usage Profile

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Click on Next button. The wizard presents now the Step 2 dialog box.

01

SC.3:OPERATION
3AL 61348 AA AA
258

117 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

B
NODE
A
NODE

A TTP LIST

MAP

B TTP LIST

LIST
B
NODE

A
NODE SELECTION

LIST

MAP

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 103. Path Create: step2


d)

By clicking on the node selection button, you will get the list of the nodes, suitable to create the
connection. From the node list, select the node and click on Apply button. The icon of the selected
node is now displayed in the source node drop area. This step can be skipped if the node has been
already selected on Netview or on Browser.

e)

Select the terminating node and of the terminating NAP. It is analogous to the point above described
for source node/source NAP selection.

f)

If you click on Next button, the port is automatically selected

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

118 / 258

g)

Select the NAP and click on Apply button. The NAP icon is displayed in the NAP drop area. See below
figure.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ANODE

BNODE

ANAP
BNAP

ANAP LIST

BNAP LIST
Figure 104. Example of NAP selection

N.B.

1AA 00014 0004 (9007) A4 ALICE 04.10

h)

ED

End points: NAPs or Nodes can be provided as end points.


In case of a Node used as end point,

if it is not virtual, the first available NAP is chosen

if it is a virtual node, a PDH port and corresponding NAP are created associated to
the node, with the required rate and with name derived from the path name
Click on Next, passing to Step 3Attributes selection. See figure which follows. Select:

01

SC.3:OPERATION
3AL 61348 AA AA
258

119 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 105. Path Create: step 3

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

120 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONFIGURATION

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Allocation rule ( User / Automatic )

Allocation Rule: it specifies if the path has to be allocated automatically after its definition
or subsequently upon users command.

Implementation rule ( User / Automatic )

Implementation Rule: it specifies if the path has to be implemented automatically after having been allocated or following an users request.

Allocation Constraint ( All Objects / Not Alarmed Objects )

Algorithm ( Automatic )

ALARM

Propagation rule ( when defined / when allocate / when implemented /when commissioned )

Client Alarm Enabling Rule ( On Implementation / On commissioning / Manual )

Transport Alarm Enabling Rule ( On Implementation / On commissioning / Manual )

ROUTING
Routing parameters for paths and trails
Main & Spare Cost gravity Factor
It indicates how strongly Main & Spare have to be forced to go in the same NPA
If equal 0 it has no effect.
As bigger is set as more the cost of NPA internal routes used by the Main is decreased attracting the spare.
Disjoint ness is in any case considered.
D&C Cost Factor
It has effect only in 2f MSSPRings and it is an indicator on how much the D&C has to be preferred
compared to another route without D&C. A value of 3 means that D&C is preferred only if has at most three
times the cost of the optimised root.
It works increasing the cost of the arcs in the direction where the D&C cannot be performed (opposite
direction of the main). In previous RMs was always forced producing in some conditions not optimised
routes
N.B.

If the user, when creating the path, selects Alarm Enabling Rule: Manual, for this Path it will be
possible to enable / disable the involved alarms ( from the Path List: menu Actions: SDH/PDH
Alarms enable/disable.

1AA 00014 0004 (9007) A4 ALICE 04.10

USER

Comment12, Customer, Text123 are text strings

Path Group , to be used when defining multiple paths belonging to the same path group

Automatic Monitoring ( True/ False ). If true starts the 24 h PM activity on path implementation

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

121 / 258

Restoration Mode ( No Restoration / On Control Plane )

Priority of the path in the ASON network

i)

Click on Finish button. The path is created and the routing view is displayed.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CP RESTORATION. It contains:

Figure 106. Path just created


N.B.

Fast Ethernet boards have been already correctly setup on the Equipment via 1353NM.

3.2.2 10/100Mbits Ethernet management (point to point)


The 10/100 Fast Ethernet board acts as a gateway towards the SDH network and is connected to
the SDH matrix via a STM4 equivalent interface. Each of the 10 or 100Mb/s Ethernet traffic interface of the board is mapped in a set of VCn (n=12, 3 or 4).
The Ethernet traffic is transported transparently in the SDH network: the board on the OMSN NE
drops Ethernet traffic towards switches or router without terminating the Ethernet frames.
Two cards constitute the board: an access card that provides 14 interfaces and a main one that provides 11 interfaces. The Ethernet traffic, mapped in the SDH transport structures, is then sent towards
the SDH matrix via a STM4 equivalent interface.
To setup an SDH path supporting, as client, the Ethernet traffic, execute the following steps:
a)

upload the Data ports. The uploaded ports are created in the RM MIB. The technology of the ports
is Data

b)

upload the Data NAPs. As a consequence of this operation the generic Data NAPs are created in
the RM MIB (no interaction with the NE)

c)

create a path connecting two Data NAPs. The user enters the following information:
the two Data NAPs

1AA 00014 0004 (9007) A4 ALICE 04.10

the type of the server SDH container (tu12, tu3 or au4) or ( tu12nV tu3nV ). If the user selects
the virtual concatenation ( tu12nV tu3nV ), he will enter the number n ( no. of TUs ).
In the fact the path creation includes the specification of the VCs. As a consequence, data NAPs are
created in the NEs accordingly.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

122 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 107. Fast Ethernet board

Figure 108. Fast Ethernet board view

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

123 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 109. Fast Ethernet board: Port view

Figure 110. Objects on browser.

3.2.3 Multi Path Create

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 111. Multiple path creation button


If the Operator selects the Multipath Create button, ( see above figure ), a dialog box is displayed. The
following values must be specified:

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

124 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 112. Multi path creation

Number of paths (numerical value)


Starting (numerical value)
Append (radio button)
Replace (radio button)

If Append is selected, the path sequential numbering is added as a suffix to the name of the path.
If you want to insert the sequential numbering in the inner of the path name, the userlabel containing the
%nd characters should be written where n corresponds to the numbering field size. In this case you have
to select Replace.
The Associate feature is provided (same route) if the following are selected:
number of paths

>1

starting

any

This feature allows to associate as constraint the first created path. The user can carefully setup the
first created path. The remaining ones will have the same route.
NOTE: Only nodes must be specified in this procedure.
3.2.4 Constraints
SDH routing is performed on a cost basis. This means that a route having the least cost will be used when
setting up a path.

1AA 00014 0004 (9007) A4 ALICE 04.10

The user can specify some constraints to be used by the allocation algorithm either during the path allocation or the path add protection activities. These constraints are used to:

ED

specify the involved resource,

indicate if the path has to cross the specified resource or not,

01

SC.3:OPERATION
3AL 61348 AA AA
258

125 / 258

The user is informed at the end of the allocation activity.


Execution of path operations can be scheduled to a specified time.
The user is able to protect/unprotect a path in a given topology or in the whole network.
3.2.5 Path Constraints

Path constraints allows the user to specify the constraints to be used by the allocation algorithm during either the allocation or the protection activity or the addition of a leg in a broadcast path (i.e. Allocate path and Protect path services broadcast path end point add). The user specified constraints
overrides the cost based allocation policy.
The constraints are defined by the following characteristics:

Involved resources : they can be subnetworks, ETs, nodes, link connections, physical connections, CTPs, server trails and routing links.

Constraint type : it specifies whether the path must use the specified resources or not

Route Type : it specifies if the constraint is applied for the main route only, for the spare route
only or for both routes.

1AA 00014 0004 (9007) A4 ALICE 04.10

UPON CREATING A PATH AND SPECIFYING THE NOT ALARMED RESOURCES ONLY OPTION, RM ONLY TAKES INTO ACCOUNT THE ROUTING RESOURCES AND NOT THE NAP
ONES.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

126 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

specify if the constraint has to be applied to the path main route or to the spare one or both;

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.3 1 Gigabit path


The system is able to support the GigaEthernet rate adaptive on single VC4 virtually concatenated
(VC41v).
The following table lists the foreseen services to be supported by RM and the mapping with the Transport
rate inside the Transport Network:
SERVICE TYPE

SERVICE RATE

TRANSPORT RATE

ETHERNET

1 Gbit/s Ethernet transparent

AU4nV
(concLevel=8)

1 Gbit/s Ethernet Rate adaptive

AU4nV
(concLevel=17)

10/100 Mbit/s Ethernet Rate TU12nV


adaptive
TU3nV
AU4

Paragraphs which follow describe:

1 Gigabit transparent path. See para 3.3.1 on page 127

3.3.1 1 Gigabit transparent path


DEFINITION
The 1 Gigabit transparent path makes use of a virtual concatenation of 8 AU4s to support the AU48V
connection rate.
The connections in topology between the 1 Gigabit NAP and the CTP are fixed, i.e. they cannot be
changed or deleted by 1354RM.
With reference to Figure 113. , the 8 trails, which are virtually concatenated can be allocated to different
routes within the network
connection in topology FIXED

LC

AU48V

CTP
CAP1

1AA 00014 0004 (9007) A4 ALICE 04.10

CAP8

CTP
hotrail1
hotrail8

AU41
AU48

Figure 113. 1 Gigabit connection structure

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

127 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.3.1.1 Create 1 GB transparent path

The following figure show an example of creation of 1 GB transparent path

Figure 114. GB Eth path create step1

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

128 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 115. Path create step 2


3.3.1.2 Display 1 GB transparent path

1AA 00014 0004 (9007) A4 ALICE 04.10

The path routing display is shown in the following figure. Notice that the link connection configuration
state is implemented. Click on Server trail icon. The trail list of the 8 virtually concatenated trails is
displayed. See Figure 117.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

129 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 116. 1 Gigabit path routing display

Figure 117. Trail list


If all 8 trails are allocated, the attribute Server connectivity of the path is equal to fully connected.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

130 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

If only some trails are allocated, the attribute Server connectivity of the path is equal to partially connected. In this case the operator may add resources and subsequently allocate trails whose working
state is fail to allocate.
d)

Launch path implementation. The system executes the implementation of the 8 trails.
It is possible to launch path implementation also on a path having some trails allocated and some
defined. In this case the path goes implemented, its defined trails remain defined, the allocated trails
go implemented or partially implemented.

3.3.1.3 EXAMPLES
EXAMPLE 1
A path has 7 trails allocated and 1 trail fail to allocate. By launching the implementation on the trail failed
to allocate, the server connectivity of the path goes fully connected.
EXAMPLE 2
A path has 1 trail allocated and 7 trails defined. By launching the deallocation on the allocated trail , the
path goes defined and all involved trails are deleted.
EXAMPLE 3
A path is allocated. By launching the implementation on one trail , the path goes partially implemented

3.3.1.4 1 GBit path protection


The Add Protection operation is available for the entire path or at trail level.
The protection can be viewed on the trail routing display.
3.3.1.5 Constraints
Constraints can be given at level of path or at level of trail. As usual, the system makes use of constraints
during allocation phase.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure which follows shows an example of constraint setup.

Figure 118. Path: Modify Constraints

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

131 / 258

3.3.2 1 Gbit/s Ethernet Rate Adaptive

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The 1 Gbit/s Ethernet Rate Adaptive path can have rate AU4nV with n=17.
An example is shown in figures which follow.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 119. 1 Gbit/s Ethernet Rate Adaptive path attributes

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

132 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

TRAIL LIST

Figure 120. 1 Gbit/s Ethernet Rate Adaptive path routing display

Figure 121. 1 Gbit/s Ethernet Rate Adaptive path trail list

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

133 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The User, directly to a Server HO Trail, can perform the Allocation, Deallocation, Implementation, Deimplementation, Add protection, and Remove protection operations.
The operations allowed on the server HO Trail depend only on their configuration state, regardless the
GbE concatenated path configuration state. The path working state is checked in order to avoid concurrent
operations.
The configuration state and server connectivity of AU41v link connection and concatenated path are always reevaluated. After an add/remove protection applied to a server trail, also the path protection type
is reevaluated.
3.3.2.2 GbE Path Route, Server HO Trails and GbE Path Attributes display
The Operator can visualize the routing of a GbE Path and from the route display of GbE paths, starting
from the AU41v LC, it is possible to retrieve all the server HO Trail.
In addition for the HO Trail participating in the virtual concatenation group (also if only in this particular
case), it is possible to retrieve the client GigE Path or the AU41v LC.
3.3.2.3 Redolog
The system will trace in the redolog all the operations performed by the User on a concatenated path and
on the server HO trail.
3.3.2.4 GbE Path and Server HO Trail Alarms
Elementary Alarms related to the GbE Ports, NAPs, CAPs, CTPs are correlated to the Server HO Trail
and GbE Path, which affect the GbE functionality.
Alarms related to the HO Trail are managed as usual, while alarms related to a GbE Paths are issued when
the GbE service is affected.
3.3.2.5 GbE Path Highlight

1AA 00014 0004 (9007) A4 ALICE 04.10

The system, as for all the other type of paths, allows to highlight on the Map where a GbE Path is passing
through.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

134 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.3.2.1 Operations on server HO Trail

3.4 LCAS Management

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LCAS (Link Capacity Adjustment Scheme), is a protocol that improves Virtual Concatenation.
This protocol applies to the following boards:

boards belonging to the Integrated Service Adapter (ISA) board family, named ES1 and ES4. The
ES1 board has a throughput, towards the SDH network, of 155Mb/s while the throughput of the ES4
one is 622Mb/s.

ISA Gbe ( with LCAS )

The management of these boards makes use of LCAS (Link Capacity Adjustment Scheme), which is a
protocol that improves Virtual Concatenation, allowing to:
hitless increase/decrease the capacity of a Virtual Concatenation Group ( VCG ) link
temporarily remove a member link that was affected by a failure (this member is hitless added again after
failure recovery)
This paragraph describes the following procedures:

Path creation

Optimized diverse routing of server trails

LCAS enabling/disabling on an already defined path

LCAS parameters configuration

3.4.1 Path creation


3.4.1.1 10/100Eth Rate Adaptive (no concatenation) service
The usual information to create this type of path has to be provided by the user.
3.4.1.2 10/100Eth Rate Adaptive (virtual conc.) & 1Gbit Eth Rate Adaptive services
a)

The user, to create a path, has to provide the following information:

serviceType=Ethernet
serviceRate of the path eth1GbRateAdapt / eth10or100MbRateAdapt
type of the server SDH container to be used to transport the traffic (transportRate). The allowed values
are:

au4nV for eth1GbRateAdapt (automatically provided by the system)

tu12nV or tu3nV for eth10or100MbRateAdapt

concLevel of the path

1AA 00014 0004 (9007) A4 ALICE 04.10

all the other information required for the path creation (user label, ...)
The list of the NAP is available to the user, satisfying the following conditions:
napRate attribute matching the service rate of the path

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

135 / 258

If the user selects the NAPs, the compatibility of the two selected NAPs is verified accordingly.
N.B. The user can select the node instead of one or two NAPs. The compatibility of the two NAPs is automatically verified.

1AA 00014 0004 (9007) A4 ALICE 04.10

At this point, the lcasControl and the diversesrvTrailsRoutingPreferred attributes of the path are set
according to the following table:
Aend type

Zend type

LCAS control

server trails rout- proposed/modifiing


able to/by the
user NOTE 2

virtual node

virtual node

enabled

diverseRoutingPreferred

virtual node

real node

enabled

diverseRoutingPreferred

virtual node

nap
not available
conc type DIFFERENT FROM virtualLCAS

uniformRoutingPref

virtual node

nap
not available
conc type = virtualLCAS

diverseRoutingPreferred

real node

real node

NOTE 1

real node

nap
not available
conc type DIFFERENT FROM virtualLCAS

uniformRoutingPref

real node

nap
NOTE 1
conc type = virtualLCAS

NOTE 1

nap
conc type DIFFERENT FROM virtualLCAS

nap
not available
conc type DIFFERENT FROM virtualLCAS

uniformRoutingPref

nap
nap
not available
conc type DIFFER- conc type = virtualENT FROM virtual- LCAS
LCAS

uniformRoutingPref

napconc type
virtualLCAS

diverseRoutingPreferred

ED

01

NOTE 1

= nap
enabled
conc type = virtualLCAS

SC.3:OPERATION
3AL 61348 AA AA
258

136 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

au4maxSupportedConcLevel (tu3maxSupportedConcLevel, tu12maxSupportedConcLevel) equal or


greater than the concatenation level of the path

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

NOTE 1. The values of the two attributes are calculated by the TRS (Transport Management process)
taking into account the type of the two NAPs chosen by the TRS itself.
NOTE 2. The Y value in the column means that the values specified in the two previous columns are presented to the user and he can modify them in the path creation phase; the N value means that the values
specified in the two previous columns are not presented to the user and are automatically set by the TRS.
b)

The user launches the path creation. The path is created.

The following steps are performed on the two involved NAPs:


the lcasControl attribute is set according to the value of the lcasControl attribute of the path. In particular:
if the lcasControl attribute is equal to enable, the lcasControl attribute of the two involved NAPs is
set to enable
if the lcasControl attribute is equal to disable, the lcasControl attribute of the two involved NAPs is
set to disabled
if the lcasControl attribute is equal to notAvailable, the lcasControl attribute of the two involved NAPs
is set to notAvailable. Anyway, if one of the two NAP has the concatenationType attribute equal to
virtualLcas, the lcasControl attribute of the NAP itself is set to disable
3.4.2 Optimized diverse routing of server trails
If the user, during the path creation selects the diverse routing option (diversesrvTrailsRoutingPreferred
attribute of the path equal to diverseRoutingPref), the allocation of the server trails will apply the diverse
routing mechanism. In particular:
the trail numbered n+1 (even) has to have a different routing from its previous trail numbered n (odd)
So a fault (i.e.cut fiber) impacts only a route providing anyway a minimum level of functionality.
If there are not resources problem, this diverse routing mechanism allows:
to have the 50% of the server trails on a route and the other 50% on another route
to add and remove bandwidth maintaining the distributions of the server trails on the two diverse routing
These points cannot be guaranteed when the network resources are not enough to allow the diverse routing. In this case, the odd and the even trails could have the same route (partial or total).

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B. The user can modify the srvTrailsRouting attribute of an already created path in any allowed configuration state (confSt equal to defined, allocated, implemented, ...). In this case the new provided value will
be taken into account for the allocation of new trails (the already allocated trails are not rerouted).

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

137 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 122. Server trail routing modification

3.4.3 Path removal


When a path is removal, the lcasControl attribute of the two involved NAPs is set according to the Port/NAP
configuration table paragraph in this document.
3.4.4 Add/remove bandwidth
It is possible to add/remove bandwidth to/from a concatenated path increasing/decreasing its transport
rate (changing the number of the server trails). This is performed by means the modification of the concatenation level attribute of the path.
The trails are added/removed started from the last existing trail. This means that no intermediate trails can
be added or removed.

3.4.5 Activation/deactivation of an intermediate server trail


The intermediate trails can be activated/deactivated, that is included/excluded in/from the concatenation
group. In case of deactivation, the transport resources are not released.

3.4.6 LCAS enabling/disabling on an already defined path

1AA 00014 0004 (9007) A4 ALICE 04.10

The lcasControl attribute allows the interworking between an NE not providing the LCAS protocol and
another providing it. This means that a path can be allocated between an end point supporting the LCASprotocol and another no: the LCAS protocol has to be disabled on the end point supporting it.
To have the LCAS functionality, the LCAS protocol has to be enabled on both the end points.

The user, on the User Interface, has to select the path and to choose the LCAS control command.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

138 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

N.B. LCAS protocol can be enabled/disabled also in the path creation phase. See following figure.

LCAS CONTROL ENABLED

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 123. Path create:ethadapt:es:step 3: LCAS

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

139 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 124. Path: Modification: Lcas control menu

Figure 125. Path: Modification: Lcas control dialog box

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

140 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.5 Compatibility tables

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The following tables list the compatibility between the NAPs rate, the Ethernet mapping, the Transport rate
and the Service rate of the path.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

141 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

142 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

143 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

144 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

145 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Path Service rate: 1 Gb transparent

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

146 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

147 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The ports supported by the 16xGbE board in the 1678MCC R3.1A or later are compatible with all the portsproviding a 1GbEth Rate Adapter service. The particularity of these ports is that they can work only with
a fixed rate (vc47V).
To create a path involving one or both these ports, the usual information to create a normal eth1GbRateAdapt path have to be provided by the user. Concerning the concatenation level value, RM does not check
that it has to be equal to 7. This means that if the user specifies a different concatenation level value RM
does not return any error: the error will be returned only by the NE.

1AA 00014 0004 (9007) A4 ALICE 04.10

It has to be noted that the server trails related to the path (or only a part of them or none) can cross the
ASON domain.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

148 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.5.1 Path creation using 16xGbE boards

3.5.2 Rate adaptive path : Modification: Bandwidth

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to modify the banwidth of a rate adaptive path.

SEQUENCE
a)

From the path list point to the rate adaptive path and select Path: Modification: Bandwidth. The wizard
dialog box opens.

b)

The user can:

ED

1)

verify the concatenation status:

Maximum supported concatenation level

Total concatenation level

Active concatenation level

2)

select the action:

Increase bandwidth

01

SC.3:OPERATION
3AL 61348 AA AA
258

149 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 126. Modification: Bandwidth: Increase bandwidth


If you select Increase bandwidth you will enter:
the no. of trails to add

1AA 00014 0004 (9007) A4 ALICE 04.10

the status of the added trails : Defined / allocated / implemented / Activated


trail(s) protection type: None, SNCP, D & C SNCP
Click on Finish button to complete the action. The action report is provided.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

150 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 127. Action report: Increase bandwidth

1AA 00014 0004 (9007) A4 ALICE 04.10

From the path routing display, clicking twice on the DISPLAY SERVER TRAILS icon, you can display the
trail list of the involved path.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

151 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

DISPLAY SERVER TRAILS (click twice)

Figure 128. Display server trails button.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

152 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ADDED TRAIL
Figure 129. Server trail list
The created trails are added as the last items of the trail list

Decrease bandwidth

If you select Decrease bandwidth you will enter:


the no. of trails to remove
automatic deactivation or not of active trails to remove
Removed trails are the last items of the trail list

Activate trails

If you select Activate trails you will enter:


the no. of trails to activate

1AA 00014 0004 (9007) A4 ALICE 04.10

Trails are activated sequentially starting from the first idle trail.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

153 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 130. Modification: Bandwidth: Activate Trails

Deactivate trails

If you select Deactivate trails you will enter:


the no. of trails to deactivate

1AA 00014 0004 (9007) A4 ALICE 04.10

status of the trails being deactivated ( deactivate / deimplement / deallocate )


Trails being deactivated are the last active ones.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

154 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 131. Modification: Bandwidth: Deactivate Trails

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

155 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.5.3 Path: Ethernet mapping

This procedure allows to define the Protocol format to be used for an Ethernet path.
CONDITIONS
Path status is defined or allocated
SEQUENCE
a)

Point to the Ethernet path and select Configuration: Ethernet mapping. The relevant wizard is displayed.

Figure 132. GFP Protocol Modification wizard


b)

You can select among:


null extension header with FCS (used for interworking between Ethernet and ISA/IP board)
null extension header without FCS (used for interworking between Ethernet and other vendors
board)

1AA 00014 0004 (9007) A4 ALICE 04.10

linear extension header with FCS (used in case of grooming Ethernet interfaces into a single vcn)
linear extension header without FCS (used in case of grooming Ethernet interfaces into a single
vcn)
c)

ED

Click on Finish button to confirm.

01

SC.3:OPERATION
3AL 61348 AA AA
258

156 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE

3.6 Path Allocate,Implement, Commissioning and Display

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This paragraph describes the commands used to modify path configuration state and to display the path.
3.6.1 Path Allocate
The Path state is defined after having been created. The operator can allocate the path, i.e. the network
resources can be assigned to it.
a)

Open the Path list: from the Browser point to the Network icon and issue the Display: Related items
pop up command. From the list of the available items select Paths in Topology and click on button
No Filter.

Figure 133. Path list


b)

From the list select the path to allocate and select the Actions: Configuration: Configuration State
Modification: Allocate pulldown menu. This command is also available as popup menu.
A warning box alerts: Action correctly started... .
The Path working state changes from allocating to normal at the end of the allocation.

1AA 00014 0004 (9007) A4 ALICE 04.10

The Path configuration state changes from defined to allocated at the end of the allocation.
N.B.

The Path Allocation can be executed only if the network is properly configured.

N.B.

The allocation of a certain path can be prioritized with respect to the allocation already
requested for other paths if you enter Configuration: Configuration State Modification: Allocate
with Priority

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

157 / 258

a)

From the Path List select the path and the Actions: Configuration: Configuration State Modification:
Implement pulldown menu item. This command is also available as popup menu.

The Path Implement activity consists in sending commands to the NEs in order to set up the NE internal
connections.
The Path working state changes from implementing to normal at the end of the implementation.
The Path configuration state changes from allocated to implemented at the end of the implementation.
3.6.3 Path Commissioning
a)

From the Path List select the path and the Actions: Configuration: Configuration State
Modification:Commission pulldown menu item.

1AA 00014 0004 (9007) A4 ALICE 04.10

When the path is in this state no other operations are possible except for path decommissioning and
performance monitoring and TCAs enabling/disabling. (Threshold crossing).

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

158 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.6.2 Path Implement

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.6.4 Displaying the path route


It is possible to display the path route for allocated, implemented and commissioned paths from browser
or path inventory applications and from SDH netview.
3.6.4.1 Path route from Path List
From the Routing Display window you can display the Route Report by selecting View: Report: Route
full....

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 134. Route report example

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

159 / 258

3.6.4.2 Path Routing view

From the Path Routing view you can display the route report of the path by entering the command View:
Report: Route full. An example of report is shown in Figure 134.
The Path Routing view wholly represents the connectivity objects belonging to a defined path.
The view is subdivided into vertical columns (named Main, Spare, Service), each of which represents a
whole route.
Some cases can be distinguished:

in case of an unprotected path the Main route is only available;


if the path is of the SNCP protected type, the Main route and the Spare one are available;
if the path is of the D&C SNCP protected type, all the route graphical representations are present:

Main
Spare (more than one spare route can be present)
different service routes

The number of service and spare connections depends on how the path has been constructed.
Moreover if the path is broadcast, the different legs are separately represented.
The main and spare routes are represented for each leg if the path is of the broadcast and protected type.
3.6.4.3 Main Route
The Main route graphical representation comprises (in the area relevant to the first column):

on the upper lefthand side the connection in topology icon at network level
From the first row on are listed the connections in topology at subnetwork level and eventually the
first connection in topology at level of Elementary Topology (ET).
Note that for each connection in topology, a continuous vertical line permits to identify the end points.
If one connection in topology is inside one route only, the vertical line directly connects the TPs (TTPs
or CTPs) involved.

On the righthand side of the different connections in topology the first end point (NAP) is depicted, hence
in the column are displayed the CTPs and the link connections connecting the CTPs belonging to different
nodes.
The link connection icon contains the label describing the relevant payload position.
The representation of the Switch connections in topology ( either Switch or Bridge & Switch ) contains
an icon (Resource Type) indicating the actual switch status. It can be:

M
S

Main
Spare

The switch is set at Main


The switch is set at Spare
It is used only for a D&C type switch, i.e. for the service type connections. It
indicates that the switch is set at Service.

1AA 00014 0004 (9007) A4 ALICE 04.10

The connection in topology of the Switch, B&S, or Service type may also contain the Operation Mode
information (bidirectional arrow) which can be Revertive or not Revertive.
N.B.

ED

The Path Routing View permits to display the actual route of the path. For this purpose the
switch Resource Type indications should be analyzed. In the following Figure 135. are given
two examples:

01

SC.3:OPERATION
3AL 61348 AA AA
258

160 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This view displays the complete path route including the main resources dedicated to the selected path.

MAIN
M

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

MAIN

SPARE
SPARE
Figure 135. Actual route

Figure 136. Path Routing example


Clicking on the group icon Routing display located on the view next to the link connection, it is possible
to display the objects relevant to the Link Connection at higher order .

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

161 / 258

N.B.

For a path crossing a NPE Ring the path routing view displays the Main route: the link
connection label contain a R or a U to identfy if the path is a High Priority (HP=Reliable)
or a Low Priority (LP=Unreliable). HP paths make use of the Working capacity; LP paths make
use of the Protection capacity.
For a path crossing a NPE Ring, the user can verify the connections on the traffic map.

3.6.4.4 Path route on the map


The scope of this procedure is to display the path/trail route in the Netview maps. The Highlite/Locate
button is present in the Path list/ Trail list and in other drawing windows containing the object to show( Naps
view, Routing view, Paths in Trail, Physical connection...etc). The sequence listed herebelow refers to the
locate of a path from the path list.
Notice that the view is not automatically refreshed after a modification of the protection (Add/Remove
protection) ; in this case the sequence of operations must be executed again.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

From the path list select the path to display and click on Highlight/Locate button.

Figure 137. Highlight button.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

162 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Clicking on Nap view button inside the icon bar it is possible to open the view to display all paths
terminations.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1)

If the transport is not protected the following are displayed: ( see icons in the figure below)

mainnap

mainnapservice

mainsparenap

mainspareservicenap

Parent Flag

Object Flag

Figure 138. Symbols used by Hyghlight feature

LOCATE

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 139. Path Locate button

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

163 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 140. Example of Path locate on subnetwork map

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

164 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 141. Example of protected Path locate

MAIN
SPARE

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 142. Locate path: protected on the same link group


N.B.

ED

Sometimes happens that asking for Path Status in Physical Connection the status of the path
is indeterminate even if the traffic is stable in the physical connection.

01

SC.3:OPERATION
3AL 61348 AA AA
258

165 / 258

an operation is already in progress on the PATH/TRAIL. TRS agent inhibited the operation
NE_G/NE is unreachable
NE fault

1AA 00014 0004 (9007) A4 ALICE 04.10

The first case is a tipical situation when different users execute at the same time the same operation. The
same situation is also reached if the same user asks many times the same operation.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

166 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

A path is indeterminated when it is not possible to synchronize switches on the NEs. The reason of the
failure of the synchronization could be:

3.7 Service state modification

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

DEFINITION
This feature allows to declare the Service State ( INSERVICE or NOT_IN_SERVICE) for a transport entity.
The transport entities involved are:

physical connections (automatically propagated to the related HO/MS trail

client/path

The INSERVICE declaration is entered by the user for:

implemented physical connections

implemented or partially implemented OCH/HO Trail

client/path (implemented / partially implemented / commissioned)

The NOT INSERVICE declaration is issued by:

user for physical connections / OCH/HO Trail / client/path

system for physical connections / OCH/HO Trail / client/path at deimplementation

1AA 00014 0004 (9007) A4 ALICE 04.10

Alarms on INSERVICE or on NOT INSERVICE entities are automatically acknowledged by AS. Separate counters are provided, namely:

alarms on both INSERVICE or on NOT INSERVICE entities

alarms on INSERVICE entities

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

167 / 258

EXAMPLE OF SERVICE STATE MODIFICATION

a)

Point to the physical connection to modify and issue the popup menu item Configuration: Service
State Modification

b)

A dictionary is displayed, allowing to select between INSERVICE and NOTINSERVICE. Select


the desired service state and click on OK button.

Figure 143. Service State Modification box and dictionary

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

It is possible to supervise the successful Service State Modification on the AS Counter Summary.

01

SC.3:OPERATION
3AL 61348 AA AA
258

168 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE

3.8 Path /TrailConstraints

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCCPE
This procedure allows to setup constraints on a path or trail, i.e. to get/exclude the use of certain
resources for a path or trail.
CONDITIONS
The use of the constraint/s allows the operator to execute:
fully manual allocation. The path route can be fully specified, including the payload position. Namely the
user can specify the lower order link connection as constraint.
partially automatic allocation. The user specifies only a part of the route. The allocation algorithm
completes the research of the route resources.
WARNING
The constraint is accepted as mandatory condition by the allocation algorithm, so the path/trail allocation
will fail if a constraint cannot be satisfied. If a path/trail allocation fails, the user is fully informed by the Path
Fail to Allocate tool. See Section Maintenance of this Handbook.
OPERATION
The Path Constraints can be always issued but they will be taken into account during the path allocation
phase: so if the path is implemented, the operator must deimplement and deallocate it and subsequently
issue a new allocation.
Trail Constraints can be always issued but they will be taken into account during the trail setup phase:
so if the trail is set, the operator must deimplement and deallocate it and subsequently issue a new
allocation.
SEQUENCE
a)

In order to create a new constraint, select the path from Path List and click on the Path Constraints
tool button.

b)

The Path Constraints dialog box is opened. See Figure 144. on page 170 Two possibilities are
available:
1)

From Browser select the object to utilize as a constraint. The objects available are:

1AA 00014 0004 (9007) A4 ALICE 04.10

2)

topological objects: node, subnetwork


physical connection
ctp
routing link
lc
path
trail

From the map (Netview) create the constraint by selecting the object to utilize as a constraint
and the Path: Constraint pulldown menu .

In this manner the object is added in the constraint list.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

169 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Path/Trail drop area


Constraint drop area

Figure 144. Path Constraints dialog box


After having added the constraint/constraints, for each constraint the selection is done between Use
Main and Use Spare for an unprotected path.

1AA 00014 0004 (9007) A4 ALICE 04.10

If a protected path is involved selection concerns:

ED

Use Main
Use Spare
Not use Main
Not use Spare
Use Main and Spare
Not use
Use Service (for a D&C protected path)
Not use Service (for a D&C protected path)
Overlapped if the object utilized as a constraint is a path
Disjointed if the object utilized as a constraint is a path

01

SC.3:OPERATION
3AL 61348 AA AA
258

170 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Use Main as A. This constraint can be applied only to a CTP, used as constraint to a unidirectional
or broadcast path. See Figure 145.

NAP
source
A

CTP

CTP

CTP

CTP

CTP

Figure 145. CTP as constraint.

Use Main as Z. This constraint can be applied only to a CTP, used as constraint to a unidirectional
or broadcast path. See Figure 145.

Use Main and Spare as A, if the main and spare route are using the same CTP as A termination.

Use Service Forwards

Use Service Backwards


The values Use Service Forwards and Use Service Backwards are significant for paths crossing a
Dual Node SNCP network.
The user drops as constraint one of the Physical connections between the two D& C nodes, or a link
connection, or a CTP, then must select between Use Service Forwards and Use Service Backwards.
If the user selects Use Service Forwards, the object dropped as constraint will be used as service
route/termination to protect the forward transmission direction (from A to Z or from the left to the right
or the TX). See Figure 146. herebelow.

1AA 00014 0004 (9007) A4 ALICE 04.10

If the user selects Use Service Backwards, the object dropped as constraint will be used as service
route/termination to protect the backward transmission direction (from Z to A or from the right to the
left or the RX). See Figure 146. herebelow.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

171 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

FORWARD

BACKWARD

THIS PHYSCON IS USED

THIS PHYSCON IS USED

AS CONSTRAINT:

AS CONSTRAINT:

USE SERVICE FORWARD

USE SERVICE BACKWARD

Figure 146. Use Service Forward/Backward for Dual Node SNCP network
Example of Path Constraint create

1AA 00014 0004 (9007) A4 ALICE 04.10

In the following an example of Path Constraint Create is given.


a)

Select the defined path from Naps view or from browser and click on Add Constraint button. The
Add Constraints window is displayed, already containing the defined path which will follow the
constraint

b)

Select the constraint to add, e.g. from the trail list select the trail and drag it with the middle mouse
button to the below region ( the constraint region ) of the Constraints window.

c)

By releasing the mouse button the constraint is placed in the Constraints window.

d)

Click on button Create.

N.B.

ED

The drag and drop operation must be used to declare the constraint, while the Add
Constraint button starts the Add Constraints application on the selected object.

01

SC.3:OPERATION
3AL 61348 AA AA
258

172 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.9 Adding /Removing a leg to a path


a)

From the Path List or from browser select the path (monodirectional/broadcast)

b)

Enter the command Add: Leg either by selecting the relevant tool button or by using the menu
Modification: Add Leg . See Figure 147. The Add Leg dialog box opens. The path icon is contained
in the path drop area. See Figure 148.

c)

Select the node from the browser/node list or the NAP from the nap list and enter the command Add:
Leg either by selecting the relevant tool button or by using the menu Modification: Add Leg. The
selected node now appears in the Leg drop area of the Add Leg dialog box. Alternatively you can
drag the node from browser to the Add Leg window, as per Figure 149.

d)

Click on button Add Leg. See Figure 150. The leg is allocated and implemented.

e)

Figure 151. shows an example of routing display of a broadcast path.

Removing a leg
Select the sink NAP to remove and issue the action Broadcast Path Modify: Remove Leg. It is possible
to release the NAP or to keep it associated to the path.

Figure 147. Add Leg menu item.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

173 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Leg drop area

ED

01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

Path drop area

Figure 148. Add Leg dialog box.

SC.3:OPERATION

3AL 61348 AA AA

258

174 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

BROWSER / MAP

DRAG

Figure 149. Drag from browser

Add Leg

Figure 150. Add Leg button.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

175 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 151. Routing display of a broadcast path.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

176 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.10 Path in NPE ring

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The attributes relevant to NPE features are:

Server MS protection usage profile: it represents the profile of the MS resources to be used in
allocating the path.
The possible values are:

ED

Normal

(default)

For 1664SM rings, the RIP mechanism is used, i.e. when crossing 4 Fibers MSSpring,
the path uses only working (high priority) resources, except for primary and secondary
nodes of the double interconnection with another ring, because these nodes are
characterized by the Drop & Continue protection ( RIP )
as a result, in the segment between service nodes:

if the path is bidirectional, the used resource (nodes E, D, H, I) can be only the
protection one: a bidirectional D&C IC on protection is performed in the primary
nodes (D, H);

if a path is unidirectional pointtopoint , the used resource is:

protection if the signal flows into the service nodes (B, C): a unidirectional D&C IC
on protection is performed in the primary node (B);

working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node (E); this allows the user to perform subsequent add
leg operation;
it is possible to use the protection resource instead of the working (nodes E, D), e.g.
forced by a constraint ;

if a path is broadcast , the used resource is:

protection if the signal flows into the service nodes (B, C) like in a unidirectional
pointtopoint path: a unidirectional D&C IC on protection is performed in the primary
node;

working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node);
it is not possible to use the protection resource instead of the working one.
As a result of the previous rules defined for unidirectional and broadcast paths, a
unidirectional pointtopoint path can become broadcast only if the working
resources are used between service nodes (nodes E, D ).

For 1670SM rings the path uses only working resources ( RIW )

Protection preferred
When crossing a 4 Fibre MSSpring, the path uses protecting (low priority) resources.
If the routing algorithm must use the working resource in one span of the 4F MSspring (e.g.
no free resources in the protection, or a constraint is applied), all working resources are used
in the ring, in order to avoid jumps between working and protection resources (jumps not
foreseen for the management of ring traffic map).
If the path is protected and main and spare routes are crossing the same MSSpring, each route
crosses separately the ring itself since D&C connection are not available for protecting
resources.
As a consequence of this behavior and of the fact that the SNCP connection is not available on
a 4f MSSpring, if the protected HO path is completely inside a 4f MSSpring, the allocation
will always fail.

Protection only
the path uses only protecting (low priority) resources.

01

SC.3:OPERATION
3AL 61348 AA AA
258

177 / 258

The procedure used to create a path crossing a NPE Ring is the same as described in the
previous paragraphs.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

N.B.

3.10.1 Examples of path crossing mixed rings


TX

SNCP

RX

NPE
F

SNCP

SNCP

RX

B
NPE

Equipment=1664SM
SNCP

1AA 00014 0004 (9007) A4 ALICE 04.10

TX
Figure 152. Bidir. Path, 1664SM, RIP

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

178 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

TX

SNCP

ED

01
B

E
C

NPE

RX

SNCP
SNCP

RX

A
B
NPE
C

F
E
D

Equipment=1670SM

SNCP

TX

Figure 153. Bidir path, 1670SM, RIW.

SC.3:OPERATION

3AL 61348 AA AA

258

179 / 258

3.11 Drop and Continue path

4Node Drop and Continue


D & C path in a 2Node SNCP network
Path Constraints in a 2Node SNCP network
D & C path in a 1Node Enhanced SNCP network
3.11.1 4Node Drop and Continue
(see Figure 154. on page 181, Figure 155. on page 182, Figure 156. on page 183, Figure 157. on page
183.)
Drop and Continue is a way of protecting a path crossing a number of subnetworks, e.g., rings.
The subnetworks should be connected through at least two nodes (so realizing two independent
connections).
The equipment is configured as DROP and CONTINUE on each interconnection node.
The subnetworks equipment implement the SNCP/I 1+1 connection.
The resulting architecture affords protection against multiple failures (evenly distributed one per
subnetwork) tolerated without traffic loss (node failure or single cable cut).
The traffic entities interconnected by the drop and continue feature can be TU12, TU3 and AU4.
The Drop and Continue feature improves traffic availability as compared with the simple endtoend
SNCP/I. More subnetworks are connected the further is availability increased.
The Drop and Continue features simultaneously realizes the following on one node:

unidirectional passthrough

protected drop

insertion in the opposite direction with respect tothe passthrough direction.

1AA 00014 0004 (9007) A4 ALICE 04.10

The configurations achievable are:

D/CW INSW

D/CE INSW

D/CE INSE

D/CW INSE

D/C stands for Drop and Continue, the letter after it (W=West, E=East) indicates the drop protected side
(e.g., W means West main side, and spare side is the EAST one).
The end letter (INSE or INSW) indicates the insert side.
The Unidirectional passthrough is always in the direction opposite to that of the insert side (e.g., when
INS E the passthrough is from East to West).

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

180 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The main topics described in this paragraph are:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

For further information refer to Figure 154. on page 181 which shows the D/CW INSW configuration.

WEST

AGGREGATES

EAST
Tx

Rx
Tx

Rx

TRIBUTARY

Tx

Rx

Figure 154. Drop and Continue D/C W INS W


The Drop and Continue featuring two connected rings
Figure 155. on page 182.

(with dual connection) is

indicated in

Nodes 3, 4, 6 and 10 are configured as Drop and Continue.


SNCP/I protection is enabled throughout the equipment. When in normal condition, the unidirectional way
of traffic from 1 to 8 is supposed to be:1, 2, 3, 6, 7, 8.
After a failure on the 1st ring between nodes 2 and 3 (see Figure 156. on page183 ), the link direction
is: 1 , 5 , 4 , 3 , 6 , 7, 8.
Passthrough is used between nodes 4 and 3, and switch on node 3.
After a second failure on the 2nd ring between nodes 6 and 7 (see Figure 157. on page 183) the selected
direction on the link is : 1 , 5 , 4 , 10 , 9 , 8.

1AA 00014 0004 (9007) A4 ALICE 04.10

The operative switch is on node 8 and the previous pass through between nodes 4 and 3 is no more used.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

181 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED
5

01
D/CW
3
INSW

D/CW
E
W

INS
W

INSW
D/CE
4

6
D/CE

258

INSE

INS
W

TRIB

3AL 61348 AA AA

INS
E

TRIB
E

INS
E

INSE
10
9

Figure 155. Drop and Continue

SC.3:OPERATION

182 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ED

01
5

3
4

6
10

7
9

Figure 156. Drop and Continue 1st failure

2
5

3
4

6
10

Figure 157. Drop and Continue 2nd failure

SC.3:OPERATION

3AL 61348 AA AA

258

183 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

With reference to a network like the one shown in Figure 155. select the end nodes and issue Tools:
Create Path.

b)

In the path create wizard select protection = D & C SNCP. Execute the complete sequence of path
create, as required by the wizard. Finally click on Finish button.

c)

The path is created and the NAP view is displayed.

d)

Allocate the path

e)

Clicking on Routing view button it is possible to display main, spare and service routes.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

184 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.11.1.1 Path create in D & C network with ADMs (4node D & C network)

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.11.2 D & C path in a 2Node SNCP network

ET1
1

1
2

ET2

1
ET3
1

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 158. Network submaps of the 3 2nd level subnetworks (ET1 , ET2, ET3) for 2 Node D & C

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

185 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2N D&C

ET3
ET1
tpA
tpAZ

tpZ

tpZA

tpAZ
tpA

tpZA
tpZ

ET2

SIDE A

SIDE B

Figure 159. Example Network.

1AA 00014 0004 (9007) A4 ALICE 04.10

The path create procedure described at para 3.11.2.1 herebelow refers to the example network of
Figure 158. and Figure 159.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

186 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.11.2.1 D & C path create in a 2Node SNCP network


The Path Create procedure is the same as described in the previous paragraphs, with the following
exceptions:

Rate=140 Mb,

Protection type=D & C SNCP.

3.11.2.2 D & C path allocate in a 2Node SNCP network


Upon path allocation, the system evaluates, as in case of basic D & C ( see Figure 160. )

main route

spare route

two service routes

1AA 00014 0004 (9007) A4 ALICE 04.10

SWITCH STATUS ICONS

The graphical appearance of this figure has been changed while contents maintain their validity
Figure 160. Routing view for 2N D & C path.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

187 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

If you click on the icon of the Switch status, the system opens a subwindow which displays the switch
status. Figure 161. shows the subwindows relevant to the routing display view of Figure 160.

Z
Z

ZA

ZA

AZ

AZ
A

MAIN ROUTE CONNECTION VIEW


( ref. 1,3,6 of Figure 160. )

SPARE ROUTE CONNECTION VIEW


( ref. 2,4.5 of Figure 160. )

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 161. Status switch subwindows for 2N D & C.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

188 / 258

ZA

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

AZ

DASHED LINE=SPARE SWITCH POSITION

LINE=MAIN SWITCH POSITION


= the actual switch position is MAIN
Figure 162. Main route connection view detail

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

The drawing of the switch shows the main switch position (line) and spare switch position (
dashed line). The actual switch position is marked by a M ( switch turned on main ) or S ( switch
turned on spare ). See above Figure 162.

01

SC.3:OPERATION
3AL 61348 AA AA
258

189 / 258

BOARD

NODE NAME

SUBRACK
RACK

PORT
Channel (N.A.)
PAYLOAD POSITION

Figure 163. CTP name detail.


N.B.

The CTP name ( see above figure ) contains the port name; then from the CTP issue Display:
Related items: Ports. From the Port issue Display: Related items: Physical Connection.

For the subwindow of Figure 161. the connections are:

tp A: comprises a switch for the connections coming from tp Z and tp ZA, one point to point from tp
A to tp Z, one point to point from tp A to tp AZ

tp Z: comprises a switch for the connections coming from tp A and tp AZ, one point to point from tp
Z to tp A, one point to point from tp Z to tp ZA

tp ZA: comprises one point to point from tp ZA to tp A, one point to point from tp Z to tp ZA

tp AZ: comprises one point to point from tp AZ to tp Z, one point to point from tp A to tp AZ
The default switch type is NOT revertive.
N.B.

As in the case of the normal D&C, it is not possible from the User Interface to select the TPs
involved in the D&C but they are automatically selected by the algorithm. The TPs can be
selected from the command mode because this is needed to support the redolog
functionality.

It is also possible to add or to remove the D&C protection to path without or with D&C protection. Relevant
commands are under menus:
Protection: Add submenu
Protection: Remove popup submenu
3.11.3 Path Constraints in a 2Node SNCP network
The values Use Service Forwards and Use Service Backwards are significant for paths crossing a
Dual Node SNCP network.

1AA 00014 0004 (9007) A4 ALICE 04.10

The user drops as constraint one of the Physical connections between the two D& C nodes, or a link
connection, or a CTP, then must select between Use Service Forwards and Use Service Backwards.
If the user selects Use Service Forwards, the object dropped as constraint will be used as service
route/termination to protect the forward transmission direction (from A to Z or from the left to the right
or the TX). See Figure 164.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

190 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CTP NAME DETAIL

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

If the user selects Use Service Backwards, the object dropped as constraint will be used as service
route/termination to protect the backward transmission direction (from Z to A or from the right to the
left or the RX). See Figure 164.

FORWARD

BACKWARD

THIS PHYSCON IS USED

THIS PHYSCON IS USED

AS CONSTRAINT:

AS CONSTRAINT:

USE SERVICE FORWARD

USE SERVICE BACKWARD

Figure 164. Use Service Forward/Backward for Dual Node SNCP network

3.11.4 D & C path in a 1Node Enhanced SNCP network


This connection is usefull to increase the protection level when a single NE is interconnecting multiple
rings.

1AA 00014 0004 (9007) A4 ALICE 04.10

In fact, a path supported by a single virtual ring between the end points A and Z, is not able to survive to
a double failure. See Figure 165. herebelow.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

191 / 258

1664SX cross connect equipment

Figure 165. Double failure for a SNCP path (w/o enhanced)

3.11.5 D & C path create in a 2Node SNCP network


The Path Create procedure is the same as described in the previous paragraphs, with the following
exceptions:

Rate=140 Mb,

Protection type=D & C SNCP.

3.11.6 D & C path allocate in a 2Node SNCP network


Upon path allocation, the system evaluates, as in case of basic D & C

main route

spare route

two service routes

1AA 00014 0004 (9007) A4 ALICE 04.10

If you click on the icon of the Switch status, the system opens a subwindow which displays the switch
status. shows the subwindows relevant to the routing display view of Figure 160.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

192 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

The graphical appearance of this figure has been changed while contents maintain their validity

Figure 166. Path routing view ( one node D & C )

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

193 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

DASHED LINE=SPARE SWITCH POSITION


LINE=MAIN SWITCH POSITION
= the actual switch position is MAIN

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 167. Enhanced SNCPone node connection detail.


N.B.

Figure 167. shows the involved connections . The default switch type is NOT revertive

N.B.

The drawing of the switch shows the main switch position (line) and spare switch position
(dashed line). The actual switch position is marked by a M ( switch turned on main ) or S ( switch
turned on spare ). See above Figure 167.

The implementation of the enhanced SNCP causes the creation of 4 unidirectional SNCP in the NE: .

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

194 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

tp A: comprises a switch for the connections coming from tp Z and tp ZA, one point to point from tp
A to tp Z, one point to point from tp A to tp AZ

tp Z: comprises a switch for the connections coming from tp A and tp AZ, one point to point from tp
Z to tp A, one point to point from tp Z to tp ZA

tp ZA: comprises one point to point from tp ZA to tp A, one point to point from tp Z to tp ZA

tp AZ: comprises one point to point from tp AZ to tp Z, one point to point from tp A to tp AZ

N.B.

As in the case of the normal D&C, it is not possible from the User Interface to select the tps
involved in the D&C but they are automatically selected by the routing algorithm. The tps can
be selected from the command mode because this is needed to support the redolog
functionality.

It is also possible to add or to remove the D&C protection to path without or with D&C protection by either
pointing to the topology where the interconnection NEs are included (e.g. the ET which contains the Cross
connect equipment) or to the whole path.
By using an enhanced SNCP the protection level of the path increases.
The default switch type is not revertive .

1AA 00014 0004 (9007) A4 ALICE 04.10

The RM behavior is as follows:

the enhanced SNCP is automatically inserted at path/trail allocation time for protected paths/trails
when the main and the spare are crossing the same NE and the equipment supports this type of
protection.

The user can add / remove the enhanced SNCP protection in two different ways:

ED

applying the add/remove service to the whole path/trail: the enhanced SNCP protection is also
removed

applying the add/remove service to the connection in topology at NE level: the enhanced SNCP
protection is modified only at NE level.

No limitation should be present on the NE support of the connection since the result in this case
is the failure in implementing the protected path

01

SC.3:OPERATION
3AL 61348 AA AA
258

195 / 258

The Add / Remove Protection command can be executed on a path/trail or directly on the connections in
topology.
The following paragraphs give examples of usage of this command.
The resources needed for a successful command completion could be used by other paths; it is
advisable to create protected paths instead of adding subsequently the protection; namely in
this case the allocation algorithm makes the reservation of nonoverlapped routes.
In case of overlapping of an existing route with the new protection route required by the Add
Protection command, it is possible to find the existing route by using the Paths in trail view
invoked on the trails terminated to the nodes where terminates the path to be protected.
locate

routing view

PATH

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 168. Add/Remove Protection Tool button

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

196 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.12 Add / Remove Protection

3.12.1 Add Protection ( path )

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

a)

Select the path from the path list and click on Add/Remove Protection Tool button. The Add/Remove
Protection Tool wizard is displayed. See below figure. Possible options are:

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 169. Add/Remove Protection wizard step1

Add Protection Spare. The spare route is allocated and implemented.

Remove Protection Spare

Add Service. This item is selectable only if the path protection type is D & C. The service route is
allocated and implemented.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

197 / 258

Remove Service. This item is selectable only if the path protection type is D & C. The service route
is removed

b)

Select option item Add Protection Spare. Click on Next button. The Add/Remove Protection wizard
step 2, allowing the selection of the switch is presented. See following figure.
path routing button

SELECT button

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 170. Add/Remove Protection wizard step 2: selection of the switch


c)

Click on upper path routing button which retrieves the path routing view. From this view select the
switch where you want to start the protection and click on button Select to confirm. The routing view
automatically closes and the selected switch is displayed in the main window

d)

Click on lower path routing button which retrieves again the path routing view. From this view select
the switch where you want to end the protection and click on button Select to confirm. The routing
view automatically closes and the selected switch is displayed in the main window. See following
figure.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

198 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 171. Add/Remove Protection wizard step 2: switches selected

1AA 00014 0004 (9007) A4 ALICE 04.10

e)

ED

Click on Finish to confirm. The action is started and the report is displayed. See following figure.

01

SC.3:OPERATION
3AL 61348 AA AA
258

199 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

f)

ED

01

3AL 61348 AA AA

258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

REFRESH

Figure 172. Add/Remove Protection report

Click on Refresh button. The routing view is updated. See following figure.

SC.3:OPERATION

200 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

REPORT

Figure 173. Path routing view after protection

g)

ED

Click on Report button to display the route report. See following figure.

01

SC.3:OPERATION

3AL 61348 AA AA

258

201 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 174. Path routing report


3.12.1.1 Remove Protection ( Path )
a)

Select the path icon from the routing display and move the mouse to Remove protection menu item.
Two options are selectable:
1)

Remove protection with check. The following options are selectable:

Keeping main. If the actual route corresponds to the main one, the protection route ( the spare
one ) is removed and the path remains on the main route .
Keeping spare. If the actual route corresponds to the spare one, the protection route ( the main
one ) is removed and the path remains on the spare route .
Service. If the actual route corresponds to the main/spare route, the service route is removed
and the path remains on the main/spare route.

1AA 00014 0004 (9007) A4 ALICE 04.10

2)

ED

01

Remove protection without check. The following options are selectable:


SC.3:OPERATION
3AL 61348 AA AA
258

202 / 258

Keeping main. The protection route ( main or spare one ) is removed and the path remains/is
routed on the main route .
Keeping spare. The protection route ( main or spare one ) is removed and the path remains/is
routed on the spare route .
Service. The service route is removed and the path remains/is routed on the main/spare route.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

203 / 258

3.13 OS driven restoration for HO paths & trails

3.13.1 Create a restoration rule


Create a restoration rule means enable the restoration function for the selected transport ( path or trail )
according to the rule being created.
a)

From the path list or trail list select an HO path or an HO trail and select button Create Restoration
Rule. See Figure 175. The Create Restoration Rule is displayed. See Figure 176. on page 205

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 175. Restoration:Create Restoration Rule.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

204 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The OS driven restoration applies to HO paths and trails.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 176. Create: Restoration Rule.


b)

Select the following attributes:


1)

Restoration strategy. Possible values are:

optimized add protection (for point to point transports only) .This strategy does not cause
a complete path rerouting but only finds a spare route inside the lowest level topology
( e.g. a ring ) affected by the fault.

end to end add protection. (for point to point and broadcast transports) This strategy
causes a complete path rerouting by allocating the path spare route.

remove protection + end to end add protection (for point to point transports only). It
removes the protections and adds one end to end spare route. For paths protected by the
D&C mechanism both spare and spare+service connections are removed; only one end
to end spare route is allocated.

1AA 00014 0004 (9007) A4 ALICE 04.10

the default value is optimized add protection.


2)

Hold Off Time (sec) . This time is the waiting time before starting the restoration subprocess.

3)

Used Resources. Possible values are:

4)

not alarmed objects ( default )

all objects. This option will successfully restore the transport upon repair of the related
resources.

Constraint Rule. Possible values are:

ED

01

do not use constraints ( default )


SC.3:OPERATION
3AL 61348 AA AA
258

205 / 258

c)

use default constraints. This option sets the usage of the spare constraints for the
transport restoration. The spare constraints are added by means of the Path Constraints
application.

Click on the functional button Create. The restoration rule is created. Its name coincides with the
transport name.

3.13.2 Display a restoration rule


a)

From the browser point to the network domain and issue the command Display: Related Items. Select
Restoration Rules. The icon of the restoration domain is displayed in the browser window ( see
Figure 177. ) and the restoration rule list opens. See Figure 178.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 177. Browser: restoration domain.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

206 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 178. Restoration Rule list.


The displayed attributes are:

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

user label. It coincides with the transport name.


object type. The possible values are path or trail.
restoration strategy. See paragraph 3.13.1.
hold off time . See paragraph 3.13.1.
restore working state. It can assume one of the following values:

normal. No restoration activity is in progress.

hold off active. The restoration activity will start at hold off time expiration.

waiting for concurrency. It is an internal waiting state.

restoring. The restoration activity is in progress.


last restoration result. It can assume one of the following values:

none. No restoration has been requested for the transport.

successfull. The restoration process completed the allocation.

failed. The restoration process did not complete the allocation because of lack of resources.

not performed. The restoration process did not complete the allocation because of external
conditions.
date of the last successful restoration result
You can display other attributes by selecting the transport and issuing the command
Actions:Details:Show/Set Attributes. The dialog box of Figure 179. is presented.

01

SC.3:OPERATION
3AL 61348 AA AA
258

207 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 179. Restoration Rule attributes.


For trail or path the attribute Restoration state can assume one of the following values:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

none. No restoration rule is associated to the transport.


supervised. A restoration rule is associated to the transport.
restored. The transport has been restored. A subsequent restoral cannot visualized. In
order to return to the supervised status, the operator must select the transport ( from the
list ) and issue the command Actions:Restoration:Set to Supervised.

SC.3:OPERATION
3AL 61348 AA AA
258

208 / 258

3.14 Join/Split Path

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Join/Split path are used to merge a pair of paths into one single path or to split a path into a pair of paths.
3.14.1 Join Paths
SCOPE

The scope of this procedure is to merge a pair of paths into one single path.

CONDITIONS
a)

In the example which follows a path crossing R1 must be merged to a path crossing R2. T

Figure 180. Rings to be merged.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

By clicking twice on the icons of R1 and R2 it is possible to display the two ring submaps. See
Figure 181.

01

SC.3:OPERATION
3AL 61348 AA AA
258

209 / 258

Both RING1 and RING2 are crossed respectively by path P1 and path P2 which physically are the
same path. Namely both P1 and P2 are terminated to virtual nodes NE_V1 and NE_V2. The Path
List containing P1 and P2 is shown in Figure 182. To display the Path List, from the browser, point
to the Network icon and issue Actions: Display: Related items: Paths in Topology + No Filter.
The Path List is displayed. See Figure 182. on page 210

Figure 181. Submaps of ET Meshed and ET_2F_QB3*

HIGHLIGHT

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 182. Path List containing paths P1 and P2


SEQUENCE

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

210 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

c)

From the path list (see Figure 183. herebelow) join paths P2+P3. Select the paths and issue Actions:
Modification: Join.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

a)

Figure 183. P2+P3 Join path pulldown menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

In the Join path dialog box enter the name of the joined path (e.g. P ) and click on the functional button
Join path. After a few seconds paths P2 and P3 are deleted and the new path P is created and
implemented.

Figure 184. Join path dialog box

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

211 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 185. Joint Report

Figure 186. Path list after join operation..

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

212 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.14.2 Split path

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The split path is the reverse operation of the join path.
SEQUENCE
a)

Select the path P to split from the path list and issue Actions: Modification: Split

b)

In the Split path dialog box enter the names of the two paths which are replacing the path to split and
click on Split path button. The system presents to the user the list of the nodes along the path route.

c)

Select the node where the path must be split and confirm. Path P is deleted and the new paths are
created and implemented.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 187. Actions: Manage path: Split path

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

213 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 188. Split path dialog box.

Figure 189. Node selection.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

214 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.15 JoinSplit Trail


Two HOTrails entering in a given NE can be joined in order to reduce the LO usage of resources or an
HOTrail crossing at HO a Node can be split in order to perform crossing at LO.
3.15.1 Split a HOTrail
A given HOTrail crossing at HO a Node can be split in order to perform crossing at LO. This enables the
usage of LO resources in the splitting Node.
The operation reproduces in the splitting node the same payload structure of the starting trail.
The operation can be performed after the split of a Physical Connection.
Input to the operation is the HOTrail to split.
SEQUENCE
a)

Point to the trail to split and select Trail: Modification: Split

Figure 190. Trail: Modification: Split

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

in the Split trail dialog box enter the trail names of the new trails and click on Start Split button.

01

SC.3:OPERATION
3AL 61348 AA AA
258

215 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 191. Split trail dialog box

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

The system presents the list of the possible splitting nodes. Select the node and click on OK.

Figure 192. Common node selection.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

216 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

As a consequence of the operation:

the old HOTrail is deleted

two new HOTrails are created

The LOPaths crossing the splitting Node are modified by adding LO passthrough connection.
The related protection indexes are updated.
The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
splitting node.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 193. Split trail report


The operation reduces the impacts on the existing traffic: the LOPaths client of the involved HO trails are
disconnected only for the time necessary to perform the operation: only the segment of network between
the end nodes of the involved HO trails is affected.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

217 / 258

3.15.2 Join two HOTrails

SEQUENCE
a)

From the trail list select the HOTrails to join. See Figure 194.

b)

Select the command Actions:Modification: Join. The Join trail dialog box is presented, containing the
two selected trails, as per Figure 195. Enter the name of the new joined trail.

c)

Click on button Join trail to start the operation.

RM performs the following checks:

the 2 HO Trails must have the same payload structure;

it must be possible to create an HO connection in the intermediate node;

all LOpaths using the original HOTrails are crossing with passthrough connections the
intermediate NE without LO timeslot interchange.
As a consequence of the operation:

the old HOTrails are deleted

the new HOTrail is created

the LOPaths crossing the original HOTrails are modified by removing the passthrough
connections in the intermediate NE. The related protection indexes are updated.
The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
intermediate node.

1AA 00014 0004 (9007) A4 ALICE 04.10

The operation reduces the impacts on the existing traffic: LOPaths client of the involved HO trails are
disconnected only for the time necessary to perform the operation and only in the segment of network
between the end nodes of the involved HO trails.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

218 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Two HOTrails entering in a given NE can be joined in order to reduce the LO usage of resources.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 194. Actions: Modifications: Join.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

219 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 195. Trail: Modification: Join dialog box.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

220 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.16 JoinSplit Physical Connection


According to different ring configurations, the usage of the join / split physical connection is inserted in different macroprocedures. Please refer to paragrapf Network Modifications.

3.16.1 Split Physical Connection


SCOPE
The Split Physical Connection is used to insert a new Node into a preexistent topology.
STATUS CONDITIONS
Allowed Physical Connection working states are: Normal, Failed to Split, Failed to undo Split, Failed to
disconnect.
Allowed Physical Connection Implementation state is Implemented.
HO LCs working state must be Normal (no payload configuration in progress)
TOPOLOGY CONDITIONS
If the PhysCon is included in a ring the node to insert is not connected and placed in the ring map. See
example herebelow.
If the PhysCon is not included in a ring ET working state=Normal and ET Implementation state=Implemented.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From browser interface point to the icon of the Physical Connection to split and issue the command
Topology Modification: Split.

01

SC.3:OPERATION
3AL 61348 AA AA
258

221 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 196. Topology Management popup menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

The guided interface structure ( the so called wizard ) opens. See Figure 197. herebelow. It contains
in the upper part of the window the icons of the physical connection to split and the connected ports.

01

SC.3:OPERATION
3AL 61348 AA AA
258

222 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 197. Split wizard: step1

1AA 00014 0004 (9007) A4 ALICE 04.10

The central part of the window allows to select the node to insert. Click on the selection button ( three
points ). The node list is presented. See Figure 198.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

223 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 198. Node list.

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

Select the node to insert and click on Apply button. The icon of the selected node appears in the wizard. See Figure 199. herebelow. You can also display the node in the map by clicking on the Highlight
button.

Figure 199. Node inserted.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

224 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

d)

Click on Next button to continue the procedure. The wizard now presents the first port of the physical
connection being splitted and the node being inserted. Click on the selection button in order to select
the port of the new node to connect to the first port of the physical connection being splitted. The relevant port list is displayed. See Figure 201.

Figure 200. Step 2. First port to use.

1AA 00014 0004 (9007) A4 ALICE 04.10

e)

ED

Select the port to connect and click on Apply button. The icon of the selected port is presented in the
wizard. See Figure 202.

01

SC.3:OPERATION
3AL 61348 AA AA
258

225 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 201. Port list

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

226 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 202. Step 2. First port to use.


f)

Enter the new connection name and click on Next button to continue.The wizard now presents the
second port of the physical connection being splitted and the node being inserted. Click on the selection button in order to select the port of the new node to connect to the second port of the physical
connection being splitted. The relevant port list is displayed.

g)

Select the port to connect and click on Apply button. The icon of the selected port is presented in the
wizard.

h)

Enter the new connection name and click on Next button to continue.The wizard now presents the
summary view of the operations executed by the user. See Figure 203. herebelow.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

227 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 203. Split connection summary dialog box.

1AA 00014 0004 (9007) A4 ALICE 04.10

i)

ED

If you click on Finish button the existing physical connection is deimplemented and deleted, while te
new physical connections are created, implemented and structured accordingly. In particular, the following steps are performed:
1)

Disconnect client paths/hoTrails

2)

SDH ports assignment

3)

Insert node in ET

4)

MSTP structure

5)

create the objects in DB

6)

Connect client paths/hoTrails

01

SC.3:OPERATION
3AL 61348 AA AA
258

228 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

229 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.16.2 Join physical Connection

The Join Physical Connection is used to remove a Node from a topology


CONDITIONS
The toplogy implementation state is Implemented and the working state is Normal.
SEQUENCE
a)

From browser interface point to the icon of the Physical Connection to slit and issue the command
Topology Modification: Join. The Join Physical Connections dialog box is displayed. See
Figure 204. on page 230

b)

From browser window drag and drop the second physical connection to join, enter the connection
name and click on Start Join button.

Figure 204. Join Physical Connections dialog box.

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

A report window is presented containing all messages

01

SC.3:OPERATION
3AL 61348 AA AA
258

230 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 205. Join Physical Connection report

3.16.3 Fail to join working state


If following a join physical connection procedure, the physical connection enters the Fail to join state, the
operator can select the Undo Join physical connection.
3.16.4 Fail to split working state
If following a slit physical connection procedure, the physical connection enters the Fail to split state, the
operator can select the Undo Split physical connection.
3.16.5 Fail to disconnect working state

1AA 00014 0004 (9007) A4 ALICE 04.10

If following a join/slit physical connection procedure, the physical connection enters the Fail to disconnect
state, the operator can select the Connect path action or repeate the failed action.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

231 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

If following a join/slit physical connection procedure, the physical connection enters the Fail to connect
state, the operator can select the Connect/Disconnect Path/Trail

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

232 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.16.6 Fail to connect working state

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.17 ISDN primary access management


3.17.1 Introduction
This feature activates the adaptation function of the incoming 2 MB/s ISDNPRA signal to process a
framed or not framed signal.

3.17.2 ISDNPRA Procedure


a)

From the path popup menu select item Client Alarms: PDH alarm monitoring. The ISDNPRA dialog
box is presented. See Figure 207. on page 234. The dialog box is structred in two sequential views.
The first window allows to select the PDH alarm monitoring type. See Figure 207. on page 234 .

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 206. Path: Alarms: Operations: On Clients: PDH framing

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

233 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 207. ISDNPRA step 1 dialog box ( alarm monitoring type)


b)

You can select among the following options:

unframed ( default value ). No path frame monitoring is performed.

framed. The pdh signal frame is monitored and consequent alarms are generated. The monitoring
direction ( ingressing / egressing, both or none )

ISDNPRA ( Integrated Service Data NetworkPrimary Access=2 Mb/s ). This option is allowed for
bidiectional paths only. Only one of the two ports must be marked as NT ( Network Termination ). PDH
monitoring ( frame monitoring ) will be activated only on the port marked as NT, which is the one connected to the TE ( Terminal Equipment = Users premises

leased line PRA. This option is allowed for bidiectional paths only. One or both of the two ports can
be marked as NT ( Network Termination ). PDH alarm monitoring will be applied only on NT ports.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

234 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 208. ISDNPRA step 2 dialog box (Port role assignment)

c)

ED
Select the desired option and click on Next button.

01

SC.3:OPERATION

3AL 61348 AA AA

258

235 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 209. ISDNPRA: NT Ports selection.

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

236 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.18 4 x ANY
3.18.1 Introduction
The 1696MetroSpan provides the 4XANY TDM card.
The 4XANY TDM card is a TDM concentrator board, based on the following concepts:
The following client signals can be transported:

FDDI (125 Mb/s)


Fast Ethernet (FE) (125 Mbit/s)
ESCON (200 Mbit/s)
Digital Video (270 Mbit/s)
STM1 (155 Mbit/s)
STM4 (622 Mbit/s)
FC (1.062 Gbit/s)
Gigabit Ethernet (GE) (1.25 Gbit/s)

The board accepts at most 4 signals and mapping is performed into a STM16 (2.5 Gbit/s) port
The architecture of TDM concentrator board is based on the concept of virtual concatenation, and on the
mapping of SDH on OTN:
Data traffic is packet into VC4 structures (virtually concatenated)

VC4s are groomed into a STM16 structure


STM16 signal is transported through the optical network as RS Client Path

The following table resumes the traffic that can be transported and the number of VC4 required:
Traffic

Speed

FDDI

125 Mb/s

VC41v

Fast Ethernet

125 Mb/s

VC41v

ESCON

200 Mb/s

VC42v

DV

270 Mb/s

VC42v

STM1

155 Mb/s

VC42v

STM4

622 Mb/s

VC45v

FC

1.062 Gb/s

VC48v

Gigabit Ethernet

1.25 Gb/s

VC48v

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

SDH Transport Structure

Applicable for STM1 and STM4 terminations. Only the SDH physical connection between the 2 SDH NE is described in RM and the manual correlation function can permit
to associate the underlying DATA PATH to it. Fiber cut on the fiber connecting the
SDH NE adjacent to the SDH port of the 4xany card will be detected on SDH NE side and
will impact the mentioned above SDH physical connection.

The 4XANY card can be:

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

237 / 258

Connected inside the 1696MetroSpan to the OPC card to perform the SNCP protection of the RS
client path in the OTH network (Optical protection).
Alone inside the 1696MetroSpan (CPE configuration case). In this case, 1696MetroSpan, configured as CPE, could be connected to either another 1696MetroSpan (not configured as CPE), a
1686WM or a 1640WM (either through B&W or coloured interface), an SDH NE (through B&W interface).
Due to the fact that the RS signal is terminated on the 4XANY, the 1696MS hosting this board has to be
visible both in SDH and OTH domain, i.e. the STM16 port of the 4XANY board has to be managed as:
UNI B&W or coloured port of an SDH NE. In particular in the first and second above listed cases,
the STM16 port will be connected by the user, through an internal physical connection, to the OPS
port of respectively the transponder or the OPC card.
In the third case, the user will create a physical connection connecting the STM16 port of the 1696WM
(CPE) and the OPS port of either a 1686WM or a 1640WM.
On the client side (data port) the 4XANY can be physically connected to an OMSN NE to transport an
STM1/STM4/GigabitEthernet traffic, coming from the SDH network, into the OTH network. It is not possible to describe in the RM this physical connectivity (between an STM1/STM4/GigabitEthernet port of
the 4xANY and an OMSN NE port at the same rate); the user has to correlate through the correlation function the SDH physical connection between the two external OMSN NEs to the Data path terminated on
the two 1696MS NEs.
3.18.2 Upload of the Data ports
When uploading a gMAUTTP port of the 1696MS, the system automatically creates the following objects:
A RM port characterized with:
Technology: Data
Physical Port Type: is set according to the value of the dataClientType attribute of the
gMAUCTPBid MOC retrieved from the NE
Au4maxSupportedConcLevel and concLevelMode are set according to the following table

1AA 00014 0004 (9007) A4 ALICE 04.10

physicalPortType

Au4Supported ConcLevel

concLevelMode

Eth/100Mbtransp

notModifiable

Eth/1Gbtransp

notModifiable

Fddi

notModifiable

Escon

notModifiable

DigitalVideo

notModifiable

FiberChannel

notModifiable

Stm1

notModifiable

Stm4

notModifiable

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

238 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Connected inside the 1696MetroSpan to the Transponder card to transport Data traffic on the RS
signal (STM16) on the OTH network.

3.18.3 Create Path

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

To create a path involving a 4XANY board, the user, during the path creation activity, has to select:
Service Type either Ethernet or Data.
According to the selected Service Type all consistent values of Service Rate attribute are presented to
the user.
In case of Service Type =Ethernet and Service Rate =1Gbit/s Ethernet Transparent , the list of NAP
s available on either 1670SM or 1696MS(4XANY) is provided. For all the other cases, only NAP s on
1696MS will be listed. The path is created with Transport Rate attribute equal AU4nV, concLevel attribute equal to the concLevel attribute of NAP s and concLevelMode equal notModifiable.

3.18.4 Example
a)

From the browser node list select the node which houses the 4XANY board and issue Search: Main
Related items: Ports in Node

STM16 board

DATA boards

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 210. Ports in node


b)

Ports managed by the 4xANY are:

STM16 board
DATA boards, according to the table explained above at para 3.18.1 on page 237

c)

The path using these ports is Ethernet with Service rate=AU4nV (concatenated).

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

239 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

240 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4 NETWORK MODIFICATIONS
4.1 Introduction
The main procedures described in this Chapter are:

Adding a Network Element to a SNCP Ring case 1

Adding a Network Element to a SNCP Ring case 2

Removing a Network Element from a SNCP Ring

Add Q3 NE to a 2F MS Spring

Add QB3 STAR NE to a 2F MS Spring

Remove Q3 NE / Remove QB3 STAR NE from a 2F MS Spring

Add NE to a 4Fiber NPE ring

Remove NE from a 4Fiber NPE ring

Adding a PDH Tributary Board

Removing an SDH Tributary Board

Adding an SDH Tributary Board

Configuration of a Transmux board

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

The execution of the RedoLog file does not cause the allocation of the path/trail; however
some checks take into account the topological modifications:

in case of node insertion the passthrough connection is added in the new node.

in case of node remove the passthrough connection thru the removed node is ignored.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

241 / 258

4.1.1 Adding a Network Element in a SCNP network, case 1

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The new Network Element must be inserted in the network as shown in Figure 211.

NE2
NE3
NE1
NEW NETWORK ELEMENT

Figure 211. Adding a new Network Element, case 1CONDITIONS


CONDITIONS
It is assumed that the new NE is already managed by EML.
SEQUENCE
a)

The upload of the EML info from EML to RMMIB is automatically performed.

b)

Create the new NE.

c)

By means of the command Create Connection, create the connection between the involved
NEs/topologies.

d)

Execute the Implementation of the new Physical Connection. (This causes also the NE
implementation, i.e. the reset of the NE )

1AA 00014 0004 (9007) A4 ALICE 04.10

The procedures which follow are:

Upload NAP of the new NE

Payload Configuration

Path Management

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

242 / 258

4.1.2 Adding a Network Element (NE) to a SNCP ring case 2

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to insert a NE into a SNCP ring.
CONDITIONS
The new Network Element must be inserted in the network as shown in Figure 212.

NE2
NE3
NE1

NEW NETWORK ELEMENT

Figure 212. Adding a new Network Element to a SNCP ring


SEQUENCE
a)

The user can protect paths using the physical connection to be interrupted ( NE1 Thru NE3 ). The
user can verify by means of the command Physical Connection: ( display ) Paths active in
physical connection which is the path actual route.
If traffic survivability is required, from the path list select all paths and protect them by means of Add
Protection: Spare. Verify, with reference to Figure 212. ,that the upper route is working for all paths.
Execute the force operation to the upper route for all involved paths and verify that all paths have been
successfully forced and are operational.

b)

Move all paths from the physical connection to be interrupted (NE1 thru NE3)
1)

1AA 00014 0004 (9007) A4 ALICE 04.10

2)

For paths protected at above point a ), select them and use option Remove Protection: Keeping
Spare.
For paths previously protected, reroute manually on the main or spare route according to the
route type crossing the physical connection.

c)

If the node to be inserted is a QB3* node, put the node in download disable condition.

d)

Execute the split physical connection procedure. See paragraph 3.16.1 on page 221.

e)

If the node to be inserted is a QB3* node, put the node in download enable condition and execute
Global Download on QB3* NE.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

243 / 258

Remove the undesired protections and forced conditions.

SCOPE
The scope of this procedure is to remove a Network Element from a SNCP ring.
CONDITIONS
The SNCP reference ring is shown in Figure 212. on page 243. Some paths are crossing the NE being
removed.
SEQUENCE
a)

On the node issue the command Display: Paths active starting/ending from a node

b)

The user can protect paths using the physical connection to be interrupted ( NE1 Thru NE3 ). The
user can verify by means of the command Physical Connection: ( display ) Paths active in
physical connection which is the path actual route.
If traffic survivability is required, from the path list select all paths and protect them by means of Add
Protection: Spare. Verify, with reference to Figure 212. ,that the upper route is working for all paths.
Execute the force operation to the upper route for all involved paths and verify that all paths have been
successfully forced and are operational.

c)

Move all paths from the physical connection to be interrupted (NE1 thru NE3)
1)
2)

d)

For paths protected at above point a ), select them and use option Remove Protection: Keeping
Spare.
For paths previously protected, reroute manually on the main or spare route according to the
route type crossing the physical connection.

1354RM
Execute the Join Physical Connection Procedure

4.1.4 Add Q3 NE to a 2F MS Spring


SCOPE
The scope is to insert a Q3 NE into a 2F MS Spring ring.
CONDITIONS
The ring is mixed, i.e. it contains Q3 NEs and QB3 STAR NEs.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

Execute the Force Switch operation on adjacent protection blocks, where the new NE must be
inserted: Force West on one side and Force East on the other side.
The information of Node Position in ET and Node Id in ET can be displayed by issuing the Show/Set
Attributes command on the Protection Block.

b)

ED

Configure Download: Disable.

01

SC.3:OPERATION
3AL 61348 AA AA
258

244 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.1.3 Removing a Network Element (NE) from a SNCP ring

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1)

Execute the command Configure Download: Disable on QB3 STAR Network Elements.

2)

Execute the command Configure Download: Disable on Q3 Network Elements.

3)

Click twice on the physical connection group ( line between the two nodes involved. The
physical connection list opens.
Select the Physical Connection and issue Topology Modifications: Split Physical Connection.
Execute the split connection procedure.

c)

Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run
Level: 3 Ntw Consistency

d)

Select all QB3 STAR NEs and execute Consistency Download: Global.

e)

Change the Run Level to Full Functionality.

f)

Enable the download on all QB3 STAR NEs

g)

Enable the download on all Q3 NEs


DO NOT ENABLE THE DOWNLOAD ON THE INSERTED NE; THIS IS TO BE DONE LATER

h)

Execute all cable unplug and plug operations NOW, before activating the MS Spring on the inserted
NE.

i)

Enable the download on the inserted Q3 NE.

4.1.5 Add QB3 STAR NE to 2F MS Spring


SCOPE
The scope is to insert a QB3 STAR NE into a 2F MS Spring ring.
CONDITIONS
The ring is mixed, i.e. it contains Q3 NEs and QB3 STAR NEs.
SEQUENCE
a)

Execute the Force Switch operation on adjacent protection blocks, where the new NE must be
inserted: Force West on one side and Force East on the other side.
The information of Node Position in ET and Node Id in ET can be displayed by issuing the Show/Set
Attributes command on the Protection Block.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

Configure Download: Disable.


1)

Execute the command Configure Download: Disable on QB3 STAR Network Elements.

2)

Execute the command Configure Download: Disable on QB3 STAR Network Elements and on
Q3 Network Elemets

3)

Click twice on the physical connection group ( line between the two nodes involved. The
physical connection submap opens. Select the physical connection and browse it by means of
Supervion: Browse: Object.

01

SC.3:OPERATION
3AL 61348 AA AA
258

245 / 258

c)

Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run
Level: 3 Ntw Consistency

d)

Select all QB3 STAR NEs and execute Consistency Download: Global.

e)

Change the Run Level to Full Functionality.

f)

Enable the download on all QB3 STAR NEs

g)

Enable the download on all Q3 NEs


DO NOT ENABLE THE DOWNLOAD ON THE INSERTED NE; THIS IS TO BE DONE LATER

h)

Execute all cable unplug and plug operations NOW, before activating the MS Spring on the inserted
NE.

i)

Enable the download on the inserted QB3 Star NE.

j)

Release switches

4.1.6 Remove Q3 NE / Remove QB3 STAR NE from a 2F MS Spring


SCOPE
The scope is to remove a Q3 NE /QB3 STAR NE from a 2F MS Spring ring.
CONDITIONS
The ring is mixed, i.e. it contains Q3 NEs and QB3 STAR NEs.
SEQUENCE
a)

Execute the Force Switch operation on adjacent protection blocks, where the NE must be removed
Force West on one side and Force East on the other side.
The information of Node Position in ET and Node Id in ET can be displayed by issuing the Show/Set
Attributes command on the Protection Block.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

Configure Download: Disable.


1)

Execute the command Configure Download: Disable on QB3 STAR Network Elements.

2)

Execute the command Configure Download: Disable on Q3 Network Elements.

c)

Disconnect the physical fibers from the node being removed.

d)

Join physical connections

ED

1)

From the map click twice on the first physical connection group. The physical connection list
opens. Select the physical connection.

2)

From the map click twice on the second physical connection group. The physical connection
list opens. Select the physical connection.

01

SC.3:OPERATION
3AL 61348 AA AA
258

246 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

From the browser select the Physical Connection and issue Topology Modifications: Split
Physical Connection.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Select the two Physical Connections to join and issue Topology Modifications: Join Physical
Connection. Execute the join physical connection procedure.
e)

Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run
Level: 3 Ntw Consistency

f)

Select all QB3 STAR NEs and execute Consistency Download: Global.

g)

Change the Run Level to Full Functionality.

h)

Enable the download on all QB3 STAR NEs

i)

Enable the download on all Q3 NEs

j)

Execute all cable plug operations

k)

Release all switches

4.1.7 Add NE to a 4Fiber NPE ring


SCOPE
The scope is to add a NE to a 4F MS Spring ring.
CONDITIONS
No protection is active ( nor alarm neither command is active )
SEQUENCE
a)

Set Download Disable mode on the node to be added

b)

Execute the Split Physical Connection on the relevant Physical connection

c)

Set Forced Ring Switch on the adjacent nodes

d)

Remove the physical fibers SPARE between the nodes

e)

Remove the physical fibers MAIN between the nodes

f)

Set Download Enable mode on the node, which has just been inserted

g)

Perform the physical fiber connections for the working fibers

h)

Perform the physical fiber connections for the protecting fibers

i)

Remove the Forced Ring Switch on the nodes adjacent to the inserted node

4.1.8 Remove NE from a 4Fiber NPE ring


SCOPE

1AA 00014 0004 (9007) A4 ALICE 04.10

The scope is to remove a NE from a 4F MS Spring ring.


CONDITIONS
No protection is active ( nor alarm neither command is active )

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

247 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

Set Download Disable mode on the node to be removed

b)

Execute the Join Physical Connection on the relevant Physical connections

c)

Set Forced Ring Switch on the nodes adjacent to the node being removed

d)

Remove the physical fibers from the node being removed, by respecting the following order:
1)

remove RX spare

2)

remove TX spare

3)

remove RX main

4)

remove TX main

e)

Perform the physical fiber connections for the working fibers

f)

Perform the physical fiber connections for the protecting fibers

g)

Remove the Forced Ring Switch on the nodes which were adjacent to the removed node

h)

Set Download Enable mode on the node, which has just been inserted

ED

01

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE

SC.3:OPERATION
3AL 61348 AA AA
258

248 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2 Add/Remove Tributary Board


4.2.1 Remove a PDH Tributary Board
SCOPE
The scope is to remove a tributary board.
SEQUENCE
a)

On the relevant NAP List verify that no path is using any trib. port of the board being removed i.e.
the nap idle indicator should be Idle.

b)

On the relevant NAP List select the NAP related to the trib. ports to be removed and issue the
command Actions:Remove:Remove NAP. The relevant ports pass from Assigned to Observed.
On the 1353NM station delete the relevant board. The board is no longer present in the views.
In the NE port list the ports deleted are no longer present.

c)
d)

4.2.2 Removing an SDH Tributary Board


SEQUENCE
a)
b)

c)

Select the physical connection associated to the SDH port to be removed.


Then select Display Related items: Paths in Physical Connection to verify that no path is using that
physical connection.
Should a path been using the involved physical connection, the path should be
deimplemented/deallocated or rerouted, if possible.
On the map delete the connection:
1)
2)

d)

Deimplement the connection


Remove objects from RM

On the 1353NM station delete the relevant board. The board is no longer present in the views.

4.2.3 Adding a PDH Tributary Board


SEQUENCE
a)
b)

On the 1353NM station create the relevant board.


Execute an Upload NAPs for the relevant node. From this point on the ports are available to be used
in a path (NML assigned).

4.2.4 Adding an SDH Tributary Board

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

On the 1353NM station create the relevant board.

b)

On the map execute Upload NE Ports. From this point on you can use the port in the network
construction.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

249 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION

3AL 61348 AA AA

258

250 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.3 Configuration of a Transmux board


4.3.1 Payload Structure Configuration of a Transmux board
The payload configuration of a transmux board ( VC4 Synchronous to Plesiochronous ) includes a
sequence of steps to execute on both 1354RM and 1353NM. Example which follows covers the
configuration of a 140 Mb Port to 2Mb terminations.
a)

On 1354RM: Remove the VC4 NAP associated to the 140 Mb port. The detailed sequence is:
1)

From browser point to the involved node and issue Actions: Display: Main related Items: NAPs.

2)

The NAP list is displayed. Select the VC4 NAP and issue Actions: Remove NAP.

3)

the 140Mb port assignment status goes to OBSERVED.

4)

b)
c)
d)

Point to the Node and issue Actions: Display: Main Related Items: Ports. The Port List is
displayed. The 140Mb port assignment status is OBSERVED.
On 1353SH: Execute the payload structure configuration to VC12.
On 1354RM: Execute the EML: Synchronize command. The 140 Mb Port (OBSERVED) is replaced
by the 2 Mb ports ( OBSERVED ).
On 1354RM: Execute the Upload NAPs command. The detailed sequence is:
1)

From browser point to the involved node and issue Actions: Configuration: Upload NAPs.

2)

The user can display the uploaded NAPs, e.g. from browser, pointing to the node and issuing
the command Actions: Display: Main Related Items: NAPs. The NAP List now contains the
VC12 TTPs ( NAPs).

N.B.

Configuring a TMUX board from one 34Mb port to 16


2Mb ports:
The configure port is done on NM, then on RM a synch eml and a upload NAPs is performed.
Some problems occur if Upload NAPs from RM is done immediately after getting all MUX
boards (synch eml).
On NM VC12 objects exist before all VC12 TPs have been configured on DXC. The result is
misaligned ports for all missing NAPs. A second Upload NAPs which is performed some
minutes later solves this misalignment.

4.3.2 Payload Structure Remove of a Transmux board


Example which follows covers the configuration of a 140 Mb Port from the 2Mb NAPs to one VC4
TTPNAP.

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

On 1354RM: Remove the VC12 NAPs associated to the 140 Mb port. The detailed sequence is:
1)

From browser point to the involved node and issue Actions: Display: Main related Items: NAPs.

2)

The NAP list is displayed. Select the VC12 NAPs and issue Actions: Remove NAP.

3)

Point to the Node and issue Actions: Display: Main Related Items: Ports. The Port List is
displayed. The assignment status of the 64 2Mb ports is OBSERVED.

b)

On 1353NM: Remove the payload structure configuration ( from VC12 to VC4 )

c)

On 1354RM: Execute the EML: Synchronize command. The 2Mb Ports (OBSERVED) are replaced
by one 140 Mb port ( OBSERVED )

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

251 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

252 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5 EXPORT OF RESOURCES ON ISN INTERFACE FOR 1355VPN


5.1 Introduction
The procedures which follow describe the export of resources to Virtual Private Network Management
system.
They are divided in:

ED

Adding a VPN initiator

Add operator

VPN assignment of the end points

VPN assignment of the paths

VPN assignment of the paths terminated outside an RM domain

01

SC.3:OPERATION
3AL 61348 AA AA
258

253 / 258

5.1.1 Adding a VPN initiator

a)
b)
c)

Select the Administration ( SMF) icon from the vertical palette.


Select the feature Operator Administration and confirm by pressing OK.
From the Operator Administration Window select the option Add Initiator and confirm by pressing OK.
The Add Initiator window contains:

the current Initiator list

two textlines: RM Initiator and Initiator Name where the Administrator operator can digit the
RM Initiator ( integer ) and the Initiator Name (it must be unique in the file).
The Initiator Identifier must be given according to the following rules:

VPN Initiators must have Identifier greater than 300

The Identifier 301 is reserved for 1354NN (when present)

The Initiator Name is added to the possible values of the NAD attribute. The NAD attribute
is used to mark Network Resources (using the change NAD command) and to evaluate
Access Rules.
d)

Enter the suitable RM Initiator and Initiator Name and select the rules to be associated. Click on
the Rule button. The list of the available rules opens. Each item of the list has a toggle button, i.e.
you can select many rules per each Initiator. The following rules can be selected:

AC_R_VPN
AC_R_EVPN
AC_R_RVPN

for Standard VPN Operators ( not supported in this release )


for Enhanced VPN Operators
for Restricted VPN Operators

1AA 00014 0004 (9007) A4 ALICE 04.10

Click on the Add button to confirm the creation

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

254 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE

5.1.2 Add Operator

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
This function allows the Administrator to create a new operator at a time on WSs belonging to the network
configuration.
SEQUENCE
a)
b)
c)
d)

Select the SMF icon from the vertical palette.


Select the feature Operator Administration and confirm by pressing OK.
From the Operator Administration window select the option Add Operator and confirm by pressing
OK. The Add Operator dialog window is presented.
Enter the required information, in particular:

VPN Operator name. It is the same name which will be inserted by the VPN Administrator while
executing the VPN Handling procedure.

Operator Profile: Path Builder

e)

Initiator: the Initiator Name previously specified at paragraph 5.1.1 on page 254.
A subsequent confirmation box containing all data relevant to the New Operator being created is
presented. If you press OK the Operator is created. This dialog box also contains the button Abort
to abort the procedure.
you can confirm the Operator creation by pressing button Add.

f)

The Add Operator window contains the following:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

The Header Area presents the function name: Add Operator;


In the Work Area are present three sections:
WS filtering

1 listbox, selectable, which contains the list of defined WS;

1 couple of radiobuttons, with label: All WS to select all WS on which to add operator, and
Select WS to allow selection from the listbox of WS;

1 button above the WS listbox, with label Apply : it gives effect to WS selection for operator
creation, and filters the users list;
Data entering

1 listbox, unselectable, which contains the list of users existing on selected WS. The list is
equipped of an header indicating the composition of items line:
Workstation
Username
Profile
Real Name
Initiator
;

2 entries with labels: User name, Real Name;

1 popdown menu for choosing among available profiles, with label Profiles;

1 popdown menu for choosing among available initiators, with label Initiators;

2 entries for password definition: Password, Confirm Password;


Confirmations

2 buttons: Add to create described operator, Close to close the window and return to the
Main.

01

SC.3:OPERATION
3AL 61348 AA AA
258

255 / 258

5.1.3 VPN assignment of the end points

SCOPE
The scope of this procedure is to assign the desired NAP to a certain NAD ( Initiator Name ), which
corresponds to a certain RM Operator, which in turn will correspond to a certain VPN.
CONDITIONS

This assignment is required for all VPN types ( Standard / Enhanced / Restricted )

SEQUENCE
1)

Select the NAP(s) from the Nap list and issue the command NAD (Network Assignment
Domain): Change.

2)

In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph5.1.1 and confirm by clicking on OK. Click again on OK of the dialog box.

5.1.3.2 Boundary CTP Assignment


SCOPE
The scope of this procedure is to assign the desired CTP to a certain NAD ( Initiator Name ), which
corresponds to a certain RM Operator, which in turn will correspond to a certain VPN. To do so, it is required
to change the NAD of the link connection toward the virtual node.
CONDITIONS

This assignment can be executed for VPN types Standard and Enhanced

SEQUENCE
1)

Select the link connection from the lc list and issue the command NAD (Network Assignment
Domain): Change.

2)

In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph 5.1.1 and confirm by clicking on OK. Click again on OK of the dialog box.

1AA 00014 0004 (9007) A4 ALICE 04.10

As a result of this operation, the boundary CTP is assigned to the above NAD.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

256 / 258

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.1.3.1 NAP Assignment

5.1.3.3 VPN assignment of the bandwidth

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.1.4 Assignment of the link connection within an RM domain


SCOPE
The scope of this procedure is to assign the desired link connection to a certain NAD ( Initiator Name ),
which corresponds to a certain RM Operator, which in turn will correspond to a certain VPN.
CONDITIONS
Restricted )

This assignment can be executed for all VPN types ( Standard / Enhanced /

This assignment is MANDATORY for Restricted VPN


SEQUENCE
1)

Select the NAP(s) from the Nap list and issue the command NAD (Network Assignment
Domain): Change.

2)

In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph 11.2 and confirm by clicking on OK. Click again on OK of the dialog box.

5.1.4.1 VPN assignment of the paths


5.1.4.1.1 VPN Assignment of paths terminated within an RM domain
SEQUENCE
1)

Select the path(s) from the Path list and issue


Assignment Domain): Change.

the command Actions: NAD (Network

2)

In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph 5.1.1 on page 254 and confirm by clicking on OK. Click again on OK of the dialog
box.

5.1.4.1.2 VPN Assignment of paths terminated outside an RM domain


SEQUENCE
1)

Select the path(s) from the Path list and issue


Assignment Domain): Change.

the command Actions: NAD (Network

2)

In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph 11.2 and confirm by clicking on OK. Click again on OK of the dialog box.

1AA 00014 0004 (9007) A4 ALICE 04.10

The NAP and the boundary CTP are not assigned automatically: the operator must execute the
procedures described at paragraphs 5.1.3.1 and 5.1.3.2 on page 256.

ED

01

SC.3:OPERATION
3AL 61348 AA AA
258

257 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

Constraints, 169

Implementation, 84

ED

01

Ring, 63

Startup, 12
Subnetwork, 18

Leg, 173

N
U

NAP, 103
Upload, 103

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INDEX
Payload, 86

Path, 109

END OF DOCUMENT

SC.3:OPERATION

3AL 61348 AA AA

258

258 / 258

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM REL.7. 2 OPERATORS HANDBOOK

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9
9
9
10

2 FAULT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Elementary Alarms and RM Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Alarm Enabling/Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Q3 Alarm Enabling/Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 QB3* Enabling UPA on specific CTP/CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 Enable / Disable frame supervision alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4 ISDNPRA alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Alarm Severity Assignment Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 ASAP list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 ASAP create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3 ASAP correlate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.4 ASAP modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 SDH Object Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13
13
14
14
16
18
19
20
20
21
22
28
29

3 INTEGRATION OF 1354RM WITH SEC SECURITY SUBSYSTEM . . . . . . . . . . . . . . . . . . . . . . . .


3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 SEC Architecture on 1354RM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 SEC Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 Alarm Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Spurious alarm management on 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 New ASAP definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 Path Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 HOTrail Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 Physical Link/MSTrail Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

41
41
41
42
43
46
46
46
48
48

4 INTRODUCTION TO MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Alarm navigation and fault localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Path in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Physical link in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51
51
53
55

01

050207

ED

DATE

CHANGE NOTE

M.RAGNI ITAVE

V.PORRO ITAVE

APPRAISAL AUTHORITY

ORIGINATOR

1354RM REL.7.2
OPERATORS HANDBOOK

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

1 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

56
59
60
61
62
63
64
66
67
71
75
77
78
78
78
78
78
79
80
82
82
82
82
83
83
84
85
87
89

5 PATH/TRAIL ALLOCATION FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Allocation failure diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1 Show Failure information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2 Obstacles and Unsatisfied Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.3 Other errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

91
91
92
92
93
106

6 JOIN / SPLIT TRAIL FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


6.1 Joint / Split HOTrails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Split a HOTrail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2 Join two HOTrails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3 Join / Split trail diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

107
107
107
107
111

7 DIAGNOSTIC OF THE NPE RING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


7.1 The 4F MS Spring RM side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.1 Some useful definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.2 4f MSSpring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 User Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 Configuration State attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.2 MidProtocol Role ( NODE CONDITION) attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.3 Ring Active Condition attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.4 Span Active Condition attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5 Ring Pending Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.6 Span Pending Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

113
113
113
113
123
124
127
129
130
131
131

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

2 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.1.3 HOtrail in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


4.1.4 MStrail in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.5 OMS trail in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.6 OCH trail in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.7 EML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.8 Client path in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.9 NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Diagnostic of the main objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Diagnostic of the path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Diagnostic of the trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 EML Domain Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 NE Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5 NE: Consistency Status=Not aligned ( TSDIM ONLY ) . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6 NE: Consistency Status=Failed to Align ( TSDIM ONLY ) . . . . . . . . . . . . . . . . . . . . . . . .
4.2.7 NE: Consistency Status=Consistency Mismatch ( TSDIM ONLY ) . . . . . . . . . . . . . . . .
4.2.8 NE: NE Communication Problems: NE unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.9 NE Config. Download Status = fail to Disable / Enable . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.10 NE: NEnot EML Aligned_auditfailed / misaligned ( for SENIM ONLY ) . . . . . . . . . . . .
4.2.11 Physical connection diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.12 SDH Port Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.13 SDH port Consistency status ( for SENIM ONLY)=Not found . . . . . . . . . . . . . . . . . . . .
4.2.14 SDH port Consistency status ( for SENIM ONLY)=Unknown . . . . . . . . . . . . . . . . . . . .
4.2.15 SDH port Upload status ( for TSDIM ONLY)=Not found . . . . . . . . . . . . . . . . . . . . . . . .
4.2.16 SDH port Upload status ( for TSDIM ONLY)=Wrong . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.17 Routing link diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.18 Subnetwork diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.19 Subnetwork diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.20 Node diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.21 Payload Configuration Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7.2.7 Lockout Working Ring attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


7.2.8 Lockout Working Span attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.9 Inhibition chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.10 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

132
132
132
134

8 NMLEML CONSISTENCY CHECKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


8.1 NMLEML Consistency Checks ( SENIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1 Consistency audit ( SENIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.2 Consistency download ( SENIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Example of SENIM NE misaligned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 SENIM NM misaligned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 NMLEML Consistency Checks ( Q3 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.1 Download disable management ( Q3 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2 Ne isolation detection and recovery ( Q3 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.3 Consistency download management ( Q3 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4 Consistency audit management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.5 Reporting during consistency ( TSDIM ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.6 Consistency Status Diagnostic ( Q3 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5 Example of Q3 NE misaligned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

147
147
147
148
149
151
155
155
155
155
156
156
158
159

9 MAINTENANCE TRACING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 J0 Section Trace Identifier Set / Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 J0 Trace Identifier Set/Modify Virtual to real NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 J0 Trace Identifier Set/Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 J0 Trace Identifier Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 J1/J2 Trace Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Path Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.1 Send Trace Identifier Definition/Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.2 Reading Received Trace Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 Tandem Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.1 Tandem Connection Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.2 Tandem Connection display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.3 Tandem Connection Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.4 TCT/TCM deImplement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.5 TCT/TCM global automatic deimplementation ( upon path/trail deimplement ) . . . . . . .
9.5 Manual remove of TCTs and TCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6 Monitoring function (POM) on intermediate points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.7 Loopback on PDH port / NAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.8 Loopback commands on CTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9 Craft Terminal Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

161
161
161
161
166
167
171
171
174
175
175
182
185
186
187
187
189
193
196
198

10 PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 SNCP path layer switch management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Multiplex Section Layer switch management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1 Automatic Protection Switch in 2fiber MSSPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2 Squelching in case of isolated nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.3 MSSPRING Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.4 Provisioning of the APS Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Management of switches at RM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 Display of the Protection blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.2 4F NPE RING Switch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

199
199
204
204
209
210
212
218
219
221

11 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Creating the Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

223
223
225

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

3 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

229
233
237
239
240
244
247
249
249
250
250
251
253
254
255
256
259
260
260
260
260
261
262
262
263
264

12 LOGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

265

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

268

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

4 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.3 Transport object Correlation to the Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


11.4 Tps correlation to the Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 PMTP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5.1 Examples of assignement of the attribute SIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 Counter Report Profile Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Threshold Report Profiles Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.8 Report Profile Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.9 Measure Activation, Stop and Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.9.1 Measure Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.9.2 Measure Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.9.3 Measure Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10 Threshold Crossing Alarm (TCA) Profile creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.11 Threshold Crossing Alarm (TCA) Profile Correlation to the PMTP . . . . . . . . . . . . . . .
11.12 Merging of several Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.13 Displaying PM data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14 The pmNE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15 Archive Performance Monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15.1 Archive Performance Monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15.2 Retrieve Performance Monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15.3 Display Performance Monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15.4 Delete Monitored data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.16 Archive Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.17 Uncorrelate the transport from planned measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.18 Uncorrelate the tp from planned measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.19 Remove from RM menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.20 Uncorrelate the counter/threshold report profile from the measure . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LIST OF FIGURES AND TABLES


FIGURES
Figure 1. Path: Show/Set Attributes: alarm enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. CAP Alarm Enabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. CAP: Show/Set Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. CAP: Show/Set Attributes: alarm enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Alarm Profile List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. ASAP Creation dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Correlating paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Trail: Alarm: Management... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Object correlation to an alarm profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Alarm profile list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. ASAP selected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Auto Mode Disabled/Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. ASAP Profile atributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Alarm Management Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Counter summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Physical Connection Alarm sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Navigation: External Application: 1354RM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Path alarm sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Path Naps view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Path Alarm details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Physical connection structure window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Alarm details window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. HOtrail alarm sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Trail structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Alarmed object list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Example of alarm detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. MS Trail alarm sublist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. MStrail structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Alarm details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. OMS trail structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. EML sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. EML navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. EML Show/Set Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Client path routing view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Alarm detail list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. NE Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. NE Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Allocation failure management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Path List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Netscape Path/Trail allocation failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Failed Object frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Netscape Path Trail allocation failure: problem summary frame. . . . . . . . . . . . . . . . . . . .
Figure 43. ProblemType and Constraint list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Route display components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. END 1 / END 2 termination point names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Problem Detail frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Netscape Path/Trail allocation failure description window. . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. Generic Help on allocation failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Generic Help on allocation failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. Example of problem description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

15
16
17
17
20
21
22
23
24
25
26
27
28
47
52
52
53
53
54
54
55
55
56
57
58
58
59
59
60
61
62
62
63
64
64
65
65
91
92
93
94
95
95
96
96
97
98
99
99
99

SC.4:MAINTENANCE
3AL 61348 AA AA
268

5 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

100
101
102
103
104
105
106
108
109
109
116
117
117
118
124
124
125
127
128
128
129
129
130
130
130
131
131
132
132
132
135
136
137
138
139
140
141
142
143
144
145
146
146
149
149
150
151
152
153
153
154
154
162
163

SC.4:MAINTENANCE
3AL 61348 AA AA
268

6 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 51. Problem menu list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 52. Example of display of a protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 53. Example of display of a protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. Constraint List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. Processed Constraint List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. Examples of interpretation of the Constraint list rows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. Example of OTHER ERRROR display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. state diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. state A: 2 HO trails (A, B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. state H: 1 HO trail (C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. bidirectional protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. unidirectional protected path (using working resource between nodes E and D) . . . . . .
Figure 63. unidirectional protected path (using protection resource between nodes E and D) . . . .
Figure 64. broadcast protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. 4 fibre MS SP reporting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. ConfigurationState = virtual icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. ConfigurationState diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. ConfigurationState = enabled/active icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. MidProtocolRole ( NODE CONDITION ) icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. WestProtocolRole icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. EastProtocolRole icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. East/West failure Of Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 73. East/West ring active condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 74. East span active condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 75. West span active condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 76. East / West ring pending command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 77. East span pending command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 78. West span pending command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 79. East / West Lockout Working Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 80. East / West Lockout Working Span . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 81. Bidirectional Signal Fail / Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 82. Bidirectional Signal Fail / Ring cleared .WTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 83. Double Bidirectional Signal Fail / Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 84. Forced Switch / Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 85. Double Forced Switch / Ring to different nodes, node isolated . . . . . . . . . . . . . . . . . . . . .
Figure 86. Double signal Fail / ring, node isolated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 87. Forced Switch / Span . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 88. Signal Fail / Ring pending, Forced Switch / Ring pending . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 89. Signal Fail Span, Signal Fail / Ring pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 90. Span Switch Request: Exercise East menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 91. Span Switch Request: Exercise East. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 92. Ring Switch Request: Exercise East menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 93. Ring Switch Request: Exercise East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 94. 1353NM map: misaligned NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 95. Path list: the path is disabled (OOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 96. NE: Consistency Audit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 97. Consistency report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 98. Node list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 99. Consistency report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 100. Consistency Download popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 101. Confirmation dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 102. Consistency download report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 103. Physical Conn: Configuration: Trace Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 104. Section Trace Identifier wizard: Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 105. Section Trace Identifier wizard: step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 106. Section Trace Identifier dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 107. Trail: Configuration: Trace Identifier Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 108. Trace Identifier wizard: Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 109. Trace Identifier definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 110. Path: Configuration: Trace Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 111. Path trace identifier step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 112. Path trace identifier definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 113. Configuration: Tandem Connection popup menu item . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 114. Tandem Connection Management wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 115. Action selection radio buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 116. Tandem Connection createstep 2TP selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 117. TCT attributes specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 118. Path routing display ( tandem flag ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 119. Path routing view: tandem flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 120. Path icon on browser: tandem connection state icon . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 121. Tcm/tct list selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 122. Tcm/Tct list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 123. Path NAPs view with TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 124. Tandem Connection wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 125. Path: Configuration: POM on Ctps popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 126. Routing Display: path CTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 127. CTP: Trace identifier read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 128. Nap: Manage Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 129. Loopback active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 130. Nap loopback status supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 131. CTP: Internal Loopback: Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 132. CTP: Internal Loopback display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 133. Path:Manage SNCP menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 134. Example of display of a B & S connection in topology. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 135. Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 136. Connection in topology attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 137. HOTrail with and without enhanced connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 138. Effect of a BRIDGE EAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 139. Effect of a BRIDGE WEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 140. Effect of a SWITCH EAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 141. Effect of a SWITCH WEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 142. :Example of six nodes ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 143. Step 4: Final situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 144. Drop and Continue at the service nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 145. Example of squelching table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 146. MSSpring: Display All related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 147. Examples of actual position of the switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 148. PM functional buttons in the browser window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 149. Measure Creation dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 150. PM domain related items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 151. Measure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 152. Measure: Actions pulldown menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 153. Transport correlation to a measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 154. Path: Actions: Performance Measurement: Add to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 155. Performance Measurement: Add to dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 156. Correlate measure to path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 157. Performance Monitoring: Correlate to Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 158. Measure TP list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

164
165
167
168
169
172
173
174
178
179
180
180
181
182
183
183
184
184
185
187
190
191
192
193
194
195
196
197
199
201
202
202
203
204
205
205
206
208
209
211
213
219
219
223
225
227
228
229
230
231
231
232
234
234

SC.4:MAINTENANCE
3AL 61348 AA AA
268

7 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

235
236
237
239
239
239
241
242
242
243
245
246
246
247
248
252
253
254
256
257
258
263
265
267

SC.4:MAINTENANCE
3AL 61348 AA AA
268

8 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 159. PM tp related items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 160. PM tp view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 161. PMTP Show / Set Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 162. Side of the pmctps in a b&s connection ( signal from NEA to NEB ) . . . . . . . . . . . . .
Figure 163. Side of the pmctps in a b&s connection ( signal from NEB to NEA ) . . . . . . . . . . . . .
Figure 164. Side of the ctp/nap for a unidirectional connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 165. Counter Report Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 166. Counter Report profile list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 167. Counter report profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 168. Example of generated counter report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 169. Create: Threshold Report dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 170. Threshold Report Profile list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 171. Threshold report icon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 172. Measure correlation popup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 173. Correlate report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 174. TCA Profile creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 175. PMTP: Perform.Monitoring: Correlate to TCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 176. Measure merging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 177. pmNE Show/Set attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 178. PM tp view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 179. PM transport view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 180. Object containment tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 181. Event Log filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 182. Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1 INTRODUCTION
1.1 Purpose of the document
The aim of this document is to describe the operations related to the maintenance of the protection network
controlled by the 1354RM.

1.2 Target audience


This document is intended for people who are in charge of the maintenance of the network.
Before starting this document, it is recommended reading the following handbook:

1330AS Operators Handbook,

1353NM Operators Handbook,

the Operators Handbooks of the supervised Network Elements

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

9 / 268

1.3 Document description

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This section covers the following topics:


ALARM MANAGEMENT

Elementary Alarms and Probable Causes

Alarm Enabling/Disabling

ASAP

Alarm Propagation

Tandem Alarm Propagation

WDM Alarm Propagation

SEC CUSTOMIZATION AND SPURIOUS ALARM MNG

1330AS SECNAD customization

Spurious alarm Management

DIAGNOSTICS

Alarm Navigation

Diagnostic

PATH/TRAIL fail to allocate

JoinSplit trail

NPE Diagnostic

NMLEML Consistency QB3*

NMLEML Consistency TSDIM

MAINTENANCE TRACING

POM

TANDEM

SECTION TRACE

PATH TRACE

LOOPBACK

1AA 00014 0004 (9007) A4 ALICE 04.10

PROTECTION MANAGEMENT

ED

SNCP path switch management

2F MSSPRING

Management of switches at RM interface

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

10 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

PERFORMANCE MONITORING

Performance Monitoring

Create Measure

Transport Correlation to Measure

Tps Correlation to Measure

PMPT Attributes

Counter Report Profile Creation

Threshold Report Profiles Creation

Report Profile Correlation

Measure Activation/Stop/Consistency

TCA Profile Creation

TCA Profile Correlation to PMTP

Measure Merging

PM data Display

pmNE

PM Archive

Archive Session

Uncorrelate transport from Measure

Remove from RM menu

LOGGER

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

Logger

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

11 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

12 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2 FAULT MANAGEMENT
Alarm messages on elementary objects (nap, cap, ctp, port, mstp) are received from EML, processed and
propagated to the affected objects.
These alarms are propagated to the following objects:
a)

Transport entities (link connection, trail, path)

b)

Topological object (node, subnetwork, network)

Alarms are generated on paths, Physical Connections, Trails (both HO and MS).
Elementary Alarms are received from EML layer and processed by RM in order to determine the RM object
to be marked as faulty ( RM Object Impacted ). RM provides for the impacted object the Alarm Severity,
the Operational State and the Probable Cause.
SENIM and TSDIM are the protocols, respectively used for QB3* and QB3 equipments, which describe
the EML to NML communication.

2.1 Elementary Alarms and RM Probable Causes

1AA 00014 0004 (9007) A4 ALICE 04.10

Elementary Alarms are described in the documentation of the Network Elements and in the documentation
of the EML NE.

N.B.

Transport Failure means that the path is not working endtoend. The managed domain could
be not interested to this alarm if it is not interested to the endtoend service. In this case, this
alarm can be squelched using an appropriate ASAP.

N.B.

Transport Incoming Failure means that a failure is entering the managed domain. This alarm
alone does not tell if the endtoend path works or not, it just tells that a wrong signal is entering.
The managed domain could be able to recover to the failure if the path is protected.

N.B.

Transport Outgoing Failure means that the managed domain is providing to the outside at
least one flow that is in error. This alarm does not tell if the endtoend path works or not. The
endtoend path could be protected outside the managed domain in such a way that the failure
can be recovered.

N.B.

Only when the path is not working endtoend, the operational state of the path itself is set to
disable.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

13 / 268

Alarms can be enabled or disabled only for TSDIM Network Elements. For QB3* Network Elements only
the propagation of the selected alarms can be enabled / disabled at RM level.
2.2.1 Q3 Alarm Enabling/Disabling
Q3 alarms can be enabled/disabled on the involved Network Element for a certain path.
SEQUENCE
a)

On path creation
1)

On path creation. The user can modify the following attributes:

Client Alarm Enabling Rule ( On Implementation/On Commissioning/Manual ). For TSDIM


equipments.

Transport Alarm Enabling Rule ( On Implementation/On Commissioning/Manual ) . For TSDIM


equipments.

2)

If the user, when creating the path, selects Alarm Enabling Rule: Manual, for this Path it will be
possible to enable / disable the involved alarms ( from the Path List: menu Actions: Alarms:
Configuration: enable/disable for Client or Transport.

b)

After path creation, from the Path List the user can modify the Client/Transport alarm enabling rule
by selecting the menu Actions: Alarms: Configuration: Client/Transport Enable/Disable rule, as in the
case of path creation.

c)

A dialog box is presented, which allows the enabling rule selection by means of a dictionary.
Alarms on PDH ports, NAPs, boundary CTPs are enabled if the Client/Transport ( Q3 only) Alarm
Enabling rule= on Implementation.

d)

To verify the successful change of this values the user can issue a Show/Set Attributes on the
selected path. See Figure 1.

N.B.

Q3 Alarms enabled means AIS, SSF and FERF enabled.


Q3 Alarms disabled means AIS, SSF and FERF disabled.
Q3 Alarms partially enabled means AIS and FERF enabled.

N.B.

Q3 Alarm Enabling/Disabling is also available for HO trails:

1AA 00014 0004 (9007) A4 ALICE 04.10

from the HO Trail List the user can modify the Transport alarm enabling rule by selecting the
menu Actions: Alarms: Configuration: Transport Enable/Disable.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

14 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.2 Alarm Enabling/Disabling

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 1. Path: Show/Set Attributes: alarm enabling

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

15 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This includes the ability of RM to setup alarm propagation rules other than the default ones defined for
physical connections related to virtual elements or based on Line Systems / Radio Links. By default AIS
and UPA on CTPs are never received by RM and this prevents a correct alarm from being propagated on
not terminated paths.
To enable the UPA alarm you can enter the Alarm enabling: LOP,EXBER,UPA command on the selected
CAP. See Figure 2.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 2. CAP Alarm Enabling.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

16 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.2.2 QB3* Enabling UPA on specific CTP/CAP

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 3. CAP: Show/Set Attributes

Figure 4. CAP: Show/Set Attributes: alarm enabling

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

17 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.2.3 Enable / Disable frame supervision alarm

The operator can select a PDH port and execute the command to enable or disable the frame supervision.
The command is available on 1641SX (managed by WX 1.7.1) on configurable 140, 34, 2 Mbit/s PDH
ports.

1AA 00014 0004 (9007) A4 ALICE 04.10

By default the frame supervision alarm and the consequent action (AIS) are disabled.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

18 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This feature allows enabling and disabling frame supervision on bulk or structured PDH flows.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.2.4 ISDNPRA alarm management

Refer to Section Operation. In particular see paragraph ISDN

ED

01

primary access management.

SC.4:MAINTENANCE

3AL 61348 AA AA

268

19 / 268

RM Object Severity is the RM Object ALARMSTATUS field value, which depends on the correlated ASAP
(Alarm Severity Assignement Profile) .
ASAP is managed for Physical Connections, MSTrails, HOTrails, paths.
The main operations relevant to ASAP are LIST, CREATE, CORRELATE and MODIFY.
2.3.1 ASAP list
The ASAP class is inserted under the Network Domain. From the browser the operator points with the
mouse to the Network Domain, issuing Search: Related Items: Alarm Profiles . The list of the current
profiles is displayed. See Figure 5. as an example.

Figure 5. Alarm Profile List.


The severity can be no alarm if the alarm must not be emitted.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

A default ASAP is available; when a path, a trail or a physical connection is created, the default
ASAP is assigned.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

20 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.3 Alarm Severity Assignment Profile

2.3.2 ASAP create

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The user can create new ASAPs. The command is also available at the user interface from the path,
trail or physical connection views. The sequence is as follows:
1)

From the browser point with the mouse to the Network Domain and issue the command Alarm:
Create Alarm Profile. The ASAP Creation dialog box is displayed. See Figure 6.

2)

Enter via keyboard the ASAP userlabel and assign the suitable severity to the relevant probable
cause/s. Click on button Create to confirm the creation.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 6. ASAP Creation dialog box.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

21 / 268

A correlation action is available in order to assign a new ASAP to relevant objects. The command
is also available at the user interface from the path, trail or physical connection views. One of the
possible sequences is as follows:
1)

Select the path/paths from path list and select Actions: Alarm: Management... as indicated in
the window shown in Figure 7. Figure 8. shows an other example. The object correlation to an
alarm profile dialog box is displayed ( See Figure 9. on page 24 ).
This dialog box contains
also the ASAP create button. See above paragraph 2.3.2 on page 21.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 7. Correlating paths

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

22 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.3.3 ASAP correlate

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 8. Trail: Alarm: Management...

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

23 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

REFRESH
END POINT LIST

ASAP LIST

EQPT ALARM

ENABLE/DISABLE

Figure 9. Object correlation to an alarm profile


2)

Select the ASAP list button as can be seen from Figure 9.

1AA 00014 0004 (9007) A4 ALICE 04.10

The Alarm profile list window is presented ( see Figure 10. on page 25).

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

24 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 10. Alarm profile list

1AA 00014 0004 (9007) A4 ALICE 04.10

3)

ED

01

Select the involved profile and click on button Apply. The selected ASAP icon is displayed in
the Correlate ASAP dialog box, as per Figure 11. Click on Next button to continue.

SC.4:MAINTENANCE
3AL 61348 AA AA
268

25 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 11. ASAP selected.

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

26 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 12. Auto Mode Disabled/Enabled


AUTO MODE button
The auto mode button can be set to enable or disable. This feature allows managing the auto mode
defined, according to ITUT G.806, in the alarm port mode. This mode is supported by OMSN (Low
Capacity starting from release 4.3B and 1670SM starting from release 4.3) on SDH ports, PDH ports and
on Ethernet Gigabit ports.
A port, in terms of defect supervision, can be:
Not monitored (i.e. the detected defects are never reported). In the current NE implementation, this is
achieved by setting an appropriate ASAP able to disable the reporting

1AA 00014 0004 (9007) A4 ALICE 04.10

Monitored (the detected defects are reported. This is achieved using an ASAP enabling the reporting).
Auto: the port is not monitored but waiting to go to the monitored state (provided the ASAP is different
than no alarm). The trigger to go from auto to monitored state is the first detection of the signal (i.e. the
clearing of the LOS defect) or a command from the NMS (e.g. RM).
The Auto state is initialized by means of a NMS command.
4)

ED

01

Click on Finish button.


SC.4:MAINTENANCE
3AL 61348 AA AA
268

27 / 268

2.3.4 ASAP modify

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The user can modify a profile simply issuing a Show/Set Attributes of the profile. See Figure 13.

Figure 13. ASAP Profile atributes.


When a new ASAP is assigned to an object or the associated one is modified, the severity of alarms
present on the object is reevalueted clearing the alarm and then generating the alarm with the new
severity if different from no alarm
remSDHFailure alarm activation

1AA 00014 0004 (9007) A4 ALICE 04.10

By default this alarm is deactivated since the default ASAP sets it to notAlarmed.
To activate it, a new ASAP has to be created and correlated to the involved path.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

28 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.4 SDH Object Alarm Propagation


The tables listed in the following, summarize the alarm propagation. Elementary Alarms are received from
EML layer and processed by RM in order to determine the RM object to be marked as faulty ( RM Object
Impacted ). RM provides for the impacted object the Alarm Severity, the Operational State and the Probable Cause.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

29 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

30 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

31 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

32 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

33 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

34 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

35 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

36 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

37 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

38 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

39 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

40 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3 INTEGRATION OF 1354RM WITH SEC SECURITY SUBSYSTEM


3.1 Introduction
This Chapter deals about the following subjects:

SEC Architecture on 1354RM System

SEC Administration

Alarm Access Configuration

3.1.1 SEC Architecture on 1354RM System


The SEC Subsystem is composed of two permanent processes:

secim process, which is the agent of the Security Subsystem and keep all the informations related
to the users and the system. Secim process is running only on 1354RMIM.

lss process, which is a kind of gate for applications related to user Security profile. One lss process
is instantiated for each workstation/server belonging to the 1354RM system (1 for each presentation
and each IM).
These permanent processes are configured to automatically run after the installation.

The SEC integration on 1354RM, as a first step, is intended only for the integration of Security
Management within AS (Alarm Surveillance). This means that each 1354RM operator using AS is able
to view/manage only alarms coming from Network resources that it can manage.

1AA 00014 0004 (9007) A4 ALICE 04.10

In order to have inside SEC Subsystem all the informations concerning Security, SEC is also integrated
in SMF, in order to get informations related to new users, user removal, and initiator management .
Moreover the integration of SEC in SMF is also related to the Backup operation. Each time a new Operator
backup is performed also SEC database is backuped.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

41 / 268

SEC Subsystem is provided with a default customization for which on an RM is automatically configured
to run secim process if RMIM and lss process for each kind of RM (IM|US.
The default configurations are put in the directory /usr/sec/1354RM_<NTWDOMAIN>.
In order to distinguish 1354RM SEC processes from the 1353SH ones the RM processes are called
<process_name>_1354RM_<NTWDOMAIN>.
The SEC configuration is also related to the automatic start of SEC process: in the /etc/inittab file is inserted
1
line
for
each
permanent
SEC
process.
This
line
invokes
the
script
run_SECIM|LSS_1354RM_<NTWDOMAIN> that checks for SEC abilitation to run and launch the
secim|lss_1354RM_<NTWDOMAIN> process. The automatic start of SEC processes is set on runlevel
4 that is the 1354RM runlevel default. No checks are performed on the 1354RM effective runlevel (it
is supposed to be 4).
During Operator Backup and Restore the SEC subsystem is stopped in order to add to the Operator
Informations also Informations related to SEC. The actions related to SEC start and stop are automatically
launched by SMF.
If some problem occurs during SMF>Operator Administration and SEC DB is not updated by the changes
done on RM through the SMF, it is possible to launch the script as snml user :
/usr/sec/integration/script/alignsecdb
This procedure starts from the last successful SEC command and alignes the SEC DB to the actual RM
Security definitions.
If at login time the user is alerted by the Message Box:
Security for 1354RM_<NTWDOMAIN> is not activated.
Please contact your System
Administrator, the problem is that the user is not defined in the SEC DB, or the SEC Subsystem has been
stopped (Restore proc.) or internal error.
N.B.: If the Message doesnt say 1354RM it is belonging to the SEC installed for SH
RESTRICTIONS

1AA 00014 0004 (9007) A4 ALICE 04.10

SEC 5.0 doesnt manage the scheduling time. This means that if an user has a scheduled rule this rule
is applied everytime. This limitation is not due to the integration level but to the fact that SEC 5.0 doesnt
support it.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

42 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.1.2 SEC Administration

3.1.3 Alarm Access Configuration

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Depending on 1354RM user definitions the following AS Access Rights are granted:

Where:
AS Access Rights means the AS accessability in terms of AS Administration:
ADMIN: Users can invoke AS Administration and Synchronization
VIEW: Users can invoke AS Synchronization but cannot interact with AS Administration functionalities
Alarm Access Rights shows the Alarm accessability rules that are allowed to user:

1AA 00014 0004 (9007) A4 ALICE 04.10

MGT: Users that have this capability, if allowed by the NAD Rule (see below), can manage accessible
alarms ( acknowledgement)

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

43 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Where:
Alarm AccessType shows the alarm accessibility
MGT means that user have the possibility to Acknowledge alarms (ManaGemenT)
RO means that user can only access alarms in a view mode (ReadOnly)
The MGT Alarm Accessability is granted if allowed by the System Profile (previous table) otherwise (for
LookOnly users) is set to RO.
X show which alarm types that can be accessed by user with the corresponding NAD Rule associated
X* show alarm types (only marked with user NAD) that can be accessed by user with the corresponding
NAD Rule associated
In order to provide a flexible way to configure AS Access on Alarm the configuration file
/usr/snml/conf/sec/1354RM_Ruler is provided.

1AA 00014 0004 (9007) A4 ALICE 04.10

This file drives the user Access Rights definition in the SECDB and have to be changed before the SEC
installation in order to keep coherent user creations.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

44 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In particular in order to give to LookOnly users the possibility to manage all the Alarms without keeping
into account the RM Rule change the line:
System_Profile
:
LookOnly
ASHISTUSM_FAD@AsHistoricalUsm :

ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,

as follows:
System_Profile
:
LookOnly
:ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm,
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm, ASHISTUSM_FAD@AsHistoricalUsm
On the other side, if the LookOnly users Accessability have to be extended to manage alarms depending
on 1354RM Access Rules (second table), change the line:
System_Profile
:
LookOnly
ASHISTUSM_FAD@AsHistoricalUsm :

ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,

as follows:
System_Profile
:
LookOnly
:
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,
ASHISTUSM_FAD@AsHistoricalUsm : ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

45 / 268

3.2 Spurious alarm management on 1354RM

3.2.1 New ASAP definition


Define a new ASAP setting the severity of all probable causes to Indeterminate. To do this perform the
following steps:
a)

Start the browser.

b)

Select the 1354RM icon.

c)

Point with the mouse at the Network Domain and issue the command Alarm: Create Alarm Profile.

d)

Fill User Label field with Indet_Alarm_Profile

e)

Change to Indeterminate the severity associated to all the proposed probable causes.

f)

Click on Create button.

3.2.2 Path Alarm Management


The following procedures describe how to manage paths in order to avoid that alarms on them are reported
to 1330AS while they are under test.

1AA 00014 0004 (9007) A4 ALICE 04.10

3.2.2.1 Naps view after path creation


a)

The path has been created with Implementation Rule = User (default) and Propagation Rule = When
Implemented (default).

b)

As soon as the path is created a new window is opened reporting the path icon with its Naps (Naps
View). Click on Alarm icon making available all the icons relevant for alarm management.

c)

Select the path icon.

d)

Select menu Actions: Alarm Management...; the correlation window is opened.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

46 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

It is possible to avoid alarm generation for objects under testing.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 14. Alarm Management Icons


e)

If in the ASAP space the Indet_Alarm_Profile is already present go to step h). (N.B. the ASAP
possibly provided is not the ASAP currently associated to the path, but it is the last referred ASAP).

f)

Click on Alarm Profile list button; the list of the available ASAP is provided.

g)

Select the Indet_Alarm_Profile ASAP. Click on Apply.

h)

Click on Next button, then on Finish button. At this point the path is correlated to the relevant ASAP.

i)

Implement the path.

From this point in time on alarms are reported to the path and visible by means of 1354RM USM, but no
alarm on this path is reported to 1330AS. Tests can be performed on the path without affecting
maintenance people.

1AA 00014 0004 (9007) A4 ALICE 04.10

3.2.2.2 Path commissioning


a)

From the Path List window select the relevant path.

b)

Select menu Actions: Alarm Management...; the correlation window is opened.

c)

If in the ASAP space the default ASAP is already present go to step f )

d)

Click on Alarm Profile list button; the list of the available ASAP is provided.

e)

Select the Indet_Alarm_Profile ASAP. Click on Apply.

f)

Click on Next button, then on Finish button. At this point the path is correlated to the relevant ASAP.

g)

At this point the path is correlated to the default ASAP. Since this point in time alarm on the path(s)
are reported also to 1330AS.

h)

Commission the path.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

47 / 268

3.2.3 HOTrail Management

a)

Setup the trail setting Setup Rule = User (N.B. Default value is Automatic).

b)

As soon as the trail is defined a new window is open (Paths in Trail View).

c)

Open the popup menu on the trail icon (pressing right button of the mouse) and select the command
Alarms: Management... A new window is open (correlation wizard).

d)

If the Indet_Alarm_Profile is already present within the correlation window go to step g).

e)

Click on Alarm Profile list button; the list of the available ASAP is provided.

f)

Select the Indet_Alarm_Profile ASAP. Click on Next button.

g)

Click on Finish button. At this point the trail is correlated to the relevant ASAP .

h)

Allocate the trail.

i)

Implement the trail.

3.2.3.2 Trail commissioning


a)

There is no explicit commissioning on HOTrail. The scope of this phase is to cause the trail to report
alarms to 1330AS.

b)

On the Trail list window (possibly filtered on HOTrail) select the relevant trail(s).

c)

Select the command Action>Alarms>Management...

d)

A new window is open (correlation wizard).

e)

If in the ASAP space the default ASAP is already present click on Next button and go to h).

f)

Click on Alarm Profile list icon; the list of the available ASAP is provided.

g)

Select the default ASAP and click on Next button. The ASAP icon is inserted into the correlation
window.

h)

On the correlation window click on the icon Finish (the same as before). At this point the trail(s)
is(are) correlated to the default ASAP. From this point in time on alarms on trail(s) are reported also
to 1330AS.

3.2.4 Physical Link/MSTrail Management

1AA 00014 0004 (9007) A4 ALICE 04.10

3.2.4.1 Physical Link/MSTrail creation


a)

Activate the Physical Connection; this action causes that alarms possibly present on it are
immediately reported to 1330AS too.

b)

Navigate from Browser to the Physical Connection.

c)

From the popup menu associated to the Physical Connection (on browser) select the command
Configuration: Implement to create the associated MSTrail; this action causes that alarms possibly
present on the MSTrail are immediately reported to 1330AS too.
The Physical connection implementation creates the MSTrail(s)

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

48 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.2.3.1 Trail creation

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

d)

From the popup menu associated to the Physical Connection select the command Display: All
Related Item.

e)

Select MSTrail within the box that is open.

f)

Press No filter button; the associated MSTrail is provided below the Physical connection.

g)

From the popup menu associated to the Physical connection select the command Alarm:
Management; a new window is open (correlation window).

h)

If in the ASAP space the Indet_Alarm_Profile is already present go to step m).

i)

Click on Alarm Profile list button; the list of the available ASAP is provided )

j)

Select the Indet_Alarm_Profile ASAP and click on the icon Next. The ASAP icon is inserted into the
correlation window

k)

On the correlation window click on Finish button . At this point both the Physical Connection and the
MSTrail are correlated to the relevant ASAP. Alarm possibly sent to 1330AS are automatically
cleared (but must be acknowledged by operator to make them disappear).

l)

From the popup menu associated to the MSTrail select the


Alarm>CorrelateAlarmProfile; the MSTrail is added to the correlation window.

command

m ) On the correlation window click on the icon Start correlating all the specified objects . At this point
both the Physical Connection and the MSTrail are correlated to the relevant ASAP. Alarm possibly
sent to 1330AS are automatically cleared (but must be acknowledged by operator to make them
disappear).
3.2.4.2 Physical Link/MSTrail commissioning
There is no explicit commissioning of these entities. The mean of this phase is to cause both Physical Link
and MSTrail to report alarms to 1330AS.
a)
b)

c)
d)
e)
f)
g)

1AA 00014 0004 (9007) A4 ALICE 04.10

h)

ED

Put on the browser the relevant Physical Connection.


From the popup menu associated to the Physical Connection select the command Display>All
Related Item; select MSTrail within the box that is opened and then No filter button; the associated
MSTrail is provided below the Physical connection.
From the popup menu associated to the Physical connection select the command Alarm:
Management; a new window is open (correlation window).
Drag and drop the MS trail to the correlation window.
f in the ASAP space the default ASAP is already present go to step h)
Click on Alarm Profile icon; the list of the available ASAP is provided.
Select the default ASAP and click on the icon Next. The ASAP icon is inserted into the correlation
window.
On the correlation window click on the icon Finish. At this point both the Physical Connection and
the MSTrail are correlated to the default ASAP. Alarm relevant for these entities are sent again to
1330AS.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

49 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

50 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4 INTRODUCTION TO MAINTENANCE
Maintenance operations consist of several functions that have to be executed following failures on the
network.
Note that the protection network comprises:

Telecommunication network (Network Elements and physical connections)

Control network consisting of 1354RM and 1353NM

Data Communication Equipment (Routers and Bridges)

The maintenance operations inherent to the Routers and Bridges are described in the documentation of
the Routers and Bridges.

4.1 Alarm navigation and fault localization


The telecommunication network can bear various failures depending on the size of the resources.
The paths affected by a failure are automatically rerouted on the available route (spare or main).
Should a Network Element fully breakdown, the system will attempt to reroute all paths crossing it.
Therefore, should one NE breakdown, only local drop traffic would be lost.
The RM Operators control the network on the Workstation through the graphical interface.
The operator is informed on the telecommunication network alarms through:

A1330AS application.
Notice that from 1354RM Rel.5.2.B on, alarms reported at 1330AS application are ONLY those
affecting the resources managed by the actually logged operator. This mainly applies to VPN
operators.

the map displaying objects in different colours identifying the status

the browser

The navigation from the Counter summary window is the first level maintenance procedure.
This procedure which is described in the following, applies to each row of the Counter summary window.

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From the Counter summary window open the Alarm sublist clicking twice on the relevant row of the
Counter summary window. As an alternative select the row and issue the Sublist: Open pulldown
menu item. See Figure 15.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

51 / 268

The relevant Alarm sublist is presented. Figure 16. shows an example of Physical Connection Alarm
sublist.

Figure 16. Physical Connection Alarm sublist

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

Select the alarm from the sublist and navigate it by selecting the Navigation: External Application:
1354RM pulldown menu item.( See Figure 17. ). A confirmation dialog box appears. Click on OK
to confirm.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

52 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 15. Counter summary window

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 17. Navigation: External Application: 1354RM.

4.1.1 Path in service


The Path alarm sublist is shown in Figure 18.

Figure 18. Path alarm sublist

1AA 00014 0004 (9007) A4 ALICE 04.10

For the Path object the Nap view window and relative navigation window is presented:

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

53 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 19. Path Naps view


The severity can be no alarm if the alarm must not be emitted.

1AA 00014 0004 (9007) A4 ALICE 04.10

An example of Alarms details is shown in Figure 20.

Figure 20. Path Alarm details

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

54 / 268

4.1.2 Physical link in service

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

For the Physical connection object the physical connection structure window is presented:

Figure 21. Physical connection structure window

1AA 00014 0004 (9007) A4 ALICE 04.10

Alarmed objects are marked by an alarm icon. By clicking on this icon a window is presented, which
gives details on the selected alarm. See Figure 22.

Figure 22. Alarm details window.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

55 / 268

4.1.3 HOtrail in service

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The HOtrail alarm sublist is shown in Figure 23.

Figure 23. HOtrail alarm sublist

1AA 00014 0004 (9007) A4 ALICE 04.10

For the HOtrail object the path in trail window and the relevant navigation window is presented:

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

56 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 24. Trail structure

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

57 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 25. Alarmed object list

Figure 26. Example of alarm detail

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

58 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.1.4 MStrail in service

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The MStrail alarm sublist is shown in Figure 27.

Figure 27. MS Trail alarm sublist.

1AA 00014 0004 (9007) A4 ALICE 04.10

For the MStrail object the physical connection structure and relative navigation window is presented:

Figure 28. MStrail structure

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

59 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Alarmed objects are marked by an alarm icon. By clicking on this icon, the Alarms details window is
displayed. See Figure 29.

Figure 29. Alarm details.

4.1.5 OMS trail in service

1AA 00014 0004 (9007) A4 ALICE 04.10

Fro the OMS trail alarm sublist select the alarm and issue the navigation command. The OMS trail
structure window is presented.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

60 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 30. OMS trail structure


Alarmed objects are marked by an alarm icon. By clicking on this icon, the Alarms details window is
displayed.
4.1.6 OCH trail in service
From OCH trail alarm sublist select the alarm and perform the navigation.

1AA 00014 0004 (9007) A4 ALICE 04.10

The OCH trail structure window opens.


Alarmed objects are marked by an alarm icon. By clicking on this icon, the Alarms details window is
displayed.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

61 / 268

4.1.7 EML

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In the following is presented the Alarm processing sublist:

Figure 31. EML sublist


For Alarm processing (EML object), only the navigated object is presented in the browser window.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 32. EML navigation

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

62 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 33. EML Show/Set Attributes

4.1.8 Client path in service

1AA 00014 0004 (9007) A4 ALICE 04.10

From the Client path alarm sublist select the alarm and open the navigation. The relevant client path
routing view is displayed. See below figure.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

63 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 34. Client path routing view


Alarmed objects are marked by an alarm icon. By clicking on this icon, the Alarms details window is
displayed.

Figure 35. Alarm detail list

4.1.9 NE
In the following is presented the Alarm processing sublist:

1AA 00014 0004 (9007) A4 ALICE 04.10

For Alarm processing (NE object), only the navigated object is presented in the browser window.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

64 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 36. NE Alarm Sublist

Figure 37. NE Navigation

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

65 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This paragraph describes the diagnostic procedures to be executed for the main RM objects in case of
malfunction.

1AA 00014 0004 (9007) A4 ALICE 04.10

The objects are:

path

trail

EML Domain

NE

Physical Connection

SDH Port

Subnetwork

Node

Payload

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

66 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2 Diagnostic of the main objects

4.2.1 Diagnostic of the path

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The path diagnostic concerns the following attributes:

Path Alarm status

Path working status

4.2.1.1 Path Alarm status


Regardless the path alarm status, navigate the path from the Alarm Counter Summary
N.B.

The Path Alarm Status is Cleared if the path operational status is Enabled ( InService ), this
implies that a path using its spare route is not alarmed.

4.2.1.2 Path working status


The Path working status can be visualized on the Path List.
All the statuses whose description contains the ing suffix are of the workinprogress type. Hence the
path is in this status only for a certain period of time; the path should assume the Normal condition when
a certain timeout has expired. This condition does not require the Operators intervention. He must
intervene if one of the following conditions occurs:

failed to Add Leg

failed to Add Protection

failed to Release Resources

failed to Remove Leg

failed to Remove Protection

failed to Alllocate

failed to Deallocate

failed to Implement

failed to Deimplement

failed to Align SNCPs

failed to manage SNCPs

failed to change SNCP Mode

failed to connect

failed to disconnect

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

67 / 268

CONDITIONS

The path involved is of the broadcast type. The Operator entered an Add Leg
command on the Path involved.

CAUSES

Lack of resources

ACTIONS

Verify the resources (physical connections and payload structure).


Should the path be protected, the protection can be removed and command
Add Leg can be entered again.

4.2.1.4 Path: Failed to Add Protection


CONDITIONS

The path involved is of the unprotected type. The Operator entered command
Add Protection.

CAUSES

Lack of resources, i.e. the spare resource corresponding to the main one is
not available.

ACTIONS

Verify the resources (payload structure).

4.2.1.5 Path: Failed to Release Resources


CONDITIONS

The Operator has entered an Add Protection or Remove Protection command


on the path.

CAUSES

The cause is due to software latent errors.

ACTIONS

Contact Alcatel Technical Assistance Center.

4.2.1.6 Path: Failed to Remove Leg


CONDITIONS

The Operator has entered a Remove Leg command on a broadcast path.

CAUSES

The cause may be due to the fact that the path section deimplementation has
failed (leg to be removed).

ACTIONS

After having entered the command, perform an inspection at EML and NE layer
level.

1AA 00014 0004 (9007) A4 ALICE 04.10

4.2.1.7 Path: Failed to Remove Protection


CONDITIONS

The Operator has entered a Remove Protection command on the path.

CAUSES

The two possible causes are:

ACTIONS

ED

01

1)

if the command has been entered through the With check option, the
failed attempt to remove the protection may be due to the fact that the path
is utilizing the spare route.

2)

if the command has been entered through the No check option, the failed
attempt to remove the protection is due to the unsuccessful spare route
deimplementation.

In the second case above described, inspect the EML and NE layers.

SC.4:MAINTENANCE
3AL 61348 AA AA
268

68 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.1.3 Path: Failed to Add Leg

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.1.8 Path: Failed to Allocate


CONDITIONS

The user enters a path allocation command.

CAUSES

Lack of resources.

ACTIONS

Execute a provisioning of the suitable resources.

NOTE

For more detailed information refer to Chapter 5

PATH/TRAIL

ALLOCATION FAILURES
4.2.1.9 Path: Failed to Deallocate
CONDITIONS

The user entered a Path: Deallocation command.

CAUSES

Software latent errors.

ACTIONS

Contact Alcatel Technical Assistance Center.

4.2.1.10 Path: Failed to Implement


CONDITIONS

The user entered a Path Implementation command.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command, inspect at EML and NE layer level.

4.2.1.11 Path: Failed to Deimplement


CONDITIONS

The user entered a Path Deimplementation command.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command, perform an inspection at EML and NE layer
level.

4.2.1.12 Path: Failed to Change SNCP Mode


CONDITIONS

The Operator has previously entered a Set revertive/Set not revertive command
on the SNCP Operation mode attribute.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command, perform an inspection at EML and NE layer
level.

1AA 00014 0004 (9007) A4 ALICE 04.10

4.2.1.13 Path: Failed to Align SNCPs


CONDITIONS

The operation has been automatically launched by the system which aligns the
paths and trails whose attribute is SNCP status=unknown. It can be launched
in a manual mode by the Operator via command Synchronize Switch on
logically protected Path/trail/connInTopol.

CAUSES

The problem is mainly at EML level or is a RMEML communication problem.

ACTIONS
1)
2)

ED

01

Identify the protected connection that has failed.


In the Browser navigate up to the EML level.

SC.4:MAINTENANCE
3AL 61348 AA AA
268

69 / 268

CONDITIONS

The Operator has requested an SNCP management (Forced Switch


Main/Spare/Lockout.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command, perform an inspection at EML and NE layer
level.

4.2.1.15 Path: Failed to connect/disconnect

1AA 00014 0004 (9007) A4 ALICE 04.10

CONDITIONS

The Operator has requested one of the following operations:

HO trail join

HO trail split

HO trail connect/disconnect

path connect/disconnect

CAUSES

Data base misaligned

ACTIONS

Contact Alcatel Technical Assistance Center.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

70 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.1.14 Path: Failed to manage SNCPs

4.2.2 Diagnostic of the trail

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The trail diagnostic concerns the following attributes:

Alarm status

Working status

4.2.2.1 Trail Alarm status


Regardless the trail alarm status, navigate the trail from the Alarm Counter Summary. See Paragr. 4.1
4.2.2.2 Trail working status
The Trail working status can be visualized on the Trail List.
All the statuses whose description contains the ing suffix are of the workinprogress type. Hence the
trail is in this status only for a certain period of time; the trail should assume the Normal condition when
a certain timeout has expired. This condition does not require the Operators intervention. He must
intervene if one of the following conditions occurs:

failed to Add Protection

failed to Release Resources

failed to Remove Protection

failed to Alllocate

failed to Deallocate

failed to Implement

failed to Deimplement

failed to configure

failed to Remove

failed to Align SNCPs

failed to manage SNCPs

failed to change SNCP Mode

failed to connect

failed to disconnect

failed to split

failed to join

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

71 / 268

CONDITIONS

The trail involved is of the unprotected type. The Operator entered command
Add Protection.

CAUSES

Lack of resources, i.e. the spare resource corresponding to the main one is
not available.

ACTIONS

Verify the resources (payload structure).

4.2.2.4 Trail: Failed to Release Resources


CONDITIONS

The Operator has entered an Add Protection or Remove Protection command


on the trail.

CAUSES

The cause is due to software latent errors.

ACTIONS

Contact Alcatel Technical Assistance Center.

4.2.2.5 Trail: Failed to Remove Protection


CONDITIONS

The Operator has entered a Remove Protection command on the path.

CAUSES

The two possible causes are:

ACTIONS

1)

if the command has been entered through the With check option, the
failed attempt to remove the protection may be due to the fact that the trail
is utilizing the spare route.

2)

if the command has been entered through the No check option, the failed
attempt to remove the protection is due to the unsuccessful spare route
deimplementation.

In the second case above described, inspect the EML and NE layers.

4.2.2.6 Trail: Failed to Allocate


CONDITIONS

The user enters a trail allocation command.

CAUSES

Lack of resources.

ACTIONS

Execute a provisioning of the suitable resources.

NOTE

For more detailed information refer to Chapter 5

PATH/TRAIL

ALLOCATION FAILURES

1AA 00014 0004 (9007) A4 ALICE 04.10

4.2.2.7 Trail: Failed to Deallocate


CONDITIONS

The user entered a Path: Deallocation command.

CAUSES

Software latent errors.

ACTIONS

Contact Alcatel Technical Assistance Center.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

72 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.2.3 Trail: Failed to Add Protection

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.2.8 Trail: Failed to Implement


CONDITIONS

The user entered a Path Implementation command.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command, inspect at EML and NE layer level.

4.2.2.9 Trail: Failed to Deimplement


CONDITIONS

The user entered a Path Deimplementation command.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command, perform an inspection at EML and NE layer
level.

4.2.2.10 Trail: Failed to Change SNCP Mode


CONDITIONS

The Operator has previously entered a Set revertive/Set not revertive command
on the SNCP Operation mode attribute.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command, perform an inspection at EML and NE layer
level.

4.2.2.11 Trail; Failed to Align SNCPs


CONDITIONS

The operation has been automatically launched by the system which aligns the
paths and trails whose attribute is SNCP status=unknown. It can be launched
in a manual mode by the Operator via command Synchronize Switch on
logically protected Path/trail/connInTopol.

CAUSES

The problem is mainly at EML level or is a RMEML communication problem.

ACTIONS
1)
2)

Identify the protected connection that has failed.


In the Browser navigate up to the EML level.

1AA 00014 0004 (9007) A4 ALICE 04.10

4.2.2.12 Trail: Failed to manage SNCPs


CONDITIONS

The Operator has requested an SNCP management (Forced Switch


Main/Spare/Lockout.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command, perform an inspection at EML and NE layer
level.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

73 / 268

4.2.2.13 Trail: Failed to configure


The working state is Fail to Configure.

CAUSES
1)

Negative answer from EML: failed creation / connectivity object removal

2)

Communication error received from EML. It may be due to a crash of EML.

3)

Violation of the contraints on nodes (sometimes).

1)

Inspect the NM side in order to detect a possible NMRM disalignment

2)

Verify that EML is running and reexecute the payload configuration

3)

Perform again payload configuration. Consult Event Logger and


Additional Info. It may be necessary to launch the Consistency Download
operation on the EML involved.

ACTIONS

4.2.2.14 Trail: Failed to connect/disconnect


CONDITIONS

The trail working status is Failed to connect/disconnect.

CAUSES

One or more of the paths belonging to this trail is in the Fail to


connect/disconnect status. This is due to data base misalignment.

ACTIONS

Contact Alcatel Technical Assistance Center.

4.2.2.15 Trail: Failed to join/split


CONDITIONS

The user launched the trail join/split operation.

CAUSES

From the multiple reply of the Event Logger it is possible to determine:


1)

The operation was interrupted during a connect/disconnect phase.

2)

The operation was interrupted during a configuration phase.

ACTIONS

1AA 00014 0004 (9007) A4 ALICE 04.10

After having entered the command, perform an inspection at EML and NE layer
level.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

74 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONDITIONS

4.2.3 EML Domain Diagnostic

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.3.1 EML Alarm status


Regardless the EML alarm status, navigate EML from the Alarm Counter Summary as described at
paragraph 4.1 .
As an alternative, from the Browser you can select the 1354RM icon and issue the command Actions:
Display Main Related items: EML Domain.
The displayed object is blue if cannot be reached; otherwise it is green colored.
Furthermore the following attributes are presented:

Alarms Aligned

Alarms alignment. It can be: Normal, Failed, In progress. This attribute reflects the consequences
of the Synchronize command launched by the Operator.

EML Domain Alignment

The conditions cited herebelow:

EML not reachable

EML Alarms Aligned false

EML Alarms Alignment Failed

EML Domain Alignment Failed

are described in the following.

4.2.3.2 EML Not Reachable


CONDITIONS

blue EML= Not reachable

CAUSES
1)

EML erroneously registered on the local registration file

2)

EML processes not running

3)

TCPIP problems

1)

Verify the EML id on RM and NM.

2)

Restart EML

3)

Check the workstation physical connections. The last possible choice is


rebooting the workstations.

1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

75 / 268

CONDITIONS

From Browser the attribute EML Alarms Aligned is false / the attribute EML
Alarms Alignment is Failed / the attribute EML Domain Alignment is Failed.

CAUSES

The possible causes are indicated in the Event Logger.

1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

ED

01

1)

From Browser enter command EML Domain: Synchronize / Synchronize


Alarms.

2)

If the Synchronize Operation fails, display the events associated to the


EML Domain object from the Event Logger.
The affected object inspection involves the NEs/ports whose attribute is
Consistency status= normal. Moreover compare the same attributes
considering the values displayed on RM and those presented on NM/NE.
The Operator can now try to solve the problem at NE level utilizing the CT
(Craft Terminal) or the corresponding NM.
If the problem is not solved, launch Consistency Download on the NE
involved.

SC.4:MAINTENANCE
3AL 61348 AA AA
268

76 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.3.3 Alignment False/ Failed

4.2.4 NE Diagnostic

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The NE attributes displayed in the browser window are:

Alarm status

Consistency status. for TSDIM ONLY.


The values to consider for diagnostic are:

Not aligned.

Failed to align

Consistency Mismatch

NE communication problems. for TSDIM ONLY.


The values to consider for diagnostic are:

NE unreachable.

Configuration Download state


The values to consider for diagnostic are:

Fail to Disable

Fail to Enable

EMLreachable. Refer to EML diagnostic.

NE DB modified by CT. ( for TSDIM ONLY). The CT has been automatically enabled because of
isolation problem and some modifications have been made by the CT operator.

Craft Terminal Access State. The possible values are:

CT access granted=CT enabled+CTconnected

CT access required=CT disabled+CTconnected

CT not connected enabled

CT access denied=CT disabled+CT not connected

NE not EML aligned. for SENIM ONLY


The values to consider for diagnostic are:

neNotEmlAligned_auditfailed

neNotEmlAligned_misaligned

Upload status. for TSDIM ONLY.

1AA 00014 0004 (9007) A4 ALICE 04.10

The values to consider for diagnostic are:

ED

Not found=the NE is misaligned about physical objects, such as ports....

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

77 / 268

CONDITIONS

From Browser it is displayed as an icon

CAUSES

The consistency download is probably disabled

ACTIONS

Verify that the Consistency download is enabled. Then execute a consistency


download: ( i.e. global) toward the NE.
NOTICE THAT FOR TSD_IM NE THE RUN LEVEL CHANGE TO EXECUTE THE
CONSISTENCY DOWNLOAD IS NOT REQUIRED .

4.2.6 NE: Consistency Status=Failed to Align ( TSDIM ONLY )


CONDITIONS

From Browser it is displayed as an icon

CAUSES

Following an Audit operation a/some mismatches

ACTIONS

Inspect the browser Error Log.

4.2.7 NE: Consistency Status=Consistency Mismatch ( TSDIM ONLY )


CONDITIONS

From Browser it is displayed as an icon

CAUSES

The NE is probably unreachable.

ACTIONS

Inspect the browser Error Log and eventually execute a consistency download:
( i.e. global) toward the NE
NOTICE THAT FOR TSD_IM NE THE RUN LEVEL CHANGE TO EXECUTE THE
CONSISTENCY DOWNLOAD IS NOT REQUIRED .

4.2.8 NE: NE Communication Problems: NE unreachable


CONDITIONS

From Browser it is displayed as an icon.

CAUSES

The NE did not answer following a certain operation executed by RM. ( E.g. an
operation on a path, trail,...). The polling toward the NE is automatically started
and an automatic download is then executed.

ACTIONS

Verify, by means of the Error Log the last operation executed on the involved
connectivity object of the NE.

1AA 00014 0004 (9007) A4 ALICE 04.10

4.2.9 NE Config. Download Status = fail to Disable / Enable


CONDITIONS

From Browser it is displayed as a title

CAUSES

Wrong answer from EML

ACTIONS

Verify the EML layer

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

78 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.5 NE: Consistency Status=Not aligned ( TSDIM ONLY )

4.2.10 NE: NEnot EML Aligned_auditfailed / misaligned ( for SENIM ONLY )

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONDITIONS

From Browser it is displayed as a title

CAUSES
1)

EML/NE erroneously registered

2)

EML processes not running

3)

TCPIP problems

1)

Verify EML id/NE address

2)

Restart EML

3)

Verify the workstation physical connections

ACTIONS

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

79 / 268

4.2.11 Physical connection diagnostic

A physical connection failure is denoted by a color variation on the map.


Regardless the physical connection alarm status, navigate the path from the Alarm Counter Summary as
described at paragraph 4.1 .
4.2.11.2 PhysCon Working status
The Physical Connection working status can be visualized on the Browser.
From Brower the diagnostic relevant attribute is Working State if it assumes the following values:

Failed to Configure

Failed to Implement

Failed to Remove

All the object statuses, the description of which contains suffix ing are of the workinprogress type and
as a consequence are temporary.
4.2.11.3 PhysCon Failed to Configure
CONDITIONS

The working state is Fail to Configure. The user has previously started to modify
the payload.

CAUSES
1)

Negative answer from EML: failed creation / connectivity object removal

2)

Communication error received from EML. It may be due to a crash of EML.

3)

Violation of the contraints on nodes (sometimes).

1)

Inspect the NM side in order to detect a possible NMRM disalignment

2)

Verify that EML is running and reexecute the payload configuration

3)

Perform again payload configuration. Consult Event Logger and


Additional Info. It may be necessary to launch the Consistency Download
operation on the EML involved.

1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

80 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.11.1 PhysCon Alarm status

4.2.11.4 PhysCon Failed to Implement

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONDITIONS

The user has previously launched the Physical Connection Implementation


operation.

CAUSES
1)

Negative answer from EML: connectivity object implementation failed.

2)

Communication error

1)

Inspect the NM side in order to detect a possible NMRM disalignment

2)

Verify that EML is running and launch again the Physical Connection
Implementation operation.

ACTIONS

4.2.11.5 PhysCon Failed to Remove


CONDITIONS

The user has entered a Delete command from MIB

CAUSES
1)

Negative answer from EML: object removal failed.

2)

Communication error

1)

Inspect the NM side in order to detect a possible NMRM disalignment

2)

Verify that EML is running and launch again the Remove operation.

1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

81 / 268

The SDH ports are displayed from Browser by utilizing command NE: Display Related Items: SDH Ports.
The attribute involved are

Operational Status= disabled

Consistency status ( for SENIM ONLY). The values relevant to diagnostic are:

Not found. The board has been extracted. Objects assigned to RM belong to this board. Verify
alarms on related objects at RM and NM level.

Unknown. Communication problems at OS level.

Upload status ( for TSDIM ONLY). The values relevant to diagnostic are:

Not found. The board has been extracted. Objects assigned to RM belong to this board. Verify
alarms on related objects at RM and NM level.

Wrong Communication problems at OS level.

4.2.12.1 SDH port disabled


CONDITIONS

The icon displayed from the browser is distinguished by a bar and there is an
alarm icon near it.

CAUSES

Hardware or connected signals

ACTIONS

Inspect the port at hardware level.

4.2.13 SDH port Consistency status ( for SENIM ONLY)=Not found


CONDITIONS

This attribute is displayed by an icon in the browser

CAUSES

The board has been extracted. Objects assigned to RM belong to this board.

ACTIONS

IVerify alarms on related objects at RM and NM level.

4.2.14 SDH port Consistency status ( for SENIM ONLY)=Unknown


CONDITIONS

This attribute is displayed by an icon in the browser

CAUSES

Communication problems at OS level.

ACTIONS

Verify the communication between OS. Refer to EML diagnostic.

1AA 00014 0004 (9007) A4 ALICE 04.10

4.2.15 SDH port Upload status ( for TSDIM ONLY)=Not found


CONDITIONS

This attribute is displayed by an icon in the browser

CAUSES

The board has been extracted. Objects assigned to RM belong to this board.

ACTIONS

Verify alarms on related objects at RM and NM level.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

82 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.12 SDH Port Diagnostic

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.16 SDH port Upload status ( for TSDIM ONLY)=Wrong


CONDITIONS

This attribute is displayed by an icon in the browser

CAUSES

Communication problems at OS level.

ACTIONS

Verify the communication between OS. Refer to EML diagnostic.

4.2.17 Routing link diagnostics


The routing link diagnostic is intended as a verification of the values of counters displayed from Browser
and listed herebelow:

Idle disabled. It informs on the idle, disabled link connections

Busy disabled. It informs on the busy, disabled link connections.

The actions required are:

display the disabled link connections

continue the link connection diagnostic procedure.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

83 / 268

4.2.18 Subnetwork diagnostic

failed to Implement

failed to Remove

4.2.18.1 Subnetwork: Failed to Implement


CONDITIONS

The user entered a Subnetwork Implementation command.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command perform an inspection at EML and NE layer
level.

1AA 00014 0004 (9007) A4 ALICE 04.10

4.2.18.2 Subnetwork: Failed to Remove


CONDITIONS

The user entered a Subnetwork Delete from MIB command.

CAUSES

The subordinate EML/NEs.

ACTIONS

After having entered the command perform an inspection at EML and NE layer
level.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

84 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The Subnetwork diagnostic concerns the Working status attribute when assumes the following values:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.19 Subnetwork diagnostic


A failure along the ring is denoted by a color variation in the map. In the Browser the attribute taken into
consideration for diagnostic is Working State if it assumes the following values:

Failed to Configure

Failed to Implement

Failed to Remove

All the statuses whose description contains the ing suffix are of the workinprogress type. Hence the
object is in this status only for a certain period of time.

4.2.19.1 Subnetwork Failed to Configure


CONDITIONS

The Working state is Failed to configure. The user has previously launched
the Payload Modify operation.

CAUSES
1)

Negative answer from the NE: connectivity object creation/removal failed.

2)

Communication error received from EML. It may be due to an EML crash.

3)

Constraints violation on the nodes (in some cases).

1)

Inspect the NM side in order to detect a possible NMRM disalignment

2)

Verify that EML is running and reexecute the payload configuration

3)

Perform again payload configuration. Consult Event Logger and


Additional Info. It may be necessary to launch the Consistency Download
operation on the EML involved.

ACTIONS

4.2.19.2 Subnetwork Failed to Implement


CONDITIONS

The user has previously launched the Ring Implementation operation.

CAUSES
1)

Negative answer from the NE: connectivity object implementation failed.

2)

Communication error.

1)

Inspect the NM side in order to detect a possible NMRM disalignment

2)

Verify that EML is running and launch again the Implementation operation.

1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

85 / 268

4.2.19.3 Subnetwork Failed to Remove


The user has previously launched a Delete command from MIB.

CAUSES
1)

Negative answer from EML: object removal failed.

2)

Communication error.

1)

Inspect the NM side in order to detect a possible NMRM disalignment.

2)

Verify that EML is running and launch again the Remove operation.

1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

86 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONDITIONS

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.20 Node diagnostic


A node failure is denoted by a color variation in the map. In the Browser the attributes considered for
diagnostic are:

CT access status:

Working status:

Failed to Remove

Failed to Reset

Failed to Activate MS Spring

Reachable/Not reachable

4.2.20.1 Node Failed to Remove


CONDITIONS

The user has previously launched a Delete Command from MIB.

CAUSES
1)

Negative answer from EML: object removal failed.

2)

Communication error.

1)

Inspect the NM side in order to detect a possible NMRM disalignment.

2)

Verify that EML is running and launch again the Remove operation.

ACTIONS

4.2.20.2 Node Failed to Reset


CONDITIONS

The user has launched an Implementation command on the topology.


The command has been unsuccessful in that the NEs have not been reset.

CAUSES
1)

Negative answer from EML.

2)

Communication error.

1)

Inspect the NM side in order to detect a possible NMRM disalignment.

2)

Verify that EML is running and launch again the Implementation operation.

1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

87 / 268

4.2.20.3 Node Failed to Activate MS spring


The user has launched a Ring Implementation command.

CAUSES
1)

Negative answer from EML: connectivity object implementation failed.

2)

Communication error.

1)

Inspect the NM side in order to detect a possible NMRM disalignment.

2)

Verify that EML is running and launch again the Implementation operation.

ACTIONS

4.2.20.4 Node Reachable/Not reachable


CONDITIONS

blue NODE in the map= not reachable

CAUSES
1)

NE address erroneously registered

2)

EML processes not running

3)

TCPIP problems

1)

Verify the NE addresses

2)

Restart EML

3)

Verify the workstation physical connections

1AA 00014 0004 (9007) A4 ALICE 04.10

ACTIONS

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

88 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONDITIONS

4.2.21 Payload Configuration Diagnostic

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.21.1 Payload working status


The user issued a payload modify command. The payload modify command can be executed on:

PhysConn

HOlc

HOtrail
The working state of the above listed objects is Normal after the successful completion of the
configuration. The working state can be Fail to Configure for unsuccessful completion.
4.2.21.2 Fail to Configure
CONDITIONS

One of the objects is Fail to Configure; this condition is propagated to its


superordinate object ( e.g. the ET is the superordinate and the PhysConn is the
subordinate ).

CAUSES

The subordinate EML/NEs.

ACTIONS

Inspect the browser Show additional information to display the cause of the
problem and execute one of the following actions:

ED

01

1)

Execute again the payload modify command.

2)

In case of data misalignment perform the consistency download on the


affected objects.

SC.4:MAINTENANCE
3AL 61348 AA AA
268

89 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

90 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5 PATH/TRAIL ALLOCATION FAILURES


5.1 Introduction
Path/Trail allocation failures are localized in the browser Path/Trail list. Selecting the involved path/trail and
clicking on the Show Failure Information Tool button, the Netscape browser application starts and
displays all information relevant to the failure.
The failure identification tool is based on Internet technologies, such as HTML, Java programming
language and HTTP protocol.
The allocation failure of a path or trail is detected by the user by looking at the transport to allocate, whose
configuration state goes to Failed to allocate. This state is displayed in the path or trail list.
The information provided in case of allocation failure are summarized in Figure 38. on page 91, namely:

OBSTACLES AND UNSATISFIED CONSTRAINTS are managed with the following structure:

OBSTACLES. This problem type is described by a problem description which helps in solving
the problem.

UNSATISFIED CONSTRAINTS. A Constraint List is provided, indicating the failed constraint(s)

OBSTACLES AND UNSATISFIED CONSTRAINTS. Both Problem description and Constraint


List are provided.
OTHER ERRORS are not described in detail. They indicate errors for which no further information
is provided.

For OBSTACLES AND UNSATISFIED CONSTRAINTS Problem description and Constraint List are
presented with the support of a simple graphical representation of the path/trail routing.
The tool usage is described in the following paragraphs.

ALLOCATION FAILURE

OTHER
ERRORS

OBSTACLES AND
UNSATISFIED CONSTRAINTS

UNSATISFIED

1AA 00014 0004 (9007) A4 ALICE 04.10

OBSTACLES

CONSTRAINTS

OBSTACLES
&
UNSATISFIED
CONSTRAINTS

Figure 38. Allocation failure management

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

91 / 268

5.2.1 Show Failure information


SEQUENCE
a)

Select the involved path/trail and click on the Show Failure Information Tool button. This button
is also present in the path/trail routing view. The Netscape browser application starts and displays
the Netscape Path/Trail allocation failure window. See paragraph 5.2.3

SHOW FAILURE INFORMATION

WORKING STATE=FAILED TO ALLOCATE

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 39. Path List

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

92 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.2 Allocation failure diagnostic

5.2.2 Obstacles and Unsatisfied Constraints

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In case of Obstacles and Unsatisfied Constraints, the complete netscape view is provided.
SEQUENCE
a)

Select the involved path/trail and click on the Show Failure Information Tool button. This button is
also present in the path/trail routing view. The Netscape browser application starts and displays the
Netscape Path/Trail allocation failure window. See Figure 40. herebelow.

PROBLEM
WINDOW TITLE

SUMMARY

FAILED OBJECT

FRAME

FRAME

1AA 00014 0004 (9007) A4 ALICE 04.10

PROBLEM DETAIL FRAME

Figure 40. Netscape Path/Trail allocation failure.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

93 / 268

The Netscape Path/Trail allocation failure window shown in detail in Figure 42. on page 95 .
contains the following frames:
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

Window title: Netscape Path/Trail allocation failure.


Failed object frame. It contains:
path/trail userlabel (name)
type ( point to point or broadcast )

failure date
failure time
no. of failed legs ( for broadcast paths only )

Figure 41. Failed Object frame


Problem Summary frame. See Figure 42. It contains:
frame title: PATH: path type or TRAIL
one row per each failed leg. The relevant leg number is shown in the lefthand column.
Each leg is described as:
End1 label (node+port) and End2 label (node+port)

1AA 00014 0004 (9007) A4 ALICE 04.10

PROBLEM TYPE, reference to the html Problem Detail frame. The following cases
are possible:

ED

01

NO PROBLEMS. This string can be present only in correspondance to the Main


route when PROBLEMS are present on the Spare route

OBSTACLE PROBLEMS. The route cannot be completed because of a lack of


resources

CONSTRAINTS PROBLEMS. The route cannot be completed because some


constraints cannot be satisfied

OBSTACLE AND CONSTRAINTS PROBLEMS. Both obstacle and constraints


problems are present.

SC.4:MAINTENANCE
3AL 61348 AA AA
268

94 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Two columns are displayable: MAIN (problems on the main route) and SPARE (problems
on the spare route, only for protected paths/trail)

Figure 42. Netscape Path Trail allocation failure: problem summary frame.
b)

At this point you can select the problem type, or in case of unsatisfied constraints you can select the
constraint list. See Figure 43. herebelow.

Figure 43. ProblemType and Constraint list


1)

If you click on the Problem Type, reference to the html Problem Detail frame ( named
OBSTACLES and CONSTRAINTS PROBLEMS), the Problem Detail frame view will display the
selected leg. See Figure 46. on page 97.
The Problem Detail frame contains:
header ( upper lefthand side), constituted by:
Leg no. ,i.e. the selected leg number. This field is not present for point to point paths

1AA 00014 0004 (9007) A4 ALICE 04.10

ROUTE: End1 (node+port) and End2 (node+port)


route type: Main or Spare, followed by the PROBLEM TYPE
Failed routing display (lefthand side). It shows, per each row:

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

95 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

node icon (green triangle) with node name or link connection icon (yellow icon)
with link connection name: node A name node B name AU/TU pointer No.

Figure 44. Route display components.

1AA 00014 0004 (9007) A4 ALICE 04.10

END 1 name and END 2 name. See Figure 45. on page 96.

Figure 45. END 1 / END 2 termination point names.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

96 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Problem Type ( yellow string which is the html reference to the Path/Trail allocation
failure description window of Figure 47. on page 98.

Figure 46. Problem Detail frame.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

From the Problem Detail frame of Figure 46. select the problem type. The Path/Trail allocation failure
description window is displayed. See Figure 47. on page 98.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

97 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

FRAME

Figure 47. Netscape Path/Trail allocation failure description window.


The Path/Trail allocation failure description window contains:
Window title: Netscape Path/Trail allocation failure.
Failed object frame above described.
Problem Summary frame above described.

1AA 00014 0004 (9007) A4 ALICE 04.10

Generic Help on Allocation Failure. See Figure 48. on page 99. It contains a generic
description of the allocation failure.
A Main wiindow reload button is present in this frame,allowing the operator to display the main
window.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

98 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 48. Generic Help on allocation failure.

Problem description. See example in Figure 50. herebelow. It contains the detailed problem
description (Title and Explanation) of the problem and suggestions ( Hints ) how to solve the
problem.
Figure 49. Generic Help on allocation failure.

Figure 50. Example of problem description


The different problem types are:

NE Connection Not Supported


Explanation: The path/trail could not use a NE because it could not support a connection as
the one required.
Hints: If a constraint to use that NE has been set, try to remove it.

1AA 00014 0004 (9007) A4 ALICE 04.10

NE Connection State Not Allowed


Explanation: The path/trail could not use a NE because it does not allow the connection with
the current set of connections already engaged.
Hints: Try to remove some other connection for this NE.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

99 / 268

Infinite Cost

Hints: Change the cost of the related physical connection

No Free Link Connections


Explanation: The system tried to use a routing link without free link connections
Hints: Deallocate some paths/trails which use the same routing link or change the payload
configuration in order to create new link connections at the proper rate.

Improper Payload Configuration


Explanation: No one hop routing link exists related to a physical connection. This can be due
to an improper payload configuration or to the presence of a user defined HO trail
Hints: Try to change the payload configuration or split the HO trail.

Unsatisfied Constraints
Explanation: One or more of the constraints given to the path/trail cannot be satisfied
Hints: The only way to allocate the path/trail is to remove/modify some constraints

The left hand side frame contains the Problem menu list. Each menu item, if selected, will display its
problem explanation and some hints to solve it.

PROBLEM MENU

Figure 51. Problem menu list

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 52. and Figure 53. herebelow display an example of protected path allocation failure.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

100 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Explanation: The routing algorithm has found a route which uses a routing link with infinite cost

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

MAIN ROUTE

SPARE ROUTE

Figure 52. Example of display of a protected path

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

101 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SPARE

Figure 53. Example of display of a protected path

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

102 / 268

If you click on the Constraint List icon, as per Figure 43. on page 95, the Constrain List is
presented. See Figure 54. on page 103. Per each leg its Constraint List can be displayed in case
of Unsatisfied Constraints.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2)

Figure 54. Constraint List

1AA 00014 0004 (9007) A4 ALICE 04.10

An example of Constraint List is shown in Figure 55. on page 104.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

103 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 55. Processed Constraint List.


This graphical table contains one row per each constraint. The table is constituted by : (see Figure 55. )

title: PROCESSED CONSTRAINTS LIST ( route ), where route is equal to Main or Spare

four columns, namely:


satisfied/unsatisfied constraint. The green semaphore icon means that the constraint is
satisfied. The red semaphore icon means that the constraint is not satisfied. In the latter case
the deletion of this constraint will probably solve the allocation problem.

1AA 00014 0004 (9007) A4 ALICE 04.10

constraint usage in the main route. The oneway icon means USE while the no entry icon
means NOT USE.
constraint usage in the spare route. The oneway icon means USE while the no entry icon
means NOT USE.
topology used as constraint. It includes the icon and the userlabel of the topological object
An example of interpretation of some rows is given in Figure 56. on page 105

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

104 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 56. Examples of interpretation of the Constraint list rows.

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

105 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

OTHER ERRORS are not described in detail. They indicate errors for which no other information is
provided.
An example of other error display is shown in Figure 57. herebelow.

OTHER ERROR

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 57. Example of OTHER ERRROR display

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

106 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.2.3 Other errors

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6 JOIN / SPLIT TRAIL FAILURE


6.1 Joint / Split HOTrails
The Split / Joint Physical Connections and HOTrails are part of a suit of tools for Network Modification.
6.1.1 Split a HOTrail
A given HOTrail crossing at HO a Node can be split in order to perform crossing at LO. This enables the
usage of LO resources in the splitting Node.
The operation reproduces in the splitting node the same payload structure of the starting trail.
The operation can be performed after the split of a Physical Connection.
Input to the operation is the HOTrail to split.
From the user point of view, the split trail operation consists of 2 phases:
a)

the user specifies the trail to split: RM checks in which nodes of the trail the split can be performed
(i.e. nodes where LO capability is available, nodes not belonging to protected parts of the trail ...) and
prompts to the user the list of these nodes; no other action is accomplished by RM neither in RM MIB
nor in the NEs;

b)

the user selects the splitting node and the operation can be executed.

As a consequence of the operation:

the old HOTrail is deleted

two new HOTrails are created

The LOPaths crossing the splitting Node are modified by adding LO passthrough connection.
The related protection indexes are updated.
The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
splitting node.
The operation reduces the impacts on the existing traffic: the LOPaths client of the involved HO trails are
disconnected only for the time necessary to perform the operation: only the segment of network between
the end nodes of the involved HO trails is affected.
6.1.2 Join two HOTrails
Two HOTrails entering in a given NE can be joined in order to reduce the LO usage of resources.

1AA 00014 0004 (9007) A4 ALICE 04.10

Inputs to the procedure are :

the HOTrails to join.


RM performs the following checks:

the 2 HO Trails must have the same payload structure;

it must be possible to create a HO connection in the intermediate node;

all LOpaths using the original HOTrails are crossing with passthrough connections the intermediate NE without LO timeslot interchange.
As a consequence of the operation:

the old HOTrails are deleted

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

107 / 268

the new HOTrail is created


the LOPaths crossing the original HOTrails are modified by removing the passthrough connections in the intermediate NE. The related protection indexes are updated.

The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
intermediate node.
The operation reduces the impacts on the existing traffic: LOPaths client of the involved HO trails are
disconnected only for the time necessary to perform the operation and only in the segment of network between the end nodes of the involved HO trails.
6.1.2.1 Description of the operations
Both split and join HO Trails are complex operations: they are composed of elementary operations (payload configuration, trail implementation,...), as described in the following state diagram.

disconnect client paths


from 1W to 4 E
deconfigure trail A
deconfigure trail B
deimplement conn 2 of trail A
deimplement conn 2 of trail B

JOIN

A
B
C

connect client paths


from 1W to 4E
configure trail A
configure trail B
implement trail A
implement trail B

D
split trail C into A,B

join trails A,B into C

SPLIT

E
implement trail C

deimplement conn 2 of trail A

F
deconfigure trail C

configure trail C
connect client paths
from 1W to 4 E

disconnect client paths


from 1W to 4E

H
Figure 58. state diagram
The join trails is an operation that changes the state from A to H, passing through intermediate states.
The split trails is an operation that changes the state from H to A, passing through intermediate states.
The states are described below.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

state A (see below): HO trails A and B are implemented and LO configured; some LO LCs (e.g. LC
A and B) and their CTPs are busy because they belong to a path; LO CTPs in the transit node 2 are
connected with pointtopoint connections in topology without timeslot interchange; these connections can be allocated or implemented;

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

108 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

NAP

LO CTP
LO CTP
A1
A2
LO LC A
HO trail A
HO LC A

1
W

LO CTP B1

NAP

LO CTP B2

LO LC B
HO trail B

HO LC B1

2
E

HO LC B2

3
E

4
E

Figure 59. state A: 2 HO trails (A, B)

state B: HO trails A and B are implemented and LO configured; for all the LO paths that before used
LO LCs A and B:

the objects between 1W and 4E are freed:

the connections in topology in node 2 are removed, both on EML and on RM database;

the LO CTPs in node 2 are idle; in nodes 1 and 4 are still busy;

all the LO LCs are idle;

the path is set to partiallyConnected;


for HO objects, no differences compared with state A;
state C: HO trails A and B are implemented and partially configured at LO: the ports 1W and 4E are
still LO configured (with LO CTPs busy), but all the LO link connections have been removed; in node
2 HO CAPs are virtual and LO CTPs are deleted;
state D: HO trails A and B are partially implemented and partially configured at LO: the HO connections in topology are all implemented except the 2 CTPCAP in node 2;
state E: HO trail C between nodes 1 and 4 is partially implemented and partially configured at LO:
the HO connections in topology are all implemented except the one in node 2; no LO LC exists;
state F: HO trail C is implemented and partially configured at LO: all the HO connections in topology
are implemented; no LO LC exists;
state G: HO trail C is implemented and LO configured; LO LC C is client of HO trail C; it is idle even
if it is terminated by the old LO CTPs that are still busy; LO path is still partiallyConnected;
state H (see below): HO trail C is implemented and LO configured; LO LC C and its CTPs are busy
because they belong to a path, which is fullyConnected;
NAP

LO CTP A1

HO LC A

1
W

HO trail C
HO LC B1

2
E

NAP

LO CTP B2

LO LC C

HO LC B2

3
E

4
E

Figure 60. state H: 1 HO trail (C)


Note: in every state there is no difference in nodes 1 and 4.

1AA 00014 0004 (9007) A4 ALICE 04.10

Both join and split can be executed:

in a single step: a new action is defined in order to perform automatically all the activities that join or
split trails (i.e. that move, if successful, from A to H or viceversa);

step by step: the user can execute an action at a time.

Join and split trails are completely reversible: if a join trails is interrupted after an action, e.g. in the state
B after the first action, it is possible to go back to previous state, applying the action connect client paths
from 1W to 4E. It is also possible to continue the join trails, applying the same action (i.e. join trails) or
the remaining actions (deconfigure trail A, B, deimplement connections ...).

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

109 / 268

a)

to continue, performing the following steps:


1)
2)
3)

b)

implement trail B;
configure trail B;
connect client paths from 1W to 4E;

to go back, executing the join trails (A, B) or performing the following steps:
1)
2)
3)
4)

deimplement connection in node 2 of trail B;


deconfigure trail A;
deimplement connection in node 2 of trail A;
execute the steps that move the trails from D to H.

The state transitions C D and E F are not symmetrical: the deimplementation is applied to a single connection in topology for each trail (the one in the common node), while the implementation is applied to the
whole trail: this is due to the fact that, in MSSPRING, the implementation could modify the squelching
tables in the connections in topology contained in the other nodes of the same MSSPRING, while the deimplementation of a single connection leaves those squelching tables to the old values.

1AA 00014 0004 (9007) A4 ALICE 04.10

A report is presented to the user indicating in real time which phase of the operation is in progress and
its result when completed. All the LOPaths impacted by the operation (supported by the involved HO
Trails) are reported too.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

110 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Also when an action is not completed (e.g. it fails, an agent crash occurs, ...), it is always possible to continue or to go back. For example, if during the split trail the implementation of trail B fails leaving this trail
partially implemented, while the trail A has been successfully implemented and configured, it is possible:

6.1.3 Join / Split trail diagnostic

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.1.3.1 Join trail diagnostic


With reference to Figure 58. on page 108 , A to D statuses describe a condition which includes two trails
E to H statuses describe a condition which includes only one trail

In case the Join operation is blocked in the B,C,D statuses, the possible user operations are:

the user can manually revert (step by step) to A status

or

the user can try to relaunch the join operation, since the probable reason of the interruption is the
condition of EML/NE not reachable

In case the Join operation is blocked in the E,F,G statuses, the possible user operations are:

the user wants to complete the join operation by manually proceeding (step by step) to H status

or

the user wants to manually revert (step by step) to A status by reissuing the split command

N.B.

Connect/Disconnect commands must be executed from the HO trail/s

6.1.3.2 Split trail diagnostic


With reference to Figure 58. on page 108 , A to D statuses describe a condition which includes two trails
E to H statuses describe a condition which includes only one trail

In case the Split operation is blocked in the G,F,E statuses, the possible user operations are:

the user can manually revert (step by step) to H status

or

the user can try to relaunch the split operation, since the probable reason of the interruption is the
condition of EML/NE not reachable

1AA 00014 0004 (9007) A4 ALICE 04.10

In case the Split operation is blocked in the D,C,B statuses, the possible user operations are:

the user wants to complete the split operation by manually proceeding (step by step) to A status

or

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

111 / 268

the user wants to manually revert (step by step) to H status by reissuing the join command
Connect/Disconnect commands must be executed from the HO trail/s

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

N.B.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

112 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7 DIAGNOSTIC OF THE NPE RING


7.1 The 4F MS Spring RM side
7.1.1 Some useful definitions

Serving nodes: the two nodes that talk to each other on the K1K2 channel, sending their protocol
messages in order to serve their requests. If more than one request is served on the ring, the serving
nodes may be more than two.

Intermediate nodes: the nodes that are not directly interested by the fault.

MSSPRING request (trigger): any kind of valid input to the MSSPRING machine:
equipment/signal failure, signal degrade, external commands, and protocol requests/replies.

protocol request: a protocol message issued by a Tail node toward its peer request node (that may
either be a Tail node or Head node, depending on the nature of the trigger).

protocol reply: a protocol message issued by a Head node back to its peer Tail node to acknowledge
a Tail nodes protocol request.

protocol message: a K1K2 code sent on the K1K2 channel that may either be a protocol request
or protocol reply.

Lockout of Working channels ring (LWR): command that disables the node capability to issue
a ring protocol request of any kind. The node is anyway allowed to issue ring protocol replies. The
command is local, i.e. it is not forwarded to the other nodes through K1K2 channels.

Lockout of Working channels span (LWS): command that disables the node capability to issue
a span protocol request of any kind. The node is allowed to issue span protocol replies. The
command is local, i.e. it is not forwarded to the other nodes through K1K2 channels.

Lockout of Protection channels span (LPS): command that prevents the use of the protection
channels over the addressed span. The command is not local, i.e. it is forwarded through K1K2
channels also to the other nodes that, as a consequence, do not take any action involving the
addressed span.

Routing in Working ( RIW). For 1670SM equipment. The protection route is within the working
capacity

Routing in Protection (RIP). For 1664SM equipment. The protection route is within the protection
capacity

7.1.2 4f MSSpring
The ring can be made up of a maximum of 64 ADMs. 1664SM equipments can build 4Fiber STM16 rings
with Routing in Protection mechanism.

1AA 00014 0004 (9007) A4 ALICE 04.10

1670SM equipments can build 4Fiber STM64 rings with Routing in Working mechanism.
For Paths and Trails an attribute enables the usage of low priority resources. This attribute is taken into
account during path allocation.
The protection capabilities of the ring are based on the information stored in the Ring Traffic Map and
evaluated by each NE in order to take the appropriate decisions in case of fault.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

113 / 268

In order to avoid misconnections, RM, during implementation phase, sends the update of the ring traffic
maps before the creation of connections, and viceversa, during the deimplementation phase, updates
the maps only after the deletion of connections.
The ring traffic map is not shown to the RM operator, because the same information are provided by the
path/trail route display functionality.
The D&C is performed using protecting resource between Service Nodes while using 1664SM with RIP
mechanism and using working resource between Service Nodes while using 1670SM with RIW
mechanism.
As a consequence of limitations existing on equipment side:

for 1664SM rings D&C on interconnected NPE rings is not always able to survive to double
failures, a failure per ring, (this happens when the primary node of one ring is connected to the
secondary node of the other ring)

In addition to the previous limitation:

the timeslot interchange on protecting resources is not available

7.1.2.1 Path
The attributes relevant to NPE features are:

Server MS protection usage profile: it represents the profile of the MS resources to be used in
allocating the path.
The possible values are:

Normal

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

(default)

For 1664SM rings, the RIP mechanism is used, i.e. when crossing 4 Fibers MSSpring,
the path uses only working (high priority) resources, except for primary and secondary
nodes of the double interconnection with another ring, because these nodes are
characterized by the Drop & Continue protection ( RIP )
as a result, in the segment between service nodes:

if the path is bidirectional (Figure 61. ), the used resource (nodes E, D, H, I) can be
only the protection one: a bidirectional D&C IC on protection is performed in the
primary nodes (D, H);

if a path is unidirectional pointtopoint (Figure 62. ), the used resource is:

protection if the signal flows into the service nodes (B, C): a unidirectional D&C IC
on protection is performed in the primary node (B);

working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node (E); this allows the user to perform subsequent add
leg operation;
it is possible to use the protection resource instead of the working (nodes E, D), e.g.
forced by a constraint (Figure 63. );

if a path is broadcast (Figure 64. ), the used resource is:

protection if the signal flows into the service nodes (B, C) like in a unidirectional
pointtopoint path: a unidirectional D&C IC on protection is performed in the primary
node;

working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node);

SC.4:MAINTENANCE
3AL 61348 AA AA
268

114 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The component of the ring traffic map related to each path and trail is evaluated and sent to all NEs in
the ring.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

it is not possible to use the protection resource instead of the working one.
As a result of the previous rules defined for unidirectional and broadcast paths, a
unidirectional pointtopoint path can become broadcast only if the working
resources are used between service nodes (nodes E, D in Figure 64. ).

ED

For 1670SM rings the path uses only working resources ( RIW )

Protection preferred
When crossing a 4 Fibre MSSpring, the path uses protecting (low priority) resources.
If the routing algorithm must use the working resource in one span of the 4F MSspring (e.g.
no free resources in the protection, or a constraint is applied), all working resources are used
in the ring, in order to avoid jumps between working and protection resources (jumps not
foreseen for the management of ring traffic map).
If the path is protected and main and spare routes are crossing the same MSSpring, each route
crosses separately the ring itself since D&C connection are not available for protecting
resources.
As a consequence of this behavior and of the fact that the SNCP connection is not available on
a 4f MSSpring, if the protected HO path is completely inside a 4f MSSpring, the allocation
will always fail.

Protection only
the path uses only protecting (low priority) resources.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

115 / 268

7.1.2.1.1 Trail
Server Ms protection usage profile is added to HO trails (see the description given for paths).
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

working
protection

NPE
F

NPE
N

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 61. bidirectional protected path

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

116 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

working
protection
SNCP

B
NPE

SNCP

Figure 62. unidirectional protected path (using working resource between nodes E and D)

working
protection
SNCP

B
NPE

C
D

1AA 00014 0004 (9007) A4 ALICE 04.10

SNCP

Figure 63. unidirectional protected path (using protection resource between nodes E and D)

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

117 / 268

working
protection

B
NPE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SNCP

SNCP

Figure 64. broadcast protected path


7.1.2.1.2 Physical Connection

1AA 00014 0004 (9007) A4 ALICE 04.10

An attribute specifies if the Physical Connection is Working (i.e. it connects main ports, involved in a MS
protection mechanism) or Protecting (i.e. it connects spare ports) or Normal (i.e. it connects ports not
involved in any MS protection mechanism.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

118 / 268

7.1.2.1.3 4f MS Protection Block

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The 4f MS Protection Block contains the following information:

Containment information (network Id, subnetwork Id, et Id, node Id)

fdnMapper. It identifies the object inside the NE.

Configuration State. It is the state requested at the interface Functional Agent / TSDIM Front End
Processor and can assume the following values:

virtual.
The MSSPRING et topology is only planned inside the RM (i.e. is in the state defined) and
is not established inside the NE (the ring coordinator object is not present in the NE)

enabled (foreseen for future usage).


The MSSPRING et topology is enabled inside the NE, i.e. all the relevant objects are created
inside NE but the MSSpring mechanism is not active; the NE transmits idle code on the K1/K2
channel (see also Transition State)

active.
The MSSPRING et topology is active in the NE, i.e. it is implemented in RM (see also
Transition State)

Transition State. It describes the transition state of the MSSPRING in the NE during the
configuration phase. The following values are possible:

idle. It is the value corresponding to the value virtual of the Configuration State

defined. The ring has been defined by the action applied on the Protection Manager MOC in
NE: the information on working/protecting east/west msTTPs have been provided to the NEs.
As a result the Ring Coordinator object is created in the NE and all other objects (Ring Map, Ring
Traffic Map or Squelch Table, Ring Protection Group, Ring Protection Units ...) are created and
correlated to the Ring Coordinator. The Ring Coordinator has the status enabled

populated map. The Ring Map has been populated according to the information contained in
the ring map info attribute through the populate action applied to the Ring Coordinator. As a
result, the information describing the map of the nodes inside the ring have been stored both
inside the Ring Map and in the Ring Traffic Map accordingly.

activated. The Ring Coordinator has been activated (activate action). As a result, the protected
msTTPs, unprotected CTPs, working/protecting east/west side have been put in relation
according to the ring type (2/4 fiber with/without extratraffic) and the MSSpring mechanism
is active

1AA 00014 0004 (9007) A4 ALICE 04.10

The Configuration State attribute active is consistent with the NE status if the 4F protection block
entered the sequence defined, populated map, activated, i.e. if the Ring Coordinator is
activated. In this case the attribute value is activated and the Consistency Status is normal .

node id: it refers to the node id attribute inside the node entity

ring map info: it is a string representing the sequence of node identifiers following the direction
eastwest in the ring. It is used to provide to the NE the information usefull when filling the Ring Map
object (e.g.: x,y,z,w. Starting from the node x and moving to east the found nodes are in the
sequence y, z, w, where x,y,z,w are the identifiers of the nodes).

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

119 / 268

traffic map: the attribute is a sort of token used to apply the alignment of the Ring Traffic Map inside
the NE, according to the info, if any, contained in the AU4 Transport Map, plus the implicit information
that, when the au4(s) or piece(s) of au4(s) are not contained inside the AU4 Transport Map, no
connection has to be present inside the Ring Traffic Map.

Consistency Status: normal, not aligned, failed to align.


It represents the consistency between RM object and NE objects (not aligned if at RM level a
misalignment between the two objects has been forced; failed to align if the realignment procedure,
either automatic or manual, has failed, normal if the realignment procedure is successfull)

West Reliable ( protected ) Resource: it is the id of the reliable msCtpCap on the west main port

East Reliable Resource: it is the id of the reliable msCtpCap on the east main port

West Working Unreliable Resource: it is the id of the unreliable msCtpCap on the west main port

East Working Unreliable Resource: it is the id of the unreliable msCtpCap on the east main port

West Protecting Unrealiable Resource: it is the id of the unreliable msCtpCap on the west spare
port

East Protecting Unreliable Resource: it is the id of the unreliable msCtpCap on the east spare port

Ring WTR (Wait To Restore time): it containes the value to provide to the NE during the MSSpring
provisioning phase.

West Span WTR (Wait To Restore time): it contains the value (west side) to provide to the NE during
the MSSpring provisioning phase.

East Span WTR (Wait To Restore time): it contains the value (east side) to provide to the NE during
the MSSpring provisioning phase.

Current User Command. The attribute indicates the command (none, lockout working west, lockout
working east, west ring force switch...) requested by the RM user.

West /East Ring Active Condition


This attribute indicates the ring command that is currently stored to and served by the NE on the West/
East side of the node. The following values shall apply:

no command: null

Ring forced switch: forced

Ring manual switch: manual

Ring WTR running: wtrRunning


N.B.

1AA 00014 0004 (9007) A4 ALICE 04.10

exercise

West /East Ring Pending Command


This attribute indicates the ring command that is currently stored to but not served by the NE on its
West side. The following values shall apply:

ED

the WTR has been put together with the possible active commands because, even
if it is not a user command, it can be cleared through a user command as well as the
others.

no command: null
01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

120 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Ring forced switch: forced

Ring manual switch: manual

exercise

West / East Span Active Condition


This attribute indicates the span command that is currently stored to and served by the NE on the
West / East side of the node. The following values shall apply:

no command: null

Span forced switch: forced

Span manual switch: manual

Span Lockout of Protection: lockoutProtection

Span WTR running: wtrRunning

exercise

West / East Span Pending Command


This attribute indicates the span command that is currently stored to but not served by the NE on its
West side. The following values shall apply:

no command: null

Span forced switch: forced

Span manual switch: manual

exercise

East / WestLockout Working Ring


This attribute indicates whether a Lockout of Working Channels Ring command is currently stored
to the NE on its East /West side. It can assume the following values: none, lockoutWorking.

East / West Lockout Working Span


This attribute indicates whether a Lockout of Working Channels Span command is currently stored
to the NE on its East / West side. It can assume the following values: none, lockoutWorking.

West / East Failure of Protocol


This attribute indicates the K1K2 protocol failure detected on the West / East side of the node. The
following values shall apply:

ED

no protocol failure detected: none

default APS code detected: defaultKBytes

improper APS code detected: improperCode

node Id mismatch detected: nodeIdMismatch

inconsistent code

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

121 / 268

Node Condition (Mid Protocol Role)


This attribute represents the status of a node in terms of how the node is acting on the protocol
channel in order to serve either a local (on west side) or remote trigger. The values of this attribute
may be:

role not known: unknown


the MSSPRING is enabled (configured) but not active (protection mechanism not running) at
the node: standby
the MSSPRING is enabled and active at the node; the role of the node is actually determined
by the West and east Protocol Role (see below): idle
the MSSPRING is enabled and active at the node; either the node received/detected nothing
and some other node is serving an external command or the node received/detected a trigger
but some other node is serving another trigger of higher priority: intermediate
end. It is the tailHead node, i.e. the node which initiates or terminates the protocol request.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

West / East Protocol Role


This attribute represents the status of a node in terms of how the node is acting on the protocol
channel in order to serve either a local or remote trigger regarding its West / East side. The values
of this attribute may be:

the node a) received no external command, or b) received no protocol request, or c) detected


no failure/degrade, or d) is isolated form the other nodes at MS level: idle

the node is serving an external commandring or failure/degradering that involves its


West/East side: tailHeadRing ( interruption RING )

the node is serving an external commandspan or failure/degradespan that involves its


West/East side: tailHeadSpan ( interruption SPAN )

the protection MS on the West / East side of the node is unavailable or locked out (via LPS
only): protUnav

the node is serving an external commandring or failure/degradering that involves its West /
East side, the protection MS on the West / East side is unavailable or locked out: ( ext )
RingProtUnav

tailHeadExrcRing external exercise Ring

tailHeadExrcSpan external exercise Span

thRingExrcRingProtUna the node is serving an exercise command that involves its West /
East side, the protection MS on the West / East side is unavailable or locked out

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

122 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7.2 User Presentation


The protection status reporting window displays the current status of the MS SPring, in terms of:

triggers =external commands and/or failure/degrade conditions. The nodes whose triggers are being
served are named served nodes. A served node has at least one trigger served and may have some
pending triggers.

the reaction of the ring to those triggers, namely what triggers are being served, and which ones are
pending. (waiting to be served, either because they are at lower priority, or there are specific protocol
rules). The nodes that have no triggers or only pending ones are called intermediate nodes.
N.B.

The protection status reporting screen is neither intended to display the status of the K1K2
signaling, nor the status of the physical switches. With the 2F MS SP ring application, the
bridge&switch at multiplex section level always occurs at served nodes, whereas protection
channels passthrough is made by intermediate nodes. With the 4F MS SPring application,
bridge&switch at AU4 level may take place at whatsoever node, depending on traffic
distribution.

It should be noted that according to the MSSPring protocol rules any of the following scenarios may occur:

no trigger is present, no protocol request (namely, K1K2 code other than noRequest) is signaled on
the ring;

1 trigger is present, 1 protocol request is signaled and served;

N (>1) triggers are present, N protocol requests are signaled, only 1 is served (higher priority);

N triggers are present, N protocol requests are signaled and served (same priority);

N triggers are present, N protocol requests are signaled, none is served (same priority, but not
allowed to coexist).

1 trigger is present and served, no protocol request is signaled (1);

M (>1) triggers are present, N (<M) protocol requests are signaled, only 1 is served (higher priority);

M triggers are present, N (<M) protocol requests are signaled and served (same priority);

M triggers are present, N (<M) protocol requests are signaled, none is served (same priority, but not
allowed to coexist).
(1) The Lockout of Working channels commands make the scenario even more complicated, as those

commands are not signaled but are actually served, in the sense that they influence the behavior of
the node to which they are addressed.

1AA 00014 0004 (9007) A4 ALICE 04.10

The window can display up to 16 node icons (see Figure 65. )

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

123 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 65. 4 fibre MS SP reporting screen

7.2.1 Configuration State attribute


Two node icons are associated to the values of the ConfigurationState attribute of the
MSSPRingProtectionBlock:

ConfigurationState = virtual, icon

ConfigurationState = enabled, icon (not managed in this version release)

ConfigurationState = active, icon


When the ConfigurationState is virtual for a node (because the relevant TFEP fails) an allgrey icon
(the virtual node icon) is displayed as a placeholder for that node, but no additional information can be
displayed on top of that icon about that node (see Figure 66. ).

Figure 66. ConfigurationState = virtual icon


The virtual node icon being displayed means that the MSSPRING is not configured at the node.
When the ConfigurationState is either enabled or active for a node, the node icon shown in
Figure 68. is displayed. Such an icon then acts as a background for all the icons associated to the
attributes of the MSSPRingProtectionBlock.

1AA 00014 0004 (9007) A4 ALICE 04.10

The node icon always reports the actual condition of the node in terms of the protocol role the node
is playing to react to the MSSPRING triggers, and the external commands being stored to the
node. If the condition required by the RM and the actual node condition do not match, the not
aligned indication is displayed along with the node icon.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

124 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

virtual

topology implementation
topology deimplementation

MSSPRING activation
enabled

active
MSSPRING deactivation

Figure 67. ConfigurationState diagram

1AA 00014 0004 (9007) A4 ALICE 04.10

The following table describes the rationale that drives the display of the various icons according to the
ConfigurationState state diagram (see Figure 67. ).

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

125 / 268

node condition

displayed icons

operation

virtual

MSSPRING not configured

virtual node icon

topology implementation failure (TFEP


stalled)

active

MSSPRING not configured

virtual node icon

topology implementation failure (TSDIM establish failed)

active

node icon +MidProtocolRole = unknown


icon on top

node unreachable

enabled
(not managed in this
version release)

enabled

node icon +MidProtocolRole = standby


icon on top

MSSPRING deactivation successful

enabled
(not managed in this
version release)

active

node icon + other icons


on top to show protocol
role and stored commands +
not aligned indication

MSSPRING deactivation failure

active

active

node icon +
other icons on top to
show protocol role and
stored commands

topology implementation successful or MS


SPRING activation successful

active

enabled

node icon +
MidProtocolRole =
standby icon on top +
not aligned indication

topology implementation failure (TSDIM


populate failed) or
MSSPRING activation
failure

The node icon is a rectangle plus arrows that represent the fiber optics to connect the nodes to each other.

1AA 00014 0004 (9007) A4 ALICE 04.10

Plus, the node icon features a number of rectangles (see Figure 68. ) to hold icons associated to all the
attributes of the MSSPRingProtectionBlock MOC:

the icon for the MidProtocolRole attribute;

the icon for the WestProtocolRole attribute;

the icon for the EastProtectionRole attribute;

the set of six icons for the WestRingActiveCondition, WestSpanActiveCondition,


WestRingPendingCommand, WestSpanPendingCommand, WestLockoutWorkingRing, and
WestLockoutWorkingSpan on the West side of the node icon;

the set of six icons for the EastRingActiveCondition, EastSpanActiveCondition,


EastRingPendingCommand, EastSpanPendingCommand, EastLockoutWorkingRing, and
EastLockoutWorkingSpan on the East side of the node icon;

the icon for the FailureOfProtocol to be placed outside the node icon next the bottom left and
righthand corner;
The reason for providing each node icon with 6 icons for the local commands comes from the combinations
of active and pending commands that are allowed to coexist at each node.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

126 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ConfigurationState

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7.2.2 MidProtocol Role ( NODE CONDITION) attribute


The central rectangle with a black triangle in it representing the NE is the place where the values of
the MidProtocolRole are displayed (see Figure 69. ).
When MidProtocolRole = idle and all other attributes are = null, no additional icon is placed on top of
the node icon, so that all commandrelated rectangles still look gray to show that no external command
is stored to the node, namely either active or pending and the rectangles on the side of the central triangle
both looking green, to mean that both the East and WestProtocolRole are in an idle condition, namely
the node is neither serving any trigger nor acknowledging a trigger to be served by some other node on
the ring.
Whenever the MidProtocolRole attribute changes from idle to another value, the icon associated to that
new value is displayed on top of the central rectangle with the black triangle in it.
Whenever either the East and WestProtocolRole, or both, change to a value different from null, the icon
associated to the new value (see Figure 70. and Figure 71. ) are displayed on top of the designated green
rectangle.
Whenever any of the external commands is given to and stored by a node to go either active or pending,
the icon associated to the new value (see Figure 78. ) are displayed on top of the designated gray
rectangle

west ring pending command

east ring pending command


east span pending command

west span pending command

working fibers

east protocol role

east ring active condition


east span active condition
east Lockout W ring status
protection fibers
east Lockout W span status
west protocol role

west span active condition


west ring active condition
west Lockout W span status

east failure ofprotocol

1AA 00014 0004 (9007) A4 ALICE 04.10

west Lockout W ring status

Figure 68. ConfigurationState = enabled/active icon

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

127 / 268

intemediate

unknown

end

standby

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

idle

no icon

GREEN

(not supported)

GREEN

Figure 69. MidProtocolRole ( NODE CONDITION ) icons


7.2.2.1 West and EastProtocolRole attributes

null

tailHeadRing
(interruption Ring)

tailHeadSpan
(interruption Span)

protUnav

(EXT) thRingProtUnav

no icon

RED
tailHeadExrcRing

RED

RED

RED

thExRingProtUnav

BLUE

BLUE

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 70. WestProtocolRole icons.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

128 / 268

tailHeadRing

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

null

tailHeadSpan

protUnav

thRingProtUnav

no icon

RED

tailHeadExrcRing

RED

RED

RED

thExRingProtUnav

BLUE

BLUE

Figure 71. EastProtocolRole icons.


7.2.2.2 Protocol Failure attribute
This attribute has icons (see Figure 72. ) associated to each of its values to represent the various failure
conditions that may affect the K protocol. When a node detects a protocol failure in the incoming K bytes
on a given side, the relevant icon is displayed.

null

defaultKBytes

improperCode

nodeIdMismatch

RED

RED

RED

inconsistentCode

no icon

RED

Figure 72. East/West failure Of Protocol

1AA 00014 0004 (9007) A4 ALICE 04.10

7.2.3 Ring Active Condition attributes


Each of these values is represented on the screen by an icon (see Figure 73. ) located at the designated
position for this attribute, and pointing at the side of the node to which the command is addressed. Each
value other than null indicated either a command (forced, manual) given by the manager or a condition
(wtrRunning) automatically forced by the NE: each of those can be removed by the manager by the
appropriate release command. Specifically, a release WTR command forces the WTR counter inside the
NE to immediate expiration.
Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

129 / 268

forced switch ring

null

exercise

wtr ring

no icon

YELLOW

RED

CIAN

Figure 73. East/West ring active condition

7.2.4 Span Active Condition attributes


Each of these values is represented on the screen by an icon (see Figure 74. and Figure 75. ) located at
the designated position for this attribute. Each value other than null indicated either a command (forced,
manual, lockoutProtection) given by the manager or a condition (wtrRunning) automatically forced by the
NE: each of those can be removed by the manager by the appropriate release command. Specifically, a
release WTR command forces the WTR counter inside the NE to immediate expiration.
Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.

manual switch span

forced switch span

wtr span

exercise

null

no icon

YELLOW

CIAN

RED

Figure 74. East span active condition

manual switch span

forced switch span

wtr span

exercise

null

no icon

YELLOW

CIAN

RED

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 75. West span active condition

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

130 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

manual switch ring

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7.2.5 Ring Pending Command


Each of these values is represented on the screen by an icon (see figure below) located at the designated
position for this attribute. Each value other than null indicates a command given by the manager and that
can be removed by the manager by the appropriate release command.
Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.

manual switch ring

forced switch ring

null

exercise

no icon

YELLOW

CIAN

RED

Figure 76. East / West ring pending command

7.2.6 Span Pending Command


Each of these values is represented on the screen by an icon (see figure below) located at the designated
position for this attribute, and pointing at the side of the node to which the command is addressed. Each
value other than null indicates a command given by the manager and that can be removed by the manager
by the appropriate release command.
Manual and Forced switch are represented by same symbol on different color, yellow and red respectively.

manual switch span

forced switch span

exercise

null

no icon

YELLOW

RED

CIAN

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 77. East span pending command

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

131 / 268

forced switch span

null

exercise
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

manual switch span

no icon

YELLOW

RED

CIAN

Figure 78. West span pending command

7.2.7 Lockout Working Ring attributes

null

Lockout working ring

no icon

Figure 79. East / West Lockout Working Ring

7.2.8 Lockout Working Span attributes

null

Lockout working span

no icon

Figure 80. East / West Lockout Working Span

7.2.9 Inhibition chain

1AA 00014 0004 (9007) A4 ALICE 04.10

The possible requests are listed herebelow in decreasing priority.

LPS (Lockout Protection Span), SFP (Signal Fail Protection), LOWR (Lockout Working Ring),
LOWS (Lockout Working Span); LOWR, LOWS LPS

FSS (Forced Switch Span)

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

132 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

FSR (Forced Switch Ring)

SFS (Signal Fail Span)

SFR (Signal Fail Ring)

SDP (Signal Degrade Protection)

SDS (Signal Degrade Span)

SDR (Signal Degrade Ring)

MSS (Manual Switch Span)

MSR (Manual Switch Ring)

WTR (Wait to Restore Time)

EXER (Exercise)

EXCEPTIONS

Two MSS (Manual Switch Span): no action

SFR and FSR : no action

Two SDR : no action

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

133 / 268

7.2.10 Scenarios

7.2.10.1 Bidirectional Signal Fail / Ring Scenario


DESCRIPTION
A Bidirectional Signal Fail / Ring is present on AB span. The relevant aggregate boards are affected
by LOS alarm.
SERVED REQUESTS DISPLAY
Bidirectional Signal Fail / Ring on AB span (indicated by RING INTERRUPTION (tailHeadRing) icons
on AB span)
OPERATION
The traffic affected by the failure is recovered on protection channels away from the failure. All LP traffic
paths whose channels are needed to recover HP traffic are preempted.
HP traffic is maintained. LP traffic paths whose channels are needed to recover HP traffic is lost.
REPAIR ACTION
Two alternatives are possible:
a)

First execute the repair of the main span. HP traffic reverts to the main span while LP traffic still is
lost.
1)

b)

Click on the alarm icon displayed on the main span. The alarm detail window is presented, giving
the information needed to repair the span.

First execute the repair of the spare span, so moving to the Span switch scenario.The LP traffic not
overlapping HP traffic is restored.
1)

Click on the alarm icon displayed on the spare span. The alarm detail window is presented,
giving the information needed to repair the span.

1AA 00014 0004 (9007) A4 ALICE 04.10

The scenario after the repair of the affected spans is described at paragraph 7.2.10.2.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

134 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This paragraph describes various ring scenarios , as shown in the graphical interface.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Alarm icon

Ring Interruption (tailHeadRing)

Node Condition=intermediate
(not directly affected by the fault)
Node Condition=End
Figure 81. Bidirectional Signal Fail / Ring
7.2.10.2 Bidirectional Signal Fail / Ring cleared .WTR
DESCRIPTION
The bidirectional Signal Fail / Ring on AB span is cleared as a consequence of a repair action. The last
node detecting the signal failure clear starts the WTR ( wait to restore time )
SERVED REQUESTS DISPLAY
Bidirectional Signal Fail / Ring on AB span (indicated by RING INTERRUPTION (tailHeadRing) icons
on AB span) is still displayed.
The east ring active condition icon reports WTRrunning.
OPERATION
All nodes dropping/inserting HP traffic that was affected by the failure still recover it on protection channels
away from the failure.
All LPtraffic paths whose channels are needed to recover HP traffic are still preempted.
Node A (the last detecting the signal failure clear) is running
REPAIR ACTION

1AA 00014 0004 (9007) A4 ALICE 04.10

The WTR timer may be forced to expiration by RM via Clear WTR command. ( not implemented in this
version )

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

135 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

WTR

Figure 82. Bidirectional Signal Fail / Ring cleared .WTR


7.2.10.3 Double Bidirectional Signal Fail / Ring
DESCRIPTION
Bidirectional Signal Fail / Ring on AB span.
Bidirectional Signal Fail / Ring on DE span.
SERVED REQUESTS DISPLAY
Bidirectional Signal Fail / Ring on AB span (indicated by RING INTERRUPTION (tailHeadRing) icons
Bidirectional Signal Fail / Ring on DE span (indicated by RING INTERRUPTION (tailHeadRing) icons
OPERATION
All nodes dropping/inserting HP traffic that was affected by the failure still recover it on protection channels
away from the failure.
HP traffic that was affected by either failure is not recovered
All LPtraffic paths whose channels are needed to recover HP traffic are preempted.
REPAIR ACTION

1AA 00014 0004 (9007) A4 ALICE 04.10

The scenario after the repair of one of the two faults is described at paragraph 7.2.10.1.
It is suggested the repair of the main span first.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

136 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Alarm icon

Ring Interruption (tailHeadRing)

Node Condition=Idle

Figure 83. Double Bidirectional Signal Fail / Ring


7.2.10.4 Forced Switch Ring
DESCRIPTION
A Forced Switch / Ring command is entered to A/East for AB span.
SERVED REQUESTS DISPLAY
Forced Switch / Ring command (indicated by tailHeadRing (RING INTERRUPTION) icons facing the AB
span, and the FS/R icon pointing to the relevant node and side. This FS/R icon means that a command
is being served and may be removed).
OPERATION
All nodes dropping/inserting HP traffic that is traversing the addressed span is recovered on protection
channels away from that span (just like an SF/R affecting the same span).

1AA 00014 0004 (9007) A4 ALICE 04.10

All LPtraffic paths whose channels are needed to recover HP traffic are preempted.
REPAIR ACTION
This command is used in the Add/Remove Node procedures.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

137 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

B
Forced Switch Ring East

Figure 84. Forced Switch / Ring


7.2.10.5 Double Forced Switch / Ring to different nodes, node isolated
DESCRIPTION
Forced Switch / Ring command given to A/East for AB span and Forced Switch / Ring command given
to C/West for BC span.
This scenario can be established to put node B in local maintenance condition.
SERVED REQUESTS DISPLAY
Forced Switch / Ring command given to A/East (indicated by tailHeadRing icon facing the AB span, and
the FS/R icon . FS/R icon means that a command is being served and may be removed).
Forced Switch / Ring command given to C/West (indicated by tailHeadRing icon facing the BC span, and
the FS/R icon . FS/R icon means that a command is being served and may be removed).
OPERATION
Node B is isolated, as the two Force Ring commands partition the ring into two segment, [B] alone and
[C, D, A].

1AA 00014 0004 (9007) A4 ALICE 04.10

HP traffic that is traversing both the involved spans is recovered on protection channels away from those
spans.
HP traffic that is traversing one of the involved spans is not recovered.
All LP paths whose channels are needed to recover HP traffic are preempted.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

138 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

REPAIR ACTION
After the completion of the local maintenance condition of node B, enter the Release Forced Switch / Ring
on nodes A and C.

Forced Switch Ring East

C
Forced Switch Ring West

Figure 85. Double Forced Switch / Ring to different nodes, node isolated
7.2.10.6 Double signal Fail / ring, node isolated
DESCRIPTION
Bidirectional Signal Fail / Ring on AB span.
Bidirectional Signal Fail / Ring on BC span.
SERVED REQUESTS DISPLAY
Bidirectional Signal Fail / Ring on AB span (indicated by tailHeadRing icons facing both the AB span).
Bidirectional Signal Fail / Ring on BC span (indicated by tailHeadRing icons facing both the BC span).
OPERATION
Node B is isolated, as the two Force Ring commands partition the ring into two segment, [B] alone and
[C, D, A].
HP traffic that is traversing both the involved spans is recovered on protection channels away from those
spans.
HP traffic that is traversing one of the involved spans is not recovered.
All LP paths whose channels are needed to recover HP traffic are preempted.

1AA 00014 0004 (9007) A4 ALICE 04.10

REPAIR ACTION
a)

ED

Execute the repair of the main span. HP traffic reverts to the main span while LP traffic still is lost.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

139 / 268

Click on the alarm icon displayed on the main span. The alarm detail window is presented, giving
the information needed to repair the span.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1)

Figure 86. Double signal Fail / ring, node isolated


It is suggested the repair of the main span first.
7.2.10.7 Forced Switch / Span
DESCRIPTION
A Forced Switch / Span command is entered to B/West for AB span.
This command is used when the AB main span requires a local maintenance.
SERVED REQUESTS DISPLAY
Forced Switch / Span command (indicated by tailHeadSpan icons facing the AB span, and the FS/S
icon pointing to the relevant node and side).
OPERATION
Nodes A and B recover on the protection channels the traffic traversing the involved span (just like an SF/S
affecting the same span). The only channels that are bridged and switched by A and B are those that
actually carry traffic over AB.
All LPtraffic paths whose channels are needed to recover HP traffic are preempted.
REPAIR ACTION

1AA 00014 0004 (9007) A4 ALICE 04.10

After the completion of AB main span local maintenance the Release Switch Span West can be entered.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

140 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Span Switch

Force Switch Span West

Figure 87. Forced Switch / Span


7.2.10.8 Forced Switch / Ring pending
DESCRIPTION
Bidirectional Signal Fail / Ring on AB span.
Forced Switch / Ring command given to D/West for DC span.
SERVED REQUESTS DISPLAY
Forced Switch Ring pending icon on D node.
OPERATION
Forced Switch / Ring command is pending (actually it is higher priority than the SF/R, but it cannot be
served because the protocol fails to complete on the long path).
REPAIR ACTION

1AA 00014 0004 (9007) A4 ALICE 04.10

Release Forced Switch Ring.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

141 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Forced Switch Ring pending

Figure 88. Signal Fail / Ring pending, Forced Switch / Ring pending
7.2.10.9 Double Fault/ Ring pending
DESCRIPTION
Bidirectional Signal Fail on Protection on BA span.
Bidirectional Signal Fail / Ring on DE span.
It is a double fault service affecting. The fault between A and B nodes ( SFP ) has priority greater than
the fault between C and D nodes ( SFR)
SERVED REQUESTS DISPLAY
Bidirectional Signal Fail on Protection (indicated by protection unavailable icons facing the AB span)
OPERATION
Bidirectional Signal Fail / Ring is pending (it is lower priority than the Signal Fail /Span), affected traffic
is not recovered, all LPtraffic remains.

1AA 00014 0004 (9007) A4 ALICE 04.10

Bidirectional Signal Fail on Protection prevents the use of the protection channels on the AB span.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

142 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ED

01
B
C
D

Protection Unavailable

Figure 89. Signal Fail Span, Signal Fail / Ring pending

SC.4:MAINTENANCE

3AL 61348 AA AA

268

143 / 268

7.2.10.10 Span Switch Request: Exercise East

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

DESCRIPTION
A Span Switch Request: Exercise East is issued on node B.
SERVED REQUESTS DISPLAY
East Protocol Role=TailHeadExrcSpan on B node
West Protocol Role=TailHeadExrcSpan on C node
OPERATION
The Exercise command does not affect the traffic carried by the NPE ring

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 90. Span Switch Request: Exercise East menu option

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

144 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 91. Span Switch Request: Exercise East.


7.2.10.11 Ring Switch Request: Exercise East
DESCRIPTION
A Ring Switch Request: Exercise East is issued on node B.
SERVED REQUESTS DISPLAY
East Protocol Role=TailHeadExrcRing on B node
West Protocol Role=TailHeadExrcRing on C node
OPERATION

1AA 00014 0004 (9007) A4 ALICE 04.10

The Exercise command does not affect the traffic carried by the NPE ring.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

145 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 92. Ring Switch Request: Exercise East menu option

Figure 93. Ring Switch Request: Exercise East

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

146 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

8 NMLEML CONSISTENCY CHECKS


In the following are described the consistency audit and consistency download activities that can be
executed either on a single NE or the whole EML DOMAIN.

8.1 NMLEML Consistency Checks ( SENIM )


8.1.1 Consistency audit ( SENIM )
The Consistency Audit activity verifies the misalignments between the EML and the NML. This
activity does not perform any corrective actions.
The Consistency Audit activity is required if the operation launched by 1354RM fails on EML.

To execute the consistency audit:


a)

Activate the Network Consistency Agent. ( Set Run Level=3 from Monitor application )

b)

On the involved EML/NE execute the Consistency Audit popup menu.

The available options are:


1)
2)
3)
4)

Global
PDHPort NAP
SDHPort MStp
at HO/LO level

The option Global causes the execution of all the remaining checks from 2 ) thru 4 ).

1AA 00014 0004 (9007) A4 ALICE 04.10

The reporting of the operations is performed using multiple messages in order to display the current state
of the ongoing operations (number of not aligned objects, etc...) Otherwise from the Browser the
misaligned objects (tps) can be displayed by selecting the NE and issuing Display: Related items: All
Misaligned Objects.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

147 / 268

The Consistency Download activity verifies the misalignments between EML and NML and alignes EML
data to RM data.
a)

Execute a Download Disable command

b)

Activate the Network Consistency Agent ( Run Level=Consistency )

c)

On the involved EML/NE execute the Consistency Download popup menu.

The available options are:


1)
2)
3)
4)
5)

Global
PDHPort NAP
SDHPort MStp
at HO/LO level
Performance Monitoring (Only for Download)

The option Global causes the execution of all the remaining checks 2 ) thru 4 ).

1AA 00014 0004 (9007) A4 ALICE 04.10

The reporting of the operations is performed using multiple messages in order to display the current state
of the ongoing operations (number of not aligned objects, etc... Otherwise from the Browser the
misaligned objects (tps) can be displayed by selecting the NE and issuing Display: Related items: All
Misaligned Objects.
d)

Set Run Level=Full Functionality

e)

Execute checks on an eventual EMLNE misalignment. From browser point to the Node icon and
issue Display: Related items: Alarmed Objects, to verify the presence of a Configuration Mismatch
alarm

f)

Set Configure Download: Enable on all the NEs/EMLs.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

148 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

8.1.2 Consistency download ( SENIM )

8.2 Example of SENIM NE misaligned

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

MISALIGNMENT INDICATIONS
The following indications of misalignment are perceived by the operator:

On the 1354RM map a node is misaligned.

On the 1353SH map the corresponding NE is misaligned. See following figure.

Figure 94. 1353NM map: misaligned NE

a path is disabled, probably as a consequence of the misalignment


.

1AA 00014 0004 (9007) A4 ALICE 04.10

DISABLED

Figure 95. Path list: the path is disabled (OOS)

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

149 / 268

1)

Set the Run Level=Consistency. See following figure.

2)

From the NE list select the misaligned NE and issue Consistency Audit: Global

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE OF LOCALIZATION OF THE MISALIGNMENT

Figure 96. NE: Consistency Audit menu


3)

The consistency report does not include any indication of misalignment, then the misalignment is localized between 1353NM and Network Element.

1AA 00014 0004 (9007) A4 ALICE 04.10

In addition, the errors are located at NE level, because are traffic affecting.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

150 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 97. Consistency report


4)

Set the Run Level to Full Functionality.

CORRECTIVE ACTION SEQUENCE


Due to the fact that the wrong data are localized at NE level, it is necessary to execute a download
of the data from 1353NM to the involved NE.
1)

From 1353NM map window select the NE and issue: Operations:Supervision: Stop....

2)

At this point the NE is no longer supervised. Execute NE: Supervision: Align down

3)

Click on the NE name and confirm by clicking on OK button.

4)

After a few seconds the alignment is completed.

5)

From the NE list it is possible to verify that the involved NE is aligned.

6)

From the 1354RM map the user can verify that the disalignment ceased

1AA 00014 0004 (9007) A4 ALICE 04.10

8.3 SENIM NM misaligned


MISALIGNMENT INDICATIONS
The following indications of misalignment are perceived by the operator:

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

151 / 268

On the 1354RM map a node is misaligned.

On the 1354RM node list a node is misaligned. See following figure.


All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 98. Node list.

On the 1353NM map the corresponding NE is misaligned.

Traffic service is not affected

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE OF LOCALIZATION OF THE MISALIGNMENT


a)

From 1353NM select the involved NE and issue Supervision: MIB: Compare

b)

In the Supervision: MIB: Compare confirmation box click on OK to confirm.

c)

From the Compare dialog box NE1 is misaligned with respect to 1353NM.

d)

At this point, from 1354RM interface:

ED

7)

Set the Run Level=Consistency.

8)

From the NE list select the misaligned NE and issue Consistency Audit: Global. The example
which follows reports an example of audit report on connections ( at Lo / Ho )

9)

The consistency report includes an indication of misalignment, in particular a mismatch has


been discovered for one subnetwork connection missing on 1353NM. See following figure.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

152 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 99. Consistency report


The 1353NM MIB is misaligned with respect to 1354RM MIB and 1353NM MIB is misaligned
with respect to the NE MIB, then the problem is located in 1353NM MIB.
CORRECTIVE ACTION SEQUENCE
Due to the fact that the wrong data are localized at NM level, it is necessary to execute a download
of the data from 1354RM to 1353NM

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

From 1354RM execute Consistency Download.

Figure 100. Consistency Download popup menu

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

153 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 101. Confirmation dialog box.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 102. Consistency download report


b)

Set Run Level=Full Functionality

c)

From the NE list it is possible to verify that the involved NE is aligned.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

154 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

8.4 NMLEML Consistency Checks ( Q3 )


With TSDIM, RM interacts directly with the NEs and directly manages alignment, consistency, isolation
and download enable / disable.
8.4.1 Download disable management (

Q3 )

The operator is able to specify for TSDIM NEs the download disabled / enabled mode (download enabled
mode is the default condition)
When a NE is in download disabled mode, all changes are buffered in the RM MIB, being not sent
to NE.
Objects in the RM MIB that, as a consequence of the download disable mode, are not aligned with the NE,
are marked with the value of the consistency status attribute (not aligned).
When the download disabled mode is removed and the NE is reachable, RM data are downloaded to NEs.
If the download disabled mode is removed and the NE is not reachable, the operation is rejected.
If problems are detected during the download, the NE is put in isolation mode.
During the downloading activity on a given NE, all concurrent operations requested by RM operator and
involving the same NE are rejected.
8.4.2 Ne isolation detection and recovery (

Q3 )

RM is able to detect not reachable NEs as a consequence both of problems in the EML, in the DCN or
in the NE.
When a NE is in download enabled mode and is not reachable, RM behavior is similar to the one
described for the download disable mode.
Elementary alarms are correlated to the impacted transport entity allowing a better identification of the
transport entity impacted by the isolation problem.
The isolation is detected as a consequence of a failure of an operation addressed to the NE.
The recovery from the isolation is detected by means of a slow polling performed by RM on the isolated
NE.
When an isolated NE is detected as reachable, the download is automatically started.
During downloading activity, the same considerations made for download disable to download enable
transition are applicable.
The OS isolation alarm received by NM and the NM isolation alarm detected by mean of a slow polling
performed by RM are reported as alarms at the RM user interface.
8.4.3 Consistency download management (

Q3 )

1AA 00014 0004 (9007) A4 ALICE 04.10

The objective of this feature is to align the NE to RM.


The operation is available for Q3 NEs while1354RM is in normal online runlevel.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

155 / 268

8.4.4 Consistency audit management


The objective of this feature is to verify the alignment between NE and RM Mib.
The operation is available for TSDIM NEs while the RM system is in normal online runlevel.
Two types of consistency audit are available:

Mark :
differencies are marked. These differencies will be taken into account and downloaded during the
operations of enabling the download and isolation recovery.

Notify:
differences are marked and wil be not taken into account during the operations of enabling
download or isolation recovery.

The consistency audit is available on the NE, only if the NE is not isolated and the 1354RM is in Download
Disable mode.
8.4.4.1 Consistency audit on objects
Objects impacted by the consistency audit are RM elementary objects like ports, single TPs, subnetwork
connections, ...
8.4.4.2 Download disabled to enabled transition
All current operations on the NE must be completed before serving the transition.
8.4.4.3 Startup / Restart scenario
RM elementary objects are taken into account by layers in a server to client order: physical ports, NAPs,
MSTPs, HOCTPs, HO connections, HOTTPs, LOCTPs, LO connections.
8.4.4.4 Ne reachable to unreachable transition
All the current operations on the NE must be completed considering the NE unreachable even if the state
changes again before the end of the current operations.
8.4.4.5 Download enabled to disabled transistion
All the current operations on the NE must be completed before serving the transition. For these operations
the NE has to be considered as still in download enabled.

8.4.4.5.1 Reporting

1AA 00014 0004 (9007) A4 ALICE 04.10

From browser issue Display: Related Items: All Misaligned Objects.


8.4.5 Reporting during consistency ( TSDIM )
This feature allows to present the list of RM objects not consistent with the NE ones.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

156 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The operation is available when the NE is not isolated and in download enabled mode. If the
communication is lost during the download, the operator is informed at user interface and the NE is left
in the download enabled mode; when the communication is resumed no automatic restart of the
consistency download is performed.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

An object can be not consistent due to the misalignment of one or more attributes. For each attribute the
following information are presented :

object class
user label
attribute: attribute of the object that causes the not consistency
error type: reason of the inconsistency
date

The user label field contains the user label of the object with the following exceptions:

msProtBlock4f = user label of the node


ctp (ho) = user label of the port payload position
nap = user label of the port
au4RTM = user label of the node au4
ctp (lo) = user label of the port payload position
connInTopol = user label of the path

The user can choose, using two different commands, to display a global or a restricted list of the objects.
The global list comprises:

ne
port (sdh)
msCtpCap
msProtBlock4f
ctpho
port (pdh)
nap
au4RTM
cap
ctplo
connInTopol
pmTp

The restricted list comprises only traffic affecting attributes:

ne (only if it is not reachable)


msCtpCap (au4Structure, removeFromProtSchema, allAttributes)
msProtBlock4f (msProtConfState, allAttributes)
ctpho (disconnectOnNe, allAttributes)
nap (disconnectOnNe, allAttributes)
au4RTM (consistSt, allAttributes)
cap (virtual, tug1Cfg, tug2Cfg, tug3Cfg, allAttributes)
ctplo (disconnectOnNe, allAttributes)

1AA 00014 0004 (9007) A4 ALICE 04.10

The allAttributes value is used when it is not possible to determinate the attribute that caused the
inconsistency.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

157 / 268

8.4.6 Consistency Status Diagnostic ( Q3 )

Fail to align. failure.

The following table gives an overall mapping of the values of consistency status and consistency activity.

1AA 00014 0004 (9007) A4 ALICE 04.10

Consistency
Status

Semantic

Normal

RM MIB = NE MIB.

Not aligned

NE not reachable
NE in download disable mode
NE in mark audit

Failed to align

The operator can click on the Consistency Status icon, thus displaying the report
identifying the RM failed operation, i.e. the not aligned attributes and the causes of
themisalignment

Config Mismatch

Notify Audit

Aligning

alignment in progress

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

158 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The Consistency Statuses are:

8.5 Example of Q3 NE misaligned

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The following indications of misalignment are perceived by the operator:

On the 1354RM a node is misaligned. ( From the map or from attibute NENOTEMLALIGNED on the
NE list)

a path is disabled, probably as a consequence of the misalignment

SEQUENCE
a)

Set the Network Element to Download Disable mode.

b)

Issue Consistency Audit: Mark Audit

c)

Select NE: Search all related objects: (Not Aligned) Misaligned Objects.

The list of Not aligned (misaligned) objects is displayed.


d)

ED

Enter Configure Download: Enable. The misalignment is recovered.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

159 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

160 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

9 MAINTENANCE TRACING

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This chapter covers the following topics:

J0 Section Trace Identifier Set / Modify

J1/J2 Trace Identifier

Path Trace

Tandem Connection

Monitoring function (POM) on intermediate points

9.1 J0 Section Trace Identifier Set / Modify


SCOPE
The mechanism of section trace identifier ( byte J0 of the RSOHRegenerator Section OverHead ) is used
to control the continuity of the trail in the regenerator section.
Trace Identifier is supported by ADM and DXC NEs according the following rules:
Section Trace Identifier is supported only on SDH ports
Section Trace Identifier is supported if a dedicated info model package ( rsTrailTraceSource/SinkPackage) is instantiated ( under the rsTTP related to the SDH port )
9.1.1 J0 Trace Identifier Set/Modify Virtual to real NE
The operation is not allowed if the port belongs to a virtual NE (external network reference), even if the
user can perform the operation on the other involved physical port.
9.1.2 J0 Trace Identifier Set/Modify
CONDITIONS
Definition or change of J0 is available only for an already Implemented physical connection
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

To configure the Section Trace Identifier, the user has to point to the involved physical connection
and issue the menu Configuration: Trace Identifier: Set/Modify/Read. See Figure 103.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

161 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 103. Physical Conn: Configuration: Trace Identifier

b)

ED
The section trace identifier wizard is displayed. See Figure 104.

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

162 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 104. Section Trace Identifier wizard: Step 1

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

In this step the user can select either Set/Modify or Read the Section Trace Identifier. Select Set /
Modify. The Section Trace Identifier wizard: Step 2 is displayed. See Figure 105. herebelow.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

163 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 105. Section Trace Identifier wizard: step 2


The two ports ending the physical connection are presented.

1AA 00014 0004 (9007) A4 ALICE 04.10

For each supported port the user can configure:

Sent Trace Identifier

Expected Trace Identifier

Enabling/disabling of the Trace Identifier mismatch detection. It specifies if the detection of the Trace
Identifier mismatch is enabled or disabled

Mode1: 16 bytes string (the first byte used for CRC7)

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

164 / 268

Expected Trace Identifier value may be different from Sent Trace Identifier if regenerators are
present along the physical connection.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

N.B.

Figure 106. Section Trace Identifier dialog box.

1AA 00014 0004 (9007) A4 ALICE 04.10

d)

ED

To prevent traffic loss the user has to perform the configuration operations in the following sequence:
1)

Disable the Trace Identifier mismatch detection by setting to FALSE the Expected Trace Identifier Enabling

2)

Configure the Expected value of one port to the desired value

3)

Configure the Sent value of the other port to the desired value

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

165 / 268

Click on Finish to update the values in the equipments

5)

Open again the Section Trace Identifier wizard on the same physical connection and Enable
the Trace Identifier mismatch detection of the previously disabled port by setting to TRUE the
Expected Trace Identifier Enabling

Implement the physical connection with the trace identifier enabled

9.1.3 J0 Trace Identifier Read


SCOPE
The user can ask to read the values of the received Trace identifier on the physical connection if the trace
identifier handling has been enabled on the related port.

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

To read the Section Trace Identifier, the user has to point to the involved physical connection and
issue the menu Configuration: Trace Identifier: Set/Modify/Read. See Figure 103.

b)

The section trace identifier wizard is displayed. See Figure 104.

c)

In this step the user can select either Set/Modify or Read the Section Trace Identifier. Select Read.
The Section Trace Identifier wizard: Step 2 is displayed.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

166 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

e)

4)

9.2 J1/J2 Trace Identifier

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The mechanism of trace identifier ( byte J1 of the VC4 / VC3 or byte J2 in the VC12 ) is used to control
the continuity of the trail / path.

Figure 107. Trail: Configuration: Trace Identifier Management

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From the Trail Routing display point to the trail icon and issue Configuration: Trace Identifier. The
window of Figure 108. is presented.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

167 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 108. Trace Identifier wizard: Step 1

b)

ED

Click on Next button, thus passing to Trace Identifier definition, as per Figure 109.

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

168 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 109. Trace Identifier definition

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Enter the desired values for Sent Trace Identifier ( max 15 characters ) and click on Finish button to
confirm.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

169 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

170 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.3 Path Trace

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

DEFINITION
The trace identifier mechanism is used to control the continuity of a path/trail.
The end point of the transport entity (i.e. path/HOtrail) can be configured to send in the ongoing/egressing
direction a socalled trace identifier. The trace identifier is put into the byte J1 for 140Mb and 34Mb or
J2 for 2Mb.
OPERATION
The trace identifier sent at the end points in the two directions (one for unidirectional paths) can be
compared with the expected value programmed by the OS on end and intermediate points in the ingressing/egressing direction. If a mismatch is found as a consequent action the client layer (e.g. PDH) , will
receive AIS.
When a mismatch of the identifier is found a trace identifier mismatch alarm can also be generated according to the severity defined in the ASAP.
The trace identifier can be monitored also in the intermediate points of the transport entity in the ingressing
and/or egressing direction. Also in this case the received Trace Identifier can be read. If the expected value
is programmed, an alarm can be generated.
The functionality is not managed for QB3* NEs.
9.3.1 Send Trace Identifier Definition/Change
CONDITIONS
Trace Identifier setup is allowed on a defined, allocated, implemented path.
SEQUENCE
The Send Trace Identifier can be defined/changed only for an already created path/HOtrail.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From the path list open the path popup menu and select Path: Configuration: Trace Identifier. See
below figure.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

171 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 110. Path: Configuration: Trace Identifier

b)

ED
The Trace Identifier wizard is displayed. See below figure.

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

172 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 111. Path trace identifier step 1

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Click on Next button. The Trace Identifier wizard displays step 2 dialog box, ( see below figure ), asking the operator to enter the sent Trace Identifier for Source and sink TP

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

173 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 112. Path trace identifier definition.


d)

Click on Finish button to confirm.

9.3.2 Reading Received Trace Identifier


CONDITIONS
Trace Identifier reading is allowed on a implemented or commissioned path.
DEFINITION
The Path Trace functionality is supported at least by the source end point (if the value of the supportedPathTrace attribute of the source end point is unknown the Path Trace Identifier definition is refused).
If the Path Trace functionally is not supported by the sink end point, the operation is accepted to allow,
eventually, the management of the functionality in the intermediate points (if supported)

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
The user, on the path/HOtrail routing display. selects a single CTP/NAP where the TIM ( Trace Identifier
Mismatch ) alarm is present. Choosing the Read received Trace Identifier , the user will see, after the
NE response, the Received and the Expected Trace Identifier.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

174 / 268

9.4 Tandem Connection

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

DEFINITION
The Tandem connection is a mechanism defined in SDH and OTN that makes use of:
Tandem Connection Termination points (TCT) on NAPs and/or CTPs
Tandem Connection Monitoring points (TCM) on intermediate CTPs of the Tandem Connection
The Tandem connection allows:

The handling of Tandem connection specific alarms.

The collection of performance data (15 minutes unidir. and 24 hours unidir. and bidir. ) on end points
(TCT) and on intermediate points (TCM) of the TC.

The handling of the Trace Identifiers.

The handling of elementary Threshold Crossing Alarms on TCT and TCM

The handling of protections inside the TC not affected from external faults (SNCP/S)

FUNCTIONAL DESCRIPTION
A tandem connection represents the part of a path/HO trail that requires monitoring independently from
the monitoring of the complete path/HO trail.
Tandem connections may be directly monitored at one end by writing and reading a portion of the original
trails overhead.
Tandem connections cannot be overlapped in SDH while 6 levels of TCM are defined for the OTN in G.709.
PROCEDURES
In the following the Tandem Connection management procedures are described.
9.4.1 Tandem Connection Create
SCOPE
The scope of this procedure is to define a Tandem Connection; starting from a path/trail, the user can select
a single TP (NAP/CAP or CTP) and specify:
The type: TCM (for CTPs) or TCT (for CTPs or NAPs/CAPs)
The level (always 0 for SDH)
The direction:
Ingressing or Egressing for TCM

1AA 00014 0004 (9007) A4 ALICE 04.10

Including Matrix or Excluding Matrix for TCT. In particular, NAP s and CAP s can only support
Including Matrix TCT
The enabling or disabling of the consequent action (i.e. the enabling or not of AIS insertion in case of TC
problems).

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

175 / 268

The definition is possible only when the path/HO trail is at least allocated and it is lost when the path is
deallocated.
OPERATION
The performed checks are related to unidirectional paths only and are the following:

An Ingressing TCM cannot be instantiated below a CTP with sink role in the crossconnection

An Egressing TCM cannot be instantiated below a CTP with source role in the crossconnection

Following the definition of at least one TCT or TCM, on the using path/trail, an attribute specifies that a
manual TCM have been enabled.
Where possible, restrictions at NE level, should be taken into account during this definition phase.
Possible restrictions to be detected in this phase are related to:
NE type and version.
The support in the same TP, of TCT with more than one direction (e.g. it is not possible to have two TCTs,
before and after matrix on the same AU4 for starting and ending two different tandem connections in the
same TP).
On SDH it is not possible to instantiate a TCM and a TCT on the same TP, on OTN it will be possible at
different levels
TCT and TCM are managed as new classes contained in NAPs, CAPs and CTPs.
Once created TCT and TCM have a configuration state set to defined.
The system automatically sets the ASAP OF TCT/TCM according to the following rules:
For a unidirectional path, the ASAP of a created TCT is set depending on both the role of the related CTP
in the connection and the TCT direction (Including Matrix, Excluding Matrix), i.e. is set according to the
following table
Source CTP

Sink CTP

Including Matrix

All disabled (*)

Ferf&Ais disabled

Excluding Matrix

Ferf&Ais disabled

All disabled (*)

(*) All disabled in order to not detect the Unequipped alarm in the not used sink direction.
For a bidirectional path:
The ASAP of a created TCT is set Ferf&Ais disabled
The ASAP of a created Ingressing TCM instantiated below a boundary CTP is set None disabled

1AA 00014 0004 (9007) A4 ALICE 04.10

The ASAP of a created Egressing TCM instantiated below a boundary CTP is set Ferf&Ais disabled
The ASAP of a created TCM instantiated below a not boundary CTP is set None enabled. This because
the functionality to instantiate a TCM below a specific not boundary CTP has to be used for performance
monitoring purpose and not for fault localization (in this case another function will be provided to the user
to activate on all the CTPs internal to the TC the monitoring function).

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

176 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONDITION

AUTOMATIC DEFINITION of TC termination or monitoring points

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The user can ask for the automatic definition of TC for a path or a HO trail.
The command is only accepted if the path or HO trail is
Partially terminated and there is only one boundary CTP
Fully not terminated and there is only two boundary CTPs.
The system automatically creates the TCT for the NAP and for the boundary CTP(s).

SEQUENCE
a)

ED

To open the popup menu, point to the path icon from the browser window or select the path from
the path list and press the right mouse button.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

177 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 113. Configuration: Tandem Connection popup menu item

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

Select Configuration: Tandem Connection. The Tandem Connection Management wizard opens.
See Figure 114. herebelow.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

178 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 114. Tandem Connection Management wizard

1AA 00014 0004 (9007) A4 ALICE 04.10

The possible actions you can select from the radio buttons box are:

ED

Creation

Implementation

Consequent Actions Enabling

Consequent Actions Disabling

Deimplementation

Removal

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

179 / 268

Select option Creation and Creation modality. You can select between AUTOMATIC and MANUAL.
If you select AUTOMATIC the system creates TCTs on NAP/s and boundary CTP/s.
If you select MANUAL, you will select the termination points
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

c)

Figure 115. Action selection radio buttons


d)

Tandem Connection createstep 2 allows to select manually the TPs. By clicking on the selection
button, the selection list is presented, as per Figure 116. herebelow. The upper selection button allows to select the point/s on which TCT /s is/are to be defined. The lower selection button allows to
select the point/s on which TCM/s is/are to be defined.

e)

Select the termination point and click on Apply. The icon of the selected termination point is displayed
ROUTE DISPLAY ICON

SELECTION BUTTONS

1AA 00014 0004 (9007) A4 ALICE 04.10

TP SELECTION LIST

Figure 116. Tandem Connection createstep 2TP selection

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

180 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 117. TCT attributes specification


f)

Select TCT attributes:

The direction:
Ingressing or Egressing for TCM

1AA 00014 0004 (9007) A4 ALICE 04.10

Including Matrix or Excluding Matrix for TCT. In particular, NAP s and CAP s can only support
Including Matrix TCT
The enabling or disabling of the consequent action (i.e. the enabling or not of AIS insertion in case of TC
problems).
The operation is accepted either when the TCT is defined or implemented.
In case of TCT implemented, the operation (Enabling consequent action) may affect the traffic.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

181 / 268

If the consequent action is not enabled, the far end counters are not managed both for TCM and TCT.
Click on Finish button to complete the Tandem Connection definition.

9.4.2 Tandem Connection display


SEQUENCE
a)

Point to the path icon and select path routing display. Notice that a graphical flag is drawn in correspondence
of
the
path
icon.
See
below
figure.
In addition, dedicated flags are shown for TCT and TCM .

1AA 00014 0004 (9007) A4 ALICE 04.10

On each TP where at least one TCM or TCT has been at least defined, a flag is set to indicate this condition.

Figure 118. Path routing display ( tandem flag )

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

182 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

g)

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 119. Path routing view: tandem flag

Figure 120. Path icon on browser: tandem connection state icon


Starting from a path, it is possible to visualize the list of TCM or TCT: select the path from the path list and

1AA 00014 0004 (9007) A4 ALICE 04.10

issue Search: Related Items: TCM/TCT list. see following figure.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

183 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 121. Tcm/tct list selection

Figure 122. Tcm/Tct list.

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

184 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

On a given TCT or TCM, it is possible to visualize all the attributes (e.g. consistency status, direction, level
etc.). Select the TP and issue Show/Set Attributes.
In addition, in the NAPs view, a NAP involved in a Tandem Connection is marked by a dedicated icon.
See below figure.

Figure 123. Path NAPs view with TC

9.4.3 Tandem Connection Implement


The user can manually implement (i.e. create in the NE) TCT and TCM through a manual command to
be issued on single TCTs and TCMs. The single TCT/TCM must be defined; if not, the command is refused.
The belonging path/trail must be implemented.

1AA 00014 0004 (9007) A4 ALICE 04.10

Once created in the NE, the TCT or the TCM takes the configuration state equal to implemented.
If, at creation time, the NE provides a KO specifying that the TCT/TCM service is not supported, the
TCT/TCM consistency state is set failed to align with error type feature not supported. The user will
manually deimplement and remove TCT/TCM .

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

185 / 268

The user can manually implement all the defined TCTs and TCMs through a manual command to be
issued at path/trail level. The Path/HO trail must be implemented; if not, the command is refused.
Please refer to the above Manual Implementation of TCT and TCM for each TCT/TCM implementation
activity inside the system.
9.4.4 TCT/TCM deImplement
9.4.4.1 TCT/TCM manual deimplementation
The user can manually deimplement TCT and TCM through a manual command to be issued on single
TCTs and TCMs. The single TCT or TCM must be implemented: if not, the command is refused.
Once removed in the NE, the TCT and the TCM takes the configuration state equal to defined.
If the consistency state of the TCT/TCM was feature not supported, no removal is performed towards
the NE.
This operation requires also an interaction at TCT/TCM level with the management of Performance
Monitoring (see SDH/PM section)
9.4.4.2 TCT/TCM global manual deimplementation
The user can manually deimplement all the TCTs and TCMs through a manual command issued at
path/trail level. Path/HO trail must be implemented: if not, the command is refused.

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

From the Tandem Connection wizard select action button Deimplement

b)

Click on Finish button.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

186 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.4.3.1 TCT/TCM global manual implementation

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 124. Tandem Connection wizard

9.4.5 TCT/TCM global automatic deimplementation ( upon path/trail deimplement )


TCT and TCM are removed in the NE if the path or trail containing TCT and TCM is deimplemented.
This is done as an implicit activity of the path/trail deimplementation command.

9.5 Manual remove of TCTs and TCMs


Single TCTs and TCMs can be removed through an operator command.

1AA 00014 0004 (9007) A4 ALICE 04.10

The TCT/TCM to be removed must be in the defined state. If the removal is performed in download
disable mode, the information of misalignment with respect to the NE will be reported on the related TP
If, under a given CTP or NAP, all the TCTs/TCMs are removed, the flag indicating the TC point is also reset.
All the flags on TPs and path/HO trail are updated in a consistent way.
NOTE

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

187 / 268

When a path/HO trail (or a portion of it) is deallocated, the defined TCTs and TCMs are automatically
removed.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All the flags on TPs and path/HO trail are updated in a consistent way.

SC.4:MAINTENANCE
3AL 61348 AA AA
268

188 / 268

9.6 Monitoring function (POM) on intermediate points

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

DEFINITION
The user can ask to enable or disable the monitoring function on the intermediate points of a path/HO trail.
By default when a path/HO trail is implemented, the monitoring function on intermediate points is disabled.
Enabling the monitoring function on intermediate points means:
The instantiation of the POM (Path Overhead monitoring function) on intermediate CTPs (both egressing
and ingressing according to the real availability in the NE and the path directionality)
The enabling of all alarms on the POM.
The enabling of all alarms on the intermediate CTPs (LOP, AIS, etc.).
When the monitoring function on intermediate points is disabled, alarms and Overhead Monitoring
capability is only enabled on Naps and on boundary CTPs.
This functionality is targeted to perform the needed troubleshooting on a not working or not properly
working path/HO trail.
The enabling of this functionality is intended only as a transitory state.
The user should limit the use of this functionality in order to not overload the system.
The user can only ask to enable this functionality when the path is totally or partially implemented (not
commissioned).
The system enables the monitoring function only on intermediate CTPs belonging to QB3 NEs. QB3*
NEs are not taken into account.
If the path/HO trail has the Trace identifier enabled, the expected trace identifier is set also on intermediate
points according to the type of the path.
The alarms received on POM functions and on CTPs are NOT propagated to the paths and are only used
to give information to the user. The main graphical view to be used for troubleshooting is the path/HO trail
route display.
The enabling status of this functionality is represented by a global attribute of the path/trail. To be noted
that the value enabled is only referred to the NEs supporting the functionality and it has in general the
meaning of where possible.
When a path is deimplemented the monitoring function on intermediate points is disabled first.
The enabling of this functionality is performed regardless to the state of the QB3 SDH alarm enabling
status of the belonging path/HO trail.

1AA 00014 0004 (9007) A4 ALICE 04.10

The interworking between Trace identifier management, alarm enabling/disabling on paths/HO trails,
monitoring function on intermediate points, is giving from the following table
Nap and boundary
CTPs
Trace identifier
Enabling of alarms

ED

01

CTPs in
SNCPN

Generic intermediate CTPs

Enable trace identifier on path/HO trail


Enable path/HO trail
alarms

Enable Monitoring function on intermediate points

SC.4:MAINTENANCE
3AL 61348 AA AA
268

189 / 268

How to enable POM on a path, by pointing at the path icon and issuing the following command:
Path: Configuration: POM on Ctps: Enabling

Figure 125. Path: Configuration: POM on Ctps popup menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

path routing display: all alarms on intermediate CTPs are visible

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

190 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figures which follow show:

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 126. Routing Display: path CTP

ED

Trace Identifier read on a certain CTP, by issuing the command Trace Identifier: Read.

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

191 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 127. CTP: Trace identifier read

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

192 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

9.7 Loopback on PDH port / NAP

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The following loopback commands can be launched on PDH naps/ ports:

No Loop

Line Loop & AIS

Internal Loop & AIS

Line Loop & Continue

Internal Loop & Continue

Figure which follows shows the Manage Loop popup menu available on NAP.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 128. Nap: Manage Loopback

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

193 / 268

In this case, as shown in the following figure, on the port corresponding to the first NAP a line loop is executed. AIS signal is sent toward the network, detected by the far end NAP and sent back.

SHOW/SET
ATTRIBUTES

AIS

LOOPBACK
ACTIVE

AIS

Figure 129. Loopback active

1AA 00014 0004 (9007) A4 ALICE 04.10

The NAP loopback status can be shown via Show/set Attributes of the involved NAP. see below figure.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

194 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

EXAMPLE OF LINE & AIS loopback

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 130. Nap loopback status supervision


EXAMPLE OF INTERNAL & AIS loopback
In this case, as shown in the following figure, on the port corresponding to the first NAP a loop is executed
toward the network. No alarm is detected by the network, while AIS signal is sent on the line and detected
by the client 2 Mb equipment.

1AA 00014 0004 (9007) A4 ALICE 04.10

The NAP loopback status can be shown via Show/set Attributes of the involved NAP.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

195 / 268

9.8 Loopback commands on CTP

Set

Remove

Figure which follows shows the Manage Loop popup menu available on CTP. Point to the CTP and issue
Internal Loopback: Set to setup the loop or Internal Loopback: Remove to remove the loop.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 131. CTP: Internal Loopback: Set

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

196 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The following loopback command can be launched on CTP:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

EXAMPLE OF CTP loopback


In this case, as shown in the following figure, on a CTP a loop is executed toward the network. AIS signal
is sent toward the network and detected by the connected NAP.

LOOPBACK

LOOPBACK

AIS

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 132. CTP: Internal Loopback display

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

197 / 268

9.9 Craft Terminal Supervision

1AA 00014 0004 (9007) A4 ALICE 04.10

CT Access Granted

CT Access Required

CT not connected enabled

CT Access Denied

ED

01

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

From browser the following information are displayed:

SC.4:MAINTENANCE
3AL 61348 AA AA
268

198 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10 PROTECTION MANAGEMENT
10.1 SNCP path layer switch management
The SNCP switch management commands can be applied to SNCP paths or to Bridge & Switch
connections in topology

Figure 133. Path:Manage SNCP menu.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

199 / 268

SEQUENCE
a)

From the browser window, e.g. from the Routing display, point with the mouse at the path icon and
open the Manage SNCP popup menu. It is possible to obtain this menu by selecting the path icon
and selecting the Actions:Manage SNCP pulldown menu. The Manage SNCP menu allows to
further select between:

Synchronize. This command retrieves the actual switch status of the B & S connections from
EML.

Release. This command clears the previously issued lockout/forced/manual command. This
command is available for all types of Network Element.

Lockout. This command either locks( forces ) the path/switch to the main route if a Set
Revertive command has been previously entered or locks the path/switch to the actual position
if a Set not Revertive command has been previously entered.

Force Main . This command forces the path on the main route. The path will remain on the main
route even in case of failure. This condition can be modified only by means of the Release
command.This command is available for all types of Network Element.

Force Spare . This command forces the path on the spare route. The path will remain on the
spare route even in case of failure. This condition can be modified only by means of the Release
command. This command is available for all types of Network Element.

Manual Main . This command switches the path to the main route. The switch is rejected in case
of failure and if a previously issued Force/Lockout command is active. The Force/Lockout
condition can be cancelled by means of the Release command.

Manual Spare . This command switches the path to the spare route. The switch is rejected in
case of failure and if a previously issued Force/Lockout command is active. The Force/Lockout
condition can be cancelled by means of the Release command.

Set Revertive. This command causes the path to revert to the main route after the repair of the
involved objects. The Wait to restore time parameter is managed at Equipment layer. This
command is available for all types of Add and Drop Multiplexers; it is not applicable to 1641SX
cross connect.

Set not Revertive. ( default ) The path does not revert to the main route after the repair of the
involved objects. This command is available for all types of Add and Drop Multiplexers; it is not
applicable to 1641SX cross connect.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 134. shows an example of display of a B & S connection in topology.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

200 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Events which manage the switch position have a priority mark; in particular Forced SNCP commands have
priority greater than failure events, while failure events have priority greater than Manual SNCP
commands.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 134. Example of display of a B & S connection in topology.


The switch status can assume the values:

M main. It means that the switch is turned to the main position

S spare. It means that the switch is turned to the spare position

C service. It means that the switch ( only for D & C ) is turned to the service position

The last operation executed on the switch can assume the values:

F( forced) . It means that the switch has been forced.

R (released). It means that the switch has been released.

L (lockout) . It means that the switch has been locked.

None. No action has been executed on the switch.

The Revertive operation mode icon is present if the switch has been set to Revertive.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

After the execution of a Manage SNCP command a report is forwarded to the operator.
See Figure 135.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

201 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 135. Report.

Figure 136. Connection in topology attributes.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

For a SNCP path the attribute SNCP status can be:

01

unknown. The actual position of one/more switch/switches is unknown. A Manage SNCP:


Synchronize command is required.

idle. No force/manual command has been previously entered.


SC.4:MAINTENANCE
3AL 61348 AA AA
268

202 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

N.B.

forced SNCP. At least one switch is set to forced.

manual SNCP. At least one switch is set to manual.

For a SNCP trail the same commands apply. Notice that The trail can be terminated with an
SNCP connection only in case of 1661SMC equipment with Enhanced connectivity (able to
create an SNCP connection with grooming). Otherwise the trail must utilize an unprotected
physical connection and create the SNCP connection in another NE.

HOTrail protected with enhanced connectivity

SPARE

LOLCs
LOCTPs

LOCTPs

MAIN

HOTrail protected without enhanced connectivity

SPARE

LOCTPs

LOLCs

LOCTPs

MAIN

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 137. HOTrail with and without enhanced connectivity

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

203 / 268

10.2.1 Automatic Protection Switch in 2fiber MSSPRING


10.2.1.1 Bridge and Switch
In case of fiber breaks, the APS for 2F MSSPRING uses a synchronized sequence of bridge and switch
operations that modify the internal connections of the two NEs adjacent to the failure.
The bridge operation on the East (West) side has the effect of routing the outgoing high priority
West (East) traffic also to the outgoing protection East (West) capacity.
When a switch operation is in effect on the East (West) side, all of the connections that have
as a source an Au4 belonging to the West (East) working capacity are replaced by connections
that have as a source the incoming East (West) protection traffic.
when one end of a connection is modified from working traffic to protection traffic, the Au4 of the protection
traffic that replaces the Au4 of the working traffic has an index that is always (n/2) greater (i.e., in case of
Stm16 aggregates, the Au4 #2, is substituted by the Au4 #10, where 10 = 2 + (16/2) ).
Note that the bridge and switch operations on the same side can coexist (this is the typical case,
indeed): since they affect different class of connections, the final configuration is given by the sum of the
two.

protection
working

BEFORE

AFTER

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 138. Effect of a BRIDGE EAST

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

204 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10.2 Multiplex Section Layer switch management

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ED

01

BEFORE

BEFORE
protection
working

protection
working

W
E

AFTER

Figure 139. Effect of a BRIDGE WEST

W
E

AFTER

Figure 140. Effect of a SWITCH EAST

SC.4:MAINTENANCE

3AL 61348 AA AA

268

205 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01
E

BEFORE
W

protection
working
W

3AL 61348 AA AA

268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

AFTER

Figure 141. Effect of a SWITCH WEST

SC.4:MAINTENANCE

206 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10.2.1.2 Steps of a ring switch


In case of failure of a span, the failed span is replaced with the capacity of the protection traffic of the spans
not affected by the failure (note that the protection switching can also be triggered by a command issued
by the OS, as will be described in the following). This situation is the result of the following sequence of
steps, synchronized via a protocol that uses the byte K1K2 of the MSOH;
1)

The node that detects the failure (Tail End), sends a Bridge Request to the node that is adjacent
along the direction where the failure is present (that becomes the Head End): this Bridge
Request is sent on both the long and the short path.

2)

The intermediate nodes substitute all of the connections pertaining the low priority traffic with
bypasses among the two aggregates.

3)

When the Head End receives the Bridge Request on the short path, it sends back to the tail end
a Reverse Request on the short path and a Bridge Request on the long path.

4)

When the Head End receives the Bridge Request also on the long path, it performs a ring Bridge
and sends to the Tail End, on both paths, the notification of this new status

5)

When the tail end receives, on the long path, the bridge request from the Head End it performs
a ring bridge and sends the notification of this new status to the head end, using both paths.

6)

When the tail end receives, on the long path, the notification of the execution of the bridge on
the head end, it performs a ring bridge and switch and sends the notification of this new status
to the head end, using both paths.
When the head end is aware of the bridge and switch activated on the tail end, via the report
of the bridge status on the long path, it performs a switch, so that both ends are now in bridge
and switch

7)

When a protection switch is in effect, all of the protection capacity is used to recover the working traffic;
in this situation no low priority connections can be established on the protection capacity and it is required
that, in order to avoid misconnections, all of the tributaries that terminate a lowpriority connection output
an AIS signal (this operation is called squelching).

1AA 00014 0004 (9007) A4 ALICE 04.10

After the failure has been removed, a similar sequence of operations is performed by the head and tail
end; if the failure was single, the reverse procedure can starts after a specified time interval, called Wait
Time to Restore (WTR).

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

207 / 268

The following diagrams depict the sequence of operations that occur in a sixnodes ring when a single
failure (signal degrade, in this case) occurs on the fiber that carries the traffic from node 2 to node 3.
Figure 142. depicts the initial situation, where a tributary at node 1 is connected with another tributary
at node 4, using the clockwise direction for the path going from node 1 to node 4 . The remaining
capacity, both working and protection, is used to source and terminate unequipped VC between the
adjacent nodes.

Tributary

Tributary

Working Channels
Protection Channels
Figure 142. :Example of six nodes ring

1AA 00014 0004 (9007) A4 ALICE 04.10

a failure affects the connection from node 2 to node 3.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

208 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10.2.1.3 Example of ring switch in a 6nodes 2f MSSPRING

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Tributary

Working Channels
Protection Channels

Bridge

Tributary

Switch

Figure 143. Step 4: Final situation


A squence of bridge and switch operations occurs. The final configuration is shown in Figure 143.
10.2.2 Squelching in case of isolated nodes
With some classes of multiple failures, some nodes in a 2f MSSPRING could be isolated, i.e. unreachable
by the other nodes. When a node is unreachable, it can be demonstrated that, due to the bridge and switch
operations that are performed by the ring itself, some tributaries could be misconnected, i.e. connected
to the wrong source or destination. In order to avoid this effect, a technique called SQUELCHING consists
in the injection of an AIS signal on the VCs that come from or go to an isolated node.

1AA 00014 0004 (9007) A4 ALICE 04.10

The squelching technique requires that two different squelching actions are taken on the HVC and on the
LVC. The HVC are squelched only at the switching nodes, i.e. at the nodes that perform bridge and switch,
while the LVC are squelched where they are terminated. Furthermore, a different squelching action is
taken on the HVC according if they are accessed at the LVC level or not; in detail, if the VC4 is composed
of VC12 that are terminated at different nodes, the squelching performed at the switching nodes must be
removed after the final bridge and switch state has been reached: this is necessary in order not to loose
LVCs that would be otherwise unnecessarily squelched.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

209 / 268

When a 2f MSSPRING is interworked with another ring (either SNC/I or MSSPRING), the
interconnection of the two is performed by connecting two pair of nodes per ring with HVC connections,
as shown in the following figure.
Each VC4 that has to cross the ring boundary (only HVC level ring interconnections are considered here)
must be output by two nodes, one of which, the primary service node (PSN) drops it and continues to the
secondary service node (SSN). In the opposite direction, the SSN inserts a copy of the VC4 into the ring
and the PSN selects between the VC4 coming from the SSN and the VC4 that can be locally inserted. The
selection is performed on the basis of the pathAIS.
The protection mechanism works on the hypothesis that the other ring selects one of the two version of
the incoming VC4 and transmits two identical copies of the VC4 towards the PSN and the SSN (this is
guaranteed if the other ring is an MSSPRING or an SNC/I ring).
Note that the PSN and the SSN need not to be adjacent and need not to be the same for all of the VC4
that cross the ring boundary: i.e. each crossing VC4 has two associated nodes that act as PSN and SSN.
It is also possible to connect two rings at more than two points, but this is usually unfeasible with the normal
ring topologies and has not been considered here.

1AA 00014 0004 (9007) A4 ALICE 04.10

This document does not address the case where the VC4 that crosses the boundary is terminated at its
primary service node.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

210 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10.2.3 MSSPRING Interworking

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2f MSSPRING

Primary
Service
Node

ED

01
Secondary
Service
Node

SNCP or MSSPRING

Figure 144. Drop and Continue at the service nodes.

SC.4:MAINTENANCE

3AL 61348 AA AA

268

211 / 268

10.2.4 Provisioning of the APS Controller

First of all, the APS Controller must know whether it shall operate or not, e.g. because the ring is protected
with a different strategy: this information will be called APS Controller enabling and can be considered
as a binary value (enabled or disabled).
APS Controller must be explicitly activated to exchange K1 and K2 bytes with the other N.E.; also this
information can have only two values (activate or inactive). Note that an enabled but inactive APS
Controller is in a well defined state, which corresponds to a particular set of transmitted K1K2 bytes,
default APS bytes; It is required that the default APS code on K1K2 is a pattern of all zeroes
An enabled APS Controller (even when it is inactive) needs to know the node identifier of the N.E.
where it is operating; the node identifier is a number in the range 0 through 15, and is unique within
the ring.
An enabled and active APS controller must be aware of the topology of the ring, i.e. of the sequence
of nodes (ring map) that is encountered when traversing the ring in a specified direction (e.g.
clockwise); the crossed nodes are identified by their node id and may not be more that 15 (the total
number of N.E. in a 2F MSSPRING is 16) neither less than 2.
A final parameter that must be known by the APS Controller is the Wait Time to Restore value; this value
may range from 0 to, at least, 15 minutes (a step of 1 minute is accepted);
10.2.4.1 Squelching tables: definition and size
The HpSq block needs to receive two sets of squelching tables that contain some routing information
that is necessary to properly identifiy where and when inject AIS.
The first set is composed of four tables that will be called, in the following, VC4 squelching tables. There
is a VC4 squelching table for each aggregate input and output of the network element. The structure of
the four tables is identical: for each incoming (or outgoing) High Priority Au4 (i.e. Au4 1..2 for the Stm4
and Au4 1..8 for the Stm16) the table must contain the source and the destination nodes of the transported
VC4; note that, in case of ring interworking, the VC4 can have two source nodes . It is also allowed for a
VC4 to have multiple destination nodes (up to 15 in the worst case). It can be demonstrated that only one
source and one destination node is necessary for the VC4 squelching tables, namely the farthest source
node and the fartherst destination node.
If a VC4 contains LVC that have different source or destination nodes, the VC4 squelching table must
indicate this situation: for this field a binary value is enough.
If a fixed size table is chosen, the size of each row of each VC4 squelching table is 9 bits, where this number
is obtained by adding 4 bits for the source node identifier, 4 bits for the destination node identifier and 1
bit that indicates whether the VC4 is accessed at the LVC level or not. Multiplying the row size and the
number of rows and the number of tables, the final value of
4 x 8 x (4 + 4 + 1)

288 bits

(36 Bytes)

is obtained

1AA 00014 0004 (9007) A4 ALICE 04.10

The second set of squelching tables contains, for each terminated LVC, the indication of the source node
of the LVC itself. Also in this case an LVC may have two source nodes that musy be indicated in the table,
regardless of which is the primary and which is the secondary). In the worst case (8 VC4 structured as
63 TU12, all with double source) the following total size is obtained:
63 x 8 x (4 + 4)

4032 bits

(504 Bytes)

As said before, the VC4 squelching tables have to be provided to all of the nodes of the ring, while the LVC
tables are required only at the nodes where LVC traffic is terminated.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

212 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The APS Controller blocks need a set of configuration information for properly execute their functions.

10.2.4.2 Squelching tables: example

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In order to explain with the sufficient detail level, an example of squelching table computation is presented.
In the following figure, a 7 node ring is considered, where the node id are represented by capital letters
from A to G. Five connections are supposed to exist, three regarding VC12 and two regarding VC4:

VC12 #1 of VC4 #1 is supposed to be inserted at node A into the VC4 #1. The exit point of this VC12
is node G. Due to the connectivity restrictions, the VC12 will have not changed neither the TU12 nor
the Au4 along the path.

VC12 #2 of VC4 #1 has two sources, due to the ring interworking: node B is the secondary service
node, while node C is the primary. The destination node is F. Vc12 #2 always occupies the TU12 #2
of the VC4 #1 that is transported into the Au4 #1.

VC12 #63 of VC4 #1 has one source node, E, and two destination nodes, namely F and G: i.e. this
is a pointtomultipoint connection. The Vc12 #63 always occupies the Tu12 #63 of a VC4 that
always occupies the Au4 #1.

VC4 #2 follows the same path of Vc12 #63 of VC4 #1.

VC4 #8 has two sources, A and B, respectively the secondary and primary service nodes, and has
two destination nodes, E and F.

WEST

EAST

VC12 #1
VC4 #1

VC12 #2
SSN

PSN

VC12 #63
VC4 #2
VC4 #8
SSN

PSN

Figure 145. Example of squelching table configuration

1AA 00014 0004 (9007) A4 ALICE 04.10

The VC4 squelching tables for the nodes represented in the example are listed in the following. Note that
a VC4 containing LVC is terminated each time an LVC is inserted and or dropped, so that the only node
where the VC4 #1 is not terminated is node D.
VC4 squelching table for node A

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

213 / 268

Node A

From To

West Output
LVC

From To

East Input
LVC

From To

East Output
LVC

VC4 #1

From To

LVC

YES

NO

VC4 #2

VC4 #8

LVC squelching table for node A (no entries)


Node A
From:

VC4 squelching table for node B


Node B
West Input

VC4 #1

West Output

From To

LVC

From To

East Input
LVC

From To

East Output
LVC

From To

LVC

YES

YES

NO

NO

VC4 #2

VC4 #8

LVC squelching table for node B (no entries)


Node B

1AA 00014 0004 (9007) A4 ALICE 04.10

From:

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

214 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

West Input

VC4 squelching table for node C

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Node C
West Input

VC4 #1

West Output

From To

LVC

From To

East Input
LVC

From To

East Output
LVC

From To

LVC

YES

YES

NO

NO

VC4 #2

VC4 #8

LVC squelching table for node C (no entries)


Node C
From:

VC4 squelching table for node D


Node D
West Input

VC4 #1

West Output

From To

LVC

From To

East Input
LVC

From To

East Output
LVC

From To

LVC

YES

YES

NO

NO

VC4 #2

1AA 00014 0004 (9007) A4 ALICE 04.10

VC4 #8

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

215 / 268

VC4 squelching table for node E

West Input

VC4 #1

West Output

From To

LVC

YES

From To

East Input
LVC

From To

East Output
LVC

VC4 #2

VC4 #8

NO

From To

LVC

YES

NO

NO

LVC squelching table for node E


Node E
From:

VC4 squelching table for node F


Node F
West Input

West Output

From To

LVC

VC4 #1

VC4 #2

VC4 #8

From To

East Input
LVC

From To

East Output
LVC

From To

LVC

YES

YES

NO

NO

NO

LVC squelching table for node F


Node F

1AA 00014 0004 (9007) A4 ALICE 04.10

From:
Vc12 #2 of VC4 #1

B, C

Vc12 #63 of VC4 #1

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

216 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Node E

VC4 squelching table for node G

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Node G
West Input

West Output

From To

LVC

VC4 #1

YES

VC4 #2

NO

From To

East Input
LVC

From To

East Output
LVC

From To

LVC

VC4 #8

LVC squelching table for node G


Node G

1AA 00014 0004 (9007) A4 ALICE 04.10

From:
Vc12 #1 of VC4 #1

Vc12 #63 of VC4 #1

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

217 / 268

An MSSPRING can be created on the map by means of the command Construction: Add Object: Ring:
MSSpring... Checks are performed during validation and activation phase: only 1661SMC and 1664SM
and 1670SM are allowed.
Implementation, deimplementation and removing can only be performed on the complete ring and not
on single connections.
During the implementation, RM creates :

the MSSpring protection block


protected MSTPs
protected MSTrails

and sets the Node Identifier in the MSSPRING.


The payload configuration activity after ring implementation creates only 8 AU4s and any change of the
payload configuration requires the specification of 8 AU4s.
On the protection block, the following operations are available: ( see NO TAG)

synchronize
release
force east, west
lockout east, west
manual east, west

change Wait To Restore time (5, 300, 600, 900 sec) ( see NO TAG)

The position of the protection block is displayed using 4 attributes:

Switch position (displayed on main view) : unknown, idle, bridge east or west, bridge & switch east
or west, pass through
Switch cause (displayed on main view) : Failure, Restoration, Operator Request, None, Unknown.
Active Operator Command : Release, Lockout, Force, Manual, None.
Pending Operator Command : Release, Lockout, Force, Manual, None, Synchronize. It is the
command under execution. It is set to none when the answer (OK or KO) is received from the EML.

1AA 00014 0004 (9007) A4 ALICE 04.10

At the beginning all the switch positions and switch causes are set to unknown, the pending is set to none.
After a parametric time T1, the managing process performs a synchronization for a parametric number
N of switches with the position set to unknown (i.e. not yet synchronized manually or through an event).
After another parametric time T2, the operation is repeated with another set of N unknown switches.
During this automatic synchronization, the pending command of the switches under operation is set to
Synchronize.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

218 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10.3 Management of switches at RM interface

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10.3.1 Display of the Protection blocks


A view of all the MS Protection Blocks in a MSSPRing is available in the browser. To display this view,
execute the following procedure:
a)

From the browser point with the mouse at the network and open the popup menu. Select item
Search: All related items... ( see Figure 146. )

b)

From the selection box select item NPAs and click on OK button. The NPA drawing window is
displayed.

Figure 146. MSSpring: Display All related items...

1AA 00014 0004 (9007) A4 ALICE 04.10

Switch East

Switch West

Figure 147. Examples of actual position of the switches.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

219 / 268

All the HO SbnConns belonging to HOPaths and HOTrails in MSSPRING topologies include
squelching Information (4 values : West Src / West Dst / East Src / East Dst end Nodes Identifiers).
Squelching Info are also set for the connections between HOTTP and HOCTP.
For broadcast paths, the squelching information related to legs is evaluated run time during the
implementation (when multiple legs and passthrough are merged into a single broadcast connection).
10.3.1.2 Linear MS protection (1+1)
This feature is only applied to ADMs.
The management of the protection is done by the EMLs. On RM side, only the presence of the protection
is displayed to the operator.

1AA 00014 0004 (9007) A4 ALICE 04.10

In addition to the alarm already foreseen in case of failure on both the fibers involved in the linear MS
protection, a new alarm is emitted at SENIM level also when a failure on a single fiber will occur. This will
warn the operator on the reduced degree of protection.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

220 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10.3.1.1 Squelching Info

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10.3.2 4F NPE RING Switch Management

A view of all the MS Protection Blocks in a MSSPRing is available in the browser. To display this view,
execute the following procedure:
a)

From the browser point with the mouse at the network and open the popup menu. Select item
Search: All related items...

b)

From the selection box select item NPA and click on OK. The NPA list is displayed.

c)

Point to the 4F NPE RING NPA and click on NPA view button. The NPA view is displayed.

d)

From each protection block it is possible to issue the ring switch and span switch commands.

The effect of the Span Switch and Ring Switch operations is described in Section Technical Annexes, NPE
ring.
The above mentioned commands are mainly used for maintenance purposes. See Section
MAINTENANCE, Chapter 4 Diagnostic of the NPE Ring.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

221 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

222 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11 PERFORMANCE MONITORING
11.1 Introduction
The aim of the Performance Monitoring at RM side is to allow the user to monitor transport objects, i.e.
the objects path and trail. The monitoring activity is executed on the involved tps.
In order to monitor transport objects, the user creates objects called Measures , which are performance
monitoring work sessions, defined by a set of characteristics according to the Customers needs.
After creating the measure, the user must associate (correlate) to it the transport/s to monitor and the
termination points (TPs). See NO TAGon page NO TAG.
The status of the measure can be:

Planned. This means that the measure has been defined.

Active. This means that the collection activity is working.

Stopped. This means that the collection activity is terminated. The collection activity can restart upon
entering the Activate command.

To activate a measure on paths/trails, the following conditions are mandatory:

the path/trail working state = normal


the path configuration state = implemented or commissioned
the trail configuration state = configured at LO

Figure 148. shows the PM menu items in the browser window.

Figure 148. PM functional buttons in the browser window.


N.B.

Only one measure can be active at the same time on a PM termination point for a given
granularity value ( 15 , 24 h )

N.B.

For a path terminated to all virtual objects, the relevant tps cannot be automatically correlated.

1AA 00014 0004 (9007) A4 ALICE 04.10

In the following paragraphs it is given a description of the main procedures relevant to PM.

TCA handling on 24 Hours Measurements

N.B.

This feature allows the definition of TCA profiles on 24h unidirectional measurements.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

223 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The user is able to correlate a TCA to 24h measurements. For new NEs, the Maintenance measurement
should to be used but, for compatibility, also the QoS measurement is accepted.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

224 / 268

11.2 Creating the Measure

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE
a)

From the Browser select the PM domain and open the popup menu. Select the command Create:
Measure. The object creation dialog box is presented.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 149. Measure Creation dialog box.


b)

Enter the following attributes:

measure name (userlabel) . The measure name can be modified, by means of the SHOW/Set
Attributes command, only if the measure status is PLANNED.

Objective. Possible values are:

ED

Qos ( quality of service ). Counter started are: BBE, ES, SES, UASbidi

Maintenance. Counter started are: BBE, ES, SES, UAS near end, UAS far end.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

225 / 268

Transport State

Qos for Tandem Connection. The transport being associated is involved in a tandem connection
and Counter started are: BBE, ES, SES, UASbidi

Maintenance for Tandem Connection. The transport being associated is involved in a tandem
connection and Counter started are: BBE, ES, SES, UAS near end, UAS far end.

start/end time. If you do not specify start/end time, you can subsequently activate manually the
measure by means of the command Measure Start, otherwise the Measure will be started at the Start
Time and stopped at the Stop time.

defaults tps. You can specify:


TRUE. The PM transport is created with some default TPs automatically correlated ( for each
of them a PMTP instance is created )

One pmtp ( NAP/CAP type ) for a bidirectional transport is enough because the NE
provides the information relevant to both ends (NEAR END + FAR END).
If the path is broadcast all sink ends are monitored. (Only real ends are considered.).
Virtual NAPs or CAPs are not automatically monitored; the closest real CTP ( boundary
CTP ) will be monitored.

FALSE. Only the PM transport is created; no pmtp is created.

Monitored layer. You can specify the layer of the objects monitored by the measure:

LO low order

HO high order

LO&HO you monitor transports belonging to all the path layer network ( HO / LO )

granularity. The granularity is the monitoring frequency, i.e. the frequency of historical data counters
grouping. You can select:

24 hours . Data are grouped per day.

15 minutes. Data are grouped per quarter of hour.

Counters provided. If its value is:

TRUE, the counters belonging to granularity periods will be collected, when the measure is
activated

FALSE, the historical data counters will not be collected, even when the measure is activated.
This implies that the goal of the measure is to set Threshold Crossing Alarm profiles on the
termination points only.

Automatic Purge of the Measure (TRUE/FALSE)

Purge State of the Measure (when stopped/when terminated) when

Automatic deletion Hystorical Data (TRUE/FALSE)

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

226 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

NOT SUPPORTED

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

period HDs in DB

n.o of days of permanence

The window also contains the button Create.


c)

Click on button Create.

d)

To verify the successful creation of the measure, check on the Measure Create report window.

e)

You can now navigate from the pmDomain, in order to find the new measure icon.( from the Browser
pmDomain select Search related items : Measures. The Measure List is presented).

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 150. PM domain related items

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

227 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 151. Measure list

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

228 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.3 Transport object Correlation to the Measure

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION
A measure can monitor paths and trails, i.e. transports of type path and transports of type trail. The
transports have to be correlated to the measure.
SEQUENCE
a)

Select the Measure from the list. The Measure must be planned.

b)

Select the menu Actions: Correlate/Merge. You can further select among:

Correlate paths/trails

Correlate reports

Uncorrelate reports

Merge measures

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 152. Measure: Actions pulldown menu.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

229 / 268

Select Correlate: paths/trails. The Object Correlation window is presented. The measure is already
contained in the window . Drag and drop the paths/ trails to correlate to the window drop area.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

c)

Correlate path/trail to a measure

Figure 153. Transport correlation to a measure


d)

Click on the Create button.

e)

To verify that the correlation has been properly entered, navigate the browser in order to find the icon
of the PMtransport which has been just created. From the browser point with the mouse to the
measure icon and issue Display: Related items: PMTransports. The PMTransport icon/s are
displayed in the browser window.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

The correlation MeasureTransport can be also executed starting from the transport (path /trail)
by using the relevant popup menu.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

230 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 154. Path: Actions: Performance Measurement: Add to

Figure 155. Performance Measurement: Add to dialog box

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

231 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

DRAG

measure list
Figure 156. Correlate measure to path

SC.4:MAINTENANCE

3AL 61348 AA AA

268

232 / 268

11.4 Tps correlation to the Measure

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION
For a transport ( path or trail ) to be monitored by a measure, at least one TP termination point ( NAP,
CAP or CTP) of the transport must be monitored by the measure. This means that the measure, when
activated, will collect PM_ DATA relevant to the TPs correlated. To indicate that a measure has to monitor
a certain transport in a certain TP, the involved TP has to be correlated to the measure; the result of the
correlation procedure is that a new object is created: the pmTP. This object is created under the
pmtransport.
LIMITATIONS
In the correlation of a TP to a Measure, the following limitations apply:

A TP can be correlated to a measure ( and so a PMTP can be created under a measure ) only if the
transport the TP belongs to is already correlated to that measure

A TP can be monitored by at most 2 ( two ) activated measures at the same time, and the measures
must have different pmGranularity values.

A virtual TP cannot be monitored.

The measure state to correlate can be planned, activated or stopped.

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

Select from Browser view the ctp / nap / cap to correlate. They must belong to a transport which is
already correlated to at least one Measure.

b)

Issue Performance Monitoring: Correlate to Measure popup menu item.

c)

The tp is correlated to the Measure which is already correlated to the relevant path. By using the
Browser you can verify the tp correlation to the Measure, looking for the newly created pmTP.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

233 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 157. Performance Monitoring: Correlate to Measure


N.B.

If the transport object the TP belongs to ( e.g. a path ) is correlated to many measures and you
issue the command to correlate the tp to a Measure, the system provides a measure selection
dialog box, in order to select which measures you want to correlate the tp to.

1AA 00014 0004 (9007) A4 ALICE 04.10

In addition ,from Measure: Search related items: PMtp , the list below is displayed.

Figure 158. Measure TP list

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

234 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 159. PM tp related items

Among PM tp related items you can select the PM tp view. See figure which follows.

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

235 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 160. PM tp view

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

236 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.5 PMTP Attributes

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

If you issue a Show/Set attributes of a PMTP object, you will get the dialog box of Figure 161.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 161. PMTP Show / Set Attributes

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

237 / 268

REQUIRED SIDE. The REQUIRED SIDE is the direction of the signal to monitor. It can be set
by the 1354RM to one of the following values:

sink

source

both
Examples of assignement of the SIDE are given in paragraph 11.5.1 herebelow.

ACTIVE SIDE. It represents the actual direction monitored on equipment for the specified TP.

REQUIRED MODE. It represents the required mode to start the monitoring on the PMTPs.
The Mode (UNI or BIDI) determines the type of UAS counter to be collected by EML (SH/WX)
for a certain tp. The possible values are:

unidirectional, RM will receive the values of two counters: Near End UAS (Unavailable
seconds) and FEUAS (Far End Unavailable Seconds)

bidirectional, RM will receive the values of only one counter BIDUAS which represents
the logical OR function of the Near End UAS (Unavailable seconds) and FEUAS (Far End
Unavailable Seconds) counters.

ACTIVE MODE. It represents the actual mode monitored on equipment for the specified TP.
REQ SIDE and REQ MODE are automatically selected by RM after executing the command
Correlation of the tp to the measure . They are chosen taking into account:

the equipment type the tp belongs to

the used direction of the tp (monodirectional / bidirectional)

the type of tp ( ctp / nap / cap )

ACTIVE PM. This attribute is set to TRUE if the RM wants to have PM available on that TP, e.g.
when the measures passes from the status planned to the status activated. This attribute is
set to FALSE if the RM does not want to have PM available on that TP, e.g. in case of transport
rerouting.

sink/source REQUIRED TCA. This attribute is the name of the desired Threshold Crossing
Alarm profile on the termination point.

sink/source ACTIVE TCA. This attribute is the name of the actual Threshold Crossing Alarm
profile on the termination point.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

ACTIVE SIDE/ACTIVE MODE are not meaningful when the measure is planned.
After activating the measure it is possible to show the actual ACTIVE SIDE and the actual
ACTIVE MODE of the tp in the PMtp show/set attributes window. These attributes show the
situation present on the equipments. If the PMTP is not consistent, this means that at least
one difference between Required and Active attributes is present.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

238 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The PMTP main attributes are:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.5.1 Examples of assignement of the attribute SIDE


An example of assignement of the attribute REQUIRED SIDE for a bidirectional path is shown in
Figure 162. and Figure 163. Notice that for a bidirectional path the involved CTPs ( if correlated ), become
PMTPs marked both as sink and source. Figure 164. shows an example of assignement of the attribute
SIDE for a unidirectional path.
NEA

NEB
ctp

ctp
MAIN
sink
B&S
B&S

ctp

source

ctp
ctp
SPARE
sink

Figure 162. Side of the pmctps in a b&s connection ( signal from NEA to NEB )

NEA

NEB
ctp

ctp
MAIN

source
sink

B&S
ctp
SPARE

ctp
source

ctp

Figure 163. Side of the pmctps in a b&s connection ( signal from NEB to NEA )

ctp

ctp

nap

1AA 00014 0004 (9007) A4 ALICE 04.10

source

nap

source

sink

sink

Figure 164. Side of the ctp/nap for a unidirectional connection

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

239 / 268

11.6 Counter Report Profile Creation

Counter reports Profiles are objects which allow the automatic generation and sending of documents
( Counter Reports) containing all the data collected by the measure in a range of time (T1, T2).
The document name derives from the measure userlabel by adding the character _ ( underscore ) as
prefix and the characters _CO as suffix. As an example, the document name of the counter report
associated to the measure MEASURE1 will be _MEASURE1_CO.
First of all, the counter Report Profile instance has to be created, then it must be correlated to all the
measures that require the generation of documents; only when the measures will be activated, the
document will be periodically generated and sent.
A counter report profile can be associated to more than one measure at the same time.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

To create a counter report, from the browser, point to the PM domain and issue the command PMdom:
Create: Counter Report. Enter:

userlabel, to identify the counter report profile.

type (on file/ printer / mail). The generated reports can be stored on file, printed or sent by Email.

destination name (e.g. the filename)

frequency (15/ 1 h / 1 Day / 1 Week / 1 Month / 1 Year). This attribute means that the counter
reports for the activated measures will be generated each quarter of hour / each hour / each
day...

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

240 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 165. Counter Report Create


b)

Confirm the creation by selecting the button Create.


Now the counter report profile can be correlated to the measure. ( see paragraph 11.8 herebelow
)
While doing the correlation, measure granularity and Report window must be compatible, i.e.
the window must be a multiple of the granularity, according to the following table:

Measure granularity

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Report window

15m

15m / 1h / 1day

24h

1 day / 1 week / 1 month


/ 1 year

To verify the correlation, point at the measure and issue Display: Related items: counter Reports. See
Figure 166. and Figure 167.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

241 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 166. Counter Report profile list.

Figure 167. Counter report profiles.

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

242 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

An example of the document that will be generated by a counter report profile is shown in Figure 168.

Figure 168. Example of generated counter report

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

The environmental variable PM_FORMAT can be set by the administrator to:

PROPERTY ( format shown in Figure 168. )

CSV ( new format with improved placement of rows, columns )

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

243 / 268

11.7 Threshold Report Profiles Creation

Threshold report profiles are objects which allow the automatic generation and sending of documents
( Threshold reports).
These documents contain only the values collected by the measure which exceed some user specified
threshold values.
As in the case of the counter report profiles, first you must create the threshold report profile object; then
it can be correlated to each measure you want the threshold reports to be generated for; threshold reports
will be sent only after measure activation.
SEQUENCE
To use this function you can execute the following steps:
a)

From the pmDomain select Create: Threshold Report. Enter:

userlabel, to identify the threshold report

type (on file/ printer / mail). The threshold report can be stored on file, printed or sent by Email.

destination name (e.g. the filename)

window (15/ 1 h / 1 Day / 1 Week / 1 Month / 1 Year). This attribute means that the reports for the
activated measures will be generated each quarter of hour / each hour / each day...

granularity: 15 min. or 24 hours

The threshold values which will determine the contents of the generated documents.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

The environmental variable PM_FORMAT can be set by the administrator to:

PROPERTY ( format shown in Figure 168. )

CSV ( new format with improved placement of rows, columns )

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

244 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 169. Create: Threshold Report dialog box


To execute a correlation, Measure granularity and Threshold report granularity must be the
same. The granularity value and the Report window must be compatible, i.e. the window must
be a multiple of the granularity, according to the following table:
granularity
15m
24h

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

window
15m / 1h / 1day
1 day / 1 week / 1 month / 1 year

You can verify, by using the browser, that the Threshold Report Profile has been created. See
Figure 170.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

245 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 170. Threshold Report Profile list.

Threshold
report

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 171. Threshold report icon.


Now measure and Threshold report profiles can be correlated.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

246 / 268

11.8 Report Profile Correlation

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope is to correlate a measure to a certain report profile.
SEQUENCE
a)

From Measure list select a measure and issue Correlate/Merge:Correlate Report. A dialog box is
presented.

Figure 172. Measure correlation popup menu.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

From Browser drag and drop the report profiles ( counter and threshold ) to the Correlation dialog
box drop area and click on button Create.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

247 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 173. Correlate report

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

To verify the correlation, in the browser, from the measure issue Search: Related Items: Counter
reports/ Threshold Reports.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

248 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.9 Measure Activation, Stop and Consistency


11.9.1 Measure Activation
INTRODUCTION
Planned measures may become activated when:

their start time is reached ( this is automatically done )

the user activates manually the measure. Stopped measures can be only manually reactivated.

Only when activated, the measure realizes the goal it has been created for: data collection from Network
Elements, automatic generation and sending of counters / thresholds reports (if they have been
correlated), generation of threshold crossing alarm ( in case TCA profiles have been correlated to pmTPs
belonging to the measure).
The conditions to activate a measure are:

all correlated transports are allocated or implemented

at least one tp is correlated for each monitored transport


The activity period of a measure terminates manually ( by means of a Measure: Stop command ) or
automatically ( when the measure end time is reached ).
SEQUENCE
a)

Select from the browser the measure and issue the Specific: Start / Consistency / Stop : Start
command. The icon of the measure becomes green and the icon of the transport ( path or trail ) is
marked by an indication of the measure granularity.

granularity
After the activation of the measure, if the measure is marked as consistent, this means that the
activation command has been successfully completed for all the correlated points. This means that
the NEs have started the monitoring action and the EMLs will provide the required data.

1AA 00014 0004 (9007) A4 ALICE 04.10

If the measure is displayed as not consistent, it means that the activation command has failed for
at least one of the tps actually correlated to the measure. It is required to execute a Consistency
activity on the measure.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

249 / 268

11.9.2 Measure Stop

An activated measure may become stopped in one of the following cases:

Manually, by means of the Measure: Stop action.

Automatically, when the end time of the actually activated measure expires.

When Stopped, the measure will no longer collect data from the Network Elements and will not generate
reports or threshold crossing alarms.
After being stopped, the measure can be either Consistent or Notconsistent
A stopped measure can be manually reactivated.
SEQUENCE
a)

Select from the browser the measure and issue the Specific: Stop command. The icon of the measure
becomes lightblue.

11.9.3 Measure Consistency


INTRODUCTION
A Measure with Consistency attribute equal to Not consistent can be set consistent by means of the
Consistency action.
A measure is said consistent if all monitored TPs will provide the expected data to the measure.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

Select from the browser the measure and issue the Actions: Start/Consistency/Stop: Consistency
command.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

250 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION

11.10 Threshold Crossing Alarm (TCA) Profile creation

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION
A Threshold Crossing Alarm Profile object allows the user to have the automatic generation of alarms for
each counter type, when the counter values run out of a range of values fixed by the user himself.
When the granularity period expires the alarm reset is performed.
SEQUENCE
a)

From the browser, point with the mouse at the PM Domain and issue the command Create: TCA
Profile. Specify the high threshold value, the low threshold value and the severity for the counters
listed in the following. Maximum values are listed herebelow.

Performance Parameter

Maximum Value
(15minute period)

Maximum Value
(24hour period)

BBE, FEBBE

539,100

51,753,600

STM1 MS: BBE, FEBBE

2,159,100

207,273,600

STM4 MS: BBE, FEBBE

8,639,100

829,353,600

STM16 MS: BBE, FEBBE

34,559,100

3,317,673,600

OFS, ES, UAS, FEES, PSD, PSC 900

86,400

SES, FESES

810

78,760

PJCHigh, PJCLow

1,800,000

172,800,000

b)

Select button Create to confirm.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

At least one threshold value must be specified since default values are not present.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

251 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 174. TCA Profile creation.

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

252 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.11 Threshold Crossing Alarm (TCA) Profile Correlation to the PMTP

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE
a)

In the browser point with the mouse at the PMTP to correlate.

Figure 175. PMTP: Perform.Monitoring: Correlate to TCA


b)

Point with the mouse at the PMTP to correlate and issue the popup menu Performance Monitoring:
Correlate to TCA. The following conditions can be met:
1)

The correlation is executed if in the RM exists only one TCA profile with granularity and rate
compatible with the PMTPs to correlate.

2)

If in the RM exists more than one TCA profile with granularity and rate compatible with PMTPs
to correlate, a dialog box is presented. The operator has to select the specific TCA to correlate.

3)

Select the TCA and press OK.

4)

To verify the successful correlation, from the browser point with the mouse to the involved PMTP
and issue the Display: Main Related items: TCA Profile.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

In the QB3*ADMs all TPs with same rate and granularity must have the same TCA profile, then
if you try to associate to a certain PMTP a TCA profile different from the TCA profile already
assigned to another TP, a dialog box is presented, asking the user either to force or not the TCA
profile on that NE.
The above limitation does not apply to QB3 ( INFO MODEL ) cross connect equipment.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

253 / 268

11.12 Merging of several Measures

The merging of more measures (input measures) into another one (target measure) is a complex action
which allows to put together more monitored objects (paths, trails and their termination points) into one
measure.
SEQUENCE
a)

From the measure list select one of the measures to merge and click on button Merge. The Merge
dialog box is displayed. It contains in the upper area the previously selected measure, whose name
will be the name of the merged measure being created. See Figure 176.

Figure 176. Measure merging.

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

Drag to the drop area the measures to merge and select the button Merge measure. The measures
are merged into a new one. The dropped measures are deleted from MIB.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

254 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION

11.13 Displaying PM data

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The detailed explanation of the displaying data function can be found in document PMDS.
The collected PM data can be presented to the user by means of the Displaying PM data option.
a)

ED

Select the measure from the browser and select the functional button Show Performance Monitoring
Data.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

255 / 268

A pmNE object is automatically created the first time the user executes the correlation of a TP belonging
to a certain NE.
Starting from the PM domain, you can navigate, by means of the Display: Related Items command, to the
Monitored NEs. See figure below.

Figure 177. pmNE Show/Set attributes

1AA 00014 0004 (9007) A4 ALICE 04.10

The Show/Set attributes from this object contains the following attributes:

userlabel

NE type

last collected file15m / last collected file 24h. These attributes are used to keep a history of the file
that has been collected from RM and to ask EML for sending the not yet received files.

working status. This attribute is usually set to normal. It changes to Synchronizing when the attribute
On going activity is in one of the following states:

ED

Collect in progress ( receiving PM data from EML )

Analyze in progress ( storing PM data in the RMMIB )

Consistency in progress ( a consistency activity is being executed )

PM misalignment ( true/false ). This attribute is applicable to SENIM Network Elements, as specified


by the attribute IM type.
01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

256 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.14 The pmNE

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In addition, from browser it is possible to display the PM tp view and the PM transport view. See figures
which follow.

Figure 178. PM tp view

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

257 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 179. PM transport view

ED

01

SC.4:MAINTENANCE

3AL 61348 AA AA

268

258 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

11.15 Archive Performance Monitoring data

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION
To Archive Monitoring data means to memorize PM data on a storing support ( tape / file )
Data archived are those relevant to:

measures
PM transport
pmTPs
historical data

The result of the Archive procedure is to obtain a series of magtapes, each one storing data relevant to
a certain period.
The Archive procedure must be executed to avoid memory disk saturation, with the objective of maintain
hystorical data and transfer them to tape.
The Archive procedure is not executed automatically but must be launched by the 1354RM user.
Only archived data can be deleted from disk.
It is strongly recommended to execute Archive and Delete procedures of the PM hystorical data with the
following time periods:

one month for the 24 hours data

one week for the 15 minutes data

1AA 00014 0004 (9007) A4 ALICE 04.10

It is strongly recommended to execute Archive and Delete procedures of the PM


hystorical data upon reception of diagnostic messages alerting: Disk Full ...

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

259 / 268

11.15.1 Archive Performance Monitoring data

a)

From TMNOS view select the RM icon and issue the Actions: SMF: PMDS DB Administration item.

b)

See detailed description in document PMDS User Guide.

11.15.2 Retrieve Performance Monitoring data


INTRODUCTION
To Retrieve Monitoring data means to memorize on RM_MIB data stored on archived tape.
SEQUENCE
a)

From TMNOS view select the RM icon and issue the Actions: Performance Monitoring menu item.

b)

See detailed description in document PMDS User Guide.

11.15.3 Display Performance Monitoring data


INTRODUCTION
To display Performance Monitoring data means to display data that have been previously retrieved.
SEQUENCE
a)

From TMNOS view select the RM icon and issue the Actions: Performance Monitoring menu item.

b)

See detailed description in document PMDS User Guide.

11.15.4 Delete Monitored data


INTRODUCTION
To Delete Monitored data means to delete from RMMIB all archived data. Only historical data are deleted.

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

From TMNOS view select the RM icon and issue the Actions: Performance Monitoring menu item.

b)

See detailed description in document PMDS User Guide.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

260 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE

11.16 Archive Session

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION
The Archive session allows to display previously completed archive to tape operations and programmed
archive operations.
SEQUENCE
Starting from the PM domain, you can navigate, by means of the Display: Related Items command, to the
Archive Session. The list of the Archive sessions is presented. For each item of the list the Show/Set
attributes dialog box contains the following attributes:

user label, automatically built on from date and the granularity (e.g.: an archive performed on
15 min data from the 15/06/1998 will be given the following user label: 15 minutes counters
1998/06/15)

tip dates (from date and to date)of the data period

granularity of the archived data

the date the archive operation has been performed

the date the archived data have eventually been removed

An instance of archive session, concerning the next archive session, is automatically generated at the
end of each archive operation.
11.16.1 Attribute Setting

1AA 00014 0004 (9007) A4 ALICE 04.10

The only attribute which can be set by the user is the attribute to date, in order to anticipate or postpone
the next archive operation.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

261 / 268

11.17 Uncorrelate the transport from planned measures

This is the action opposite to the Correlate Transport to planned Measures; by uncorrelating a transport
from a planned Measure the user indicates that the termination points belonging to that transport will not
have to be monitored by the Measure.
SEQUENCE
a)

From the browser point at the transport icon and issue the Performance Monitoring: Remove from
command.

b)

Two cases are possible:


1)

More than one measure is correlated. The system provides the list of the planned measures
which are monitoring the involved transport object.The user selects the measure to uncorrelate
and clicks on the confirmation button.

2)

Only one measure is correlated. The uncorrelate action is automatically executed.

11.18 Uncorrelate the tp from planned measures


INTRODUCTION
This is the action opposite to the Correlate tp to planned Measures; by uncorrelating a tp from a planned
Measure, the user indicates that data concerning that tp are no more interesting for him: they will not be
collected when the measure will enter the activated state.

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

From the browser point at the tp icon and issue the Performance Monitoring: Uncorrelate from Measure popup menu.

b)

Two cases are possible:

ED

1)

More than one measure is correlated. The system provides the list of the planned measures
which are monitoring the involved tp object.The user selects the measure to uncorrelate and
clicks on the confirmation button.

2)

Only one measure is correlated. The uncorrelate action is automatically executed.

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

262 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION

11.19 Remove from RM menu

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION
The Remove from RM menu item allows to remove the following objects:

pm TP

PM transport

Measure

The object containment tree is shown in Figure 180. , i.e. if you remove an object, all the contained objects
are automatically removed.
N.B.

The Remove from RM action applies only to stopped or planned measures.

MEASURE

REPORT
COUNTER/
THRESHOLD
PM TRANSPORT

PMTP

HISTORICAL
DATA

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 180. Object containment tree

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

263 / 268

11.20 Uncorrelate the counter/threshold report profile from the measure

This is the action opposite to the Correlate Counter/threshold report to planned Measures, by
uncorrelating a Counter/threshold report profile from a planned Measure.

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

From the browser, point at the measure icon and issue the Performance Monitoring: Uncorrelate
from Measure command. The list of the associated reports is presented.

b)

Select the report to uncorrelate and click on OK.

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

264 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INTRODUCTION

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

12 LOGGER
The event logger displays the current events and the list of the events which have been stored in the log
file.
The Event Log dialog box is shown in Figure 181.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 181. Event Log filter

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

265 / 268

This box allows the user to select the following parameters:


Class Type. The operator can choose to display events relative to:

all classes (wildcard)


path
emlDomain
ne
port
physicalConn
ntw
sbn
et
node
lc
trail
connInTopol
nap

Event Type. The operator can select among the following types:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

all types (wildcard)


attributeValueChange
stateChange
objectCreation
objectDeletion

Log Type. Two options are available:

Immediate. The report window will work as a virtual printer ( FIFO ), displaying messages in real
time.
From Log File. The Report will contain data extracted from the historical event log file of HPOV.

Start Time/End Time, to be specified for searching from Log File.

Object_Instance. From Browser drag the object(s) whose event log is required and drop into this
area. A wrongly dropped object should be deleted by means of the Delete popup option. The
presence of objects in this area automatically makes not meaningfull the content of the above
described ClassType box.

1AA 00014 0004 (9007) A4 ALICE 04.10

The window contains four toolbuttons;

Cancel, to cancel the operation and close the window.

Apply, to start the event log process.

Cancel Get, to abort the data retrieval.

Users info

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

266 / 268

EVENT LOG

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The Event Log dialog box is shown in Figure 182.


The pulldown menu line contains items File and Actions.

Item File contains the following options:

Open, to start a read operation on an ASCII file. This file is selected by the user by means of
a file filter.

Save as... to save on file the content of the Event Log.

Print all to print the Event Log content on the default printer.

Print Selected to print part of the Event Log content on the default printer.

Item Actions contains the only option Font.

still closed.
An example of event log is shown in Figure 182.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 182. Event Log

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

267 / 268

Lockout of Working channels ring (LWR), 113


Lockout of Working channels span , 113
Logger, 265

A
Alarm Propagation, 29
Alarms, 13
ASAP, 20

M
MAINTENANCE, 51
Measure, 225
MSSPRING request (trigger), 113
MStrail, 59

C
CONSISTENCY, 147
Consistency audit, 147
Consistency download, 148

N
E
NE, 77
Node, 87
NODE CONDITION, 127
NPE Ring, 113

EML, 75

F
fault localization, 51
Forced Switch / Span, 140
Forced Switch Ring, 137

P
Path, 53, 67
Physical Connection, 80
Physical connection, 55
PM, 223
Probable Causes, 13
protocol message, 113
protocol reply, 113
protocol request, 113

H
HOtrail, 56

I
Inhibition chain, 132
Intermediate nodes, 113

L
Lockout , 132
Lockout of Protection channels span, 113

Scenarios, 134
Serving nodes, 113
signal Fail, 139
Subnetwork, 84

1AA 00014 0004 (9007) A4 ALICE 04.10

END OF DOCUMENT

ED

01

SC.4:MAINTENANCE
3AL 61348 AA AA
268

268 / 268

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

INDEX

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM REL.7. 2 OPERATORS HANDBOOK

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5
5
5

2 FUNCTIONALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Introduction to Functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Supported EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Supported NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7
7
8
8

3 ROUTING ALGORITHM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Routing Algorithm General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Point to point paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Unprotected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 SNCP Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 D & C Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 Protection in Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Broadcast path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Routing inside rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 NPA routing attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Service route in D&C paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Interworking scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9
9
9
9
9
10
11
11
11
12
16
16

4 ALLOCATION OF RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Choice of link connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Choice of link connections in paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Choice of link connections in HO trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21
21
21
21

5 NE CONSTRAINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23

6 NETWORK PROTECTION EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


6.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Why Transoceanic MSSPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Transoceanic MS Spring Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25
25
26
26

01

050207

ED

DATE

CHANGE NOTE

M.RAGNI ITAVE

V.PORRO ITAVE

APPRAISAL AUTHORITY

ORIGINATOR

1354RM REL.7.2
OPERATORS HANDBOOK

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

1 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

26
29
32
36
38
39
39
40
41
42
42
43
45
45
45
47
48
49
49
50
51
52
53
53
53
63
63
63

7 RM OBJECTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 OTN WDM model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Integrated approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

65
69
73
73

8 OBJECT NAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

75

9 ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

77

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

2 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.2.1 Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


6.2.2 Span protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3 Ring protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4 Multiple protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Broadcast Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2 Failure affecting all drop points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.3 Failure affecting some drop points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.4 Broadcast connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Path restoring algorythm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.1 Ring path restoring algorythm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.2 Span path restoring algorythm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Path with Drop & Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.2 Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.3 Secondary circuit on HP channels: fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.4 Secondary circuit on LP channels: fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.5 Failure cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.6 Span failure on span adjacent Service Selector of primary node . . . . . . . . . . . . . . . . . . .
6.5.7 Primary node failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.8 Ring failure on span included between primary and termination nodes (HP case) . . . .
6.5.9 Ring failure on span included between primary and termination nodes (LP case) . . . .
6.6 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6.1 General description of MSSPRING protection scheme . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6.2 MS shared protection rings Transoceanic application . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7 4F MSSpring NPE Holdoff time management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7.2 Visualization of MSTrails on 4f MSSPRing Protection Block view . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LIST OF FIGURES AND TABLES


FIGURES
Figure 1. The 1354RM in the SDH management hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Protected path routes ( automatic algorithm ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Collapsed dual node interconnection between two rings . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Stacked rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. NPA routing attributes effects in stacked rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. NPA Main & Spare Factor effects in stacked SNCP rings . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Routing in stacked MSSprings primary and secondary nodes not adjacent . . . . . . . .
Figure 8. Routing in stacked MSSprings primary and secondary nodes adjacent . . . . . . . . . . .
Figure 9. Collapsed dual node D&C for SNCP ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Collapsed single node D&C for SNCP ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Collapsed dual node D&C for SNCP ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Collapsed dual node D&C interworking for 2f MSSpring configuration 1 . . . . . . . . .
Figure 13. Collapsed dual node D&C interworking for 2f MSSpring configuration 2 . . . . . . . . .
Figure 14. Paths in stacked MSSPrings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. 4 Fibre Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Span switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. 4F MSSPRing connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. NonTransoceanic ring protection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Transoceanic ring protection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Broadcast connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Failure affecting all drop nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Failure included between drop nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. D&C protection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Secondary circuit on LP channels preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. D&C protection management: span failure on link adjacent Service Selector . . . . . . . . .
Figure 26. D&C protection management: failure on primary node . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. D&C protection management: ring failure on link between P and T nodes (HP case) . .
Figure 28. D&C protection management: ring failure on link between P and T nodes (LP case) . .
Figure 29. Broadcast path (not protected ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Unidirectional protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Routing in working ( RIW ): bidirectional path, outgoing direction . . . . . . . . . . . . . . . . . . .
Figure 32. Routing in Protection ( RIP ): bidirectional path, outgoing direction . . . . . . . . . . . . . . . . .
Figure 33. Routing in working ( RIW ): bidirectional path, incoming direction . . . . . . . . . . . . . . . . . . .
Figure 34. Routing in Protection: bidirectional path, incoming direction . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Broadcast path: i/c span fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Broadcast path: middle span fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Broadcast path: last node fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Bidir. Path, 1664SM, RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Bidir path, 1670SM, RIW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Schematic representation of the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Trail and link connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Objects involved in the structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. WDM network managed model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. WDM model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. SDHWDM interconnection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

7
10
12
12
13
14
15
16
17
17
18
18
19
19
26
29
32
33
34
38
39
40
46
48
49
50
51
52
54
54
55
55
56
56
58
59
59
61
62
67
67
68
69
70
72

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

3 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

4 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1 INTRODUCTION
1.1 Purpose of the document
This section describes the main features of the product and provides a general overview of the system
architecture, the managed equipments and the different functionalities provided by the Regional Manager.

1.2 Target audience


The Introduction Manual is intended for all Regional Manager users.

1.3 Document structure


This section covers the following topics:

ED

Transport Management

Concatenated AU4s

NPE 4Fiber

DB objects

Object names

Acronyms and Abbreviations

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

5 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

6 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2 FUNCTIONALITIES
2.1 Introduction to Functionalities
The 1354RM is a network management system that has been designed to handle SDH regional networks.
The aim of this chapter is to give an overview of the 1354RM. (See Figure 1. ). The 1354RM covers the
1st NML level ( Network Management Layer). Figure 1. shows all the functional layers and the
communication protocols.

VPN

NML

Client

http

RMI

Web

VPN
Server Server

1354NN

M
ISN
Qnn
NML

1354RM

QB3

QB3*
EML

QB3*
QB3

NE

M: MANAGER
A: AGENT

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 1. The 1354RM in the SDH management hierarchy

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

7 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

The EML supported are:

1353NM

1353WX

2.1.2 Supported NEs

Please refer to the current External Release Notes

ED

01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.1.1 Supported EMLs

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

8 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3 ROUTING ALGORITHM
3.1 Routing Algorithm General
The routing algorithm acts during the allocation of path or trail, i.e. performs the operation that allocates
resources (link connections and CTPs) to the given path/trail and defines the cross connections (named
connections in topology)
Paths can be bidirectional pointtopoint, unidirectional pointtopoint and unidirectional broadcast. HO
trails are always bidirectional pointtopoint.
paths and trails can be:
not protected: a single route (main) is defined between the end points
protected SNCP: two routes (main and spare) are defined between the end points, in order to protect the
path against link faults and node faults;
protected D&C SNCP: in addition to main and spare, one or more service route are inserted in the path,
in order to protect it against multiple faults; (available only for point_to_point paths and trails)
protected in rings: the protection (spare) is added only inside rings
The basic algorithm has the objective of finding the minimum cost route between the end points (NAPs,
CAPs ).
The basic algorithm used is a particular customization of the Dijkstra Algorithm.

3.2 Point to point paths


3.2.1 Unprotected path
This is the simplest case. The algorithm computes a single lowest cost route from the source point to the
sink one, called main route.
3.2.2 SNCP Protection
A path is called protected when supplementary arcs or connections, called spare, are allocated in addition
to the main one to provide an alternative way in case there are one or more failures along the main route.
A SNCP protected path has two routes, main and spare, from source to sink vertex, sharing as less as
possible common resources. The algorithm therefore tries to minimize the overlaps between main and
spare . As a result, an endtoend protection is obtained whenever possible.
The algorithm used is slightly different whether the path allocation is completely automatic or not.
SEMIAUTOMATIC VERSION

1AA 00014 0004 (9007) A4 ALICE 04.10

It occurs when at least one path constraint has been entered by the user
The algorithm proceeds in the following way.
1.First, the lowestcost main route is computed.
2.Then the spare route is computed with as less as possible overlaps with the main route.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

9 / 80

In this case the algorithm would find the path with the lowest cost main route, not the lowest sum of main
and spare route costs,costs. This is acceptable for a semiautomatic path allocation, since the user has
forced the routing to be not necessarily the best one.
FULLY AUTOMATIC VERSION
The Dijkstra Algorithm has been customized in order to minimize the sum of main and spare route costs,
with the minimum number of overlapped resources.

Figure 2. Protected path routes ( automatic algorithm )

3.2.3 D & C Protection


For a D&C protected path the algorithm computes a SNCP protected path with additional routes, called
services, obtained connecting, for each ring and for each direction of the path, the ring exit nodes of the
main and spare route through D&C connections in order to protect the traffic in that direction against multiple failures.
Notes:
If the path is unidirectional each ring can have at most one service, if it is bidirectional two.
The service can exist if, in the direction to protect, the main and the spare route exit from different nodes.
The algorithm proceeds in the following way:
1. First, the lowestcost main route is computed.
2. Then the spare route is computed with as less as possible overlaps with the main route (see 4.2.2).
3. Finally, it computes the service routes, with the following rules:
Allocation/Add Service (without end points). Services are allocated in rings crossed by both main and
spare routes protecting the existing traffic.

1AA 00014 0004 (9007) A4 ALICE 04.10

Add Service between specific end points. The user can specify the connections involved in the service
( without topological restrictions) choosing the direction to protect

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

10 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Notes

3.2.4 Protection in Rings

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

A path protected in ring has a protection just for the SNCP rings it crosses .

3.3 Broadcast path


If the path is not protected, Dijkstra is applied once for each leg.
If the path is protected and at least one constraint has been setup, the semiautomatic algorithm is applied
once per each leg.
If the path is protected, without constraints the fully automatic algorithm is applied once for each leg.
In general, different legs can share some arcs. It is also possible to use an arc in the main route of one
leg and in the spare route of another leg.
Legs are not routed independently: the base cost of arcs already used in a previous leg are decreased
by a configurable factor: in order to share as many as possible arcs between legs, by default the cost is
reduced to 20% of the original value if the arc is used with the same resource type, to 40% of the original
value if used with different resource type,
Inter legs checks are executed in order to avoid that 2 connections of different legs in the same node
result either in a connection not supported by the NE, or in a switch, whose main and spare TPs belong
to different legs.

3.4 Routing inside rings


Basic algorithm
This section describes the behaviour of the routing algorithm inside rings.

1AA 00014 0004 (9007) A4 ALICE 04.10

1354RM manages the possibility to insert a node in more than one ring, as shown in the following two pictures.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

11 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 3. Collapsed dual node interconnection between two rings

Figure 4. Stacked rings

1AA 00014 0004 (9007) A4 ALICE 04.10

In these cases, the routing algorithm is not based on minimum cost criteria, but it tries to avoid unnecessary
changes of rings.
3.4.1 NPA routing attributes
Two attributes are defined in NPA object:

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

12 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

NPA Usage Cost: it is an extra cost used in the routing algorithm for the usage of the NPA. It ranges from
0 to 100, like the cost of physical connection;
NPA Reduction Cost Factor: the cost of physical connections inside a NPA is reduced by this factor in
the routing algorithm.
If equals 0, it has no effect. If equals 100, the cost becomes 0.
This reduction is introduced in order to compensate the cost for the usage of the ring.
By default, the NPA usage cost is 20 (like the default cost of a physical connection); the default NPA Reduction Cost Factor is 20%. The user is allowed to modify these values. In particular, putting both values to
0 results in a minimum cost routing.
Example: in Figure 3 below, using default values a path between N2 and N5 is routed through N3 and
N4 using only ring 2 (continuous line), even if the minimum cost route, taking into account only the physical
connection costs, bypasses N3 but uses both ring 1 and ring 2 (dashed line).

Figure 5. NPA routing attributes effects in stacked rings


In fact, the cost of the chosen route (N2 N3 N4 N5) for RM routing algorithm is 68: 3*16 (cost of three
links) + 20 (access to ring 2); while the cost of the other route (N2 N4 N5) for RM routing algorithm is
72: 2*16 (cost of two links) + 40 (access to ring 1 and ring 2).
Two attributes are defined in path and trail objects, useful for the routing of spare:
NPA Main & Spare Factor: it is meaningful for SNCP or D&C SNCP paths/trails. During spare calculation,
the NPA Usage Cost, for rings already used by the main route, is reduced by this factor.
If equals 0, it has no effect, i.e. the NPA Usage Cost is not reduced by the routing algorithm.

1AA 00014 0004 (9007) A4 ALICE 04.10

If equals 100, the NPA Usage Cost becomes 0 in the routing algorithm.
By default, the NPA Main & Spare Factor is 100%.
MSSPring D&C Factor: it is meaningful for SNCP or D&C SNCP paths/trails traversing MSSPrings. It
can be used to encourage, during spare calculation, the usage of D&C inside MSSPrings.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

13 / 80

If equals 0, it has no effect.

As bigger is set the NPA Main & Spare Factor, as more main and spare are attracted to use the same rings,
resulting in a more ordered routing. This can be particularly useful for D&C paths/trails that use SNCP
rings.
Examples:
in Figure 6. below (case A), using default values, the main route of a path between N2 and N6 is routed
through N4 using only ring 1. The spare is routed through N1, N8 and N7 still using only SNCP ring 1 (continuous line), while the routing obtained disabling NPA Main & Spare Factor bypasses N8 but uses SNCP
ring 2 (dashed line), that wasnt used in the main route.
In fact, the cost of the chosen spare route (N2 N1 N8 N7 N6) for RM routing algorithm is 64: 4*16
(cost of four links), without any additional NPA usage cost; while the cost of the other route (N2 N1 N7
N6) for RM routing algorithm is 68: 3*16 (cost of three links) + 20 (access to ring 2).
not in all cases, the NPA Main & Spare Factor avoids the usage of new rings not used in the main route.
In Figure 6. below (case B), using default values, the main route of a path between N2 and N3 is routed
using only ring 2. The spare is routed through N4 (continuous line) using both SNCP ring 1 and ring 2, that
is the same route obtained disabling NPA Main & Spare Factor.
In fact, the cost of the chosen spare route (N2 N4 N3) for RM routing algorithm is 52: 2*16 (cost of two
links), + 20 (access to ring 1); while the cost of the route that uses only ring 2 (dashed line) is 96: 6*16 (cost
of six links), without any additional NPA usage cost.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 6. NPA Main & Spare Factor effects in stacked SNCP rings
As bigger is the MSSPring D&C Factor, as more the routing algorithm should automatically route main
and spare in order to create D&CIC connections compared to other possible routes. When the cost of
the route with D&CIC is too high, other solutions are preferred.
Examples:

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

14 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

By default, the MSSPring D&C Factor is 80%.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In Figure 7. below, a MSSpring is crossed by a protected path in such a way that there are a lot of NEs
between primary and secondary nodes. In this case, using default MSSPring D&C Factor, the spare route
of the path is the one represented by the red continuous line. Increasing the value of the MSSPring D&C
Factor, the dashed route can be preferred, resulting in two D&C connections in nodes N1 and N2.

Figure 7. Routing in stacked MSSprings primary and secondary nodes not adjacent

1AA 00014 0004 (9007) A4 ALICE 04.10

2. In Figure 6 below, primary and secondary nodes in the MSSpring are adjacent. In this case, using
the default value of MSSPring D&C Factor, the spare route of the path is the red continuous line with
D&CIC connection in nodes N1 and N2. Reducing the value of the MSSPring D&C Factor, the dashed
route can be preferred.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

15 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 8. Routing in stacked MSSprings primary and secondary nodes adjacent

3.4.2 Service route in D&C paths


For service routes it is possible to distinguish three different situations:
Allocation of D&C protected paths: service routes are calculated in the rings (SNCP and 2F MSSPrings
for LO paths) traversed by both main and spare. For details see section 4.2.3. The NPA usage cost is not
taken into account for rings traversed by both main and spare; all the other rings cannot be used in the
service route.
Add service to a previous SNCP protected path: the algorithm follows the same principles used for allocation.
Add service between specific TPs of a path: service routes may connect the main with the spare branch
without topological restrictions. In this new scenario it is possible, for service routes, to traverse rings used
by both main and spare, only by the main, only by the spare or previously unused rings. As consequence,
the NPA usage cost taken into account by the routing algorithm is:
Equal to 0 for rings used by both main and spare
Half the value of the NPA usage cost for rings used only by the main/spare
Not modified for rings not yet used by main and spare
These rules advantage the use of rings already used by main and spare respect to others, but doesnt
prevent the usage of any ring.

1AA 00014 0004 (9007) A4 ALICE 04.10

3.4.3 Interworking scenarios


3.4.3.1 SNCP ring interworking
For collapsed dual node D&C interworking, it is not necessary to define a specific meshed ET including
N3 and N4.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

16 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 9. Collapsed dual node D&C for SNCP ring

Figure 10. Collapsed single node D&C for SNCP ring


A path can cross a node that is part of more than two rings; see N4 in the example shown in figure below.
As usual, the service routes are added only in the rings used by both main and spare of the path (N3N4
for ring 1, N4N5 for ring 3).

1AA 00014 0004 (9007) A4 ALICE 04.10

As a result, two classic D&C connections are created in N3 and N5; one dual node D&C is created in N4.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

17 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 11. Collapsed dual node D&C for SNCP ring


3.4.3.2 Collapsed dual node D&C interworking for 2f MSSpring
Depending on the placement of the two end nodes, the two following routes can be obtained.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 12. Collapsed dual node D&C interworking for 2f MSSpring configuration 1

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

18 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 13. Collapsed dual node D&C interworking for 2f MSSpring configuration 2
In case of stacked MSSPrings, paths ending in different rings can be routed differently, depending on the
number of nodes between the end nodes. Note that SNCP connections, if supported by NEs, can be
created by the routing algorithm also inside MSSprings (Figure below case A).

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 14. Paths in stacked MSSPrings

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

19 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

20 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4 ALLOCATION OF RESOURCES
Here it is described the algorithm used by RM in order to choose the network resources (link connections)
in the allocation of paths and HO trails.

4.1 Choice of link connections


The algorithm used for the choice of the link connections is different for paths and HO trails.

4.2 Choice of link connections in paths


The algorithm used for the choice of the link connections in the paths (both HO and LO) is the following.

first the routing algorithm chooses the routing links of the path;

then, for each routing link of the path, it chooses the first link connection(s) free, i.e. the one(s) with
the lowest time slot (e.g. 01/1/1.1), with the following exceptions:

inside a MSSP Ring (both two and four fibers), the time slot interchange is not possible at HO: the
algorithm chooses the first time slot that is free in all the routing links of the ring used by the HO path;

in case of NE constraint (the protected connections in all QB3* ADMs must have the same time slot
at west and east aggregate ports), the algorithm chooses the first time slot that is free in both the routing
links adjacent to that NE.
4.2.1 Choice of link connections in HO trails
The algorithm used for the choice of the link connections in the HO trails is the following.

first the routing algorithm chooses the routing links of the trail;

1AA 00014 0004 (9007) A4 ALICE 04.10

then, in each ring crossed by the HO trail, the algorithm chooses the first time slot that is free in all
the routing links used by the HO trail.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

21 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

22 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

5 NE CONSTRAINTS

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The routing algorithm is aware about node connectivity restrictions.


The equipment doesnt support some type of connection (e.g. oldgeneration ADMs can perform
Bridge&Switch only between one tributary port and two aggregate ports)
Even if the equipment supports it, in that moment it is not able to implement it (e.g. 1661smc and 1651smc
can provide some HO connections up to a fixed limit)

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

23 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

24 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6 NETWORK PROTECTION EQUIPMENT


6.1 Architecture
Transoceanic MSSPRing is constituted by a four fibre MS shared protection ring (4F MSSPRing)
managing a different MSSPRing protocol respect to the standard one.
4F MSSPRing is a ring of nodes connected with four fibres for each span of the ring.
Working and protection channels are carried over different fibres: two fibres (one per direction) carry the
working channels; the other two (one per direction), carry the protection channels.
The working channels carry the high priority (HP) traffic, while the protection channels normally are used
to carry the low priority (LP) traffic when they are not used to restore HP traffic.
In case of protection switch, HP traffic accesses protection channels causing LP traffic to be removed from
the protection channels.
4F MSSPRing supports ring switching and span switching.
On 4F MSSPRing these two protection mechanisms cannot exist simultaneously because ring switching
occupies the overall portion of the protection channels of all the spans of the ring.
On Transoceanic 4F MSSPRing these two protection mechanisms could also coexist because ring
switching occupies only a portion of the protection channels of all the spans of the ring; but the standards
establish that during the occurrence of both ring and span failure events the performed ring switching is
preempted to allow a complete span switching operation restoring all the HP paths of the failed span.
In this way span switching mechanism is priority respect to ring switching mechanism.
Multiple span switchings can coexist on the ring since only the protection channels along one span are
used for each span switching.
The following figure shows an example of 4F MSSPRing ring.
Since the protection acts on all ring nodes, information are exchanged among the nodes.
For this aim ring APS protocol is used, carried on bytes K1 and K2 (add on K3 for proprietary transoceanic
application) inside MSOH.
The informations carried by the ring APS protocol are:

type of protection operation performed;


node status;
source node identifier;
destination node identifier;
travelling path (short or long).

In 4F MSSPRing APS protocol is sent on protection fibres.


A node on the ring may insert HP or LP traffic into channels in either direction, drop HP or LP traffic from
either direction, or passthrough channels to allow other nodes to be connected.

1AA 00014 0004 (9007) A4 ALICE 04.10

Alcatel implementation foresees rings made up by more than 16 nodes (64 maximum).

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

25 / 80

Node 1

LP Traffic

LP Traffic

HP Traffic

Node 3

Node 4

Agg East Main

Node 2

HP Traffic

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Agg East Spare

Agg West Main

Figure 15. 4 Fibre Ring

6.1.1 Why Transoceanic MSSPRing


Transoceanic MSSPRing is a different type of MS_SPRing protocol in order to avoid triple ocean crossing.

6.2 Transoceanic MS Spring Management


Transoceanic ring nodes have different behaviour in MS_SPRing protocol respect to nonTransoceanic
application.
6.2.1 Fault management
Transoceanic 4F MSSPRing is able to protect HP traffic carried over the working fibres transmitting in
opposite directions.
Failures in the network may be:

fibre optic link failures (fibre cut or damage, connector failure);

HW failures (optoelectronic component failures);

1AA 00014 0004 (9007) A4 ALICE 04.10

6.2.1.1 node failures (equipment failure, natural accidents, power loss, software bugs, procedural incorrectness).
For each type of failures the adjacent node detects one of the following alarms:
a ) LOS
b ) LOF

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

26 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

c)
d)
e)

MSAIS
MSEXBER
SD

Alarms from a) to d) are classified as Signal Failure (SF); alarm e) is classified as Signal Degrade
(SD).
SF alarms have higher priority than SD alarm. SF condition reflects traffic affected by defect, while SD
condition reflects traffic with signal degradations due to bit errors.
In 4F MSSPRing these alarms can be collected from working and protection line separately or the same
time according to failure type.
A fault condition present only on the working link determines a span protection: HP traffic is restored by
switching to the protection channels of the same span.
A fault condition present on both working and protection links determines a ring protection: the HP traffic
travelling the failed span is restored by switching it to the protection channels travelling in the opposite
direction (away from the failure).
There are two types of span and ring protection:

SF reason;

SD reason.
The activated protection mechanism results from the combination of the following conditions:

SF span protection

only working link failed on the span;

SD span protection

only working link degraded on the span;

SF ring protection

working link failed and protection link failed on the same span;

working link failed and protection link degraded on the same span;

working link degraded and protection link failed on the same span.

SD ring protection

working link degraded and protection link degraded on the same span.
In the cases of only protection link failed or only protection link degraded on a span no protection mechanism is activated and LP traffic carried by the span is lost.
Considering a span the failure may be classified as:

unidirectional if the failure affects only one transmission direction (the alarm condition is detected
only on the node interfacing the span);

bidirectional if the failure affects both transmission direction (the alarm condition is detected on both
nodes interfacing the span).
When SF or SD condition disappear, HP traffic is restored on the working channels and the preceding
preempted LP traffic is restored on the protection channels.
WTR time is used to prevent frequent oscillations between protection and working channels due to intermittent fault.

1AA 00014 0004 (9007) A4 ALICE 04.10

6.2.1.2 Protection switching protocol


Transoceanic 4F MSSPRing makes use of a bidirectional protection switching architecture.
This means that, if the failure is unidirectional, both traffic directions are switched to protection (the affected
direction and the unaffected direction).

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

27 / 80

When a node determines that a switch is required (detected alarm or command from OS/CT), it originates
the appropriate bridge request via K bytes in both directions: short path and long path.
The destination request are the adjacent nodes.
In case of unidirectional failure, signalling on the short path permits faster switch execution because
across the failed span the node will typically receive the short path bridge request much sooner than the
long path bridge request.
When a not destination node (intermediate node) receives a bridge request, it goes to PassThrough state
transmitting the same received K bytes on the other direction. In this way source and destination nodes
can mantain direct K byte communication on the long path.
In case of bidirectional failure, such as a cable cut, the destination node will have detected the similar failure itself. It then generates a bridge request in the opposite direction around the ring.

1AA 00014 0004 (9007) A4 ALICE 04.10

The main operations performed during switching are:

bridge;

switch.
In case of SF protection the protocol foresees that on a node these operations may be performed together;
in case of SD protection these operations are always distinct.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

28 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

APS switching sequences follow ITU Rec. G.841 for 4F MS_SPRing protocol for transoceanic application. (Annex A)

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.2.2 Span protection


Span switching consists in using the protection fibres of a span to carry the working channels when failures
affect only the working fibres.
An example of span switching is shown in the figure below. In span protection the operation is similar to
1:1 protected linear system: traffic is switched in both transmit and receive direction.
For every connection through the failed span, bridge operation on transmission side are executed before
switch operation on receiving side.
The corresponding LP connections crossing the span are preeempted. LP preemption consists in a
squelching operation, by inserting AUAIS on protection paths. If the LP channel coming from the failed
span is dropped by the node, AIS is forced to the tributary side; if LP channel is passedthrough by the
node, AIS is forced on the opposite aggregate side of the node.

Node 1

Node 4

Node 2

Node 3

Tx block

Working channel
Protection channel

Rx block

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 16. Span switching


The remaining portion of the protection channels is available for other span protection switches. Since multiple span switches can coexist on the ring, it is preferable to execute span protection when possible.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

29 / 80

In Transoceanic application the span protection does not involve all channels, but it is performed on a
AU4 basis in order to save those low priority time slots not required for the high priority traffic restore.
This operation requires the acknowledge of the time slots assignment in transmit and receive directions
for high and low priority traffic over the span.
6.2.2.1 Span switching mechanism
The sequences of the protection algorythm are the same used for the terrestrial rings.
A span protection switching evolves according to the following steps:
a)

a node (or both nodes if the failure is bidirectional) detects SF or SD condition only from working
fibre.
It enters in Switching state performing the following actions:

send span bridge request in both directions (SFS code or SDS code);

AIS forcing on all the time slots received from the working failed fibre (only for SF condition);

individuation of the protection channels to preempt to restore HP traffic.

AIS forcing on the received low priority traffic channels to preempt (dropped or transmitted in
the opposite direction respect the failure).

b)

the other node interfacing the failed span receives a bridge request on the short path from its adjacent
node.
It enters in Switching state performing the following actions:
If the failure is unidirectional

send span bridge request on the long path and a Reverse Request with bridge status on the
short path;

individuation of the protection channels to preempt in order to restore HP traffic.

AIS forcing on the received LP traffic channels to preempt (dropped or transmitted in the opposite direction);
Either in unidirectional and bidirectional case

span bridge (the node bridges only the working channels carrried on the failed span).

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

the node interfacing the failed span, upon reception of the bridge acknowledgement on the short path
from adjacent node, executes:

span bridge (if even it is not executed);

span switch (the node switches only the protection channels carrying the restored high priority
traffic);

signal bridge & switch status on K bytes.

d)

the other node, upon reception of the bridge & switch acknowledgement on the short path from adjacent node, executes:

span switch (the node switches only the protection channels carrying the restored high priority
traffic);

signal bridge & switch status on K bytes.

e)

all the other ring intermediate nodes, on the reception of the first long path bridge request received
from one of the node interfacing the failed span, enter in kbyte PassThrough state.
In this state the node only transmits the k bytes received from the opposite side and does not perform
any action on the own working and protection channels.

So all these nodes know the presence of a span switching, even if they are not directly involved.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

30 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In case of unidirectional failure also the other protection fibre of the same span is used to carry the high
priority traffic on the other direction.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.2.2.2 Span restoring mechanism


In the unidirectional case the node which detected the failure condition receives a Reverse Request on
the short path; in bidirectional case both nodes which detected the failure receive a bridge request with
RDI status.
An unidirectional span protection restoring starts according to the following steps:
a)

a node detects clearing of SF or SD condition.


It enters in WaitToRestore state performing the following actions:

AIS removing on all the time slots received from the working fibre (only for clearing of SF condition);

signal the new state (WTR code) in both directions;

remains in Wait to restore for the configured WTR time.

A bidirectional span protection restoring starts according to the following steps:


a)

a node detects clearing of SF or SD condition.


The node sees a SF condition on the span that preempts WTR state. It performs:

AIS removing on all the time slots received from the working fibre (only for clearing of SF condition);

sending the Reverse Request on the short path.

b)

the other node detects clearing of SF or SD condition.


It may enter in WaitToRestore state performing the following actions:

AIS removing on all the time slots received from the working fibre (only for clearing of SF condition);

signal the new state (WTR code) in both directions;

remains in Wait to restore for the configured WTR time.

1AA 00014 0004 (9007) A4 ALICE 04.10

Then a span protection restoring continues according to the following steps:


a)

the adjacent node, upon reception of the WTR bridge request on the short path:

sends out Reverse Request on the short path and WTR on the long path.

b)

when WTR interval expires, the node performs the following actions:

drop span switch restoring the high priority traffic received on working channels (AIS on these
flows is nomore present);

send No Request code on both directions.

c)

the adjacent node, upon reception of the No Request code on the short path, performs the following
actions:

drop span switch restoring the high priority traffic on the other direction;

drop bridge switch (reconnecting on the released protection channels the low priority channels);

sources the Idle status.

d)

the initial failed node, upon reception of the Idle status on the short path, performs:

drop its bridge switch (reconnecting on the released protection channels the low priority channels);

sources the Idle status.

e)

Both nodes, upon reception of the Idle status on the short path, perform:

AIS removing on the preempted low priority channels (both drop and passthrough sides). Now
the low priority traffic is restored.

f)

All the other nodes, upon reception of the Idle code from both sides, return in the Idle state.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

31 / 80

6.2.3 Ring protection

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Nodes belonging to a Transoceanic ring have a different behaviour respect to a nonTransoceanic ring.
The below figure shows an example of ring connection.

HP traffic
LP traffic
Connection under evaluation
it is carried via NE 5632 in HP channels

Figure 17. 4F MSSPRing connection management


6.2.3.1 NonTransoceanic ring
Ring switching consists in replacing the failed span with the protection fibres of all the other nodes of the
ring away from the failure.
Since the protection channels along each span (except the failed span) are used for recovery, the protection capacity is totally used and effectively shared by all spans.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure which follows shows a ring protection switching involved in a nonTransoceanic ring.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

32 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

HP traffic
LP traffic
The connection protection is carried via:
NE 56 on HP channels,
NE 654123 on LP channels,
NE 32 on HP channels.

Figure 18. NonTransoceanic ring protection management

During a ring switch, the node adjacent the failure bridges the high priority traffic that were entering on the
failed span onto the protection fibre transmitting in the opposite direction (loopback action). This bridged
traffic travels the long way around the ring on the protection fibres to the other node interfacing the failure.
Here it is switched back onto the working channels (loopback action) rebulding in this way the interrupted
path from the source node to the destination node.
In the other direction the high priority traffic is bridged and switched in the same manner.
Intermediate nodes are not involved in switching operations.

1AA 00014 0004 (9007) A4 ALICE 04.10

6.2.3.2 Transoceanic ring


Ring switching consists in rerouting all affected paths in the opposite direction toward the destination
nodes.
These paths are bridged at their source nodes to the corresponding protection channels that travel away
from the failure (corresponding means the same time slot occupied on the working line). When the affected
flows reach their final destination nodes they are switched to their original drop points.
The following figure shows a ring protection switching involved in a Transoceanic ring.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

33 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

HP traffic
OCEAN
LP traffic
The connection protection is carried via:
NE 5412 on LP channels

Figure 19. Transoceanic ring protection management


This protection mechanism allows to mantain part of the low priority traffic when a fault occurs (differently
from normal MSSPRing protocol). During ring switching HP and LP traffic on the ring is analyzed and,
according to the fault localization, some LP traffic must be cancelled to restore the affected HP traffic, but
the remaining part of it can be mantained.
The intermediate nodes are involved in switching operations as the nodes interfacing the failure.
The main differences between the two ring protection mechanisms can be so described:

in transoceanic application only the protection channels carrying the working channels affected by
the failure are managed; in nontransoceanic application all span protection channels are managed.

in transoceanic application also intermediate nodes are involved in bridge and switch operations.

1AA 00014 0004 (9007) A4 ALICE 04.10

After the fault event between Node 6 and Node 3, the LP3 Connection is lost (the AU4 is used to carry
the HP Traffic), the LP1 Connection is lost however for the failure, but instead the LP2 Connection is not
lost.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

34 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.2.3.3 Ring switching/restoring algorythm


According to ITUT Recommendation, the ring switching/restoring algorithm provides the restore of the
preempted extra traffic on the protection channels not used to restore the normal traffic. LP traffic restoration is driven by OAM messages through DCC channel.
Alcatel 4F MSSPRing Transoceanic ring switching algorythm foresees:

to follow standard protocol


during switching protection LP connections not used to restore HP traffic are neither lost nor interrupted.

These LP paths are left in the own time slots and no action is done on them.
Then there is no need for a subsequent LP traffic restoration functionality.
Ring switching needs that every node of the ring (the adjacent at the failure and the intermediate ones)
knows if its HP and LP inserted/dropped traffic is affected by the failure. HP and LP traffic maps must be
provisioned on all the ring nodes.
For HP traffic the algorithm individuates if the path is affected by failure and then must be restored on
protection channels; for LP traffic the algorithm individuates if the path must be interrupted to restore the
corresponding HP path.
To operate correctly ring switching and restoring mechanisms need a set of operations (bridge, switch,
AIS forcing) executed on more ring nodes in a synchronized way to avoid temporary misconnection on
HP and LP connections.
6.2.3.4 Ring switching mechanism
Ring switching of a HP path in transoceanic application consists in dynamically building a new path on a
portion of the ring using the corrispondent time slot of the protection channels. This is done without causing
misconnection on the lost LP paths occupying the same channels and on the HP connection itself in reconstruction phase.
The basic mechanism of ring protection involves the ring nodes in two sequencially distinct phases:

first phase: building of HP path on protection channels and preemption of affected LP paths

second phase: restoring of HP path.


To ensure correct mechanism a node may execute the operations associated to second phase only after
all ring nodes have completed the operations of the first phase.
Passthrough operation executed in intermediate nodes may occur before AIS forcing action performed
on insertion node or squelching on drop node. Thus a passthrough operation may interconnect two LP
paths without presence of AIS on the flow causing temporary misconnection on a LP path.
To avoid misconnection passthrough operation on intermediate nodes are preceded by an AIS forcing
action on transmission side.
6.2.3.5 Ring restoring mechanism

1AA 00014 0004 (9007) A4 ALICE 04.10

Ring restoring of a HP path in transoceanic application consists in the reconnection of the provisioned HP
path and rebuilding plus restoring of previous preempted LP paths. This must be done without causing
misconnection on HP path and restored LP paths.
The basic mechanism of ring restoring involves the ring nodes in three sequencially distinct phases:

first phase: connection of HP path on working channels;

second phase: deletion of HP path on protection channels and rebuilding of provisioned LP paths

third phase: restoring of LP paths.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

35 / 80

Ring restoring mechanism can be divided in two phases:

first phase: reconnection of HP path on working channels, deletion of HP path on protection channels
and rebuilding of provisioned LP paths

second phase: restoring of LP paths.


6.2.4 Multiple protection
The ring may be affected by multiple failures with different characteristics: more span failures, more ring
failures, span failure plus ring failure.
6.2.4.1 Multiple Span Failures
Span switching mechanism involves the protection channels of the affected span only. For this reason
it is possible to execute span switching in every span affected by a failure.
In presence of multiple span failures the ring is involved in multiple span switching to restore all HP paths
travelling on the ring.
6.2.4.2 Span and Ring Failures
In nonTransoceanic application span failure preempts an already present ring protection.
Span protection and ring protection cannot verify at the same time in the ring because the same protection
channels can be used either for ring switching or for span switching alternatively.
Since ring protection mechanism occupies all the protection bandwidth of all spans and span protection
occupies the protection bandwidth of only a span, the standards have given priority to span protection.
In Transoceanic application ring protection mechanism occupies only a portion of the protection bandwidth
of the ring spans.
In presence of more span failures and a ring failure a generic HP path may be in one of the following situations:
1)
2)
3)

HP path crosses only span in ring failure


HP path crosses one or more spans in span failure
HP path crosses span in ring failure and also one or more spans in span failure.

In case 1) the execution of ring switching will determine the restoring of the lost HP connections (the restored HP path on protection channels will cross all the other span failures present of the ring that does
not interrupt the path).
In case 2) the execution of multiple span switchings on the failed spans will determine the restoring of the
lost HP connections.
In case 3) the execution of ring protection will surely determine the restoring of the lost HP connection (the
restored HP path on protection channels will cross the remaining span failures present on the ring that do
not interrupt the path).
Instead the execution of span switchings however does not guarantee that the HP path is reestablished
(provisioned HP path crosses the ring failed span and then it results still interrupted).

1AA 00014 0004 (9007) A4 ALICE 04.10

If the aim is to restore the maximum number of HP connections on the ring between two protection mechanism the priority should be done to ring switching instead of span switching.
In Transoceanic application in case of contemporary presence of span and ring failures the optimal protection algorythm is:

submit to ring switching the time slots carrying HP paths affected by ring failure

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

36 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The operations belonging to a phase can be tied to a timer whose duration must be sufficient to guarantee
that signalling arrives to all ring nodes.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

submit to span switching the remaining time slots not involved in ring switching carrying HP paths
affected by span failures (in case of multiple span failures the involved time slots could be different
on each span according to the occupation of new restored HP path for ring switching).

6.2.4.3 Multiple Ring Failures


In Transoceanic application multiple ring failures does not split the ring into multiple subrings as occurs
in nonTransoceanic application, but it results segmented into a set of linear insert/drop chains separated
by cable failures.
In a ring involved in ring protection for one or more ring failures the occurrence of another ring failure always determines the loss of some other HP traffic: the HP paths affected by new failure that cannot be
restored because also the other way on the ring is interrupted by other failures.
To know which are the LP paths not interrupted by the failures , LP traffic maps are processed. Alcatel
implementation is as follows:

mantain only the restored HP paths not interrupted by the failures


restore all the provisioned LP paths on the protection channels no more used for HP restoring independently from the effective reconstitution of the path (present failures interrupt part of the LP connections).

On a ring involved in ring protection for two or more ring failure, clearing of ring failure determines the
capability to reobtain some other HP traffic: HP paths no more directly affected by the failure; HP paths
affected by the remaining failures for which the restored HP path on protection channels is available.
In case of cleared failure the situation on the ring is:

restored HP paths on protection channels are mantained because the provisioned HP path is still
affected by other failures (with multiple ring failures a restored HP path implies that the provisioned
HP path crosses all present ring failures);
provisioned HP paths no more affected by failures are reconnected without any switching operation
(previously during appearance of ring failure corrispondent provisioned HP path was restored);
some provisioned HP paths still affected by remaining failures are restored on protection channels
(this occurs only for the paths which have restored HP path on protection channels no more interrupted on the ring);
provisioned LP paths no more affected by failures and not preempted for new HP restoring are re
connected without any switching operation (previously during appearance of ring failure all the LP
paths not involved in ring switching were reconstituted).

With one or more ring failures already present in the ring another ring failure causes a partial ring restoring
operation involving the HP paths that cannot more be restored via protection channels on the other way.
With two or more ring failures present in the ring the clearing of a ring failure causes a partial ring switching
operation involving the HP paths for which the restored path on protection channels is no more interrupted.
6.2.4.4 Ring Segmentation

1AA 00014 0004 (9007) A4 ALICE 04.10

Ring Segmentation is managed according to ITU standards.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

37 / 80

A broadcast connection is an unidirectional pointmultipoints link. An unique transmitting source is connected to many receiving destinations.
In the traffic map this connection is represented as a path in which a node is the insertion point and more
nodes are drop points. On some nodes the flow enters from an aggregate side; then exits from the other
aggregate side and from tributary side. The node needs the contemporary provisioning of a time slot in
passthrough and drop connections.
This type of connection can be configured in a Transoceanic ring.
The figure below shows an example of broadcast connection carried by 4F ring on working channels. The
signal is transmitted by node 5 and received by nodes 1,2,3.
The provisioning of the connection is as follows:

node 5 insertion;

node 6 passthrough;

node 2 and 3 bridge (passthrough and drop);

node 1 drop.

HP traffic
LP traffic

1AA 00014 0004 (9007) A4 ALICE 04.10

Broadcast connection

Figure 20. Broadcast connection

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

38 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.3 Broadcast Connections

6.3.1 Fault management

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4F Transoceanic MSSPRing ring protection mechanism is used also to restore broadcast paths.
6.3.2 Failure affecting all drop points
If the ring failure occurs on the span connecting source and nearest sink node, the signal does not reach
any drop point.

HP traffic
LP traffic
Broadcast connection
Protected broadcast connection

Figure 21. Failure affecting all drop nodes


To restore the broadcast connection it is necessary to switch the flow to the other ring direction , not affected by the failure.
The actions to perform are:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

ring bridge on insertion node;


passthrough LP channel on intermediate nodes of the protected connection;
ring switch and passthrough LP channel on all the drop nodes except the nearest one;
ring switch on nearest provisioned drop node.

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

39 / 80

If the ring failure occurs on a span included between two sink nodes, the signal still reaches some drop
points.

HP traffic
LP traffic
Broadcast connection
Protected broadcast connection

Figure 22. Failure included between drop nodes


To restore the connection, the actions to perform are:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

ring bridge on insertion node;


passthrough LP channel on intermediate nodes of the protected connection;
ring switch and passthrough LP channel on the unreachable drop nodes;
ring switch on the last unreachable drop node.

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

40 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.3.3 Failure affecting some drop points

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.3.4 Broadcast connection management


The characteristic action involves the nodes of the path on which the double connection in drop and pass
through must be performed.
During ring switching operations nodes must determine if the protection channel used for restoring is involved in:

passthrough operation to build the path for the subsequent nodes;

ring switch operation to sink the signal on the drop termination.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

41 / 80

During both span and ring protection mechanisms the node determines the time slots of the LP channels
involved in a particular action.
6.4.1 Ring path restoring algorythm
During ring switching each node of the ring (not only those interfacing the failure) must determine which
are the LP paths to preempt leaving free the protection time slots to reroute the HP paths.
This activity is realized by ring path restoring algorythm.
The following information are required:

node identifier;

ring map;

traffic maps.
The input parameter is the fault localization.
According to the current node position the algorythm is able to determine which are the LP paths to preempt.
Step 1) Construction of the new HP connections on protection channels.
To determine which are the new connections to build over the protection channels as a consequence of
a failure, each node must know the traffic map of the working paths in the overall ring.
First the algorythm individuates the HP connections cancelled in consequence of the failure.
Then it rebuilds the cancelled connections on the protection channels considering that the new paths travel
in the opposite direction.
Step 2) Determination on the local node of the transmitted and received AU4 time slots of the protection
channels to preempt.
Comparing the localization of the occupied time slots of the new connections with the provisioned LP paths
involved in the node (protection path dropped, inserted or passthrouged by the node) the algorythm determines which are the LP channels to cancel.
The following tables reports the provisioned LP connections to preempt and the provisioned LP connections not involved in protection and then that are mantained on the ring.

At the end is reported the final status of the connections on working and protection channels of the ring
after a ring switching.

1AA 00014 0004 (9007) A4 ALICE 04.10

In particular the algorythm furnishes at each node the following information:

LP channels to preempt among those provisioned in drop for both directions. The node performs
AIS forcing action on them.

new built HP paths on protection channel time slots in which the node is involved. In correspondence
to the used time slot the node performs the following actions:

if used in insertion, AIS forcing and ring bridge action;

if used in passthrough, passthrough action;

if used in drop, ring switch action.


Besides normal drop/insert connections the algorythm manages also broadcast connections and D&C
connections ( on transmission direction D&C path may be seen as a broadcast connection having the termination node as source point and primary and secondary nodes as the two sink points).
For broadcast paths (and then D&C paths transmission side) it rebuilds the connection on the protection
channels of the ring with one or more nodes in bridge according to the localization of the failure.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

42 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.4 Path restoring algorythm

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

In case of multiple failures the algorythm starts from the current traffic maps of the HP connections on working and protection channels on the ring (originated by means of previous failure) to determine:

the protection channels to preempt for span switching when is already present a ring failure (they may
be provisioned LP channels or channels already used for ring protection);

the LP paths to restore when there are more ring failure conditions;

some new HP paths to rebuild (and consequent LP paths to preempt) and other LP paths to restore
when one of the ring failure conditions is cleared.

6.4.2 Span path restoring algorythm


During span protection it is necessary to individuate which are the LP channels to cancel for protection
selectivity.
The algorythm needs only to know the HP and LP connections, subdivided in transmission and receiving
direction, interfacing the failed span.
It compares HP and LP connections receiving side to determine:

receiving LP time slots to preempt.

They will be subdivided partly on tributary side for AIS forcing on dropped side and partly on aggregate
side for AIS forcing on passthrough side.
The same time slots are those involved on tributary side and aggregate main opposite side for span switch
operation.
It compares HP and LP connections transmission side to determine:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

transmitted LP time slots for span bridge on aggregate spare side.

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

43 / 80

6.4.2.1 Controls Points


Command list for East or West side:
4)
5)
6)
7)
8)
9)
10 )
11 )

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

a)

Lockout of protection
Force Span Switch
Force Ring Switch
Manual Span Switch
Manual Ring Switch
Exercise Span
Exercise Ring
Clear Command

6.4.2.2 Sense Points


a)

Commands sent and actuated for East or West side:


1)
2)
3)
4)
5)
6)
7)
8)

Lockout protection
Force Span Switch
Force Ring Switch
Manual Span Switch
Manual Ring Switch
Exercise Span
Exercise Ring
Clear Command

The command Exercise Span exercises span protection of the requested channel without completing the
actual bridge & switch. The command is issued and the responses are checked but no normal traffic is
affected.

1AA 00014 0004 (9007) A4 ALICE 04.10

The command Exercise Ring exercises ring protection of the requested channel without completing the
actual bridge & switch. The command is issued and the responses are checked but no normal traffic is
affected.
b)

Node Status: Idle, PassThrough, Switching

c)

Switch Status: Idle, Span Bridge, Span Switch, Span Bridge and Switch, Ring Bridge, Ring Switch,
Ring Bridge and Switch

d)

West side K1 K2 K3 Error/East side K1 K2 K3 Error


The errors occurring on the K1K2K3 bytes can be:

Syntax errors: the pattern contained in K1 or K2 or K3 has an unspecified meaning;

Semantic errors: the node identifiers do not belong to the ring

Protocol errors: the K1, K2, K3 pattern is not coherent with the status of the Transoceanic MS
SPring State machine.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

44 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.5 Path with Drop & Continue


6.5.1 Introduction
A Transoceanic 4F MSSPRing may be interconnected to another ring in a dual node interconnection architecture, according to ITUT Recommendation G 842.
With this architecture the Transoceanic nodes may be used as primary and secondary node of a interring
path protected in Drop & Continue.
D&C function stays on primary node. It consists into selecting (drop) one of two path (service circuit and
secondary circuit) available on the node and transmits it onwards on the ring (continue).
The service circuit arrives to the primary node from the tributary side, while the secondary circuit arrives
from the aggregate opposite side coming from secondary node.
The function is implemented by the Service Selector.
Only HP connections may be protected in Drop & Continue.
Secondary circuit between primary and secondary nodes can be carried on HP channels or LP channels.
In the description which follow P means primary node, S secondary node, T termination node.
6.5.2 Fault management
D&C provides the protection in the occurrence of the following failures:

failure on one of the two interconnection links between rings (from P of a ring to S of the other ring);

secondary node failure;

failure on a link between primary and secondary node of the ring.


Figure 23. reports the behaviour of the Service Selector for all the types of involved failures.
In all these cases will always remain available one of the two circuits (service circuit or secondary circuit)
allowing the establishment of the path.
The first example illustrates the selection of the flows coming from tributary side in the following conditions:

failure on a link included between primary and secondary node carrying the secondary circuit;

secondary node failure;

failure on the interconnection link between P and S nodes carrying the secondary circuit.
The second example illustrates the selection of the flows coming from aggregate opposite side in the following conditions:

failure on the interconnection link between P and S nodes carrying the service circuit;

failure on a link included between primary and secondary node carrying the service circuit.

1AA 00014 0004 (9007) A4 ALICE 04.10

D&C functionality associated with Transoceanic MSSPRing protection mechanism causes a completely
different interaction respect to notTransoceanic application, particularly in consequence of the bridge
and switch operations performed by intermediate nodes.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

45 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

T
P

Service circuit
Secondary circuit

P: Primary node
S: Secondary node
T: Termination node

Service Selector

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 23. D&C protection management

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

46 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.5.3 Secondary circuit on HP channels: fault management


Failures occurring on spans and nodes on the side of the ring not crossed by D&C protected connection
have no interaction with D&C function.
D&C protected path pass through the service connection ( from Primary to Secondary )
D&C function is performed by the primary node by selecting one of the two available circuits according
to the detected alarm conditions.
If the failure is localized between primary and secondary nodes the secondary circuit is not rebuilt on
protection channels on the opposite way as Transoceanic ring protection criterion should request. So the
secondary circuit is lost; the primary node selects the service circuit because the other circuit is affected
by alarm condition.
Failures affecting spans or nodes (crossed by the selected D&C path ) from primary to termination node
cause the interruption of the path. D&C connection is restored according to Transoceanic MSSPRing
ring protection mechanism by interacting with D&C function.
D&C function together with Transoceanic MSSPRing is able to protect the D&C path even in case of
failure of the primary node.
Failures are:

span failure on span adjacent primary node

ring failure on a span included between primary and termination nodes

primary node failure.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

47 / 80

Failures affecting D&C path from primary to termination nodes are restored by the Transoceanic MS
SPRing protection mechanism interacting with D&C function.
LP channels carrying secondary circuit may be used to restore HP paths when occurs particular span and
ring failures.
Infact a span failure on a span included between primary and secondary nodes may cause the use of secondary circuit channel to restore corresponding HP channel.
Secondary circuit channels may be preempted to carry restored HP path on protection channels even in
case of ring failure affecting a HP path carried by the same time slot of the secondary circuit LP channel.
The preemption of secondary circuits is signalled to avoid misconnection on D&C protected path.
This is done forcing AIS to the D&C secondary circuit on the primary node before arrival of the flow on
Service Selector.
Figure 24. illustrates the case of a D&C path selecting secondary circuit on LP channel subsequently preempted because of span failure.
Failures are:

span failure on span adjacent primary node


ring failure on a span included between primary and termination nodes (including also primary node
failure).

HP AU4#i

LP AU4#i
Node P

Node S

HP AU4#i

AIS
LP AU4#i
Node P

Node S

HP channels

1AA 00014 0004 (9007) A4 ALICE 04.10

LP channels

D&C Selector

Figure 24. Secondary circuit on LP channels preemption

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

48 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.5.4 Secondary circuit on LP channels: fault management

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.5.5 Failure cases


The failure cases causing particular management of the protection mechanism are:

span failure occurring on the span adjacent primary node on Service Selector side (applicable for
secondary circuit on HP and LP channels)

primary node failure (applicable for secondary circuit on HP and LP channels)

ring failure on a span included between primary and termination nodes (for secondary circuit on HP
channels)

ring failure on a span included between primary and termination nodes (for secondary circuit on LP
channels).

6.5.6 Span failure on span adjacent Service Selector of primary node

T
P

Service Selector

Figure 25. D&C protection management: span failure on link adjacent Service Selector

1AA 00014 0004 (9007) A4 ALICE 04.10

For secondary circuit carried on HP channels , the secondary circuit is selected executing a crossconnection operation because the signal comes from opposite side working line.
For secondary circuit carried on LPchannels, the secondary circuit is selected executing a passthrough
connection operation because the signal comes from opposite side protection line.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

49 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.5.7 Primary node failure

T
P

Service Selector

Bridge connection

Figure 26. D&C protection management: failure on primary node


The termination node receives D&C path performing ring switching of the flow from the other side.
In this case D&C function disappears; D&C path is mantained simply executing a transoceanic ring switching operation for the connection.
Secondary and termination nodes execute ring bridge and switch actions on D&C path so that also in transmission direction D&C path, starting on termination node and arriving on secondary node, is sent toward
the other ring crossing its primary node.

1AA 00014 0004 (9007) A4 ALICE 04.10

This case is managed only by Transoceanic MSSPRing manager. The D&C path is represented on traffic
map as HP connection having secondary and termination nodes as drop/insert points.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

50 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.5.8 Ring failure on span included between primary and termination nodes (HP case)
Figure 27. reports the behaviour of D&C function together with Transoceanic MSSPRing when a failure
occurs on a span or node included between primary and termination node of a D&C path.

T
P

Service Selector

Figure 27. D&C protection management: ring failure on link between P and T nodes (HP case)
According to Transoceanic concept the selected D&C path must be routed in the opposite way on the
corresponding protection channel.
The primary node still performs the Service Selector function, but moved to the other side of the node.
The selection is always between the service circuit coming from tributary side and the secondary circuit
coming from secondary node on aggregate side. The selected flow is transmitted back to the corresponding protection channel toward the secondary node.
Node operation is as follows:

the D&C function, localized on the opposite side determines the circuit

the Transoceanic MSSPRing function performs ring bridge and switch operations of the D&C flow.
Then during the persistence of the failure the node operation is:

when occurs an alarm condition on one of the two available circuits, the D&C function of the opposite
side performs the selection connecting one of the flows to the protection channel used to restore the
HP D&C path.

1AA 00014 0004 (9007) A4 ALICE 04.10

When the flow coming from aggregate side must be connected, the node must perform a loopback operation from working to protection channel. ( not common in Transoceanic application)
This choice realizes that a flow travels twice the link between P and S nodes (a first time from S to P and
then from P to S) and seems not in accordance with Transoceanic concept. But it is also true that primary
and secondary nodes of a D&C protected path usually are not positioned as nodes adjacent to an oceanic
link.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

51 / 80

The following figure reports the behaviour of D&C function together Transoceanic MSSPRing when occurs a failure on a span or node included between primary and termination node of a D&C path.

T
P

Service Selector

Bridge connection

Figure 28. D&C protection management: ring failure on link between P and T nodes (LP case)
Differently from secondary circuit on HP channels in this case it is not possible to reroute toward opposite
way D&C path on primary node after selection because the corresponding LP channel is used to transmit
the secondary circuit on the other direction.

1AA 00014 0004 (9007) A4 ALICE 04.10

D&C selection capability is lost; the unique possibility is to the route secondary circuit to the termination
node crossing other direction of the ring. This is done using the same protection channels and executing
bridge operation on secondary node and switch operation on termination node.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

52 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.5.9 Ring failure on span included between primary and termination nodes (LP case)

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.6 Features
The provided features are in accordance with ITUT Recommendation G.841, in particular the following
definitions are used:
request node: a node that generates either a protocol request or protocol reply (other than NR!). The pair
of nodes sending each other protocol request/reply are peer request nodes.
intermediate node: the node that is not a request node. It is always in the passthrough state. If such
a node executes bridge and switch of at least one AU4 it is also a bridge&switch node.
6.6.1 General description of MSSPRING protection scheme
Multiplex Section Shared Protection Ring (MSSPRING) is an SDH trail protection scheme, as it is
described in ITUT Recommendation G.841, section 6.1.
The MSSPRING application described in G.841, sections 6.1 and 7.2 is called Classic MSSPRING
application.
The MSSPRING application described in G.841, sections 6.2 and Annex A is called Transoceanic
MSSPRING application.
6.6.2 MS shared protection rings Transoceanic application
The application is fully compliant with G.841, Annex A.
6.6.2.1 Network objectives
The application is fully compliant with G.841, Annex A, section A.2 .For transoceanic applications of MS
additional network objectives apply:
1)

Switch time. The switch completion time is less than 300 milliseconds, independent of whether
the ring is carrying extra traffic.

2)

Extent of protection: b) The ring restores all traffic possible, even under conditions of multiple
bridge requests of the same priority.

3)

APS protocol and algorithm:


a)

During a failure, preempted extra traffic can be reestablished on the protection channels
not used to restore the normal traffic.

b)

For transoceanic applications, ring maps are used to switch traffic affected by a failure at
intermediate nodes. A mechanism that autoprovisions the data required for these maps,
and maintains its consistency.

c)

If a ring switch exists and a failure of equal priority occurs on another span requiring a ring
switch, then, if the priority of the bridge request is Signal Fail (Ring) or higher, both ring
switches are established resulting in the ring segmenting into two separate segments.

It is assumed that the span switch must be performed on a perAU4 basis. In this way, an unloaded
Normal AU4 will not be bridged & switched, and the corresponding ET AU4 will not be preempted.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figures which follow show examples of Routing in Working and Routing in Protection schemes.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

53 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

P
working channels
protection channels
N

E
F

Figure 29. Broadcast path (not protected )

P
working channels
protection channels
N

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 30. Unidirectional protected path

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

54 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

P
working channels
protection channels
N

E
F

Figure 31. Routing in working ( RIW ): bidirectional path, outgoing direction

P
working channels
protection channels
N

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 32. Routing in Protection ( RIP ): bidirectional path, outgoing direction

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

55 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

P
working channels
protection channels
N

E
F

= selector

Figure 33. Routing in working ( RIW ): bidirectional path, incoming direction

P
working channels
protection channels
N

E
F

1AA 00014 0004 (9007) A4 ALICE 04.10

= selector

Figure 34. Routing in Protection: bidirectional path, incoming direction

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

56 / 80

6.6.2.2 Protection algorithm operation

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Full compliance to G.841, Annex A, section A.6


6.6.2.2.1 Handling broadcast paths
Figure 29. shows a generic ring and a normal pointtomultipoint cicuit being inserted at node A and
broadcast to nodes G, H, and L.
With the Transoceanic MSSPRING, the following rules apply:

the insert node for the given path (see Figure 29. , node A) shall see the outgoing pointtomultipoint
path as being inserted locally and dropped at the farthest drop node (L);
each node dropping the incoming pointtomultipoint path shall see it as being inserted at the insert
node (A) and dropped locally. In other words, the drop&continue connection is seen as a normal drop
connection plus a passthrough connection. Every such node shall also be aware that the drop
connection is part of a pointtomultipoint path.

According to the above rules, any failure between the insert node and the first drop node, not including
the insert node failure (see Figure 35. ), is handled as follows:

Because of the ring signaling, the insert node (A) knows that a ring failure has occurred between D
and E, and bridges the affected path onto the protection channel that travels away from the failure.

Node L realizes that the failure is affecting the pointtomultipoint path it is receiving from A (because
the ring traffic map declares the path as AL, and the failure is in between) and, knowing to be the
farthest drop node for that path, drops the extratraffic according to the usual rules and converts its
drop/West connection of the failed pointtomultipoint path into a drop&continue/East of the
corresponding protection channel in the opposite direction. The drop part is necessary to receive
the good path from A, whereas the continue is necessary to forward that good path to nodes G and
H.

Likewise, node H realizes that the failure is affecting the pointtomultipoint path it is receiving from
A (because the ring traffic map declares the path as AG, and the failure is in between) and, knowing
to be an intermediate drop node for that path, converts its drop&continue/West connection into a
drop&continue/East of the corresponding protection channel in the opposite direction.

Node G realizes that the failure is affecting the pointtomultipoint path it is receiving from A and,
knowing to be the first drop node for that path, converts its drop&continue/West connection into a
drop/East of the corresponding protection channel in the opposite direction.
As a consequence of that failure, this mechanism brings about an alternative path traveling on the
protection channel in the opposite direction and feeding all the drop nodes of the pointtomultipoint path
a good signal as a substitute for the failed one.

1AA 00014 0004 (9007) A4 ALICE 04.10

A failure between the first drop node and the farthest drop node (see Figure 36. ), both not included,
is handled as follows:

Node A realizes that only the nodes preceding the ring failure (G) are still reachable: for ring
interconnection purposes, this is sufficient to guarantee that a good tributary can still be sent by A
to the other ring, and thus no switching action is required at all.

If the capability of sending to all the drop nodes is to be preserved upon single ring failure, it is
necessary that node A bridges the inserted path onto the protection channel in order to reach the
affected nodes (H and L); moreover, the nodes beyond the failure (H and L) shall behave as in above
case, Node G realizes that the failure is not affecting the pointtomultipoint path it is receiving from
A and does no switching at all.
The original pointtomultipoint path is therefore split into

a pointtomultipoint path on the working channel, from the insert node through the farthest
unaffected drop node (G), and

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

57 / 80

A failure of the farthest drop node (see Figure 37. ) is handled as follows:

Node A does no switching because the node being declared by its ring traffic map as destination of
the pointtomultipoint path it is inserting is faulty.
All the intermediate drop nodes are unaffected by the failure and keep receiving the path from A on
the working channel.

P
working channels
protection channels
N

E
G

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 35. Broadcast path: i/c span fault

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

58 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

a pointtomultipoint path on the corresponding protection channel in the opposite direction,


from the insert node through the first affected drop node (H).

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

P
working channels
protection channels
N

E
F

Figure 36. Broadcast path: middle span fault

P
working channels
protection channels
N

E
F

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 37. Broadcast path: last node fault

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

59 / 80

As the termination node A bridges and switches the path onto the protection channel away from the failure,
the two interconnection nodes behave as follows (drop & continue/working method):

the Primary node loops the path after the selector back onto the protection channel toward the
secondary node.
the Secondary node is not impacted, as it continues transmitting/receiving to/from the Primary node
using the same side.

This is the only event where a loopback is allowed with Transoceanic application. The increase of distance
to travel (all the spans between the Primary and Secondary node are gone through twice, if the secondary
interconnection is selected) is considered negligible. Note that such a loopback does not imply any
potential for misconneciton, as the paths destined to the failed node (in the event of node failure) are not
bridged & switched.
In this way the dualnode interconnection capability is preserved, still allowing the ring selfhealing when
a potential additional fault affects the secondary path (the handoff to the Secondary node).
As for the drop & continue/protection method, the loopback is not applicable as the continue portion is
preempted by the path being bridged & switched by the termination node A onto the protection channel
away from the failure to reach the Primary node. The secondary interconnection is therefore no longer
available.
6.6.2.2.1.2 Failure of the secondary node
The same behavior recommended for Classic MSSPRING applies to both drop & continue/working and
/protection methods:
for a failure of the secondary node, the tributary at the terminating node is unaffected, since it receives
its tributary from the primary node. Because of the ring signaling, the Primary node knows that the
secondary node has failed. The Primary node chooses its tributary from the traffic entering it from the other
ring.
6.6.2.2.1.3 Failure between the interconnection nodes
A failure occurring between the two interconnection nodes, is dealt with in the same way as in the
Secondary node failure case. The secondary interconnection is no longer available.

1AA 00014 0004 (9007) A4 ALICE 04.10

6.6.2.2.2 Examples of path crossing mixed rings

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

60 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.6.2.2.1.1 Failure outside of the termination, Primary, or Secondary nodes

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

TX

SNCP

ED

01
B

E
C

NPE

RX

SNCP
SNCP

RX

A
B
NPE
C

F
E
D

Equipment=1664SM

SNCP

TX

Figure 38. Bidir. Path, 1664SM, RIP

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

61 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

SNCP

ED

01
B

E
C

NPE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

TX

RX

SNCP
SNCP

RX

A
B
NPE
C

F
E
D

Equipment=1670SM

SNCP

TX

Figure 39. Bidir path, 1670SM, RIW.

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

62 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6.7 4F MSSpring NPE Holdoff time management


6.7.1 Description
The Holdoff time mechanism is used to set the time to wait before performing a protection switch after
a defect has occurred on either the protecting or the protected unit. The Holdoff time for 4f MSSPRing
is supported by 1670SM R3.1 and later releases.
The Operator from the RM User Interface can define or change of the Holdoff time value. In particular
the operator has to select the 4f MSSPRing in the Browser, to display the protection blocks view, to select
the protection block to which apply the command and than to choose the Specific/Hold Off Time command. At this stage the Operator can provide the Hold Off Time value (allowed values: 0 (no Hold Off Time),
30ms, 50ms, 70ms, 100ms, 300ms, 500ms, 700ms, 1s, 3s, 5s and 10s) for the protected unit (West and
East side) and for the protecting one (West and East side).

6.7.2 Visualization of MSTrails on 4f MSSPRing Protection Block view

1AA 00014 0004 (9007) A4 ALICE 04.10

The feature allows the displaying of the MSTrail (main and spare) related to the Physical Connection in
the 4f MSSPRing Protection Block view.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

63 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

64 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

7 RM OBJECTS

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The database contains the object classes which are described in the following.
NtwDomain
The ntwDomain (network domain) is the whole area controlled by the 1354RM.
Ntw (Network)
The network comprises all the interconnected SDH equipment. A network comprises subnetworks.
A network object instance has an associated symbol and a submap. The symbol represents the network
in the root submap, and clicking on it the corresponding submap can be opened.
EmlDomain
An EML domain is maintained by a single EML OS. This object is generated in order to inform the Operator
on the OS a certain NE belongs to.
An EMLdomain contains the NEs managed by the EML OS.
NE
A Network Element is an SDH telecommunication equipment managed by the OS.
A node has an associated symbol and a submap. The symbol is used to represent the node in the submap
describing the topology of the subnetwork or ET where the node is contained. Clicking on the node, the
asociated submap will be opened. This submap contains the uploaded ports.
Physical Connection
A physical connection connects two ports in the network. These two ports belong to different NEs and must
have the same transmission rate.
A physical connection has a symbol, that is used to represent the physical connection in the submap
associated.
Site
The site is the name of the physical location of the object.
Port
The port represents the physical accesses of the SDH equipment.
A port is a physical interface of a node. Two ports with the same interface can be connected by means
of a physical connection.
A port has a graphical symbol, that is used to represent the port in the submap associated to the node.
Path

1AA 00014 0004 (9007) A4 ALICE 04.10

The path defines a connection between ends (NAPs) of the network.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

65 / 80

The subnetwork is a partitioning of the NML network. It contains Elementary topologies and
interconnected Nodes.
A subnetwork is a grouping of nodes and ETs.
A subnetwork has a symbol and a submap.
ConnInTopol
The connInTopol (connection in topology) describes a generic connection (subnetwork connection,
network connection) between two or more ends (they can be Naps,Caps or Ctps) to realize a path in any
partitioning level.
A connInTopol between Naps corresponds to a path.

Ntw

sbn2

sbn1
connInTopol
Nap1

Nap2

Connection in topology at netwok level. Connection between Nap1 and Nap2


Cap
The Cap (Connection access point) is a higher order trail termination. It can be the client access point
towards the network.
Ctp
Connection termination point.
Ms CtpCap

1AA 00014 0004 (9007) A4 ALICE 04.10

It represents both the Msctp and the mscap entities related to an SDH physical port at MS layer.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

66 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Sbn

NE
nap
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

connInTopol
nap
LOPL
tdm

HOPL
connInTopol

MSL
msctpcap

msctpcap

Figure 40. Schematic representation of the NE


Trail
It describes the connectivity between two caps in any partitioning level and in any layer. It defines the
association between client access points in the same transport network layer.

LOlink connection
LO

ctp

ctp
HOtrail

cap

cap

HO
HO link connection
ctp

ctp

ms trail
msctpcap

MS
msctpcap

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 41. Trail and link connections


Link Connection
The link connection describes the connectivity between two CTPs in any partitioning level and in any layer.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

67 / 80

The figure which follows describes the objects involved in the structure.
NE

nap

nap
connInTopol

connInTopol

ctp3rd ord

LOlc(TU3#1)

tdm

LOPL

tdm
140cap1
(VC4)
#1

LOPL

140cap1
(VC4) #1

HOtrail(VC4S1)

connInTopol

connInTopol

ctp16

HOlc ( AU4#16)
HOlc ( AU4#1)

ctp1

HOPL

HOPL

MSL

MSL
ms trail
mstp

mstp

mstp

physConn

mstp

nap

nap

LOlc(TU3#1)

ctp3rd ord

140cap1
(VC4)
#1

140cap1
(VC4) #1

HOtrail(VC4S1)

connInTopol

ctp16
ctp1

connInTopol

HOlc ( AU4#16)

ctp16

HOlc ( AU4#1)

HOlc ( AU4#16)

ctp1

1AA 00014 0004 (9007) A4 ALICE 04.10

ms trail
mstp

physConn

ctp1

HOlc ( AU4#1)

connInTopol

ms trail
mstp

ctp16

mstp

mstp
physConn

Figure 42. Objects involved in the structure

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

68 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

NE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7.1 OTN WDM model


The model of the PREOTN WDM network managed by 1354RM includes several layers, as shown in
figure below.

CLIENT LAYER ( SDH or generic )


OCH ( B / W )

OCH ( colored )
OMS

OPSUNI

OTS ( n lambda n>=1 )

Figure 43. WDM network managed model.


where:
OTH=optical transport hierarchy
OCH=optical channel
OMS=optical multiplex section
OTS=optical transmission section
NNI=network node interface
UNI=user to network interface
CBR=constant bit rate
OCH B / W= optical channel Black and White

In particular:

OTS represents the transport section and includes:

OTS ports ( NNI )

OTS Physical connections representing the interconnections between OTS ports

Ports of Repeaters ( ILA ) are not treated by 1354RM.


Repeaters can be correlated to OTS physical connections

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

OMS represents the Optical multiplex section and includes:

OMS TPs

OMS Trails representing the logical interconnection between OMS TPs

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

69 / 80

OPSUNI represents the physical interconnection between:

UNI ports ( OGPI ) of WDM NEs ( e.g. back to back with or without transponders )

UNI ports of WDM NEs and SDH ( or CBR ) NEs


It includes:

OPS ( Optical physical section ) ports (=OGPI ports )

OPS Physical connections representing the interconnections between OPS ports

OCH ( colored ). It represents the Optical Channel (lambda) and includes:

OCH CTPs on the MUXDeMUX functional block

OCH Link Connections connection ( LCs ) logically interconnecting OCH CTPs at the same
frequency

OCH LC
OCHCTP

OCHCTP
OMS Trail
OMS TP

OMS TP
OTS Phys Conn

OTS Port

OTS Port
Figure 44. WDM model.

OCH (colored) layer includes:

OCH TTPs representing the generation of the Lambda ( on Transponders )

OCH trails representing the logical interconnections between OCH TTPs crossing OCH CTPs,
OCH LCs and OCH cross connections

Not complete OCH Trails named OCH raw connections


In addition:

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

OADMs provide OCH passthrough at the same Lambda (passthrough of the extraband),
called by 1354RM, OCH passthrough crossconnection.

1696MS is able to perform OCH passthrough crossconnections changing frequency (O/E/O


conversion in MCC)

The CLIENT LAYER represents the CBR / TDM service of the WDM network.
The Client path is the representation of this service. In case of SDH the client path is a trail at the
regenerator section layer.
The Client Layer includes:

Client CTPs on transponders, that is TPs on I/O directions like rsCTPs, gdcCTPs, ochgdc
CTPs)

Client Link Connections logically connecting client CTPs


01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

70 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ED

Client paths interconnecting client terminations ( client NAPs ) with a sequence of LCs and
crossconnections.

The Client path is never terminated on WDM NEs

OPC or OCP protections are managed by RM as client layer protected crossconnections

The OCH ( B / W ) is a technical layer added at RM level to balance the model mainly in case of
SDH interworking. It contains objects with no counterpart in the NE.

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

71 / 80

PATH
.
LOlc(TU3#1)
nap

LOPL
(VC4)

140cap1
(VC4)
#1

HOtrail(VC4S1)

140cap1
connInTopol

connInTopol

ctp16

HOlc ( AU4#16)
HOlc ( AU4#1)

ctp1

HOPL
MSL

ms trail
mstp

mstp

OSPI
OSPI

physConn
rsttp

rsttp

rs trail = CLIENT PATH

4x2.5

rsctp

clientctp

client lc

clientctp

client lc

client lc

ochtrail

ochtrail

4x2.5
ochttp

ochctp

ochtrail

rsctp

4x2.5

ochtrail

ochttp

ochttp

OCHlc

client lc

OCHlc

OCHlc

ochctp

OCHlc

ochctp

ochctp

omstrail

omstrail
OMSTP

OMSTP
opsphyscon
OPS

opsport

1AA 00014 0004 (9007) A4 ALICE 04.10

SDH
OSPIclone

otsport

otsport

LT

opsphyscon
OPS

otsphyscon
OTS

otsphyscon
OTS

otsport
OADM

opsport

otsport

SDH

LT
OSPIclone

Figure 45. SDHWDM interconnection scheme

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

72 / 80

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

connInTopol

nap

7.2 Integrated approach

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM manages SDH and WDM networks with an integrated approach.


When the WDM interconnection is inserted in RM between a SDHNE and a WDM transponder, the same
SDH port is presented two times:
SDH representation to accomplish the SDH physical connection
WDMOPS representation to accomplish the OPTICAL physical connection
Namely the SDH physical connection is merely a logical connection from SDH to SDH port, while OPTICAL physical connections maintain physical properties.

7.3 Functions
1354RM allows:
upload of WDM NEs and ports from 1353SH
placement of WDM NEs into RM topologies
definition of OTS links and single lambda interconnections (OPS) between WDM NEs. OPS links are
needed for coloured or B/W backtoback interconnections
declaration of connectivity between SDH and WDM networks on a single map
the upload of an existing connectivity at OCH and client layer during the implementation of physical connections. The uploaded connectivity first generates raw connections and then OCH trails and in turn client
raw connections and client paths.

1AA 00014 0004 (9007) A4 ALICE 04.10

The type of WDM connection is OPS for SDHWDM connection, OTS for WDMWDM connection.

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

73 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

74 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

8 OBJECT NAMES

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

RM object names characters used are:

AZ, az, 09, all special characters except: tilde (~), backslash (\), pipe (|), double quote (), TAB

The maximum object username lenght is:

ED

path
EML Domain
Netw Domain
ne
port
physical Conn
routing link
network
subnetwork
et (ring)
node
trail
perf. measure
pmTransport
TCA Profile
pmNE
pmTp
pmCountRep
tcRProfile
pmTranStProfile
pmRatioProfile
pmQpgProfile
aSSAProfile
raw connection
sublink pointer

01

86
32
24
32
88
92
46
24
24
24
32
94
100
100
48
100
100
24
24
24
24
24
32
86
44

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

75 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

76 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9 ACRONYMS AND ABBREVIATIONS


ADM

Add and Drop Multiplexer

AIS

Alarm Indication Signal

ALS

Automatic Laser Shutdown

APS

Automatic Protection Switching

ASAP

Alarm Severity Assignment Profile

AU

Administrative Unit

AU PJC

Administrative Unit Pointer Justification Counter

BER

Bit Error Rate

CDROM

Compact Disc Read Only Memory

CCITT

Telegraph and Telephone International Consultative Committee

CT

Craft Terminal

DCN

Data Communications Network

DS

Degraded Signal

ECC

Embedded Communication Channels

EML

Element Management Layer

EPS

Equipment Protection Switching

FAD

Functional Access Domain

FERF

Far End Received Failure

FLS

Frame Loss Second

Gbit/s

Gigabits per second

GNE

Gateway Network Element

HMI

Human Machine Interface

HOA

High Order Assembler

HO Matrix

High Order Matrix

HPA

High Order Path Adaptation

HPC

High Order Path Connection

HPT

High Order Path Termination

HP

Hewlett Packard

HPOV

Hewlett Packard OpenView

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

77 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

Hewlett Packard OpenView Windows

HPUX

Hewlett Packard Unix

HPVUE

Hewlett Packard Visual User Environment

HVC

Higher Order Virtual Container

IEEE

Institute of Electrical and Electronics Engineers

IM

Information Manager

Kbit/s

Kilobits per second

LAN

Local Area Network

LOF

Loss Of Frame

LO Matrix

Low Order Matrix

LOP

Loss Of Pointer

LOS

Loss Of Signal

LOT

Loss Of Tributary

LPA

Lower Order Path Adaptation

LPC

Lower Order Path Connection

LPT

Lower Order Path Termination

LVC

Lower Order Virtual Container

Mbit/s

Megabits per seconds

MIB

Management Information Base

MS

Multiplex Section

MSSPRING

Multiplex Section Protection Ring

MSP

Multiplex Section Protection

MST

Multiplex Section Termination

NAD

Network Access Domain

NAP

Network Access Point

NE

Network Element

NML

Network Management Layer

NPE

Network Protection Equipment4 fibre MS Spring

NSAP

Network Service Access Point

OFS

Out of Frame Seconds

ED

01

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

HPOVW

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

78 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

OS

Operation System

PDH

Plesiochronous Digital Hierarchy

PI

Physical Interface

PPI

PDH Physical Interface

PTM

Path Trace Mismatch

RS

Regenerator Section

RST

Regenerator Section Termination

SA

Section Adaptation

SCSI

Small Computer Serial Interface

SDH

Synchronous Digital Hierarchy

SF

Signal Failure

SPI

SDH Physical Interface

STMN

Synchronous Transport Module level N (N is an integer = 1,4 or 16)

TF

Transmit Fail

TMN

Telecommunications Management Network

TN

Telecommunications Network

TP

Termination Point

TU

Tributary Unit

TU PJC

Tributary Unit Pointer Justification Counter

USM

User Service Manager

VC

Virtual Container

XC

CrossConnect

ED

01

SC.5: TECHNICAL ANNEXES


3AL 61348 AA AA
80

79 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

END OF DOCUMENT

ED

01

SC.5: TECHNICAL ANNEXES

3AL 61348 AA AA

80

80 / 80

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM REL.7. 2 OPERATORS HANDBOOK

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5
5
5

2 WDM TECHNOLOGY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 WDM Layer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 WDM Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 WDM Equipments managed by 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 WDM NE configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Network construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Integrated management map view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Circuit provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Raw connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6 Data service VC4v Management (4xANY board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8 PRC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10 B1 based PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11 Acronims . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.1 Topological Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.2 Physical Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.3 Transport Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.4 Reference Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12 WDM Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.1 OTS conn. navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.2 OPS conn. navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.13 WDM network create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.14 Raw Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.14.1 Completed raw connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.15 Optical Network Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.15.1 Adding a transponder on 1640WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7
9
9
11
11
15
16
16
18
19
21
22
22
23
23
24
24
24
24
25
27
27
34
38
47
50
55
55

01

050207

ED

DATE

CHANGE NOTE

M.RAGNI

V.PORRO

APPRAISAL AUTHORITY

ORIGINATOR

WDM NETWORK MANAGEMENT

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

1 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

2 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.15.2 Not Applicable Extension on 1686WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


59
2.15.3 Adding an optical MUX/DEMUX on 1696MS (Metro Span) . . . . . . . . . . . . . . . . . . . . . . .
60
2.15.4 1640WM/1686WM OADM connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
60
2.15.5 1696MS OADM connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
60
2.16 Automatic upload of OADM connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
2.17 Display of the correlation between WDM world and SDH world . . . . . . . . . . . . . . . . . . .
63
2.18 Create WDM worldSDH world correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
2.19 Connect / Disconnect Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
2.19.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
2.19.2 Creating a connection by means of the Connectivity tool . . . . . . . . . . . . . . . . . . . . . . . .
68
2.19.3 Deleting a connection by using the connectivity tool . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
2.19.4 Connectivity Tool: Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
2.20 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
2.20.1 1696MS, 1696MSC. Creating an och passthrough between two mux/demux. . . . . .
85
2.20.2 1696MS, 1696MSC. Connecting 1696 to a colored SDH interface : phantom MCC board
instantiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
2.20.3 All Nes. Instantiating a phantom board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
2.20.4 1696MS, 1696MSC. Configuration of OPC (optical protection card). . . . . . . . . . . . . . .
85
2.20.5 1696MS, 1696MSC. Configuration of 1696MS to have 1354RM upload connectivity working well . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
2.20.6 1696MS. Upgrading 1696MS to add new lambdas management without loss of trafic 86
2.20.7 1696MS, 1696MS. Use of SPV_F_1310_1550 and SPV_FC board. . . . . . . . . . . . . . .
86
2.20.8 1696MS, Board MCC1 (SDH) and MCC2 (SDH). PM: change monitoring point from adjacent boundary clientctp to boundary clientctp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
2.21 Remove optical physical connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
88
2.22 Insert OADM in an optical network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
2.23 Trace Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
90
2.24 1660OADM coarse WDM management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
2.24.1 Wavelength management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
2.24.2 Coarse OPS physical connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LIST OF FIGURES AND TABLES


FIGURES
Figure 1. SDH/WDM layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. OTN multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Line Terminal Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. ILA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. OADM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. OADM repeater configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Backtoback Regenerator configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. OSNCP protection in point to point links with OCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. OTN layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Example of real network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Physical network representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Full view: physical plus logical views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. WDM network interworking with SDH network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. OTS Physical Connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. OTS Physical Connection Structure detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Usage indicator of the LC: trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Usage indicator: raw connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Optical Path name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Optical Path routing view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. OPS Physical Connection Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. WDM port attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Port WDM SDH Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. SDH Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Connection type Generic Digital Client/WDM interworking . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Connection type SDHWDM interworking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Create Connectionstep 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. OTS connection detail windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Payload configuration of the raw connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Payload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. OTSCON: Configuration: Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Optical path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Physical Connection Structure detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Raw connection routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Complete raw connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Connectivity Management: Remove from Raw Connection . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Raw connection splitted into two parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Connectivity management: Add to Raw Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Trail routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Trail: Configuration: Payload: Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. 1640 Port structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. OTS physical connection payload button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. OTS physical connection payload dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Physical Connection Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Port Structure: Bundle OCHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. WDM path: Interworking: SDH Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. SDH Physical Connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Optical Physical connection view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. RawConn:Configuration: Convert in Path/Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Convert in Path/Trail report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. Optical Physical Conn structure: optical (client) path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

SC. 6: WDM

9
10
11
12
12
13
13
14
15
16
17
17
27
28
29
30
31
32
33
34
35
36
37
39
40
41
42
43
44
44
45
46
48
50
51
52
53
54
55
56
57
58
59
61
63
64
64
65
66
67
It. 01

3AL 61348 AA AA
92

3 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 6: WDM

69
70
71
72
73
74
74
75
76
77
78
79
80
81
82
83
88
89
91

It. 01
3AL 61348 AA AA
92

4 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 51. Connectivity Tool: Connect step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 52. Connectivity Tool: Connect step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 53. Connectivity Tool: Connect step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. Connection create report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. pathWDM: Configuration: Conf. State Modification: Deimplement . . . . . . . . . . . . . . . . . .
Figure 56. Warning dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. OCH trail remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. Raw connection routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. Configuration: Connectivity tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. Connectivity tool. Step 1: Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. Connectivity tool. Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. Connectivity tool. Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. Raw connection routing display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. Connectivity tool: Modify step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. Connectivity tool: Modify step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. Connectivity tool: Modify step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. Physical connection structure (96_UP to 96_MID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. Node 96_MID to be inserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. Coarse signal in the optical network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1 INTRODUCTION
1.1 Introduction
This document aims at introducing the 1354RM WDM working environment, to the users of the system,
and explain the existing 1354RM functionalities

1.2 Target audience


This Manual is intended for RMWDM users.

1.3 Document structure


This section covers the following topics:

ED

WDM Technology

WDM Navigation

WDM Network Create

WDM Network modify

Convert path/trail

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

5 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

6 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2 WDM TECHNOLOGY
The introduction of WDM technology in transport networks is the first step toward Optical Transport Networks (OTN).
The evolution of WDM Network Elements (NE) from line systems with fixed wavelength add/drop capability to more flexible equipments (Optical Add Drop Multiplexers OADMs and Optical Cross Connect
OXC ) will allow the manipulation of optical channels as time slots are currently managed in the TDM networks.
Since the availability of a network management system is a key feature for transport networks, the current
NML OS set of applications (packaged into the 1354RM product) has to face this new technology by
introducing new functionality.
These functionalities are based on preOTN concepts, i.e. without the management of the overhead and
functionalities described in ITUT G.709 Recommendation.
ACHRONYMS
ATM

Asynchronous Transfer Mode

CAP

Connection Access Point

CTP

Connection Termination Point

DVB

Digital Video Broadcasting

EML

Element Management Layer

ESCON

Enterprise Systems CONnection

FDDI

Fiber Distributed Data Interface

FEC

Forward Error Correction

IPC

InterProcess Communication

MIB

Management Information Base

NAP

Network Access Point

NE

Network Elements

NML

Network management Layer

NML

Network Management Layer

OADM

Optical AddDrop Multiplexer

OCC

Optical Channel Carrier

OCh

Optical Channel

OCG

Optical Channel Group

OH

OverHead

OMS

Optical Multiplex Section

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

7 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

OTM Overhead Signal

OPS

Optical Physical Section

OS

Operation System

OSC

Optical Supervisory Channel

OTH

Optical Transport Hierarchy

OTM

Optical Transport Module

OTN

Optical Transport Network

OTS

Optical transport Section

OXC

Optical CrossConnect

RC

Raw Connection

RSOH

Regeneration Section OverHead

SDH

Synchronous Digital Hierarchy

SNCP

SubNetwork Connection Protection

SONET

Synchronous Optical NETwork

STMn

Synchronous Transfer Mode (n = 1, 4, 16, 64)

TDM

Time Division Multiplexing

TE

Transport Entity (generic term for Path or Trail in 1354RM)

TP

Termination Point (generic term for CTP or TTP)

TTP

Trail Termination Point

WDM

Wavelength Division Multiplexing

WLA

WaveLength Adapter

ED

01

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

OOS

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

8 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.1 WDM Layer Overview


The Optical Transport Network is seen, at NML level, as a support for the transport of the digital signals
managed at a client level.
In the Server/Client paradigm, the SDH layer (from now onwards we will use the term SDH to denote both
SDH and SONET hierarchies) is client of WDM layer.

Figure 1. SDH/WDM layering

2.1.1 WDM Terminology


The WDM signal is composed by the multiplexing of client signals (e.g. SDH at STMn rate) onto the same
optical fiber. Each signal is transported into a welldefined wavelength, usually identified as lambda .
As an example, up to 80 channels (+ 1 supervisory channel, when supported) may be currently transported
on the same optical fiber (the New Generation Platform will be able to carry up to 160 wavelengths).
The digital client signal transported at WDM layer is identified in the OTN network by Client end points
of the paths managed at WDM level (named Client path see Figure 1).
A Client path maps a logical physical connection in the SDH network in the WDM layer: typically the Client path supports several SDH paths crossing the OTN network.

1AA 00014 0004 (9007) A4 ALICE 04.10

The Client path may also represent the transport endservice delivered by an operator, if only the OTN
network is managed by the NML OS or the specific terminating non DWDM NEs are managed by another
NML OS.
The Client path concept is therefore a way to define the generic server provided by the optical transport network. NOTICE THE THE TRUE CLIENT IS THE SDH PATH.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

9 / 92

The WDM hierarchy represents the stages required by a digital client signal that has to be transported at
WDM layer:

The signal must be colored (i.e. has to be transmitted with the wavelength that has been assigned
to its channel) .
This operation is performed by specific boards named transponders or WLA (WaveLength Adapter)
This operation may be not necessary if the signal source is already coloured in the client equipment
through colored interfaces (specific transmission boards).
The colored signal belongs to the Optical Channel (OCh) layer

The Optical Channels that compose the WDM signals are multiplexed into the WDM signal.

The multiplexed signal belongs to the Optical Multiplex Section (OMS) layer

The signal is transported along the optical fiber until it is extracted to upper layers.

The signal interfaced with the optical medium belongs to the Optical Transport Section (OTS) layer

Figure 2. OTN multiplexing


As for the SDH network, the modeling of the OTN network in the NML OS is based on the concepts of End
Points (e.g. Ports), Physical Connection, Link Connection, Trail, and Path

1AA 00014 0004 (9007) A4 ALICE 04.10

A schematic representation of the layering of a Client path into the OTN network is shown in Figure
Figure 9. on page 15.
When a single Optical Channel (without supervisory channel) is transported along the optical fiber, the
OMS layer is skipped and the OTS layer is named OPS0 (Optical Physical Section 0).

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

10 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

When a SDH network is the client of the OTN network, the WDM Client path is the service provided
by the OTN to the SDH network, which will look at it as a physical connection joining the two SDH NEs
at the extremities of the WDM section (see Figure 1).

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

By extension of this concept, related to monolambda signals, in WDM layer the ports of WLA boards are
identified as OPS ports and the physical connections connecting SDH NE to WDM NE are identified as
OPS physical connections
2.1.2 WDM Equipments managed by 1354RM
1354RM is the Alcatel NML OS. It currently manages the following WDM equipments:

1640WM
1686WM
1696MSPAN
OCP
1660OPS

2.1.3 WDM NE configurations


1640WM, 1686WM, 1696MSPAN
These NEs may be equipped in four basic different configurations:

Line Terminal

The Line Terminal is where the client digital signal access/exit the OTN network and is multiplexed/demultiplexed into the OTS level signal.
WLA boards are not necessary if the input signal is already colored

Figure 3. Line Terminal Configuration

1AA 00014 0004 (9007) A4 ALICE 04.10

In Line Amplifier (ILA)

The In Line Amplifier configuration (also named as In Line Repeater) provides an optical amplification of
type OTS signal without any regeneration of the original signal.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

11 / 92

Optical AddDrop Multiplexer (OADM)

The OADM configuration offers the possibility of inserting/extracting wavelength from the optical payload.
The number of wavelength added/dropped in OADM NEs is limited (typically 48 wavelengths)

Figure 5. OADM configuration

1AA 00014 0004 (9007) A4 ALICE 04.10

The OADM may host also an amplification section. In this case the NE configuration is defined as OADM
Repeater.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

12 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 4. ILA configuration

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 6. OADM repeater configuration

Backtoback Regenerator

Two NEs may be put in backtoback configuration to offer regeneration capability for the OTS signal in
case of exceeding attenuation of the signal along the optical section.
This configuration allows to compensate the signal attenuation, the chromatic dispersion and to regenerate the signal (2R or 3R).
In addition an unlimited AddDrop capability is granted by this configuration

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 7. Backtoback Regenerator configuration


1660 OCP
These NE is dedicated to protection for WDM transmission networks.
They are pure switching equipments operating at the channel level (i.e. on a per wavelength basis).

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

13 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

OCP (Optical Channel Protection) offers the opportunity of introducing OSNCP configuration in OTN networks where the WDM NEs dont support this feature (e.g. 1686WM and 1640WM).

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 8. OSNCP protection in point to point links with OCP

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

14 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.2 Layering

The following figure shows the relationship between the network components and the model

Figure 9. OTN layering

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

15 / 92

2.3 Network construction

Upload from the EML OS the information about NEs and Ports

Definition of the physical connections between the NEs (Network topology)

Physical connection types are:


SDH (SDH port to SDH port)
OPS (SDH NEs to WDM NEs and transponders in WDM NEs)
OTS (OTS port to OTS port)
The introduction of the OPS physical connections implies that the ports in SDH NEs may be involved in
two different connections at the same time (each connection belonging to a different network view)
Because of this reason, ports in SDH NEs are fictitiously split into two objects when they are involved in
OPS connections: a second port of OPS type (a copy of the original SDH port) is used to setup the OPS
connection with the WDM NE.
In WDM NEs OPS ports are related to WLA boards equipped in the NE or, in case of colored interfaces,
to the input/output board accepting Optical Channels (Mux/Demux boards).
1354RM offers the capability to manage SDH and WDM network domains both in integrated or separate
configuration (i.e. using two instances of RM).
In case of integrated management, a flat representation of the managed network is offered to the users:
both SDH and WDM NEs are shown in the same map.

2.4 Integrated management map view


An example of real network layout is shown in the following figure

Figure 10. Example of real network

1AA 00014 0004 (9007) A4 ALICE 04.10

A set of ADM NEs connected through an OTN network section, supported by WDM NEs.
The representation of this network is:

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

16 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The network construction activity is split in the following phases:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 11. Physical network representation


Taking in account the splitting of the network representation in two different levels (SDH and WDM), the
full view of a cohosted SDHWDM network will offer this representation of the network topology:

Figure 12. Full view: physical plus logical views


Only the connections in color represent physical links (respectively OPS and OTS physical connection).
The gray connection is in practice a logical SDH connection ( conventionally called SDH physical connection)

1AA 00014 0004 (9007) A4 ALICE 04.10

This connection is anyway the only connection seen by the NML OS at SDH network level and RM routing
algorithm will refer it when an SDH path crossing the two SDH NEs will be allocated.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

17 / 92

In case of fully flexible OTN NEs, 1354RM can provide the automatic routing algorithm for path provisioning. Circuit provisioning means the creation of the SERVER OPTICAL PATH, conventionally called Client path, taking into account of the notflexible NEs, including NE internal cabling.
The following sequence depicts a simple example of set up the OTN Network layout and on how Client
path is identified by RM.

1)

In the initial situation NEs are stored in the RM MIB.

RM has no knowledge of the fixed cross connections defined inside WDM NEs.

2)

Define the connections between the WDM NEs, ( OTS connection )

As soon as a physical connection is created, the TPs at the extremities are added in RM MIB.

The RM retrieves the fixed cross connection in the WDM NE creates an Incomplete Connection.
At this point the infrastructure supporting the client level services is ready.

1AA 00014 0004 (9007) A4 ALICE 04.10

3)

ED

01

The RM operator creates the first OPS connection between one of the SDH NE at the extremities of the Client Path and the adjacent WDM NE.

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

18 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.4.1 Circuit provisioning

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

RM retrieve a second fixed cross connection, creates a second Incomplete Connection and merges it with
the previous one. The connection is still incomplete
4)

At last, an OPS connection is created at the other extremity of the WDM transport link. Also in
this case the objects up to the Client Nap are created into the SDH NE.

RM recognizes that the connection is now complete (ending on two Client NAPs) and transforms it in a
Client Path.

2.5 Raw connection


SDH NEs offer in general flexible crossconnections: internally to an NE any TP may be connected to
another TP (with some limitations depending on NE type).
Flexible crossconnections are managed through a connectivity matrix that is controlled by external management OS: Craft Terminal, EML OS (1353SH), NML OS (1354RM): they are downloaded to the target
NE.
WDM NEs currently managed by 1354RM offer a very limited flexibility in defining circuits at OTN level:
with few exceptions in 1696MSPAN, all the crossconnections defined in the NEs are either fixed or semi
fixed (e.g. the passthrough connections in OADM NEs preset for channel Add/Drop).
An external management OS cannot control the fixed connections: they are uploaded by 1354RM from
the WDM NEs deployed in the managed network.
The Client path definition mechanism is based for 1354RM on the concept of Raw Connection (RC).
A Raw Connection represents a partial connectivity or connection that cannot be mapped in a path or
in a trail. It is composed by at least a link connection and a crossconnection and is terminated by two (or
more) TPs (CTP, NAP, CAP).
Raw Connections may exist both in the SDH and OTN network: at OTN network anyway they play a key
role in circuit design.
When a physical connection is created at OTN network level, during the network construction phase, the
Trails and Link Connections representing the WDM layering are automatically created inside the RM MIB.
The new link connections are analyzed by RM and correlated to the crossconnections stored in the MIB
to identify, if possible, new RCs. It may happen that two preexisting RCs are merged in a longer RC as
a result of this analysis.
As far as the RC is ended by at least one CTP, the RC is defined as incomplete.

1AA 00014 0004 (9007) A4 ALICE 04.10

When both ends of the RC are not CTPs, the RC is defined as complete.
If both the ends of a complete RC are of the same type, the RC is automatically promoted to optical path
(if end points are NAPs) or trail (if end points are CAPs).

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

19 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

A Client path is terminated by two Client NAPs, contained in the SDH NEs (virtual, in case) accessing the
WDM layer services.

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

20 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.6 Data service VC4v Management (4xANY board)


The data service management is a real added value for metro networks integrated with the regional and
backbone SDH and DWDM networks.
1696ms provides 4xANY card, which can carry both:

SDH/SONET STM1 or STM4 (this service can be inserted/extracted only in 4xANY cards)

Data services,

using the VC4 virtual concatenation.


The 4xANY board enables to multiplex/demultiplex in the time domain up to four low bitrate signals (client data streams) in a single signal at 2.5 Gb/s (STM16).
The client data rates that the unit can manage are:

Table 1 4xANY board: supported client data streams and rates


The virtual concatenation management is managed by 1354RM both in SDH and DWDM services (Gbit
Ethernet may be managed by both OMNS and DWDM NEs).
A Gbit/s Ethernet service can be initiated/terminated in DWDM network crossing the SDH network (or vice
versa): the supporting Virtual concatenated paths are coherently managed through the two type of transport technology.
1696mspan, equipped with the 4xANY card, will act as a SDH line terminal with four ports, according to
the board capabilities. The STM16 port of this 1696mspan can be connected to an OMSN (1670SM)
or to an OMSG).

1AA 00014 0004 (9007) A4 ALICE 04.10

The board allows also to multiplex some combination of different client signals:
3 x (FDDI or FE or DV or ESCON or STM1) + 1 x STM4
2 x (FDDI or FE or DV or ESCON or STM1) + 2 x STM4
2 x (FDDI or FE or DV or ESCON or STM1) + 1 x (FC or GbEth)
1 x (FDDI or FE or DV or ESCON or STM1) + 1 x STM4 +1 x (FC or GbEth)

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

21 / 92

The incoming elementary alarms from the WDM equipments are managed by 1354RM according to the
same approach defined for SDH networks:

Collection of elementary alarms.

Correlation of the elementary alarms to transport entities.

Generation of transport alarms (including operational state change on transport entities)

Transport alarms are raised for OCH trails, OMS trails, physical connections (OPS and OTS) and Client
paths . Operational state is managed for the transport entities raising alarms and for the link connections
(OCH and Client).
Alarms on OMS Trails and OTS Physical Connections affects the whole transport service at WDM layer.
Alarms affecting OCh Trails and OPS Physical Connections impact a single channel (i.e. one lambda)
of the transport service.
Some counters have been created in the 1330AS counter summary to take in account the new alarms :

MS/OMS TRAIL: it reports all the alarms on MS/OMS Trails

HO/OCH TRAIL: it reports all the alarms on HO/OCh Trails

Other counters, even if keeping the name used when pure SDH network were managed by 1354RM collect
the alarms related to both the SDH and WDM entities:

PATH: it reports all the alarms on paths

PHYSICAL LINK: it reports all the alarms on Physical Connections

EML: it reports all the processing error alarms affecting the EML domain

It has to be pointed out that the alarms raised by SDH NEs impact only the SDH part of the managed network, i.e. even if SDH NEs may appear in WDM network views, their alarms are not processed by the WDM
manager
This is the default customization defined for AS counters at 1354RM installation time: the operators are
allowed to further customize the counters (e.g. so that alarms are reported on a per layer basis).

2.8 PRC module


Specific WDM network topologies, based on OPS NEs are managed by 1354RM by means of an additional
module named PRC (Protection and Restoration Combined).

1AA 00014 0004 (9007) A4 ALICE 04.10

Citytocity networks are protected via a mechanism based on an automatic endtoend 1+1 path
protection (SNCP) combined with a restoration application anticipating additional failures and identifying
secondary optical SNCP protected paths
The PRC module is in charge to perform such a restoration activity. This activity is performed by forcing
the OPS NEs switch positions (see Figure 9) accordingly to the alarms collected from the network.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

22 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.7 Fault Management

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Since the PRC module is not able to get from the supervised OPS NEs all the information required for the
management of the restoration application, an interface is made available by 1354RM reporting a subset
of SDH transport entity alarms (affecting physical connections and MS trails) to the PRC module.
The interface is based on IPC queue mechanism.
The alarms reported by RM are internally processed by a specific module of PRC that triggers the force
switch activities accordingly.

2.9 Performance Monitoring


The introduction of a complete management of Performance Measurement (PM) in OTN networks is related to the introduction of optical NEs compliant to Rec. G.709
Currently, the WDM NEs managed by 1354RM support only a limited set of monitorable information:

B1 byte: a byte of the RS overhead of SDH signal (RSOH) allocated for both error and PM monitoring.

The basic concepts of PM management in RM (definition of a measure, correlation of TEs and TPs to it,
graphic and report interface) are kept unchanged for WDM.
The TE correlated to a measure will be a Client path.

2.10 B1 based PM
The B1 byte, as part of the RSOH will be accessible only in 3R transponders, where the overhead contents
may be accessed and analyzed.
B1 measurement may be performed for both (sometimes in a mutual exclusive way) the incoming (ingressing) and outgoing (egressing) SDH/SONET signal.
The monitoring of the incoming signal permits to detect errors occurred in the section between the current
DWDM NE and the adjacent SDH/SONET NEs.
The monitoring of the outgoing signal permits to detect errors occurred in the DWDM Domain.

1AA 00014 0004 (9007) A4 ALICE 04.10

Although this kind of measurement is unidirectional, it could be used as acceptable approximation of the
QoS of unprotected optical path in preOTN context.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

23 / 92

In the following some simplified definitions of the resources managed by 1354RM (formal descriptions of
a lot them are available in G.803, G.805)
2.11.1 Topological Components
Network: It represents the highest level of partitioning managed by 1354RM.
A path that crosses two Networks cannot be managed by 1354RM as a single transport entity (i.e.
it will be represented with two paths)

Subnetwork: It represents the second level of partitioning (i.e. a Network can be composed by more
than one subnetworks)

ET (Elementary Topology): It represents the third level of partitioning (i.e. usually ETs are contained
in subnetworks). The elementary topologies can be linear links, meshed subnetworks, rings)

Node: It represents a Network Element.

Physical Connection: It is the logical representation of fibers and coaxial cables, between network
ports
Example:
The physical connection delimited by to network ports, e.g. two OTS physical ports.
2.11.2 Physical Resources

EML Domain: It represents one EMLIM component of 1353NM.

NE: It represents a physical NE.

Network port: It represents the physical port where e.g. the fiber is connected.

Example:
A STM16 port of a SDH NE.
An OTS port of a DWDM NE.

Access port: It represents the physical port where the client signal is added/dropped.
Example:
A PDH port of a SDH NE.
The physical port of a Transponder in DWDM NE.

2.11.3 Transport Entities

Section: It is a trail at Multiplex Section Layer.

1AA 00014 0004 (9007) A4 ALICE 04.10

Example:
MSTrail between two STMn ports of two adjacent SDH NEs.
OMSTrail between two OTS ports of two adjacent DWDM NEs.

HO (Higher Order) Trail:


An HO Trail is a HO route (e.g. infrastructure pipe) between two (either adjacent or not) SDH
NEs. It is delimited by two CAPs (Client Access Points) and it can be configured to carry LO traffic.

Path: A path (can be at either HO or LO path layer) is a route established in the SDH/SONET network.
It is delimited by NAPs (Network Access Points).
Example:

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

24 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.11 Acronims

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

A VC12 path delimited by two VC12 NAPs


A Client path delimited by two Client NAPs (RSTTP for SDH signals)

Link Connection: It is an arc delimited by the two CTPs with the same timeslot and it is supported by
the same server Trail
Example:
An Au4 Link Connection is delimited by two corresponding AU4 CTPs and is supported by a MS
Trail.
An OCh Link Connection is delimited by two corresponding OCH CTPs and is supported by an OMS
Trail
2.11.4 Reference Points

NAP (Network Access Point): It terminates a path; one Network Access Point is associated to one
access port.
Example:
A VC3 NAP (can be called also VC3 TTP) is associated to a 34 Mbit/s port (or a 45 Mbit/s port)
and it terminates VC3 path).
A Client NAP is associated to an RS TTP of a SDH signal and it terminates a Client Path

CAP (Client Access Point): It terminates a HOTrail; one CAP can support Lower Order CTPs.

Example:
A VC4 CAP can support TU12 and/or TU3 CTPs (depending how the payload has been configured) it terminates VC4 HOTrail).
An OCH CAP supports a channel in OTS signal and terminates an OCH Trail

1AA 00014 0004 (9007) A4 ALICE 04.10

CTP (Connection Termination Point): It is an intermediate point and, depending on NE capabilities,


it can provide nonintrusive monitoring functionalities in term of alarms and Performance Monitoring.
Example:
An AU416c CTP delimits an AU416c link connection.
An OCH CTP delimits an OCH link connection

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

25 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

26 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.12 WDM Network


Figure 13. shows an example of WDM network interworking with SDH network. Notice that SDH connections are black, or take the color of the most serious alarm, while WDM connections ( OPS and OTS ) are
depicted with a different color. The navigation of OTS conn. and OPS con is described in the paragraphs
which follow.
SDH CON

OPS CON
OTS CON
SDH NODE
WDM NODE

Legenda:

OTS ( Optical Transmission Section ) is used for


connections between different WDM nodes.
OPS ( Optical Physical Section ). in this picture is
used for connections originated on SDH nodes
and terminated to a WDM node.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 13. WDM network interworking with SDH network.

2.12.1 OTS conn. navigation


SEQUENCE

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

27 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

Click twice on a OTS physical connection. The physical connection list is displayed.

b)

Select the WDM physical connection and click on Physical Connection Structure button. The OTS
Physical connection structure is displayed. See Figure 14. herebelow.

Figure 14. OTS Physical Connection structure

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

28 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 13. shows an example of WDM network interworking with SDH network. To navigate from Netview
map:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

OPTICAL PHYSICAL CONNECTION WDMOTS

OPTICAL NODE

OPTICAL NODE
TRAIL WDMOMS

PORT WDM OTS

LC WDM

LC WDM
RAW CONNECTION

PATH WDM

TRAIL WDM OCH

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 15. OTS Physical Connection Structure detail

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

29 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

TRAIL

Figure 16. Usage indicator of the LC: trail

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

30 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 17. Usage indicator: raw connection

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

31 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 18. Optical Path name

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Selecting the path and clicking on Routing display button, it is possible to display the path routing
view. See below figure.

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

32 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 19. Optical Path routing view

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

33 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.12.2 OPS conn. navigation

Figure 13. shows an example of WDM network interworking with SDH network. To navigate from Netview
map:
a)

Click twice on a OPS physical connection. The physical connection list is displayed.

b)

Select the WDM physical connection and click on Physical connection structure button. The OTS
Physical connection structure is displayed. See figure herebelow.
PORT WDM SDH CLIENT

PORT WDM OP SECTION

SDH PHYSCON

LC WDM

WDM PHYSCON

PATH WDM
TRAIL WDM OCH
Figure 20. OPS Physical Connection Structure

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Figures which follow show the attributes of the WDM port, equipped on the WDM node and of the
WDM port, shadow of the SDH port equipped on the SDH node

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

34 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 21. WDM port attributes

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

35 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 22. Port WDM SDH Client

d)

ED
Click twice on the SDH Physical Connection icon; the SDH Physical connection structure is displayed.

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

36 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

WDM PATH

SDH TRAIL

ED

01
PAYLOAD

Figure 23. SDH Physical Connection

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

37 / 92

2.13 WDM network create

SEQUENCE
a)

Network Create

b)

1st level Subnetwork Create

c)

2nd level Subnetwork Create

d)

Create WDM NE

NOTES

the connection type for WDMNE to WDMNE is WDM.


If you select connection type=WDM, you will further select the WDM connection type between
OPS and OTS, where:
OTS ( Optical Transmission Section ) is used for connections between different WDM nodes.
OPS ( Optical Physical Section ) is used for connections within the same WDM node, originated
and terminated to the same node.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

the connection type for Generic Digital Client/WDM interworking is selected when connecting
to a virtual NE which represent Ethernet equipment.

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

38 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

WDM network create is similar to the creation of the SDH network. Namely the involved steps are:

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 24. Connection type Generic Digital Client/WDM interworking

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

39 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 25. Connection type SDHWDM interworking.

the connection type for SDHNE to WDMNE is SDHWDM interworking.

NOTE. The rate of the SDH to WDM transponder ( STM1 / STM4 / STM16 ) is previously set at
1353NM level.
NOTE
The rate of the SDH to DATA transponder ( STM1 / STM4 / STM16 ) is previously set at
1353NM level.
LIMITATIONS FOR SDH COLOURED INTERFACE

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

Before creating a connection between SDH equipment and 1696 equipment, it is required
to create on NM a (dummy) MCC board tuned to the desired lambda. Then execute a NE
synchronize from RM.

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

40 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

e)

Before creating a connection between SDH equipment and 1640 equipment, it is required
to create on NM a (dummy) TRB201 board tuned to the desired lambda. Then execute a
NE synchronize from RM. This operation is not required if the real board is present in the
equipment.

Create Connection. (step1 ) The example which follows details the WDM OTS connection. Start
the Create Connection wizard from the originating Node. Step 1 of the wizard allows to select connection type= WDM and WDM connection type=OTS. See following figure. Click on Next button.
connection type=WDM

WDM connection type=OTS

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 26. Create Connectionstep 1


f)

Create connection step2 allows to select originating and terminating port to connect.

g)

Create connection step3 contains the icons of the two ports to be connected. Click on Finish button
to confirm the creation. The OTS connection is created.

h)

Implement the OTS physical connections. See Figure 30. on page 44.The optical client paths are
automatically discovered.

N.B.

ED

In case an OTS physical connections does not iclude its OCHtrail, as in the following figure,
where a raw connection is present, it is required to execute the payload setting of the raw connection.
01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

41 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

RAW CONNECTION

OCHTRAIL

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 27. OTS connection detail windows.


With reference to Figure 28. on page 43, select the raw connection and click on functional button PAYLOAD CONFIGURATION. The Payload Configuration dialog box is presented. See
Figure 29. on page 44.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

42 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CLICK ON PAYLOAD CONFIGURATION

RAW CONNECTION

Figure 28. Payload configuration of the raw connection.

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

43 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SETUP
BUTTON

Figure 29. Payload Configuration

1AA 00014 0004 (9007) A4 ALICE 04.10

Click on button SETUP. The raw connection changes into an OCHtrail. At this point it is possible to implement the physical connection. See Figure 30. on page 44.

Figure 30. OTSCON: Configuration: Implement

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

44 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LOGICAL SDH CONN

Figure 31. Optical path

1AA 00014 0004 (9007) A4 ALICE 04.10

i)

ED

Supervision: Network Implement. This causes the creation of the following objects: trail WDMOMS,
LC WDM, raw connection, trail WDMOCH path WDM. See below figure.

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

45 / 92

OPTICAL NODE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

OPTICAL PHYSICAL CONNECTION WDMOTS

OPTICAL NODE
TRAIL WDMOMS

PORT WDM OTS

LC WDM

LC WDM
RAW CONNECTION

PATH WDM

TRAIL WDM OCH

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 32. Physical Connection Structure detail

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

46 / 92

2.14 Raw Connection

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

DEFINITION
The raw connection is a set of connections, structured in pointtopoint or pointtomultipoint arrangement. These connections are link connections ( lc ) and connections in topology ( connInTopol ), belonging
to the same layer.
The raw connection is terminated generically to a CAP, CTP, NAP. The raw connections between two CAPs
( Connection Access Points ) and the raw connections between two NAPs ( Network Access Points ) are
said complete raw connections; in particular the raw connection between two CAPs is a trail, while a
raw connections between two NAPs is a path.
TYPE OF CONNECTION
Within the NE the following types of connections may be present:

permanent ( fixed ). Cannot be removed from NE.


In particular, when an optical physical connection is implemented, the system discovers all related
fixed connections ( one per each optical link connection ). Two levels are available:

OCh ( Optical Channel )

Client

semifixed. It can be modified, cannot be removed ( e.g. a passthrough connection ). These are
automatically uploaded and can be modified by means of the Connectivity Tool.

flexible. It can be created, modified, removed

1AA 00014 0004 (9007) A4 ALICE 04.10

An example of routing display of a raw connection is shown in the figure which follows.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

47 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 33. Raw connection routing display

1AA 00014 0004 (9007) A4 ALICE 04.10

GENERAL OPERATION
a)

During the implementation phase, the system uploads ( discovers ) the permanent ( fixed ) connections and constructs the raw connections, by taking into account the uploaded connections.

b)

The raw connection userlabel is assigned automatically and makes use also of special characters
( e.g. $ )

c)

Complete raw connections are automatically transformed to trails and paths, if all involved link connections are implemented.

WDM PATH DEALLOCATE

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

48 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

a)

The deallocate of a path causes the identification of the permanent ( fixed ) connections and the re
construction of the raw connection

CONSTRAINT
The raw connection can be used as constraint ( the only option Use Main is available )
RAW CONNECTION MANAGEMENT
The raw connection can be extended / shortened / splitted / promoted to path or trail / deleted.
By inserting new fixed connections within the NE, new raw connections are obtained.
NOTE 1
The partitioning concept is no longer applicable to raw connection
NOTE 2
It is not possible to implement manually paths/trails derived from raw connections. The user must configure the involved physical connection or configure a related trail in use by the path to obtain the automatic
implementation of the transport object.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

49 / 92

A raw connection completed is a CAP to CAP connection at OCH level or a NAP to NAP connection at
client level.
An example of complete raw connection is shown in the following figure.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 34. Complete raw connection

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

50 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.14.1 Completed raw connection

REMOVE A CONNECTION IN TOPOLOGY

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

a)

To remove a connection in topology from a complete raw connection, point to the connection in topology and issue Connectivity Management: Remove from Raw Connection

Figure 35. Connectivity Management: Remove from Raw Connection

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

The raw connection is split into two parts. See figure which follows

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

51 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 36. Raw connection splitted into two parts


ADD A CONNECTION IN TOPOLOGY TO A RAW CONNECTION

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

To add a connection in topology to a raw connection, point to the connection in topology and issue
Connectivity Management: Add to Raw Connection. See figure which follows

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

52 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 37. Connectivity management: Add to Raw Connection

b)

ED

The raw connection is transformed in a trail. See following figure.

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

53 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 38. Trail routing display

The client path is recreated, if any.

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

54 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.15 Optical Network Modify


2.15.1 Adding a transponder on 1640WM
SCOPE
The scope of this procedure is to add a new transponder to a 1640WM optical equipment.
CONDITIONS
The 1640WM Network Element is RM assigned and the network is implemented
SEQUENCE
a)

From 1353NM execute the provisioning of the WLA board.

b)

From RM execute a global download on the NE involved.


Verify that the ochctp (one per each lambda) passes from unequipped to equipped. From the Port
Structure view the unequipped ochctp are displayed. Notice that the attribute Equipped Type of an
equipped ochctp is equal to Equipped.
Figure which follows shows an example of 1640 Port Structure.

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

In case on a trail has been issued the command Configuration: Payload: No Client, it is
possible to modify the attribute to Client. See following figure.

Figure 39. Trail: Configuration: Payload: Client

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

55 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 40. 1640 Port structure

c)

ED
Execute the payload configuration of the OTS physical connection. See following figure.

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

56 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 41. OTS physical connection payload button

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

57 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 42. OTS physical connection payload dialog box

1AA 00014 0004 (9007) A4 ALICE 04.10

Verify that the connectivity objects ( LC, trail..) have been correctly created. See following figure.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

58 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 43. Physical Connection Structure

2.15.2 Not Applicable Extension on 1686WM

THIS PROCEDURE IS NOT APPLICABLE FOR 1686WM

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

59 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.15.3 Adding an optical MUX/DEMUX on 1696MS (Metro Span)

The scope of this procedure is to increase the size of the lambdas in the 1696WM optical equipment, i.e.
an optical MUX/DEMUX is added.
CONDITIONS
The 1696WM Network Element is RM assigned and the network is implemented
SEQUENCE
a)

From RM execute a global download on the NE involved.


Verify that the ochctp (one per each lambda) passes from unequipped to equipped.

b)

Execute the payload configuration of the OTS physical connection.


Verify that the connectivity objects ( LC, trail..) have been correctly created.

2.15.4 1640WM/1686WM OADM connectivity


Optical equipments 1686WM and 1640WM can be configured as OADM Repeaters. In this case, in each
direction (east/west):

eight channels can be dropped/added for 1686WM equipment

four channels can be dropped/added for 1640WM equipment

The remaining channels are passed through, i.e. when creating an OADM board, the OCHCTP on the
west side and the corresponding OCHCTP of the same lambda on the east side are passthrough connected. This is called default connectivity.
2.15.5 1696MS OADM connectivity

1AA 00014 0004 (9007) A4 ALICE 04.10

No default connectivity is provided by 1696WM equipment. Drop/insert and pass/through connections can
be created and removed. This connections can be considered as non flexible.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

60 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE

2.16 Automatic upload of OADM connectivity

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

During the physical connection implementation all ochctps are created.


If the ctp is present on the NE, it is marked as equipped, otherwise is marked as bundle=ochctp not present on the NE but the associated lambda is passed through.
Equipped OCHCTPs. Connections involved are marked as semifixed by RM
Bundle OCHCTPs are put in fixed passthrough connections in RM, only if the corresponding OCHCTP
with the same lambda on the other OTS port is Bundle. See following figure. The icon of a bundle OCH
is marked by a B letter.

Figure 44. Port Structure: Bundle OCHs

1AA 00014 0004 (9007) A4 ALICE 04.10

During WDM network implementation, OCH LCs are created, according to the following cases:
OCHCTP west/east TYPE

OCHCTP east/west TYPE

CREATE LC

EQPD

EQPD

YES

EQPD

BUNDLE

YES

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

61 / 92

NOT EQPD

NO

BUNDLE

BUNDLE

YES

BUNDLE

NOT EQPD

NO

NOT EQPD

NOT EQPD

NO

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

NOT EQPD (not equipped) means ochctp present in RM but not in NE due to the hardware
configuration.

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

62 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

EQPD

2.17 Display of the correlation between WDM world and SDH world

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE
a)

Point to the wdm path icon and issue the Interworking: SDH Connection popup menu. The SDH
physical connection structure is displayed. See Figure 46. herebelow.

Figure 45. WDM path: Interworking: SDH Connection

1AA 00014 0004 (9007) A4 ALICE 04.10

Note that the client path icon is marked by a smal raw connection mark. See figure herebelow.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

63 / 92

raw connection mark

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CLIENT PATH

Figure 46. SDH Physical Connection structure

1AA 00014 0004 (9007) A4 ALICE 04.10

On the other hand, in the Optical Physical connection view , the client path icon is marked by a raw connection mark.

Figure 47. Optical Physical connection view

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

64 / 92

2.18 Create WDM worldSDH world correlation

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SEQUENCE
a)

Point to the wdm raw connection icon and issue the Configuration: Convert in Path/Trail popup
menu item. The SDH physical connection structure is displayed. See figure herebelow.

Convert in path/trail

Figure 48. RawConn:Configuration: Convert in Path/Trail

1AA 00014 0004 (9007) A4 ALICE 04.10

A report is displayed, to verify if the action has been correctly executed. See below figure.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

65 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 49. Convert in Path/Trail report

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

66 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CLIENT PATH

Figure 50. Optical Physical Conn structure: optical (client) path

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

67 / 92

2.19.1 Introduction
The Connect/Disconnect tool is provided to the user to manually modify connectivities outside path allocation/deallocation activity context. Note that path allocation/deallocation is not managed due to equipment limitations.
2.19.2 Creating a connection by means of the Connectivity tool
SCOPE
The scope of this procedure is to create a connection within an OADM by means of the connectivity tool.

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

From Node popup menu issue Configuration: WDM Connectivity Tool.

b)

From the Connectivity Tool wizard step 1 select Connect. Click on Next button.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

68 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.19 Connect / Disconnect Tool

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 51. Connectivity Tool: Connect step 1

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

If you click on Port selection, you will display the port list from which you can select the port to connect.
Click on CTP selection, you will display the CTP list from which you can select the CTP to connect.
Click on Next button.

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

69 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ED

01

PORT SELECTION

SELECTED CTP

CTP SELECTION
PORT LIST

SELECTED PORT
CTP LIST

SC. 6: WDM

3AL 61348 AA AA

92

SELECTED PORT

SELECTED CTP

Figure 52. Connectivity Tool: Connect step 2

It. 01

70 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2nd TP to connect selection


2nd TP selected

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 53. Connectivity Tool: Connect step 3


d)

From step 3 wizard you can select the 2nd CTP . Click on 2nd TP to connect selection button and
select the CTP from the list.

e)

Click on Finish button. The connection is created. See the Connection create report on the figure
which follows.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

71 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 54. Connection create report.

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

72 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.19.3 Deleting a connection by using the connectivity tool

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to delete a connection within an OADM by means of the connectivity tool.
SEQUENCE
a)

From the map click twice on the OTS link, getting the physical connection list.

b)

Select the WDM physical connection and click on Physical Connection Structure button. The OTS
Physical connection structure is displayed.

c)

Optical paths and OCH trails must be removed to proceed in disconnecting the OTS connection.
Optical paths and OCH trails will become raw connections

Figure 55. pathWDM: Configuration: Conf. State Modification: Deimplement

1AA 00014 0004 (9007) A4 ALICE 04.10

d)

ED

Point to optical path (so called client) and issue Configuration: Conf. State Modification: Deimplement. A warning dialog box alerts that the optical path is correlated to an implemented SDH logical
connection (so called physical connection). The optical path will be deimplemented but the SDH logical connection will not be removed. See below figure.

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

73 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 56. Warning dialog box.


e)

Remove the OCH trail by issuing Configuration: Remove.

Figure 57. OCH trail remove

1AA 00014 0004 (9007) A4 ALICE 04.10

f)

ED

Figure wich follows shows the routing display of the raw connection replacing the OCH trail

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

74 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 58. Raw connection routing display

SEQUENCE

a)

ED
Point to the relevant node and issue Configuration: Connectivity tool

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

75 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 59. Configuration: Connectivity tool

b)

ED

The connectivity tool is displayed. See Figure 60. on page 77

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

76 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

DISCONNECT

Figure 60. Connectivity tool. Step 1: Disconnect

1AA 00014 0004 (9007) A4 ALICE 04.10

Connectivity tool. Step 1 is used to select the action, in this case DISCONNECT. Click on Next to pass to
step 2.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

77 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 61. Connectivity tool. Step 2


c)

Connectivity tool. Step 2 allows to execute the following operations: (See Figure 61. )

selection of the Port to disconnect. From the Port list select the port and click on Apply. The selected
port icon is shown in the wizard main window.

selection of the CTP to disconnect. From the CTP list select the CTP and click on Apply. The selected
CTP icon is shown in the wizard main window.

1AA 00014 0004 (9007) A4 ALICE 04.10

Click on Next button.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

78 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONNECTION to which the selected TP is actually connected


remote information
Figure 62. Connectivity tool. Step 3

1AA 00014 0004 (9007) A4 ALICE 04.10

d)

Connectivity tool Step 3 shows the data previously selected by the user, asking for confirmation.
Click on Finish button to continue deleting the connection.

The remote information include:

ED

name of the far end node

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

79 / 92

name of the far end site

name of the far end port

The remote information is very useful, because allows to identify the originating and terminating points.
As an example:
If we select CTPx sited in Milan, via the involved far end CTPy sited in Bozen, it is possible to understand
that the choice of CTPx allows to realize a connection BozenMilano

Figure 63. Raw connection routing display

1AA 00014 0004 (9007) A4 ALICE 04.10

The new Raw connection routing display is shown in Figure 63. The connection in topology within
1696MID is no longer present.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

80 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.19.4 Connectivity Tool: Modify

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to modify a connection within an OADM by means of the connectivity tool.
CONDITIONS
This procedure applies to 1640WM and 1686WM equipments.
SEQUENCE
a)

From the Connectivity Tool wizard step 1 select Modify. Click on Next button.

Figure 64. Connectivity tool: Modify step 1

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

81 / 92

From step 2 wizard you can select the Port and the CTP. Click on the PORT list button and select
the Port from the list. Click on the CTP list button and select the CTP from the list. Click on Next button.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

b)

Figure 65. Connectivity tool: Modify step 2

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

From step 3 wizard you can select the connection type. See below figure. Click on Finish button to
render effective the change.

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

82 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

CONNECTION TYPE

Figure 66. Connectivity tool: Modify step 3


NOTES

1AA 00014 0004 (9007) A4 ALICE 04.10

The Connect/Disconnect tool supports the user in the selection of TP s involved in the connectivity, keeping into account possible constraints present at NE level (e.g. OADM WDM NE s).The Connect/Disconnect tool can be activated starting from one of the following cases:
1. Stand alone (nothing selected => Network Domain)
2. Topology selected (Network, Subnetwork, Elementary Topology)

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

83 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

5. CTP/CAP selected

6. NAP selected

ED

01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.

3. Node selected

4. Port selected

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

84 / 92

2.20 Warnings

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The following warnings have to be taken into account:


2.20.1 1696MS, 1696MSC. Creating an och passthrough between two mux/demux.
In case an och passthrough is created between two mux/demux of a 1696MS, to see this configuration
on 1354RM two phantom coupled MCC board have to be instantiated according to the rate/type/frequency
of the signal which is transported, configured in dropinsert and the two related OPS ports have to be used
to create the internal physical link on 1354RM.
Alternatively the cable can be described in cablelist using CT or NM and upload connectivity request
can be launched from 1354RM to automatically create the internal physical connection. See para 2.20.2
for other details.
See also para 2.20.3.
2.20.2 1696MS, 1696MSC. Connecting 1696 to a colored SDH interface : phantom MCC board
instantiation
Physical link between a 1696MS mux/demux and a colored interface SDH can be obtained in RM only
instancing a phantom MCC board on ne by NM.
The phantom MCC has to be associated to the involved mux/demux, the frequency has to be that of the
optical signal coming from SDH interface, the type has to be set according to the rate/type of the signal
that has to be transported.
This problem is due to ne software which didnt provide a GOC OPS port as interface to mux/demux.
Alarm (such as URU) on this false MCC has to be eventually inhibited by the user toward NM or CT (see
also point 14). Pay attention that an audit followed by a download from 1354RM will overwrite ASAP on
MCC and URU will reappear.
See also para 2.20.3
2.20.3 All Nes. Instantiating a phantom board
To avoid the raise of a URU alarm from board that are configured on CT / NM but are not really present
on the network element (phantom MCC), a possible way is to configure the board on phantom subrack
and not in real subrack.
2.20.4 1696MS, 1696MSC. Configuration of OPC (optical protection card).
OPC card has to be configured according to network configuration so that the main port of network element
A is connected to the main port of network element Z, the same for spare ones. Mixed configuration (mainA
with spareZ, mainZ with spareA) can not be managed by 1354RM.

1AA 00014 0004 (9007) A4 ALICE 04.10

When a mixed configuration is used the clientpath can not be discovered.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

85 / 92

Upload connectivity feature of 1354RM is very useful for uploading internal physicallinks automatically
without the operator has to do something. For a full functionality of this feature who install/upgrade
1696MS / 1696MSC has to be aware that the cable configuration has to be manually described for each
nes in Cable list available on CT and NM according to the real hardware configuration.If this step is not
done, internal physical link have to be created manually by the 1354RM operator!
Case in which cable list has to be manually updated :
4xAny board connected to an OPC card or to an MCC board. phantom coupled MCC board are used to
visualize a passthrough between two mux/demux (see para 2.20.1.).
2.20.6 1696MS. Upgrading 1696MS to add new lambdas management without loss of trafic

A special feature available on 1696MS allows to equip new lambdas adding other mux/demux board. This
operation can be done without trafic loss if done according to specific upgrade rules (see specific ne documentation).
When management of new lambdas is added to ne and OTS port of this ne are already assigned to
1354RM a global download action is needed in order to see new OchCtp over OTS port, then and a payload configuration of physical link is needed to create transport object involving new equipped OchCtp(s).
When management of new lambdas is added to ne and OTS port of this ne are already assigned to
1354RM a global download action is needed in order to see new OchCtp over OTS port, then and a payload configuration of physical link is needed to create transport object involving new equipped OchCtp(s).
2.20.7 1696MS, 1696MS. Use of SPV_F_1310_1550 and SPV_FC board.
SPV_F_1310_1550 board and SPV_FC board act as a mux/demux from a 1696MSC to a 1696MS: the
first can transport a 1310 (B&W) signal, a 1550 (Colored) signal and a OSC channel; the second can transport an OSC channel and another colored signal.
These board are transparent at 1354RM level. The optical signals multiplexed by SPV_xxx boards are
seen in 1354RM as they are transported by different OPS physical links, while the OSC signal is never
managed in RM.
2.20.8 1696MS, Board MCC1 (SDH) and MCC2 (SDH). PM: change monitoring point from adjacent boundary clientctp to boundary clientctp.
When a clientpath is correlated to a measure, the default pmtps are the adjiacent boundary clientctps.
Network element allows monitoring on boundary clientctp and on adjacent boundary clientctp but not
at the same time.

1AA 00014 0004 (9007) A4 ALICE 04.10

To change a monitored point from adjacent boundary clientctp to a boundary clientctp a procedure is
available:

stop pmtp related to adjacent boundary clientctp

remove pmtp from RM

from clientpath Action>alarms>Transport>manual disable. This is necessary to remove rsTrailMonitor from adjiacent clientctp

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

86 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.20.5 1696MS, 1696MSC. Configuration of 1696MS to have 1354RM upload connectivity working well

correlate to measure the boundary ctp and start this point of measure

from clientpath Action>alarms>Transport>manual Enable. This is necessary to reactivate


rsTrailMonitor on boundary clientctp

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

87 / 92

2.21 Remove optical physical connection

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to remove an optical physical connection
SEQUENCE
a)

From the OTS physical connection structure verify if optical paths (so called client) are present.

OPTICAL PATH

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 67. Physical connection structure (96_UP to 96_MID)


b)

Execute the deimplementation of the optical path by selecting the menu Configuration: Configuration
State Modification: Deimplement. A question box asks for confirmation. Enter YES.

c)

Deallocate the optical path by issuing the command Configuration: Configuration State Modification:
Deallocate. The user can refresh manually the PhysCon structure view.

d)

Execute Opt. Physcon: Configuration: Deimplement. See following figure.

e)

Remove the OTS optical physical connection. The OTS optical physical connection view remain
opened for a while.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

88 / 92

2.22 Insert OADM in an optical network

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope of this procedure is to insert a new OADM in a topology.
SEQUENCE
a)

Create in the suitable submap the node to be added ( node 96_MID with ref. to Figure 68. herebelow

96UP

96MID

96DOWN

Figure 68. Node 96_MID to be inserted


b)

Create the OTS physical connections 96_UP to 96_MID and 96_MID to 96_DOWN and create via
the Connectivity Tool the required passthrough connection within node 96_MID.

1AA 00014 0004 (9007) A4 ALICE 04.10

The procedure to create the OTS connection is described at para 2.13 on page 38

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

89 / 92

The Trace Identifier mechanism is used to control the continuity of the signal. The management of the
Trace Identifier in a WDM network is possible only if the transported signal is SDH.
The Trace Identifier, on the WDM NEs, can only be monitored (expected value). It can be provisioned (sent
value) only on the SDH NEs.
The Trace Identifier can be set both on the client path and on the related SDH physical connection. The
following has to be taken into account:
It is not possible to set the Trace Identifier on the SDH physical connection if the client path is present
If the Trace Identifier is set on the client path, the values are propagated on SDH ports, client NAPs and
on boundary WDM NEs (client CTPs)
If a client path is created and the Trace Identifier is already set on the SDH port, the value is is propagated
on the client NAP. When the Trace Identifier management command is executed on the client path, the
values of the Trace Identifier present on the NAPs are presented to the user that can confirm or modify
them

1AA 00014 0004 (9007) A4 ALICE 04.10

When the client path is deimplemented, the Trace Identifier is removed on client NAPs, on boundary
client CTPs and on SDH ports

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

90 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.23 Trace Identifier

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.24 1660OADM coarse WDM management


2.24.1 Wavelength management
The following differences, respect to a Dense WDM port, have to be taken into account for the management of a Coarse WDM port:
to fill the frequency attribute of a Coarse WDM and SDH coloured ports, the wavelength, expressed in
nm is used
to calculate the wdmFrequency attribute (alias = position) of the RM objects (CTPs, CAPs and LCs) related to a Coarse WDM port, the value of the wavelength, expressed in nm is used
2.24.2 Coarse OPS physical connection
A transponder with a BlackAndWhite signal at client side and a Coarse coloured one at the WDM side is
supported by 1660OADM. Moreover, a transponder with a Coarse coloured signal at client side and a
Coarse coloured one at the WDM side is supported by 1660OADM.
When an OPS physical connection involving a port (client or WDM side) belongs to a 1660OADM is
created, the following steps are performed:
the involved port is assigned
starting from the assigned port, the TP chain up to the client CTP is discovered and the related objects
are created inside the RM MIB
if the client CTP points to an other client CTP (by means the UCP/DCP pointer) already present inside
the RM MIB, the crossconnection between the two involved client CTPs is created inside the RM MIB
The output port of this transponder (Coarse) is connected to a port of a Coarse Multiplex (in the same or
in an other NE). Then the Coarse signal is transported in the network through and terminated in a NE bymeans the same type of transponder, as shown, as an example, in the following figure.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 69. Coarse signal in the optical network


As the Coarse Multiplexes are not visible through the OpticsIM interface, it is not possible to describe
in RM the Coarse links. Due to this limitation, the user can only define a Coarse OPS physical connection
between the Coarse ports of the two transponders.

ED

01

SC. 6: WDM

It. 01
3AL 61348 AA AA
92

91 / 92

1AA 00014 0004 (9007) A4 ALICE 04.10

END OF DOCUMENT

ED

01

SC. 6: WDM

It. 01

3AL 61348 AA AA

92

92 / 92

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM REL.7. 2 OPERATORS HANDBOOK

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 NETWORK CREATE ON RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 NETWORK CREATE ON NP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 ASSOCIATION MNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Create NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Port management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9
9
11

5 PATH AND CIRCUIT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

6 NAVIGATION FROM RM TO NP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Enable navigation on NPOSCA from 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Navigation of 1354NP defined on RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Definition of the RM to NP correlation for path/trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Display of the correlated object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15
15
15
15
16

7 NP PROBABLE CAUSES SENT TO RMAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

8 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23

01

050207

ED

DATE

CHANGE NOTE

M.RAGNI
V.BALCONI

V.PORRO

APPRAISAL AUTHORITY

ORIGINATOR

RM to NP INTERWORKING

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

1 / 24

1AA 00014 0004 (9007) A4 ALICE 04.10

FIGURES
Figure 1. Create NPA step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Create NPA step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. RMNP main attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Correlation selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Correlation dialog box for path/trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. WS selection dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. RMAS main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. BACKBONE NETWORK sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

SC. 7 RMNP INTERWORKING

9
10
12
16
16
17
20
21

It. 01
3AL 61348 AA AA
24

2 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LIST OF FIGURES AND TABLES

1 GENERAL

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

This section deals about RMNP interworking.


It is constituted by the following chapters:
NETWORK CREATE ON RM
NETWORK CREATE NP
ASSOCIATION MNG
NAVIGATION FROM RM TO NP
NP PROBABLE CAUSES SENT TO RMAS

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

3 / 24

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 7 RMNP INTERWORKING

It. 01

3AL 61348 AA AA

24

4 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2 NETWORK CREATE ON RM
The description which follows is the ordered list of procedures described in section OPERATION of the
1354RM operators handbook
a)

Creating the Network

b)

Creating the Subnetwork

c)

Creating the 2nd level Subnetwork

d)

Creating Nodes and ports

e)

Creating physical connections

f)

Network: Implement

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

5 / 24

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 7 RMNP INTERWORKING

It. 01

3AL 61348 AA AA

24

6 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3 NETWORK CREATE ON NP
The description which follows is the ordered list of procedures described in section OPERATION of this
1354NP operators handbook
a)

PLACE: Create

b)

SHARED RISK GROUP (CABLE) Create

c)

SRG (CABLE) Restore

d)

NETWORK ELEMENT Create

e)

NETWORK ELEMENT Restore. Via Q3 NP uploads physical ports, TTP/CTPs. MSPs

f)

TELINK Create

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

7 / 24

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 7 RMNP INTERWORKING

It. 01

3AL 61348 AA AA

24

8 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4 ASSOCIATION MNG
4.1 Create NPA
ON RM
a)

Create NPA type Fast Restoration e.g. from the 2nd level subnetwork map select Actions: Create:
NPA

b)

In the step1 NPA wizard select NPA type=Fast Restoration, enter NPA cost reduction, NPA usage
cost and NPA name (userlabel) and click on Next button.

Figure 1. Create NPA step 1

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

In the step2 NPA wizard select the internal (internal to the NP network) and interworking physical connections to assign to this NPA.

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

9 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 2. Create NPA step 2


d)

Click on Finish to confirm the creation.

e)

From the create report dialog box select button Implement and clixk on OK.

For interworking physical connection the following ACD values are setup: ACD=RM for the port controlled
by RM, sharedRM+NP for the boundary port.
For internal physical connection the following ACD values are setup: ACD=NP for both ports.

1AA 00014 0004 (9007) A4 ALICE 04.10

In the fact, NP manages NP ports and sharedRM+NP ports.

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

10 / 24

4.2 Port management

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ON NP
a)

Execute Port: Assign to Network for the NP ports and sharedRM+NP ports

b)

For sharedRM+NP ports execute Port: Modify. Set usage=local drop

c)

For sharedRM+NP ports execute Port: Restore

d)

For NP ports execute Port: Modify. Set usage=backbone and assign the port to the relevant TE
LINK.

e)

For NP ports execute Port: Restore


It is important to check the congruency of the information with RM data, i.e. the physcon on RM is
described as TELINK on NPOS (the same)
check the congruency of the information with RM data for ports, according to the below figure

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

11 / 24

NP

NP internal

interworking
NPA create

physcon

physcon

NPA impl
on RM

link type=
RM internal

on NP

PORT

PORT

PORT

link type=

link type=

link type=

drop

inni

inni

TTP
usage=
local
drop

TTP

TTP

ACD=RM+NP

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

RM

usage=
bkb

usage=
bkb

ACD=NP

ACD=NP

Figure 3. RMNP main attributes

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

12 / 24

5 PATH AND CIRCUIT MANAGEMENT

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

ON RM
a)

Create the path

b)

Set the path constraints if necessary. The NAP can be added as constraint.

c)

Allocate the path

d)

Implement the path

ON NP
a)

Create the circuit having as local drop ports the relevant CTPs of the shared ports as taken from the
path routing

b)

Activate the circuit

NOTES ON NPA
The NPA can be deimplemented if no traffic crosses its physcons
The deimplementation of the NPA removes the port attribute which were setup during the implementation
The user can add a physcon to an NPA

1AA 00014 0004 (9007) A4 ALICE 04.10

The user can remove a physcon from an NPA, in absence of traffic

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

13 / 24

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 7 RMNP INTERWORKING

It. 01

3AL 61348 AA AA

24

14 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6 NAVIGATION FROM RM TO NP

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

From RM it is possible to navigate to NP for the following objects:

path/trail. It opens on RM screen the NPOSCA graphical interface displaying the associated circuit

subnetwork connection. It opens on RM screen the NPOSCA graphical interface displaying the related NP circuit

physical connection. It opens on RM screen the NPOSCA graphical interface displaying the related
TElink

The setup of the navigation includes the following steps:


a)

Enable navigation on NPOSCA from 1354RM

b)

Navigation of 1354NP defined on RM

c)

Definition/Display/Modify of the RM to NP correlation for path/trail

6.1 Enable navigation on NPOSCA from 1354RM


Refer to NPOS Installation handbook

6.2 Navigation of 1354NP defined on RM


The user has to insert the workstation nameblanckIPaddress on which the 1354NP user interface process will be opened. The list of these addresses is stored in a text file customized by the system manager:
/usr/Systems/1354RM_<nms_instance>/conf/np_host_conf
with the following format:
tlvu13 xxx.yy.zz.ww
tlvu15 xxx.yy.zz.ww
the first string is the mnemonic name, the IP address is used as navigation command parameter.

6.3 Definition of the RM to NP correlation for path/trail


N.B.

The Definition of the correlation between 1354RM and 1354NP is required for the objects path
and trail. For snc and physical connection is set automatically.

SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

Point to path/trail to correlate and issue the menu Related objects: Edit. The correlation selection
dialog box is presented.

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

15 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 4. Correlation selection


b)

Select 1353NP and click on OK. The correlation dialog box is displayed. See following figure.

Figure 5. Correlation dialog box for path/trail


c)

Enter the name of the NPOS circuit to correlate to the path/trail and click on OK. The correlation is
then created.

6.4 Display of the correlated object

1AA 00014 0004 (9007) A4 ALICE 04.10

PATH / TRAIL
a)

Point to the path/trail and issue Search: Related. The WS selection dialog box is presented.

b)

Click on dictionary button. From dictionary selection box select the WS and click on OK.

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

16 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 6. WS selection dialog box


c)

The WS address is now present in the WS selection dialog box. Click on OK. NPOSCA graphical
interface opens displaying the associated Circuit: Show view.

1AA 00014 0004 (9007) A4 ALICE 04.10

PHYSICAL CONNECTION
a)

Point to the Physical Connection and issue Show: Details on NP. The WS selection dialog box ( see
above figure) is presented with the relevant WS already selected. Click on OK.

b)

NPOSCA graphical interface opens displaying the associated TELINK view.

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

17 / 24

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 7 RMNP INTERWORKING

It. 01

3AL 61348 AA AA

24

18 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7 NP PROBABLE CAUSES SENT TO RMAS

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The NP probable causes sent to RMAS are:


SimpleSnConnNullAlarm
SimpleSnConnInsideFailure
SimpleSnConnOutsideFailure
SimpleSnConnPathTraceMismatch
SimpleSnConnDestinationLost
SimpleSnConnLocalDropFailure
SimpleSnConnFault
SimpleSnConnProtectionFault
SimpleSnConnProtectionDegraded
SimpleSnConnDegraded
SimpleSnConnQualityDegrade
SimpleSnConnFaultProgramming
SimpleSnConnUnmapped
SimpleSnConnProtected
DoubleSnConnPathsNoDisjoint
These alarms are relevant to circuit and, for circuits correlated to RM path / trail are displayed on the AS
sublist BACKBONE NETWORK.

1AA 00014 0004 (9007) A4 ALICE 04.10

The description of the above probable causes can be found in the 1678MCC documentation.

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

19 / 24

EXAMPLE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure which follows shows the RMAS main view. The BACKBONE NETWORK sublist is selected.

Figure 7. RMAS main view

1AA 00014 0004 (9007) A4 ALICE 04.10

Opening the BACKBONE NETWORK sublist, the NP probable causes sent to RMAS are displayed on
a dedicated column. See following figure.

ED

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

20 / 24

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 8. BACKBONE NETWORK sublist

ED

01

SC. 7 RMNP INTERWORKING

It. 01

3AL 61348 AA AA

24

21 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 7 RMNP INTERWORKING

It. 01

3AL 61348 AA AA

24

22 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

8 PERFORMANCE MONITORING

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The following limitations are be taken into account:

NPOS cannot set up measurements on shared termination points

RM cannot set up measurements on termination points internal to the backbone network

Measurements on MSP (Multiplex Section Protection) are managed via 1353NM or 1354NP only.

N.B.

ED

Multiplex Section Protection internal to the backbone network or interworking are defined via
1353NM. 1354RM does not receive any notification.

01

SC. 7 RMNP INTERWORKING

It. 01
3AL 61348 AA AA
24

23 / 24

1AA 00014 0004 (9007) A4 ALICE 04.10

END OF DOCUMENT

ED

01

SC. 7 RMNP INTERWORKING

It. 01

3AL 61348 AA AA

24

24 / 24

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1354RM REL.7. 2 OPERATORS HANDBOOK

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5
5
5

2 OVERVIEW ON AUTOMATIC SWITCHED OPTICAL NETWORK (ASON) . . . . . . . . . . . . . . . . .


2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 ASON NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 Path setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4 Control Plane Domain Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5 SubNetwork Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.6 Network Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.7 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.8 NE Sharing with GMRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.9 Q3 consistency for RM/GMRE shared ports, TPs and crossconnections . . . . . . . . . .

7
7
7
8
10
10
10
10
11
11
11

3 ASON CREATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 ASON network creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Network Protection Architecture Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 NPA display & Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 NPA modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.4 NPA Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.5 NPA Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13
13
14
20
26
28
29

4 SRG (SHARED RISK GROUP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


4.1 SRG (Shared Risk Group) Create/Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Shared Risk Group Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Shared Risk Group remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 SRG (Shared Risk Group) Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Correlate/Modify the set of SRGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 SDH SRGs calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31
31
31
34
36
36
38

5 PHYSICAL CONNECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

41

01

050207

ED

DATE

CHANGE NOTE

M.RAGNI

V.PORRO

APPRAISAL AUTHORITY

ORIGINATOR

ASONGMRE

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

1 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

41
44
44
44

6 ASON CLIENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Creation of an ASON client device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Definition of a physical connection with an ASON client device . . . . . . . . . . . . . . . . . . .

51
51
51

7 ASON PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 ASON PATH Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.1 Interwork ASON2FMSSPRing with automatic squelching calculation . . . . . . . . . . .
7.1.2 Definition phase:defaultRerouting,defaultPriority and protectionType . . . . . . . . . . . . . . .
7.2 Visualization on maps of SNC Current, Nominal & Backup route . . . . . . . . . . . . . . . . .
7.3 Path: Reroute nominal route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 Modify the userLabel and rerouting attributes of a SNC . . . . . . . . . . . . . . . . . . . . . . . . . . .

53
53
53
54
55
62
66

8 ADD/ REMOVE PROTECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


8.1 Add/ Remove Protection Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1 Add Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.2 Add Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.3 Remove Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.4 Undo reroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Remove Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

69
69
69
75
75
75
76

9 EXAMPLE OF CLI CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

81

10 GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

87

11 ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

89

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

2 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.1 Physical Connection: Administrative State menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


5.2 Update TELink: move physcon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2 TELinks creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

LIST OF FIGURES AND TABLES


FIGURES
Figure 1. ASON network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Actions: Create: Npa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Create: Npa: Step 1: ASON protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Create: Npa: Step 2: Internal and Interworking physcons . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. NPA highlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Network: Display: All Related Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Item selection: NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. NPA list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. NPA view selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. ASON NPA view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Physical Connection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Control Planes list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Paths crossing ASON network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. SNC (subnetwork connection) list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. TELink list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. NPA: Actions: Configuration: Modify NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. NPA: Modify: step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. NPA: Modify: step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. NPA: Actions: Configuration: Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Shared Risk Group menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Shared Risk Group Create/Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. SRG: SRG type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. SRG Create step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. srg probability change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. SRG: Remove (selection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. SRG: Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. SRG (Shared Risk Group) Management: Correlate/Modify the set of SRGs . . . . . . . . .
Figure 28. SRG (Shared Risk Group) Management: Correlate/Modify . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. SRG selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Shared Risk Group: SDH SRGs calculation: Physcon selectrion . . . . . . . . . . . . . . . . . . .
Figure 31. Shared Risk Group: SDH SRGs calculation: SRG selectrion . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Shared Risk Group: SDH SRGs calculation: launching the calculation . . . . . . . . . . . . . .
Figure 33. Physical Connection: Administrative State menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Physical Connection: ASON: Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. ASON Maintenance wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Update TELink wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. NPA view: TELink icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. TELink list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Update TELink: move physcon to a new TELink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Update TELink: move physcon to a new TELink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Move TELink: change SRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Update TELink: move physcon to an existingTELink . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Path list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Highlight map view: Highligth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Current route Highligth display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Nominal Route Highligth display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Backup Route Highligth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. Add/Remove Protection Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Add/Remove protection:Reroute dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. Path reroute: ACONN selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED

01

SC. 8 ASONGMRE

9
15
17
17
19
20
21
21
22
22
23
23
24
24
25
26
27
28
29
31
32
32
33
34
35
35
36
37
37
38
39
40
41
42
43
45
46
46
47
48
49
50
57
58
59
60
61
62
63
63
It. 01

3AL 61348 AA AA
89

3 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 8 ASONGMRE

64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
81
82
83
83
84
85

It. 01
3AL 61348 AA AA
89

4 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 51. Path reroute: ACONN selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 52. Path reroute: confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 53. Modify: Attributes popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. SNC: Modify: Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. Show: Details on GMRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. Add/Remove Protection Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. Add/Remove Protection Toolstep 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. Add/Remove Protection Toolstep 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. AConnection selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. ZConnection selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. ACONN and ZCONN selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. Refresh of the Routing Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. Remove Protection option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. Remove Protection Toolstep 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. AConnection selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. ACONN and ZCONN selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. Warning to refresh of the Routing Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. CLI connect: click Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. CLI termconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. Question mark: 1st level help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. 2nd level help on show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. Show LSP: LSP list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 73. 3rd level help on show lsp command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 74. Show LSPIndex command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1 INTRODUCTION
1.1 Introduction
This document aims at introducing the ASON GMRE network controlled by RM.

1.2 Target audience


The Introduction Manual is intended for all 1354RM users.

1.3 Document structure


This section covers the following topics:

ED

Overview on ASON

ASON network creation

SRG (Shared Risk Group) Create/Remove

SRG (Shared Risk Group) Management

ASON CLIENT

ASON PATH

Visualization on maps of SNC Current, Nominal & Backup route

Path: Reroute nominal route

Modify the userLabel and rerouting attributes of a SNC

Add/ Remove Protection Tool

Remove Protection

Example CLI connection

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

5 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

6 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2 OVERVIEW ON AUTOMATIC SWITCHED OPTICAL NETWORK (ASON)


2.1 General
The feature allows the management of a distributed Control Plane based on GMPLS (Generalized Multi
Protocol Label Switching)
2.1.1 Control Plane
ASON network NEs, involved in the network managed by RM are shared between RM and GMRE ( Distributed Restoration Manager ). Both systems (NMS) manage resources belonging to shared NEs. In particular, ports belonging to the physical links involved in the Legacy Network are the shared resources.
These physical links represent in RM the links of interworking between the two managers for the paths
routed in ASON domain. The port at the end of the interworking link and belonging to the shared NE represents the shared port.
The TPs on a shared port can either be completely managed by RM or managed by both RM and GMRE,
according to the routing of the path involving the TP.
Both managers operates on the TP: RM will be in charge of all the normal operations on the TP, apart from
the set up of the crossconnection, setup by GMREs and dynamically changed according to GMREs restoration strategies.
Physical links and the NEs of the ASON network are represented in the RM as physical connections and
nodes.
RM provides to GMRE the description of the network belonging to the ASON domain and the links at the
boundary of that domain (interworking links). These links connect shared ports.
ASON domain topology is described in each GMRE and RM user launches the automatic discovery of the
ASON domain physical connectivity by means of J0 string.
RM, for maintenance purposes, manages the physical and the Multiplex Section layers (linear MSP included)
On the interworking links, RM can apply the payload structure; in the ASON domain, the payload structure is defined by the GMRE as a consequence of a SPC (Soft Permanent Connection) set up by RM.
RM user has anyway to perform the payload structure also on the internal links to allow path
allocation activities but the command is not propagated to GMRE.
On path setup phase, RM provides to GMRE the setup of the subnetwork connection (SPC) contained
in the ASON domain, between the two TPs of the shared ports. GMRE will be in charge of restoring, upon
failures, that subnetwork connection.

1AA 00014 0004 (9007) A4 ALICE 04.10

While the TPs ends of the above subnetwork connection are chosen by RM, the other TPs involved in
the crossconnection inside the shared NE, are moved by GMRE according to its restoration purposes.
I.e., the setup of the single crossconnections inside the NEs belonging to the ASON domain (included
the shared NEs) will be done by GMREs. For all the other operations at path layer (POM, TCT, PM, path
trace): RM is the master for the TPs on the shared ports, while GMRE is the master for the TPs of the ASON
domain.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

7 / 89

Each manager is able to distinguish between ports on which all the normal operations are allowed because
completely assigned to it and ports on which only specific operations can be performed because shared
2.1.2 ASON NPA
ASON domain is managed by RM as ASON NPA
In ASON NPA definition, the user must specify the role of the physical connection as internal or interworking: the involved port on the NE belonging to the ASON NPA is marked as shared inside RM
In case the ASON network has already been setup by the GMRE user (through CLI), the RM user, to build
the network, has to perform the following steps:
provision the Trace Identifier on the SDH ports assigned to GMRE
set the download disabled mode on the involved NEs
For each node of the domain, performs the Configuration/Upload connectivity command. The command (based on J0) automatically creates in the RM DB the physical connections involving the node selected by the user
implement the uploaded physical connections
To create the NPA providing the internal and the interworking physical connections. The port ending
an interworking physical connection on the NE belonging to the NPA is marked as shared port. During
the NPA creation phase only the nodes supporting the GMRE on top can be involved. This presence of
the GMRE is retrieved through the Q3 interface during the Synchronize NE activity and stored in the RM
MIB
implement NPA
set the download enabled mode on the involved NEs. As a consequence, all commands are sent to
GMRE

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure which follows shows an example of ASON network

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

8 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

As a consequence: ports dedicated to the interworking between RM and GMRE are marked as shared
.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1664SX

1664SX

RM
port

RM
port

RM physcon

R$
RM
port

RM
port
R$
interworking

interworking
physcon

physcon
J$
shared
port

J$
shared
port

J$
shared
port

1664SX

J$
shared
port

interworking

1674LG

physcon

G$
port

G$

G$

port

port
internal
physcon

port

internal
physcon
G$

G$

port

internal
physcon

G$

port
internal
physcon

1674LG
G$
port

G$
port
internal
physcon
G$

G$
port

physcon

G$

internal
physcon

port

1AA 00014 0004 (9007) A4 ALICE 04.10

J$ = shared type

G$

G$
port

port

1674LG
internal

internal
physcon

R$=RM port

G$
port

port
1674LG
internal physcon

G$=INNI port

Figure 1. ASON network

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

9 / 89

When the RM operator setsup a path crossing (or terminating in) the ASON domain, the subnetwork
connection at the ASON NPA level will be created and also the related crossconnection inside the Nodes.
These crossconnection will be marked in such a way that RM will not directly forward the crossconnection implementation to the NE but they will provided to the GMRE with the provisioning of the SPC nominal
route (the provisioning of the single crossconnections to the NE will be in charge of GMRE)
2.1.4 Control Plane Domain Object
The controlPlaneDomain class represents the GMRE, i.e. the Control Plane instance contained in theNetwork Element. Some important attributes are:
reachable: it indicates the Control Plane communication status.
userLabel: it is the user label of the Control Plane
operationalState, alarmStatus, ...
nativeName: it indicates the name inside GMRE
emsFactoryAddress: it indicates the GMRE Factory IOR for addressing the GMRE/Control Plane using
NMI Corba (not visible on the User Interface)
ipAddress: it indicates the IP address of the GMRE (routing IP)
assignSt: it indicates if the Control Plane has been taken in charge by RM or not
consistSt: it indicates the consistency state
2.1.5 SubNetwork Connection
Some important attributes are:
userLabel
sncActiveSt: it specifies if the SubNetwork Connection has been implemented on the Nes by the GMRE
(not visible on the User Interface).
rerouting: it specifies if the rerouting by the Control Plane is allowed or not.
2.1.6 Network Element
The following attributes are added to the ne:
controlPlaneDomId: it is the Identifier of the Control Plane Domain (not visible on the User Interface)

1AA 00014 0004 (9007) A4 ALICE 04.10

controlPlaneStatus: it identifies the Control Plane status. Allowed values:


notPresent: the Control Plane is not present on NE (default value)
notManaged: the Control Plane is not managed by RM
reachable: the Control Plane is managed by RM and it is reachable
notReachable: the Control Plane is managed by RM but not reachable

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

10 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

2.1.3 Path setup

2.1.7 Port

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The following attributes are added to the port class:


linkType: it identifies the port type inside RM. Allowed values:
rminternal: it is a port of an NE not involved in an ASON NPA (default value)
drop: it is a port (without signaling) of an NE belonging to an ASON NPA, connected to a port of
a client device
unin: it is a port (with signaling) of an NE belonging to an ASON NPA, connected to a port of a client
device
inni: it is a port of an NE belonging to an ASON NPA, connected to an NNI port of a neighboring
NE belonging to the same ASON NPA
enni: it is a port of an NE belonging to an ASON NPA, connected to an NNI port of a neighboring
NE belonging to a different ASON NPA
portNativeName: it identifies the port inside the Control Plane
remotePort: it identifies the native name of the farend port
2.1.8 NE Sharing with GMRE
The port sharing with GMRE is performed through the ACD set at Q3 interface. The ACD of the ports
shared between RM and GMRE is set by RM to J$.
2.1.9 Q3 consistency for RM/GMRE shared ports, TPs and crossconnections
In the following only the specificity of the Q3 consistency for the involved objects are reported.
For the shared ports:
the consistency of the disconnectOnNE attribute of the client TPs is performed: in case a crossconnection is discovered on the NE while no crossconnection is present on RM, the crossconnection on the
NE is removed only if the other port involved by the crossconnection is either assigned to RM or also
shared.
For the internal ports:
The ACD is set to G$
The consistency of the au4Structure attribute of the msCtpCap is not performed (this because the master
of the payload structure is the GMRE)
For crossconnections:

1AA 00014 0004 (9007) A4 ALICE 04.10

The consistency is not applied for the crossconnections with configuration state implemented on CP
where CP stands for Control Plane.
The configuration state attribute of the crossconnections belonging to an SPC is set allocated when the
SPC configuration state is set allocated and moved to implemented on CP when the SPC configuration
state is set implemented (i.e. during path implementation activity)

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

11 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

12 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3 ASON CREATION
3.1 ASON network creation
The creation of an ASON Network is split in a well defined sequence of actions that are listed in the following of this paragraph.
SEQUENCE
a)

From the EML list select the EML which contains the NE belonging to GMRE control plane and issue
Actions: Synchronize: Synchronize EML

b)

Click on Apply on the selection filter. The NE list is displayed.

GMRE NEs are listed with attribute Control Plane different from Not Present. The possible values for this
attribute are : Reachable, Not Reachable, ....
The symbol identifying a GMRE NE is also reported on the browser display as shown in the figure below.
NE with GMRE control Planes are discovered . The control plane is not managed yet. The Control plane
status is Not Managed
c)

From browser point to the ASON subnetwork and select Configuration: J0 definition. This configuration is executed automatically by the NEs belonging to the subnetwork.

d)

From browser, pointing to the subnetwork issue Subnetwork: Configuration: Upload Connectivity.

1AA 00014 0004 (9007) A4 ALICE 04.10

The physical connections are uploaded from GMREs and represented on RM database and interface.
e)

Create the NPA of type=ASON. Figures which follow shows NPA Create step 2, which requires the
specification of the internal and interworking physical connections.

f)

Click on Finish button to complete the creation.

g)

From NPA list point to Ason NPA and issue Configuration: Implement. The communication RM
GMRE is started and, after a few seconds the Control Plane of each NE becomes reachable. On
GMRE systems the objects required for the routing and restoration functions are created.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

13 / 89

3.1.1 Network Protection Architecture Create

The scope of this procedure is to create a Network Protection Architecture ( NPA )


The NPA creation tool allows to specify:
the type,
the involved physical connections and, if applicable, their associated role (e.g. Working or Protection for
4fMSSPRing, and Linear MSP).
For ASON NPA, the user must specify also the physical connections used for the interworking with the rest
of the network
A NPA can be defined independently from the Topologies used for the partitioning of the Network. This
means that a NPA can belong to different Topologies of different levels and that Topology can have NEs
and links involved in multiple NPAs
The creation tool can be started from :
A topology: Network, Subnetwork (lev.1 or lev.2)
Within the tool, the involved physical connections can be retrieved browsing from the initial topology(*) or
from a different one reached through up & down navigations.
The NPA definition ends with the creation in RM of a NPA and its visualization on the user Interface
The NPA can be created even if not valid (e.g. a ring can be open or even empty) but RM always provides
to the users the proper warnings.
Dependently from the type of NPA to be created, the creation activity requires different information and
performs different checks:
A SDH physical connection can only belong to one NPA with the following exceptions:
ASON internal / linear MSP
ASON interworking / any other NPA
SNCP / linear MSP (To Be Confirmed )
A SDH physical connection is present in RM also when supported by a WDM network. The server OTS
or OPS physical conn. Are, in RM, not part of any NPA
SNCP rings must have the same uniform rate and east/west sequence is checked for first gen. NEs
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From the browser select Actions: Create: Npa

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

14 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 2. Actions: Create: Npa


b)

The Create: Npa: Step 1: dialog box opens. Select


1)

selection of NPA type=ASON

NPA Reduction Cost Factor

NPA Usage Cost

Bundling Rule ( with same risk, alltogether, one to one ) and click on Apply.

NPA Usage Cost:


It is an extra cost to pay for the usage of a NPA. It has the target to make costly to enter and
to exit from a Network Protection.
As bigger is set as more the routing in the current NPA will be preferred compared to a less expensive detour outside the NPA in the meshed network or in another NPA.
It is not considered for the spare that uses the same ring of the main.

1AA 00014 0004 (9007) A4 ALICE 04.10

If set to 0, the routing is done not considering the NPAs.


If set to more than half of the cost of a physical link (Default value TBC), the routing is done as
it would be having only not stacked protections and an internal route is preferred to an external
one even if has a double cost

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

15 / 89

Applications of the NPA Usage Cost


With the proposed NPA Usage Cost, the routing algorithm behaves for stacked and not stacked
ring configuration in a similar way (i.e. for the routing, it is like to have a physical link between
two stacked rings)
An additional example of the stability effect of the NPA Usage Cost is the behaviour in case of
stacked and unbalanced rings.
NPA Cost Factor:
The NPA cost factor is an additional parameter of each NPA, enabling a percentage cost reduction for its links. This cost reduction has the target to balance the NPA Usage cost and makes
more attractive the routing inside a NPA compared to the one outside at least for route longer
than a given number of arcs.
In the fact, it is an indicator on how much a Main/Spare routing in a NPA has to be preferred
compared to an external route. It works together with the NPA Usage Cost making more attractive long routes in a NPA.
If equal 0 it has no effect.
As bigger is set as more the cost of NPA internal route is reduced and as more the NPA attracts
the routing.

bundlingRule attribute of the NPA itself.


oneToOne: for each physical connection a different teLink is created. The linkMetric and the
srgList attributes of the created teLink object are set with the corresponding values of the physical connection
withSameRisk: the physical connection with the same linkType, linkProtectionType, cost and
srgList are grouped in the same teLink object. The linkType, the linkProtectionType, the linkMetric and the srgList attributes of the created teLink are set with the corresponding values of the
physical connection
The TELink can also be created as a consequence of the modification of the composition of
an existing TELink.
Changing the default physical conn. cost

1AA 00014 0004 (9007) A4 ALICE 04.10

In case of particular unbalanced configurations, if the NPA Usage Cost is not enough to avoid the ring
changing, the user needs to properly set the costs of physical connections

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

16 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

By default the NPA Usage Cost cost is set to an RM installation default value but can be modified
by the user. For example if L is the default cost of a physical connection, a meaningful default
value for the NPA Usage Cost can be L/2+1 ( i.e. (L/2+1)*2 )

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 3. Create: Npa: Step 1: ASON protection

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

Select Internal and Interworking physcons and click on Finish button.

Figure 4. Create: Npa: Step 2: Internal and Interworking physcons

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

17 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Actions after NPA create


Actions available after NPA create are Modify NPA, Modify Ring Map, Implement and Unlock physical
connections

1AA 00014 0004 (9007) A4 ALICE 04.10

NPA highlight shows on the map the nodes connected by physical connections involved in the NPA.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

18 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 5. NPA highlight

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

19 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.1.2 NPA display & Views

SCOPE
NPAs can be retrieved from:
The containing network (list of all the existing NPAs)
The subnetworks (level 1 & 2) containing at least a Node (not a physical connection) involved in a NPA.
The map view of network and subnetworks
A physical connection involved in a NPA. A specific graphical flag shows that a Phys.Conn. belongs to
a NPA. This flag is represented on the payload structure view
The routing display of a path crossing one or more NPAs (LIN MSP is under analysis). See specific information on Routing.
A map of a topology containing at least a Node involved in a NPA (different from linear MSP) visualizes
a flag with the type and the name of the NPA :
The flag placement is in charge of the user (e.g. close to the right Nodes)
From the flag it is possible to retrieve the NPA and its view.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

From the browser select Network: Search: All Related Items

Figure 6. Network: Display: All Related Items

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

20 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.1.2.1 NPA display

Select option NPA

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

b)

Figure 7. Item selection: NPA


c)

The NPA list is displayed, as in the following figure

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 8. NPA list


d)

ED

Click twice on ASON NPA row and select NPA view. See following figure.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

21 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 9. NPA view selection

Figure 10. ASON NPA view

e)

ED

Clicking twice on the icons present in ASON NPA view, the following lists are displayed

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

22 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 11. Physical Connection list

Figure 12. Control Planes list

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

23 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 13. Paths crossing ASON network

Figure 14. SNC (subnetwork connection) list

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

24 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 15. TELink list

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

25 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

3.1.3 NPA modify

ASON NPA can be modified adding and removing internal or interworking physical links
The command is performed using a tool similar to the creation/modification wizard
ASON NPA can not be modified by splitting / Joining existing internal physical links. This is due to limitation
on the interface between RM and GMRE.
NOTE: Only a defined NPA can be modified.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 16. NPA: Actions: Configuration: Modify NPA

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

26 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The command is performed using a tool similar to the creation/modification wizard

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 17. NPA: Modify: step 1

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

27 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 18. NPA: Modify: step 2

3.1.4 NPA Implementation


Once a NPA has been defined, it can be implemented.
This produces the creation of the needed protection structures in the NEs.
Checks are performed during the implementation and the deimplementation:
Involved physical connections must be implemented (only for NPA implementation )

1AA 00014 0004 (9007) A4 ALICE 04.10

No path must be present in case of Rings with the exception of SNCP Rings.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

28 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 19. NPA: Actions: Configuration: Implement

3.1.5 NPA Remove


The NPA can be removed only if not implemented

1AA 00014 0004 (9007) A4 ALICE 04.10

Implement / deimplement, remove of physical connections and topologies:


In case of ASON NPAs, RM still requires to perform a payload configuration on internal links even if this
activity is only internal and not required by GMREs.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

29 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

30 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4 SRG (SHARED RISK GROUP)


4.1 SRG (Shared Risk Group) Create/Remove
The Shared Risk Group menu can be issued from the domain popup menu. This menu is constituted by
the submenu Shared Risk Group: Create/Remove and the submenu Correlate/Modify/SDH SRGs calculation. See following figure

Figure 20. Shared Risk Group menu

4.1.1 Shared Risk Group Create


SCOPE
The scope of this procedure is to create a Shared Risk Group.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From the Domain icon select Shared Risk Group: Create/Remove. The SRG Create/Remove wizard
is presented.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

31 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 21. Shared Risk Group Create/Remove


b)

Select Create and click on Next button. The Step 2 dialog box is displayed.

c)

Click on SRG type list and select from the list the desired type. Click on Apply to confirm.

1AA 00014 0004 (9007) A4 ALICE 04.10

PHYSCON LIST BUTTON

Figure 22. SRG: SRG type

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

32 / 89

Click on Finish to confirm the creation.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

d)

Figure 23. SRG Create step 2

1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.

ED

srg probability change can be accomplished via Show/Set attrbute dialog box. see following figure

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

33 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 24. srg probability change

4.1.2 Shared Risk Group remove


SCOPE
The scope of this procedure is to remove a Shared Risk Group.

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

From the Domain icon select Shared Risk Group: Create/Remove. The SRG Create/Remove wizard
is presented.

b)

Select Remove and click on Next button. The Step 2 dialog box is displayed.

c)

Click on SRG list and select from the list the SRG to remove. Click on Apply to confirm.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

34 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 25. SRG: Remove (selection)

d)

ED
Click on Finish to confirm.

Figure 26. SRG: Remove

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

35 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2.1 Correlate/Modify the set of SRGs


SCOPE
The scope of this procedure is to Correlate/Modify the set of SRGs
SEQUENCE
a)

From the Domain icon select Shared Risk Group: Correlate/Modify the set of SRGs. The Correlate/
Modify wizard is presented.

b)

Click on Physical Connection list button and select from the list the Physical Connection to correlate.
Click on Apply to confirm.

PHYSICAL CONN LIST

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 27. SRG (Shared Risk Group) Management: Correlate/Modify the set of SRGs

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

36 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

4.2 SRG (Shared Risk Group) Management

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 28. SRG (Shared Risk Group) Management: Correlate/Modify


c)

Click on Next button to proceed.

d)

Click on SRG list button and from the list select the SRG to correlate. Click on Apply button and the
click on Finish on the main window.

1AA 00014 0004 (9007) A4 ALICE 04.10

SRG LIST

Figure 29. SRG selection.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

37 / 89

4.2.2 SDH SRGs calculation

The scope of this procedure is to launch SRG calculation for WDM server
CONDITIONS
The SDH TELink inheritated the SRG values assigned to the WDM physical connections which support
the SDH physical connection. This command resets the actual (previously inherited) value and relaunches
the calculation of the SDH physical connection SRG, based upon the actual WDM SRG structure.
SEQUENCE
a)

From the Domain icon select Shared Risk Group: SDH SRGs calculation . The SDH SRGs calculation wizard is presented.

b)

Click on Physical Connection list button and select from the list the Physical Connection to correlate.
Click on Apply to confirm.

Figure 30. Shared Risk Group: SDH SRGs calculation: Physcon selectrion

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Click on Next button to proceed.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

38 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 31. Shared Risk Group: SDH SRGs calculation: SRG selectrion

1AA 00014 0004 (9007) A4 ALICE 04.10

d)

ED

The step 2 of the dialog box opens. Click on SRG list. The SRG list opens. Select the SRG and click
on Apply button. Click on Next button.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

39 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 32. Shared Risk Group: SDH SRGs calculation: launching the calculation

e)

ED
Click on Finish to complete the operation.

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

40 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5 PHYSICAL CONNECTION MANAGEMENT


5.1 Physical Connection: Administrative State menu

Figure 33. Physical Connection: Administrative State menu

1AA 00014 0004 (9007) A4 ALICE 04.10

The Physical Connection: Administrative State menu is constituted by the following items:

Set Unlock. This command forces in service the Physical Connection which was previously Locked.
The SNCs whose nominal path was crossing this Physical Connection and whose current path was
crossing a different route, revert to the nominal route.

Set Shutting down. This command rquests to GMRE the out of service the Physical Connection
with a Makebeforebreak ( soft rerouting ), i.e. GMRE will define a sequence of operations by
which the new route is made before the shutting down route is turned down.

Set Lock. This command forces out of service the Physical Connection

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

41 / 89

Check. This command asks GMRE the Physical Connection status (typically after a Set Shutting
down operation.

The above described commands can be launched also via the Maintenance wizard. See below figures.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 34. Physical Connection: ASON: Maintenance

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

42 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 35. ASON Maintenance wizard

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

43 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.2.1 Introduction
A Traffic Engineer (TE) link is a bundle of transport entities equivalent from the routing point of view. Examples of TE link are:
Bundle of physical connections / MS Trails
Bundle of HO trails
A TELink has associated a cost and a list of Shared Risk Groups (SRGs).
The definition of the TELinks inside RM applies only to ASON network. When the ASON NPA is built, the
related TELinks are automatically created in RM and in the involved GMREs.
5.2.2 TELinks creation
TELinks related to an ASON NPA are automatically created as a consequence of NPA implementation.
TELinks are composed according to the value of the bundlingRule attribute of the NPA. In particular:
oneToOne: for each physical connection a different teLink is created. The linkMetric and the srgList attributes of the created teLink object are set with the corresponding values of the physical connection
withSameRisk: the physical connection with the same linkType, linkProtectionType, cost and srgList are
grouped in the same teLink object. These attributes are set to the corresponding values of the physical
connection
The TELink can also be created as a consequence of the modification of the composition of an existing
TELink.
5.2.2.1 Update TELink
SCOPE
To update the TELink: change the cost and SRG association

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

From NPA view click twice on TELink icon: the TELink list is displayed.

b)

Select the TELink and issue Actions:Modification: Update TELink. The relevant dialog box is displayed.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

44 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

5.2 Update TELink: move physcon

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 36. Update TELink wizard


5.2.2.2 Update TELink: move physcon to a new TELink
SCOPE
To update the TELink: moving one/more physical connection/s to a new TELink, i.e. create a new TE
Link
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From NPA view click twice on TELink icon: the TELink list is displayed.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

45 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 37. NPA view: TELink icon

Figure 38. TELink list

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

Select the TELink and issue Actions:Modification: Move Physical connections. The relevant dialog
box is displayed. See below figure.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

46 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

MOVE

Figure 39. Update TELink: move physcon to a new TELink

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

47 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 40. Update TELink: move physcon to a new TELink


c)

Select the physical connection and click on MOVE button. The physcon is displayed in the destination
list.

d)

You can also change SRG, by cliccking on SRG list button, selecting the SRG and confirming with
Apply button. See below figure.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

48 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SRG LIST

ERASE SELECTED

ERASE ALL
Figure 41. Move TELink: change SRG
e)

Click on Finish to confirm . The TELink name is determined automatically.

5.2.2.3 Update TELink: move physcon to an existingTELink

1AA 00014 0004 (9007) A4 ALICE 04.10

SEQUENCE
a)

From NPA view click twice on TELink icon: the TELink list is displayed.

b)

Select the TELink and issue Actions:Modification: Move Physical connections. The relevant dialog
box is displayed. See below figure.

c)

Click on DESTINATION button. The list of TELinks having same origin and destination of the source
TELink is presented.

d)

Select the TELink where to move the Physcon and click on Apply button. The icon of the selected
TELink is now present in the dialog bo under subarea DESTINATION ( righthand side of the box)

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

49 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

e)

ED
Click on Finish button to complete the update.

DESTINATION

Figure 42. Update TELink: move physcon to an existingTELink

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

50 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

6 ASON CLIENT
A UNI (network) interface is a port that is connected to a UNI (client) port of a corresponding client device
(e.g. a router) providing Switched Connection (SC) services. The port is located on the edge of a GMRE
domain.
The management of an UNI port, implies:
Creation of an ASON client device
Definition of a physical connection with an ASON client device

6.1 Creation of an ASON client device


The user select the topology in which to create the ASON client device and issue the Create/ASON client
command. Enter the following information:
IP address of the UNIC interface
friendly name of the ASON client device
site name
Friendly name and IP address are used by the system to calculate the user label of the ASON client device
The user label of the ASON client device cannot be modified by the user.
The ASON client device is created with neType attribute = asonClient and imType attribute= virtual.

6.2 Definition of a physical connection with an ASON client device


To create an SDH physical connection involving an ASON client device, enter the UNI (client) port to create
for the selected ASON client device. In particular:
TNA address
port identifier related to the remote UNI (client)
SNPPLink identifier related to the remote UNI (client)
These information are also used by the system to calculate the user label of the UNI (client) port of the
ASON client device. The user label of the UNI (client) port of the ASON client device cannot be modified
by the user. The UNI (client) port is created with the linkType attribute set to unin.

1AA 00014 0004 (9007) A4 ALICE 04.10

The physical connection is created and the UNI (network) port is assigned to RM. This port will be assigned
to the GMRE when the NPA to which the physical connection belongs will be implemented.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

51 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

52 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7 ASON PATH
7.1 ASON PATH Create
SCOPE
Create a transport (path/trail) crossing both SDH and ASON networks.
RM provides the information to create the connection between Ingress and Egress GMREs.
In general a transport entity belonging to the ASON domain is called SNC: SubNetwork Connection. SNC
types are:

Soft Permanent Connection created by RM between two DROP ports

Switched Connection not created by RM, but by the clients (e.g. routers) of the GMPLS, between
two UNI ports

spcOnCtrlPlane: it indicates that the SNC (fully initiated and terminated into the ASON domain) is
present on the ASON DB but not in the RM DB; i.e. the DBs are not aligned.

SEQUENCE
a)

RM defines a path between aEnd and zEnd TPs

b)

RM allocates the path

c)

1)

The routing algorithm chooses to cross the ASON domain

2)

A SNC is created

RM implements the path


1)

RM, via Q3 interface, implements the cross connections belonging only to the Legacy domain

2)

RM provides to the Ingress GMRE the command to implement the SNC and the routing of the
SNC

3)

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

4)

GMRE Ingress determines also a backup SNC: in case of failure automatically the Ingress
GMRE switches on the backup SNC taking care of the all operations;

7.1.1 Interwork ASON2FMSSPRing with automatic squelching calculation


The feature permits to create a path crossing a 2F MSSPRing where it exists a NE (o more) belongs both
to a 2F MSSPRing and to the ASON domain.

1AA 00014 0004 (9007) A4 ALICE 04.10

The calculation of the squelching table of the NE(s) belonging both to a 2F MSSPRing and to the ASONdomain is still in charge of RM.
RM calculates the squelching table of the NE containing the aEnd TP (Legacy domain) and of the Ingress
NE (ASON domain).

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

53 / 89

7.1.2 Definition phase:defaultRerouting,defaultPriority and protectionType

defaultRerouting

defaultPriority

If the path/trail doesnt cross the ASON domain these attributes are not managed.

1AA 00014 0004 (9007) A4 ALICE 04.10

If the path/trail crosses the ASON domain a SNC is created and these attribute are managed. SNC attributes: rerouting and priority mirror the related attributes of the path/trail which belong to. Setting the protType attribute of the path/trail entities (in definition phase) the homonymous attribute of the SNC (belonging to the selected transport entity) get a value, but in this case it isnt a pure mirroring: the value on the
SNC depends on the result of the routing algorithm.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

54 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Two new attributes have been added to the path/trail entities:

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7.2 Visualization on maps of SNC Current, Nominal & Backup route


This feature allows the operator to visualize the current, nominal and backup route of a selected SNC
on a map. Starting from a SNC the operator can ask to highlight the path containing it. In first instance the
path highlight shows all resources.
After the first highlight the operator can ask to view only a particular path route, i.e. main, spare or service.
A filter, (applied over the resource type of the link connection and the connection in topology) put on the
option menu, allows the operator to choose among one of the following values:

Main
Spare
Service
AllRes (defaul value)

The operator can also use another filter put ever on the option menu; this filter selects the route type of
the SNC.
This route filter (applied over two local attributes routeRole and statusOnConnec) allows the operator tochoose among one of the following values:

Current (defaul value)


Nominal
Current+Nominal
BackUp

Network, NEs and links related to the selected path (in the Legacy domain) are shown with
a color in accordance with the resource type. The mapping is:
Main

Blue

Spare

Pink

Service

Green

Mapping between resource type and color (Legacy domain)


Some resources may contain resources of two different types; e.g. the two nodes containing the two naps
of a protected path. In this case the color will be the mix of the colors related to the resources type.
If a resource contains resources of three different types (e.g. a network containing a path protected with
a SNCP) the color will be white.
NAPs are shown with flags. The highlight of the SNC shows its resources with a color depending on the
route and on the resourceType.

1AA 00014 0004 (9007) A4 ALICE 04.10

Route

Resource type

color

Current

Main

Blue

Current

Spare

Pink

Nominal

Main

Light Blue

Nominal

Spare

Light Pink

C+N [current=nominal]

Main

Blue

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

55 / 89

Spare

Pink

C+N [current?nominal]

Main

Each route is shown with the related colors

C+N [current?nominal]

Spare

Each route is shown with the related colors

BackUp

Not Meaningful

White

In case of not protected path colors are those related to the resorceType=Main.
Visualization of additional SPC details through the driven zoomin on GMRE UI
The feature permits to retrieve some additional SPC details getting them by the GMRE UI.
The zoomin on GRME UI is driven, i.e. the user cannot perform any command on the GMRE UI. Selecting, by the RM browser, a SPC and choosing the Show Details on GMRE the following operations are performed:
telnet to the GMRE host (the GMRE is related to the Ingress node);
get/inventory of the additional details (the action is hidden to the user);
GMRE UI action is: show lsp lsp_index lsp_index, where lsp_index is the ID of the selected SPC.
close connection with GMRE UI.

Retrieving of SNCs/paths using an ASON physical connection (current or nominal route


The inventory starting from a physical connection provides the active path/trail crossing it. The new feature
provides others remote attributes:
SNCuserLabel: is the user label of the SPC contained into the path crossing the selected physConn;
ResourceType: indicates the resourceType of the path in case its protected (Main, Spare, Service);
RouteRole: specifies if the SPC is Nominal or backup

1AA 00014 0004 (9007) A4 ALICE 04.10

According to the possible scenarios retrieved on GMRE NEs the following combination are foreseen:
connection Status

RouteRole

Active

Nominal

NotActive

Nominal

Active

Backup

Indeterminated

Nominal

If the physical connection is not part of an ASON NPA, the role is always nominal.
APortName/ZPortName: are the end points of the path/trail;

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

56 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

C+N [current=nominal]

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

PayloadPosition.
N.B. in case of SNC protected by SNCP, the output of the inventory with filter=active is both the main andspare legs. ASON domain does not provide the active/noActive information in case of SNCP protection.

EXAMPLE
a)

From the Path list ( see Figure 43. herebelow), select the path and click on highlight button. The highlight map view is displayed. See Figure 44. on page 58

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 43. Path list

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

57 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 44. Highlight map view: Highligth

b)

ED

By selecting the option route it is possible to display current, nominal and backup route.

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

58 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 45. Current route Highligth display

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

59 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 46. Nominal Route Highligth display

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

60 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 47. Backup Route Highligth

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

61 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7.3 Path: Reroute nominal route

The scope is to change the path nominal route.


SEQUENCE
a)

The Add/Remove Protection Tool can be launched by selecting the path and clicking on the relevant
icon. See following figure.

Figure 48. Add/Remove Protection Tool

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

The Add/Remove Protection dialog box is displayed. See following figure.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

62 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 49. Add/Remove protection:Reroute dialog box


c)

Select option button Reroute and click on Next button.

1AA 00014 0004 (9007) A4 ALICE 04.10

ACONN

ZCONN

Figure 50. Path reroute: ACONN selection

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

63 / 89

Click on ACONN button. The path routing display ( nominal route ) is presented. Select the ACONNection in topology which will be the starting point of the nominal route change. Click on Select button
to confirm. The selected ACONNection in topology icon is then present in in the main box ( lefthand
side of below figure)

e)

Click on ZCONN button. The path routing display ( nominal route ) is presented. Select the ZCONNection in topology which will be the terminating point of the nominal route change. Click on Select
button to confirm. The selected ZCONNection in topology icon is then present in in the main box
(lefthand side of below figure)

Figure 51. Path reroute: ACONN selected

1AA 00014 0004 (9007) A4 ALICE 04.10

f)

ED

Click on Next button.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

64 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

d)

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 52. Path reroute: confirmation

g)

ED
Click on Finish button to launch the operation.

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

65 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

7.4 Modify the userLabel and rerouting attributes of a SNC

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
Modify the userLabel and rerouting attributes of a SNC
CONDITIONS
A path crossing the ASON domain is allocated or implemented
SEQUENCE
a)

From the routing display of the path select an SNC and issue Modify: Attributes popup menu.

Figure 53. Modify: Attributes popup menu

1AA 00014 0004 (9007) A4 ALICE 04.10

b)

ED

You can modify the userLabel and the other rerouting attributes of the selected SNC

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

66 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 54. SNC: Modify: Attributes

1AA 00014 0004 (9007) A4 ALICE 04.10

c)

ED

Verify for implemented path that the modification is propagated to the SNC selecting the Show: Details on GMRE

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

67 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 55. Show: Details on GMRE

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

68 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

8 ADD/ REMOVE PROTECTION


8.1 Add/ Remove Protection Tool
The Add/Remove Protection Tool can be launched by selecting the path and clicking on the relevant icon.
See following figure.

Figure 56. Add/Remove Protection Tool

8.1.1 Add Protection


SCOPE
The scope of this procedure is to add a protection route to an existing path.
SEQUENCE

1AA 00014 0004 (9007) A4 ALICE 04.10

a)

ED

From the path routing icon select Add/Remove Protection Tool button. The relevant wizard is presented.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

69 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 57. Add/Remove Protection Toolstep 1

b)

ED
Select option Add and click on Next button.

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

70 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

A CONNECTION

Z CONNECTION

Figure 58. Add/Remove Protection Toolstep 2

c)

ED
Click on button Get Routing Display for A connection

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

71 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 59. AConnection selection


d)

From the routing display select the A connection (in Topology) and click on Select button.

e)

Click on button Get Routing Display for Z connection

f)

From the routing display select the Z connection (in Topology) and click on Select button.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

72 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Z CONNECTION

Figure 60. ZConnection selection

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

73 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Figure 61. ACONN and ZCONN selected

1AA 00014 0004 (9007) A4 ALICE 04.10

g)

ED

ACONN and ZCONN are selected. See Figure 61. Click on Finish button to confirm. The routing
display must be refreshed. See Figure 62.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

74 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 62. Refresh of the Routing Display

8.1.2 Add Service

8.1.3 Remove Service

8.1.4 Undo reroute

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

75 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

8.2 Remove Protection

The scope of this procedure is to remove the protection route from an existing path.
SEQUENCE
a)

From the path routing icon select Add/Remove Protection Tool button. The relevant wizard is presented.

b)

Select option Remove Protection and click on Next button.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 63. Remove Protection option

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

76 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

A CONNECTION

Z CONNECTION

Figure 64. Remove Protection Toolstep 2

c)

ED
Click on button Get Routing Display for A connection

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

77 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 65. AConnection selection


d)

From the routing display select the A connection (in Topology) and click on Select button.

e)

Click on button Get Routing Display for Z connection

f)

From the routing display select the Z connection (in Topology) and click on Select button.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

78 / 89

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 66. ACONN and ZCONN selected

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

79 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 67. Warning to refresh of the Routing Display

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

80 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

9 EXAMPLE OF CLI CONNECT

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

SCOPE
The scope is to execute a connection to the 1678MCC local terminal (CLI) and launch a show operation
on ASON connections.
SEQUENCE
a)

From the map click on the Control Plane icon associated to the involved node, as per Figure 68. herebelow. The CLI terminal is displayed. See Figure 69.

Figure 68. CLI connect: click Control Plane

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 69. CLI termconnect


b)

On the CLI terminal it is possible to launch the 1st level help simply by typing question mark ?. The
1st level command options are displayed: ( see Figure 70. )

Config. Allows to configure systems entities

Delete. Deletes an item

Move. Requests a reversion

Ping. Test an IP connectivity to another node

Script. Allows the execution of a number of CLI commands as defined in the script file

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

81 / 89

Set. Configures some CLI features

Show. Displays the system configuration

Traceroute. Tests an IP connectivity to another node and records rout hope

Exit

Quit

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

The complete description of CLI commands/options can be found in 1678MCC CLI documentation.
? 1st level help

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 70. Question mark: 1st level help


c)

Enter Show, followed by the question mark, to launch the 2nd level help on the show command. The
2st level command options are displayed: ( see Figure 71. )

AlarmState. Displays the actual alarm state information of all objects

CPR. Displays the CPR systems characteristics

DPR. Displays the DPR specific characteristics

IProute. Returns the IP forwarding decisions as given to the OS_IP

Interface. Returns a list of all or specific type interfaces available at the GMRE withe the high level
attributes.

LMP. Displays LMP specific characteristics

LSP. Returns a list of all LSPs established across this node.

Label. Label

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

82 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Node. Returns nodal information.

Notification. Enables to display continuously raising notifications at CLI terminal.

NotificationHistory. Displays the last n event notifications as issued by GMRE ordered in chronological order from newest to oldest.

PM . Displays the PM specific characteristics

RSVP. Displays the RSVP specific characteristics


2nd level help

Figure 71. 2nd level help on show command


d)

Enter Show LSP to display the LSP list


.

1AA 00014 0004 (9007) A4 ALICE 04.10

LSP INDEX
Figure 72. Show LSP: LSP list

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

83 / 89

Enter Show LSP followed by the question mark, to launch the 3rdnd level help on the show command. The 2st level command options are displayed: ( see Figure 73. herebelow )

Filter. the filter tag

Interface. Returns a list of all LSPs that crosses that interface

LSPDesc. Returns a list of all LSPs according to a specified description

LSPIndex. The LSP Index

Label. Returns a list of all LSPs with a specific label

Problems. Shows the list of the problems for the path.

Sort. The sort tag

TNA. Returns a list of all LSPs for which the TNA address is registered in Generalized UNI object.
3rd level help

Figure 73. 3rd level help on show lsp command

1AA 00014 0004 (9007) A4 ALICE 04.10

f)

ED

Enter Show LSPIndex followed by the number taken from the relevant item of the list of above
Figure 72. The LSP report is displayed. See following figure.

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

84 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

e)

1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 74. Show LSPIndex command

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

85 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

1AA 00014 0004 (9007) A4 ALICE 04.10

ED

01

SC. 8 ASONGMRE

It. 01

3AL 61348 AA AA

89

86 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

10 GLOSSARY
Ingress network node:
the border node at a network at which the connection or path is entering
the network (equivalent to source node).
Egress network node: the border node at a network at which the connection or path is exiting the network (equivalent to destination node).
Source node: usually the node that requests the connection. For SDH network the ingress network node
is equivalent with source node as this node is in charge of SPC restoration actions using Source based
restoration.
Destination node: usually the node terminating the connection requests. For SDH networks the egress
network node is equivalent with destination node as this node is in charge to correlate (merge) restoration
actions.
Bridge node: The node that passes the connection along a different route. In sourcebased restoration
this is usually the source node for full path diverse routing.
Merging node:
The node that merges the restoration path back to the nominal path. For full path diverse restoration this is usually the egress network node.
SNC a subnetwork connection between the ingress and egress network node
Guaranteed SNC relates to the end to end connection across a restoration domain with guaranteed
restoration scheme from ingress to egress port of the domain.
PRC The combination of SNCP and SBR. Initially the connection is setup like an SNCP. Once one leg fails
the failed leg is restored in SBR manner and the SNCP is changed with the selected and new leg. Reversion must be supported to change back to the original SNCP once both legs are available again.
Priority Indicates the priority of the connection within the network. High priority connection can preempt
low priority connection.
Restoration coordinator A logical instance at Path Management Class category that coordinates states
of various upstream and downstream legs and requests for protection and restoration purposes.
Reversion
Provides means to revert to the nominal route once the route becomes available. Reversion can be provided in automatic mode or can be triggered manually by the operator.
SBR

source based restoration scheme from ingress to egress port of the domain

Service a service is defined in an abstract manner (e.g. gold, silver, bronze) and relates to a target connection (call) from client to client. The service is mapped to network protection restoration feature that can
be setup in various ways within the network.
Call A call is defined between two client interfaces that covers one or more connections.

1AA 00014 0004 (9007) A4 ALICE 04.10

SNCP
a permanent bridge is performed at source and destination point and both nodes performs
switching on transport plane independently. Once switched a notification report is raised at either end. Neither reversion nor restoration must be provided.
SPC
Soft Permanent Connection; initiated by RM via management plane and implemented like an
End to End path for which any protection and restoration scheme can be applied
SC Switched Connection; initiated by a source client via signaling and implemented like an End to End
path for which any protection and restoration scheme can be applied.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

87 / 89

relates to the Network route between source and destination node that is provisioned

Backup path relates to the Network route between source and destination node that is considered the
protecting (rerouted, restoration) path.
Tunnel relates to a dedicated Network path between source and destination node that might be used
for restoration paths.

1AA 00014 0004 (9007) A4 ALICE 04.10

Makebeforebreak ( soft rerouting ) defines a sequence of operations at restoration time and for
maintenance purposes that a new route is made before the old failed route is turned down.

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

88 / 89

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

Nominal route
by RM.

All rights reserved. Passing on and copying of this


document, use and communication of its contents
not permitted without written authorization from Alcatel.

11 ABBREVIATIONS
ASON

Automatically Switched Optical Network

EFD

Event Forwarding Descriptor

GMPLS Generalized MPLS


GMRE

GMPLS Routing Engine

LSA

Link State Advertisement

LSP

Label Switched Path

MPLS

MultiProtocol Label Switching

NNI

Network to Network Interface

OSPF

Open Shortest Path First

PG

Protection Group (Information object as used in Path Management)

PPRO

Primary Path Record route Object

PRC

Protection Restoration Combined

SBR

Source Based Restoration

SC

Switched Connection

SNCP

SubNetwork Connection Protection

SPC

Soft Permanent Connection

SPR

Switch Protection Report

SRLG

Shared Risk Link Groups

SRG

Shared Risk Group

SSF

Server Signal Fail

TCM

Tandem Connection Monitoring

TIM

Trail Identifier Mismatch

TNA

Transport Network assigned Address

TSF

Trail Signal fail

UNI

User to Network Interface

1AA 00014 0004 (9007) A4 ALICE 04.10

END OF DOCUMENT

ED

01

SC. 8 ASONGMRE

It. 01
3AL 61348 AA AA
89

89 / 89

Potrebbero piacerti anche