1354rm52b Manual Del Operador Vol 1

QUESTA PAGINA NON VA INSERITA NEL MANUALE
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
COD.MANUALE HDBK P/N: 957.130.872 H Ed.01 3AL 61259 AAAA Ed.01

1300NM
1354RM Rel.5.2B
OPERATOR’S HANDBOOK VOL.1/2
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

– No PAGINE TOTALI PER ARCHIVIAZIONE: = 754
– DIMENSIONE BINDER SORGENTE (du –ks): 251.526
AVVERTENZA – WARNING
IL MANUALE COMPLETO È COSTITUITO DA DUE VOLUMI – QUESTO È IL VOL.1/2
THE COMPLETE HANDBOOK IS COMPOSED BY TWO VOLUMES – THIS IS VOL.1/2
– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
SERVONO 8 SEPARATORI NUMERATI DA 1 A 8

8 REGISTERS FROM 1 TO 8 ARE NECESSARY
No pagine numerate
fase
(facciate) numbered
step
No pages da from a to
1 TARGHETTE - LABELS
2 FRONTESPIZIO - FRONT 2
3 INSERIRE SEPARATORE ’1’ - INSERT REGISTER ’1’
4 SC.1: HANDBOOK GUIDE 20 1/20 20/20
6 SC.2: DESCRIPTIONS 146 1/146 146/146
8 SC.3: NPE 188 1/188 188/188
10 SC.4: GETTING STARTED 58 1/58 58/58
CONTINUA – continues
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 VOL.1/2 RELEASED
957.130.872 TQZZA 3AL 61259 AAAA TQZZA Y 1/ 6
6

CONTINUA – continues
No pagine numerate
fase
(facciate) numbered
step
No pages da from a to
12 SC.5: OPERATION 334 1/334 334/334
ASSEMBLARE VOL.2/2 – ASSEMBLE VOL.2/2

13
UTILIZZARE I SEPARATORI 6–8 PER IL VOL.2/2 – USE REGISTERS 6–8 FOR VOL.2/2
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 748
TOTALE FOGLI A4 TOTAL A4 SHEETS: 374
WARNING FOR A-UNITS OTHER THAN A-ITALY
• Labels are done according to A-Italy binder format.

• Source file: ALICE 6.10
1AA 00014 0004 (9007) A4 – ALICE 04.10
6
Site
VIMERCATE ALCATEL OPTICS GROUP – TND
Originators 1354RM REL.5.2B

V.PORRO
ERBA,CRIPPA
FERRARI,MANCINI
OPERATOR’S HANDBOOK
Domain : NETWORK MANAGEMENT

Division : 1354RM REGIONAL MANAGER
Rubric : REL.5.2B
Type : 1354RM REL.5.2B OPERATOR’S HANDBOOK
Distribution Codes Internal : External :
Approvals
Name M.RAGNI E.CORRADINI F.CASASOLE

App.
Name
App.
INFORMAZIONI EDITORIALI
– ORIGINALE SU FILE: ALICE 6.10

• sistemazione ’figlist’
957.130.872 H
3AL 61259 AAAA
Ed.01
1300NM
1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks

1AA 00014 0004 (9007) A4 – ALICE 04.10
6
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 TQZZA
VOL.1/2 RELEASED
6
3AL 61259 AAAA TQZZA
Y
4/ 6
1300NM
1354RM Rel.5.2B
957.130.872 H Ed.01 3AL 61259 AAAA Ed.01
VOL.1/2
1300NM
1354RM Rel.5.2B
957.130.872 H Ed.01 3AL 61259 AAAA Ed.01
VOL.1/2
1300NM
1354RM Rel.5.2B
957.130.872 H Ed.01 3AL 61259 AAAA Ed.01 OPERATOR’S HANDBOOK VOL.1/2
1300NM
1354RM Rel.5.2B
1300NM
1354RM Rel.5.2B

1AA 00014 0004 (9007) A4 – ALICE 04.10
6
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 TQZZA
VOL.1/2 RELEASED
6
3AL 61259 AAAA TQZZA
Y
FINE DEL DOCUMENTO INTERNO – END OF INTERNAL DOCUMENT
6/ 6
Operator’s Handbook
Alcatel 1300NM
Network Management
1354RM Rel.5.2B
Volume 1/2:
sections 1–5
957.130.872 H Ed.01 3AL 61259 AAAA Ed.01

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01
1354RM REL.5.2B OPERATOR’S HANDBOOK
TABLE OF CONTENTS
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Handbook configuration check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 PRODUCT-RELEASE HANDBOOKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Handbooks related to the product’s software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Handbooks related to the product’s hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 1354RM REL.5.2B OPERATOR’S HANDBOOK DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 Contents of Volume 1/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Contents of Volume 2/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 LIST OF ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.1 Products, product-releases, versions and Customer Documentation . . . . . . . . . . . . . . 15
5.2 Handbook supply to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.3 Aims of standard Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.4 Handbook Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.4.1 Changes introduced in the same product-release (same handbook P/N) . . . . . . . . . . . . 16
5.4.2 Changes due to a new product-release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.5 Customer documentation supply on CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.5.1 Contents, creation and production of a CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.5.2 Use of the CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5.3 CD–ROM identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.5.4 CD–ROM updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
01 000721 validated M.RAGNI ITAVE V.PORRO ITAVE

E.CORRADINI
01A 000515 proposal M.RAGNI ITAVE V.PORRO ITAVE
E.CORRADINI
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
1AA 00014 0004 (9007) A4 – ALICE 04.10
1354RM REL.5.2B
ED 01 SC.1:HANDBOOK GUIDE
957.130.872 H 3AL 61259 AA AA 1 / 20
20
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.1:HANDBOOK GUIDE
20
3AL 61259 AA AA
2 / 20
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:
PRODUCT ANV P/N Factory P/N

1354RM 3AL 61101 AAAA 521.200.800
PRODUCT RELEASE VERSION (N.B.) ANV P/N Factory P/N

1354RM 5.2B ––– 3AL 61169 ADAA 521.560.420
SMF For NR5.x ––– ––– –––
N.B. see NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS in para.5.4.1

on page 16.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 3 / 20
20
1.3 History
Ed.01A Creation on May 15, 2000 (proposal for version 5.2B) not archived

Ed.01 Creation on July 21, 2000 (released for version 5.2B) archived

1.4 Handbook configuration check
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 01PR 01 02 03 04 05

REGISTER AND SECTION TITLE SECTION EDITION
1 HANDBOOK GUIDE 01A 01
2 DESCRIPTIONS 01A 01
3 NPE USER’s MANUAL 01A 01
4 GETTING STARTED 01A 01
5 OPERATION 01A 01
6 MAINTENANCE 01A 01
7 GRAPHICAL INTERFACE 01A 01
8 SMF USER’s MANUAL 01A 01
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 4 / 20
20
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 product’s software
Table 1. Handbooks related to the specific software application
FACTORY THIS
REF HANDBOOK ANV Part No.
Part No. HANDBOOK
1354RM Rel.5.2B
[1] 3AL 61261 AAAA 957.130.892 W
Installation Guide
1354RM Rel.5.2B
[2] 3AL 61259 AAAA 957.130.872 H
1354RM Rel.5.2B
[3] 3AL 61260 AAAA 957.130.882 U
Administration Guide
Table 2. NR 5.0B Related Handbooks
THIS
FACTORY
REF HANDBOOK ANV Part No. HANDBOOK
Part No.
or note
1330AS Rel.5.1
[4] 3AL 71109 AAAA 957.130.722 A
Table 3. Documentation on CD–ROM
See para.5.5 on page 17.
REF ANV Part No. FACTORY Part No. NOTE
Envisaged after the release of all

3AL 61262 AAAA 417.100.028
Handbooks
[5]
1AA 00014 0004 (9007) A4 – ALICE 04.10
Contains, in electronic format, the following handbooks: REF.[2] to [4]
957.130.872 H 3AL 61259 AA AA 5 / 20
20
2.2 Handbooks related to the product’s 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
• Heat–radiating Mechanical Parts
– ELECTROMAGNETIC COMPATIBILITY
– ELECTROSTATIC DISCHARGERS (ESD)
– EQUIPMENT LABELS
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 6 / 20
20
3 1354RM REL.5.2B OPERATOR’S HANDBOOK DESCRIPTION
This handbook is composed of the following volumes and sections:

3.1 Contents of Volume 1/2
SECTION 1: HANDBOOK GUIDE (This document)
The Handbook Guide gives general information on the application and use of the Handbook. The
Handbook Guide includes the following chapters:
• Chapter 1: Handbook structure and configuration check. This chapter gives information on the
whole handbook application, composition and evolution.
• Chapter 2: Product-release handbooks. This chapter lists the handbooks the Operator should
have in order to carry out the tasks allowed by the specific product–release this handbook refers
to.
• Chapter 3: 1354RM Rel.5.2B Operator’s Handbook description
• Chapter 4: List of abbreviations
• Chapter 5: General on Alcatel Customer Documentation
SECTION 2. DESCRIPTIONS
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.
This document is divided into the following chapters:
• Chapter 1: Introduction
• Chapter 2: Functionalities
• Chapter 3: Object names
• Chapter 4: Acronyms and abbreviations
SECTION 3. NPE
The aim of this document is to describe the operations related to the operation and maintenance of
the 4–F Transoceanic MS–Spring controlled by the 1354RM.
• Chapter 1: Transoceanic MS–SPRING: main concepts

• Chapter 2: Transoceanic MS_SPRING management
• Chapter 3: Broadcast Connections
• Chapter 4: Transoceanic MS_SPGRING restoring algorithm
• Chapter 5: Drop & Continue Interconnection ManagemenT
• Chapter 6: D&C Interconnection Data
• Chapter 7: APS bytes for transoceanic MS_SPRING
• Chapter 8: Features
• Chapter 9: The 4–F MS–Spring RM side
• Chapter 10: Display of the protection blocks
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 7 / 20
20
SECTION 4. 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.

The Getting Started Manual document includes the following chapters:
Chapter 2: Regional Manager graphical user interface principles
• Chapter 3: Glossary of terms
• Chapter 4: Preliminary Operations
• Chapter 5: Access to the main functionalities
• Chapter 6: Views Description
• Chapter 7: SDH Netview : map navigation
• Chapter 8: Navigation
• Chapter 9: On–Line Documentation
SECTION 5. OPERATION
This document is intended for people who are in charge of the construction of the network.
• Chapter 2: Network Configuration
• Chapter 3: Transport Management
• Chapter 4: Protection Management
• Chapter 5: Network Modifications
• Chapter 6: Special Network Views
• Chapter 7: Performance Monitoring
• Chapter 8: Operator Administration
• Chapter 9: Restricted Operators
• Chapter 10: Export of resources
3.2 Contents of Volume 2/2
SECTION 6. MAINTENANCE
The aim of this document is to describe the operations related to the maintenance of the protection
network controlled by the 1354RM.
• Chapter 2: Fault management
• Chapter 3: Integration of 1354RM with SEC Security Subsystem
• Chapter 4: Introduction to maintenance
• Chapter 5: Path/Trail Allocation Failures
• Chapter 6: Diagnostic of the NPE Ring
• Chapter 7: Logger
• Chapter 8: NML–EML consistency checks
• Chapter 9: 1354RM process control
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 8 / 20
20
SECTION 7. GRAPHICAL INTERFACE
This document is a reference handbook describing in detail the graphical interface used by the
1354RM.

• Chapter 2: Access to the main functionalities
• Chapter 3: SDH netview
• Chapter 4: SDH netview : map submenu
• Chapter 5: SDH netview: edit submenu
• Chapter 6: SDH netview: locate submenu
• Chapter 7: SDH netview: view submenu
• Chapter 8: SDH netview: construction submenu
• Chapter 9: SDH netview: supervision submenu
• Chapter 10: SDH netview: browse submenu
• Chapter 11: SDH netview: tools submenu
• Chapter 12: SDH netview: help submenu
• Chapter 13: Browser
• Chapter 14: Browser: drawing windows
• Chapter 15: Browser multicolumn windows
• Chapter 16: Browser: locate items in SDH netview
• Chapter 17: Payload configuration
• Chapter 18: Trail setup
• Chapter 19: Path create
• Chapter 20: Path/Trail constraints
• Chapter 21: Add legs
• Chapter 22: Connectivity inventory
• Chapter 23: Event logger
• Chapter 24: RM Java Browser
SECTION 8. SMF USER MANUAL
Purpose of this document is to describe to the users the services supplied by the System Management
Features in the 1354RM environment.
• Chapter 2: System Management Features
• Chapter 3: User Interface
• Chapter 4: Operator Administration
• Chapter 5: Console Administration
• Chapter 6: System Log
• Chapter 7: Periodic Actions Management
• Chapter 8: Backup / Restore
• Chapter 9: System Start / Stop
• Chapter 10: Trace Administration
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 9 / 20
20
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.1:HANDBOOK GUIDE
20
3AL 61259 AA AA
10 / 20
4 LIST OF ABBREVIATIONS
ADM Add Drop Multiplexer

ALM–IM Generic Alarm Info Model
AP Access Point
APS Automatic Protection Switching
AU Administrative Unit
BN Backbone Network
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 VC–4 that is configured to carry lower order signals is a HO–CAP)
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
DCN Data Communication Network
DNM Distributed Network Map
ECC Embedded Communication Channel
EM Element Manager
EML Element Manager Layer
EML domain A set of NEs that are maintained by the same EML–OS.
EM–OS Element Manager–Operation System
EMS Event Management Services
EPS Equipment Protection System
ESN Elementary Subnetwork
Elementary Topology. It is a grouping of some nodes connected according to specific

ET rules.
A typical ET is a ring.
FM Fault Management
1AA 00014 0004 (9007) A4 – ALICE 04.10
FOX Fiber Optic Extender
HO–AP High Order Access Points
957.130.872 H 3AL 61259 AA AA 11 / 20
20
HOP–LN High Order Path Layer Network
HOPL Higher Order Path Layer

HPOV Hewlett Packard Open View

HP-OVw Hewlett Packard Open View Windows
IAP Inventory Application
Link A transport entity provided by the client/server association.It is formed by a near–end

Connection adaptation function,a server trail and a far–end adaptation function between connection
(lc ) points. It can be configured as part of the trail management process in the associated
server layer.
LO–AP Low Order Access Point
LOF Loss of Frame alignment
LOP–LN Low Order Path Layer Network
LOPL Low Order Path Layer
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.
Map–Image Dump of the map and of the related OVwDB information in a proprietary ASCII format
MIB Management Information Base
MS–AP Multiplex Section Access Point
MS–CTPCAP Multiplex Section Termination Point
MSL Multiplex Section Layer
MS–LN 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
1AA 00014 0004 (9007) A4 – ALICE 04.10
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
957.130.872 H 3AL 61259 AA AA 12 / 20
20
PCMAP Payload Configuration Management Application
PDH Plesiochronous Digital Hierarchy

Physical A Physical Connection connects two SDH ports in the network. These two ports belong
Connection 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.
sbn Subnetwork. It is a grouping of nodes and ETs.
SDH Synchronous Digital Hierarchy
SEN–IM Simple Element Network Information Model
SNML SDH Network Management Layer
SNCP Subnetwork Connection Protection
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 near–end trail termination function, a
netwrwork connection and a far–end trail–termination function.
Trail A transport processing function which generates the characteristic information of a layer
termination 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.
TTP Trail Termination Point
TU Transport Unit
UPA Unavailable path alarm
URU Underlying Resource Unavailable
VC Virtual Container
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 13 / 20
20
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.1:HANDBOOK GUIDE
20
3AL 61259 AA AA
14 / 20
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 ”product–release” 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 Alcatel–Telecom 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.
Consequently, no supply to the Customers of design documentation (like software source programs,
programming tools, etc.) is envisaged.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 15 / 20
20
5.4 Handbook Updating
The handbooks associated to the ”product–release” are listed in para.2 on page 5.

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.4 on page 4 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 Operator’s Handbooks) are not
modified unless the new software ”version” distributed to Customers implies man–machine
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-release’s
”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
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 errata–corrige sheets is not envisaged).
1AA 00014 0004 (9007) A4 – ALICE 04.10
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.
957.130.872 H 3AL 61259 AA AA 16 / 20
20
5.5 Customer documentation supply on CD–ROM
In the following ’CD–ROM’ means ’Customer Documentation on CD–ROM’

5.5.1 Contents, creation and production of a CD–ROM
In most cases, a CD–ROM contains the documentation of one product–release(–version) and for a certain
language.
In some other cases, the same CD–ROM can contain the documentation of different
product–release(–version)s for a certain language.
As a general rule:
– CD–ROMs 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.
– CD–ROMs 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).
A CD–ROM is obtained collecting various handbooks and processing them by

Interleaf–World–View–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 CD–ROMs 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 (Interleaf–World–View) is
added and a master CD–ROM is recorded.
Suitable checks are made in order to have a virus–free product.
After a complete functional check, the CD–ROM image is electronically transferred to the archive of the
Production Department, so that the CD–ROM can be produced and delivered to Customers.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 17 / 20
20
5.5.2 Use of the CD–ROM
The CD–ROM can be used both in PC and Unix WS environments.

The minimum configuration for World View (rel.2.2.2) utilization on a PC is:

– Operative System: Windows 95 or Windows NT (3.51 and 4.00)
– Processor: Intel 486
– RAM: 16Mbyte
– Disk space: 20Mbyte
The set–up procedure is present in the booklet included in the CD–ROM box.
After the set–up 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 1981–1996

INTERLEAF Inc.
All rights reserved.
The use of WorldView is permitted only in association with the files contained
in the CD–ROMs officially supplied by Alcatel.
Alcatel documents: All rights reserved.

Passing and copying of documents and files contained in the CD–ROMs
officially supplied by Alcatel, use and communication of its contents are not
permitted without written authorization from Alcatel.
5.5.3 CD–ROM identification
Each CD–ROM is identified:
1) by the following external identifiers, that are printed both on the booklet and the CD–ROM upper
surface:
– the name of the ”product–release(s)” (and ”version” when the CD–ROM is applicable to
the versions starting from it, but not to the previous ones),
– a writing indicating the language(s),
– the CD–ROM P/N (Factory P/N 417.xxx.xxx x and ANV P/N),
– the CD–ROM 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 CD–ROM itself has been created.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 18 / 20
20
5.5.4 CD–ROM updating
The list of source handbook/document P/Ns–editions indicated in previous para.5.5.3 point 2 ) , in

association with the CD–ROM’s own P/N–edition, is also loaded in the Alcatel–Information–System as a
structured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system,
the Alcatel–Information–System automatically rises a warning toward the Customer Documentation
department, indicating the list of CD–ROMs 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 CD–ROM.
Updating of CD–ROMs always follows, with a certain delay, the updating of the single handbooks
composing the collection.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 19 / 20
20
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.1:HANDBOOK GUIDE
END OF DOCUMENT
20
3AL 61259 AA AA
20 / 20
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 FUNCTIONALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 Introduction to Functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.1 Supported EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.2 Support of SEN–IM NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.3 Support of TSD–IM NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.4 Support for Qnn 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2 EML Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2.1 EML Physical Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2.2 Support of TSD–IM based NE’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2.3 Consistency audit management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.4 Reporting during consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.5 Linear MS – Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3 Topology Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.3.2 2–Fibre MS Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.3.3 4–Fibre Transoceanic MS Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.3.4 SDH Network Layer Map Management (NETVIEW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.3.5 Map Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.3.6 Network Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.3.7 Network Access Point Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3.8 Payload Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4 Transport Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.4.1 Path Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.4.2 Path Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.4.3 Path Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.4.4 Path allocation and protection index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.4.5 OS driven restoration for HO paths & trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.4.6 Joint / Split HO–Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.5 Contiguous Concatenated AU4’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

E.CORRADINI A.CRIPPA
E.CORRADINI A.CRIPPA
1AA 00014 0004 (9007) A4 – ALICE 04.10
1354RM REL.5.2B
ED 01 SC.2: DESCRIPTIONS
957.130.872 H 3AL 61259 AA AA 1 / 146
146
2.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.5.2 AU4 C attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.6 D & C Interconnection with 1664SX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.6.1 SNCP Dual Node Interconnection with D&C in 1664SX . . . . . . . . . . . . . . . . . . . . . . . . . . 73

2.6.2 Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

2.6.3 Protection at path / trail level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.6.4 Connections in a 2 N–D&C Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.6.5 Enhanced SNCP protection in 1664SX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
2.6.6 Connection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.7 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2.7.1 Alarms on Physical Connections, Trails, HO Link Connections, Paths, Nodes. . . . . . . . 78
2.7.2 Alarm processing according to priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.7.3 QB3* Enabling UPA on specific CTP/CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2.7.4 Enable / Disable frame supervision alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2.7.5 System Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.7.6 RM to RM navigation, Multi server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
2.7.7 OS–OS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
2.8 Quality Domain and Performance Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2.8.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2.8.2 Quality Domain objects at the graphical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2.8.3 Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
2.8.4 Performance activites on objects out of Pm Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
2.8.5 Redo Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
2.8.6 Dedicated Performance Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
2.9 FAD / NAD – Functional Access Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
2.10 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
2.10.1 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
2.11 RM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
2.12 Trail Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
2.12.1 SNCP/N with POM at the incoming signal (before matrix) . . . . . . . . . . . . . . . . . . . . . . . 130
2.12.2 SNCP/N with POM at the outgoing signal (after matrix) . . . . . . . . . . . . . . . . . . . . . . . . . 131
2.13 Path/Trail Allocation Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
3 OBJECT NAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
4 ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 2 / 146
146
LIST OF FIGURES AND TABLES
FIGURES
Figure 1. The 1354RM in the SDH management hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 2. Representation for SDH radio Link equipments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Figure 3. Download enable/disable, NE isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 4. HO–Trail with and without enhanced connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 5. Example of allocation in a MS–Spring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 6. Example of allocation with B&S NE constraints in NE–1 and NE–2. . . . . . . . . . . . . . . . . . . 46
Figure 7. Path configuration status flow–chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 8. D&C SNCP – Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 9. D&C SNCP a 3 rings detailed example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 10. D&C SNCP protection – MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 11. D&C SNCP protection – Details for service connections . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 12. D&C SNCP – State diagram for protection type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 13. Broadcast path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 14. Protected broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 15. A protected Broadcast example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 16. DB representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 17. Restoration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 18. Restoration Info Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 19. Restoration Rule working states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 20. Transport Restoration States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 21. state diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 22. state A: 2 HO trails (A, B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 23. state H: 1 HO trail (C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 24. Path connectivity state diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 25. Topologies for Enhanced SNCP and 2 NE’s D&C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 26. 2–Node D & C connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 27. Double failure for a SNCP path (w/o enhanced) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 28. Topology view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 29. Enhanced SNCP connection scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 30. RM client to multiple RM servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 31. The PM fragment containment tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 32. Distribution of files in two application disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 33. Simplified representation of the 1641 SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 34. Schematic representation of the 1651 SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 35. Schematic representation of the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 36. Trail and link connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 37. Objects involved in the structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 38. POM in SNCP/N (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 39. POM in SNCP/N (II) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 40. POM in Trail Monitoring (before and after) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 41. POM in Trail Monitoring (bidirectional before and after) . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 42. POM in Trail Monitoring (detailed view of bidirectional before and after) . . . . . . . . . . . . . 134
Figure 43. trailMonitor for fault localization example( I ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Figure 44. trailMonitor for fault localization example( II ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Figure 45. trailMonitor for fault localization example( III ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 3 / 146
146
TABLES
Table 1. Starting and final Consistency status given the consistency results for consistency audit
in Mark Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 2. Initial and final Consistency status given the consistency results for consistency audit

in Notify Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 3. Objects to be taken into account when a NE becomes reachable . . . . . . . . . . . . . . . . . . . . 24
Table 4. Activity to be performed at FEP/CFG startup according to the initial Consistency Status 24
Table 5. Activity to be performed at the FEP/CFG startup according to the initial Consistency
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 6. Values of Consistency Status attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 7. Physical Connection – Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 8. MS–trail – Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 9. HO–Trail – Probable causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 10. HO–Link Connection – Probable causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Table 11. LO–Link Connection – Probable causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Table 12. Path – Probable causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Table 13. NPE Ring. Generated Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 14. Node. Generated Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 4 / 146
146
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:
• Supported EMLs and NEs
• EML Data Management
• Topology Management
• Transport Management
• Concatenated AU4s
• D&C in 1664SX
• Fault Management
• Performance Monitoring
• FAD / NAD
• Backup and Restore
• RM objects
• Trail Monitor
• Path Allocation Failures
• Object names
• Acronyms and Abbreviations

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 5 / 146
146
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.2: DESCRIPTIONS
146
3AL 61259 AA AA
6 / 146
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.
The following subjects are covered in the paragraphs which follow:
1) Supported EMLs
2) Supported NEs
3) EML Data Management Application

It manages, at NML level, data for which the EML is master (i.e. NEs, ports and the EML itself)
and forwards to the EML requested operations on them;
4) Topology management
5) SDH Network Layer Map Application

It manages HP OVw maps and the submaps and symbols contained herein. The representation
of the map is congruent with data stored in the MIB. Both logical and geographical
representations are available;
6) Network Access Point Management Application

It manages the Network Access Points (NAPs) in the HOPL and LOPL of the SDH network.
These APs are used to access the SDH network (from a PDH network);
7) Payload Configuration Management Application

It manages the assignment of the payload in established connections;
8) Transport Management
It includes the management of transport objects: path and trail
9) Fault Management
it handles the error occurrences in the network and signals it to the operator, providing also the
mapping on paths.
10 ) System Management Features

It handles all the activities related to the system management (of both RM and subordinated
EML systems).
11 ) G826 Performance Monitoring

It handles all the activities related to the Performance Monitoring measures.
12 ) FAD / NAD Management
13 ) Backup and Restore
14 ) RM objects
15 ) Path Overhead Monitoring

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 7 / 146
146
NML

A

VPN
Client
1354NN
http RMI M
Web VPN ISN

Server Server Qnn
NML
A
M 1354RM
SEN–IM + TSD–IM
EML
A
QB3* + TSD–IM
NE
A
M: MANAGER
A: AGENT
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 1. The 1354RM in the SDH management hierarchy
957.130.872 H 3AL 61259 AA AA 8 / 146
146
2.1.1 Supported EMLs
The EML supported versions make use of SEN–IM V4.0 and TSD–IM They are:
– 1353SH R5.1 and R5.2 and R5.3 SEN–IM V4.0 and TSD–IM
– 1353SH R3.1 SEN–IM V4.0

– 1353WX R1.7.1 SEN–IM V4.0
2.1.2 Support of SEN–IM NEs
These equipment are managed through their related Element Management Systems.
1353SH, by using TSD–IM, manages the following network elements:
• DXC: 1641SX
1353SH, by using SEN–IM, manages the following network elements:
• ADMs: 1641SM, 1641SMC, 1651SM, 1661SMC, 1664SM
• 1631FOX, Line Systems 1654SL & 1664SL, Microwave Eqmt. 96LUMT & 96LUHT
1353 WX, by using SEN–IM, manages the following network elements:
• DXC: 1641SX
The covered TMN functional areas are the Configuration, Fault & Performance Management ones.
The system is based on a Manager–Agent philosophy, adopted not only at the RM and EMLs (SH, WX)
interface but also between RM User Presentations and RM Information Management functions.
The communication among RM User Presentation, RM Information Management and Element
Management functions is performed through CMISE services.
In more detail, the managed equipment are:
– 1641 SM Full Matrix
– 1641 SMC
– 1651 SMC R2.0
The equipment is only able to manage 2 AU4’s for each aggregate. The 1651SMC is derived from
the 1641SM full matrix.
– 1651 SM
– 1661 SMC
See also the chapter related to path management for enhanced connectivity support and the chapter
related to network topologies for MS–SPRING support.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 9 / 146
146
– 1641 SX 5.3.2 CL1 with STM–16 ports
STM–16 SDH ports are managed.

Moreover, this includes the:

• replace of Supervised CTP with: CTP plus Trail Monitoring plus Supervised Unequipped
Bidirectional (the MIB has to be migrated)
• handling of PU from string to integer (no need for migration)
• loopback on PDH ports.
– 1641 SMD Drop–Shelf
This is the tributary extension for 1651SM and 1661 SMC. The management of this equipment is
transparent to RM. Through the PDH port name, the user can acknowledge whether the port is
related to a Drop Shelf unit or not.
– 1631 FOX
This is a tributary feature of 1641SM, 1641SMC. The Fox is presented as a NE by SH. The Fox is
connected to one or two NEs using STM–0 physical connections (see Network Topologies chapter).
The FOX ports and the 1641SM ports connected to FOX have the attributes physical port type equal
to STM0 and SDH Port Type set to Master or Slave.
The construction and activation phase checks permit to acknowledge that:

• 2 Fox cannot be connected together.
• 2 ADMs cannot be connected using STM–0 ports.
• A Fox cannot be placed in an SNCP ring.
• Ports have to be connected respecting the Master–to–Master, Slave–to–Slave rules. Master or
Slave information is displayed on the OVW icon. Consistency for run–time changes on
Master/Slave is left to the user.
After creating and implementing the objects (Nodes and physical connections), the configuration at
HO is started thus creating the AU3 HO–CTPs and AU3 HO–Link Connections.
The Physical Connection configuration can be performed. The possible values of the LO
configuration is only 21*TU12. The AU3 LC and AU3 Trail configuration cannot be achieved.
It is possible to set up the AU3 trail by specifying the end CTPs. If the Nodes are specified and one
of the two is a Fox, the operation is refused because of not managed impacts on TDL.
The setup of the Trail is available through the TDL. The Trail cannot have pass–through in the ADM
1641SM.
During the allocation activity the constraint related to the fixed mapping between a given PDH 2 Mbits
port and the time slot of the TU12 on the STM–0 Physical connection is taken into account.
Because of NE limitations is not possible to set–up SNCP at CO board level. This constraint is taken
into account by RM during the path allocation phase.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 10 / 146
146
– 3*45 Mb Tributary board
The routing algorithm is able to use TU3 resources in order to route 45 Mbits paths. A check is
performed to avoid path setup between 34 and 45 Mbits PDH ports.
– 2 / 34 Mb Transmux Board (ADMs)
RM does not manage all PDH TPs related to this board but only the 16 TU12’s.
At the user interface, the RM user is able to work on 16 * 2 MBits ”equivalent” PDH ports and related
naps.
The user can use these naps to set–up 2 Mbits paths.
Alarms on transmux PDH port and on TPS not shown by RM (e.g. 8 Mbit tp’s) are related to the
impacted ”equivalent” PDH ports (see SEN–IM specification). These ”equivalent” alarms produce
on the path an ”alarm in PDH” correlated alarm.
– 2 / 34 Mb flexible Transmux Board (1641SX )
See previous point.
In addition RM is able to ask the 1353WX the conversion between 16 * 2 Mbits PDH port and 1 * 34
Mbit port.
The operation is available in the Browser by selecting one of the appropriate 2 Mbit equivalent ports
(or the 34 Mbit port that can be configured in the reverse operation). It it is accepted by WX, all the
”equivalent” 2Mbit/s ports (or the 34Mbit port in the reverse operation) will be deleted and the new
34Mbit/s port will be created.
Note that no NAP should be defined for the ports to be removed (i.e. the ports must be observed).
RM only checks the port selected by the user and not all the impacted ports. The complete check
is performed at WX level.
– 2/140 Mb flexible Transmux Board (1641SX )
See previous points.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 11 / 146
146
2.1.2.1 SDH Microwave equipment
Microwave Equipments (9600LUH, 9600LUM) are only visible at the level of ports and MS–tp’s. The
equipment are mainly managed by the EML (1353SH) via SEN–IM.

At RM level, the target is to be able to visualize alarms, understand the topology supporting a given
physical connection and start navigation to the correct EML.
2.1.2.1.1 Procedure
In order to manage SDH Microwave equipment, the RM operator should apply the procedure described
in the following.
The procedure is based on the simple case of a physical connection (in the example PHYS_A) ”supported”
by 2 Radio Systems (in the example RL_A and RL_B) but more complex configurations are possible (e.g.
4 STM1 connections used in 4 SNCP rings based on 2 Line Systems interconnected at STM4 level
eventually in a1+1 protection configuration).
– Create, activate and implement the connection (in this case PHYS_A) according to the usual rules
and without taking into account of the Radio Systems.
This does not allow to include Radio Systems (or Line Systems) in the normal topologies used
for path management (e.g. SNCP–Rings).
– create at least one ”dedicated” subnetwork to contain only Radio Systems (or Line Systems).
This is not stricly required but it is suggested for keeping clean the network representation.
– create in the ”dedicated” subnetwork, a meshed ET devoted to contain the (2) Radio Systems
involved in the Physical Connection (in this case RL_A and RL_B)
The name of the ETs, for documentation purposes, should be related to the name of the physical
connection supported by the Radio Systems (in this case for example PHYS_A_TOP).
The Radio Systems are connected together in the ET using the Radio ports. In order to
represent optical connections between Radio Systems and NEs at the end of the physical
connection (NEs at the end of PHYS_A), the user should add the appropriate number of Virtual
Nes (in this case 2). This permits, when the meshed ET is activated, to assign at SEN–IM level
the optical ports of the Radio Systems thus enabling the collection of the related alarms.
Furthermore, the names of the physical connections in this special ET (PHYS_A_TOP in the
example) should be related to the physical connection supported by the Radio Systems
described in this topology (see Figure 2. ).
These ”special” meshed ETs should be normally not involved in any external connection.
– activate and implement the meshed ET (in this case PHYS_A_TOP)
RM prevents the HO configuration of the physical connections included in this special ET both
after the implementation and following a manual operator command. The check is performed
on the NE type at the end of the connections; the configuration of the original physical
connection (PHYS_A) is of course allowed because is terminated on normal NEs.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 12 / 146
146
1 1
1641SM 1641SM
STM1
STM–1 STM–1
PHYS_A
Step 1 ) correlate Step 2) A Link indicator is created

visualizing the alarm status of the Radio
Systems and allowing the navigation with a
double click
PHYS_A_TOP
ÉÉÉ ÉÉÉ
RL_A RL_B
ÉÉÉ
Virtual
STM1
9600luM
STM1
9600luM ÉÉÉ
Virtual
STM1
STM–1 STM–1 STM–1 STM–1 STM–1 STM–1
PHYS_A/opt_A PHYS_A/radio PHYS_A/opt_B
Figure 2. Representation for SDH radio Link equipments
– ”link” the physical connection based on Radio Systems (in this case PHYS_A) with the just
implemented ET (in this case PHYS_A_TOP)
The ”link” is an operation available in OVW acting on the physical connection.
The ”link” is represented in the submap by a dedicated symbol displayed on the physical
connection. This symbol allows the navigation to the ET (double click) and receives its color
from the synthesis (worst case) of the alarms affecting the involved Radio Systems (in this case
RL_A and RL_B).
The link information is saved in the MIB as an attribute of the physical connection. This allows
to display the relationship on all the maps.
When the layout of the Radio based physical connection (PHYS_A) is modified (e.g. following
the moving of one of the Nodes at the ends of the physical connection), all the ”link” symbols
eventually present in the submap (not just the one involved in the move operation) are deleted
and placed again in the new correct positions.
If the ”link” symbol is deleted by the user by means of a special command available in ovw, the
symbol is deleted from the map and the attribute on the Physical Connection (RM MIB) is set
to NULL. In the current implementation if more links are present in the same submap pointing
1AA 00014 0004 (9007) A4 – ALICE 04.10
to the same dedicated meshed ET (in this case PHYS_A_TOP), all the ”link” symbols will be
deleted.
957.130.872 H 3AL 61259 AA AA 13 / 146
146
If the special meshed ET (in this case PHYS_A_TOP) is deleted before cancelling the pointing
”link” symbols (i.e. one or more ”link” symbols are still present on the maps), a synchronization
activity is required.

2.1.2.2 Management of SUB STM1

The management of SUB STM1 links can only be performed in a manual way: the operator should assign
the unavailable LCs to a specific NAD / Initiator (see NAD Management) preventing the usage from normal
operators during LO path allocation activities.
2.1.2.3 Line System equipments
Same considerations done for microwave equipments are applicable for line systems (1654SL, 1664SL);
the main difference is that more Physical Connections can be based on the same meshed ET containing
Line Systems.
2.1.2.4 1686WM R3.2
The equipment is managed only partially at RM level:
– no port of the NE is available at RM level and, as a consequence no physical connection can be

defined
– no alarm nor alarm syntesis is available at RM level.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 14 / 146
146
2.1.3 Support of TSD–IM NEs
2.1.3.1 1664 SX 1.3.1 CL2

The following features are supported:

– D & C dual node
– D & C single node
2.1.3.2 1664 SM R 3.1 in NPE and SNCP configuration
This equipment introduces a new model in terms of matrix limitations: it is only able to work at HO level
and has no limitations in terms of time–slots for SNCP connections. It supports 4–F transoceanic
MS–SPRING. STM4 tributaries are supported without linear protection management.
2.1.3.3 1660SM Rel. 1.1 B
It is a mini–crossconnect with 64 STM1 equivalent ports.
The dual–node SNCP ring interconnection with D&C in stacked rings (also called “2 Nodes coupling”) is
supported only if NE’s are properly isolated in meshed ET’s as depicted in Figure 25.
2.1.3.4 1540SD and 1540PO
As far 1540SD is concerned, this includes:
– the support of SDH section ( STM–1 or STM–4 ports ). Narrow Band ssction is managed by 1353DN
and Broad Band section is managed by AWS.
As far 1540PO is concerned, this includes:
– the support of SDH section ( STM–1 or STM–4 ports ).
2.1.3.5 1664SM R3.2
As far RM is concerned, this includes:
– the support of concatenated AU4 (AU4–4c)
– the support of lockout command and WTR provisioning in NPE
2.1.3.6 1641SX R5.3–2 CL3
As far RM is concerned, this includes:
– AU4–4C
– Alarms in case of “blocked matrix”

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 15 / 146
146
2.1.4 Support for Qnn 1.1
The support of Qnn interface towards the National Network includes:

– Dynamic assignment of TP’s at the Qnn interface

– Ability to define constraints at node level for path allocation
– Ability to allocate a path without using alarmed resources
– Start–up of path creation according to the RM user
– Start–up of path list according to the RM user
– Reporting of the route of a given path in textual format
– AU4 Concatenation Management
Thru the Qnn interface the AU4 creation/deletion is notified as a consequence of concatenation /
de–concatenation activities performed by RM on boundary CTP’s
AU4–nC paths can be managed through the Qnn interface in a similar way of paths with other rate.
– Ability to define constraints at ctp level for path allocation
It has to be possible to set constraints for path allocation also on CTP’s not visible at the Qnn interface.
The set constraint operation is performed identifying the CTP’s (internal to the RM domain) through its user
label. The user label is obtained by the user through the browser after having applied a zoom–in operation
into the relevant RM.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 16 / 146
146
2.2 EML Data Management
This functional area manages, at SNML level, data for which the EML is master (i.e. NEs, ports and the
EML itself) and sends to the EML requested operations on them.
The following functions are available:
a) upload EML data (EML attributes, NEs and ports) from EML and keep them inside the SNML–DB
consistent with data inside the EML–DB;
b) Manually force, on EML basis, a procedure of re–alignment between EML and NEs (audit);
c) Manually enable/disable the configuration download from the EML to a specific NE.
2.2.1 EML Physical Data Management
The following functions are provided:
– EML management:
• EML data alignment. This function allows to upload the EML data from the EMLs, . The uploaded
data are stored in the SNML DB and kept consistent with the corresponding data stored in the
EML DB by means of messages (Notifications).
Managed EMLs can be defined in two ways:
– off–line in the SNML DB (see EML data off–line definition) or
– dynamically created when SNML receives a start–up notification from an unknown EML.
The alignment process is executed in the following cases:

– at SNML start up time (it can be inhibited by setting the attribute ”no automatic download”
on the EML),
– through a polling mechanism, with customized time out,
– when an EML becomes reachable after having been unreachable. This condition is tested
by the EML polling service.
– upon receiving the EML start–up notification.
– on user’s request.
The logical steps of this functionality are:

– data about EMLs are uploaded (commands are sent to the EML in order to get the
attributes of each EML),
– for each EML, all the managed NEs are uploaded (a command is sent to the EML in order
to get the managed NEs and their attributes),
– for each NE all the ports (SDH and PDH) are uploaded (a command is sent to the EML
in order to get the related ports and their attributes),
– commands will be sent to the EML in order to mark ”NML observed” every uploaded ports;
every EML modification involving observed ports has to be notified to the SNML by means
of notifications;
• EML polling. A polling mechanism surveys if EMLs are reachable or not. If an unreachable EML
is found, it generates an alarm and defines the EML as ”unreachable”. Should be found a
reachable EML that was defines as ”unreachable”, it marks the EML ”reachable”, removes the
previous alarm and starts the EML data alignment service.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 17 / 146
146
• EML data off–line definition. This functionality provides the user with the possibility to define the
following data:
– EML domain: defines a new EML domain as real or as virtual. A virtual EML domain must
be defined to collect virtual NE defined for routing reasons.

– virtual NEs : these represent NEs that are not really present in the Network Management

domain but they must be visible for routing reason (not terminated path),
– virtual Ports : these are defined for virtual NEs.
• EML Start Audit of a specific NE. This functionality allows to force the EML to perform the audit
activity on the specified NE in order to check if the EML DB is aligned with the NE one.
The operation is accepted if:
– the Configuration Download towards the involved NE is disabled (by means of the NE
Configuration Download Enabled/Disabled command)
– no other audit activity is already running for the EML
– the NE is not a virtual NE
• EML Configuration Download Enabled/Disabled. The operator can change the Configuration
Download mode of each NE belonging to the EML. To this purpose, the service uses the NE
Configuration Download Enabled/Disabled service.
– NE management:
• NE Configuration Download Enabled/Disabled. The operator can change the NE Configuration

Download .
If the Configuration Download mode is enabled, each request received by EML and addressed
to NE is forwarded to NE.
If the Configuration Download mode is disabled, each request received by the EML and
addressed to the NE is not propagated to the NE.
The operation is accepted if:

– no audit activity is already in progress for the NE
– the NE is not a virtual NE
If the operation is accepted, a command is sent to the EML in order to set the Configuration
Download attribute of the NE to the proper value (enabled/disabled).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 18 / 146
146
2.2.2 Support of TSD–IM based NE’s
With TSD–IM, RM interacts directly with the NEs and directly manages alignment, consistency, isolation
and download enable / disable.
2.2.2.1 Download disable management
The operator is able to specify for TSD–IM NEs the download disabled / enabled mode (download enabled
mode is the default condition)
When a NE is in “download – disabled” mode, no information exchange is performed between RM and

the NE and all changes are buffered in the RM MIB.
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”).
Nodes that have at least one “not aligned” object are put in a “not aligned” state.
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, will wait for download completion.
The maximum time to wait is configured as a global RM value.

When the time–out condition is detected before download completion, the operator requested operation
fails and a retry must be executed.
2.2.2.2 Ne isolation detection and recovery
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 SH and the SH isolation alarm detected by mean of a slow polling
performed by RM are reported as alarms at the RM user interface.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 19 / 146
146
Const.
Downloading Auditing

Consistency download Mark consistency audit
Cfg Changes Download Download disable Download

enable disable Cfg Changes
Download completed
Download enable
Comm problems Downloading
Comm. problems Cfg Changes
Ne reachable
Isolated Wait for stable state
(Download enable, isolated)
Cfg Changes
(not aligned objects) Download Disable
Figure 3. Download enable/disable, NE isolation
2.2.2.3 Consistency download management
The objective of this feature is to align the NE with RM Mib being RM the reference.
The operation is available for TSD–IM NEs while1354RM is in normal “online” run–level.
For QB3* NE’s (SEN–IM managed) the consistency download policy remains unchanged.
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 re–start of the
consistency download is performed.
When a Ne is in the consistency download phase, all the configuration changes on the specific NE are
refused if impacting on the real NE configuration (i.e. the implementation of a subnetwork connection is
refused but not the creation since an allocated connection doesn’t have any image in the NE).
As a consequence of this limitation, an activity on a transport entity (e.g. the path implementation) or on
a topology that has impact on a NE where the consistency download phase is ongoing, will fail (e.g. the
path implementation will fail but the path allocation will not).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 20 / 146
146
2.2.3 Consistency audit management
The objective of this feature is to verify the alignment between NE and RM Mib.
The operation is available for TSD–IM NEs while the RM system is in normal online run–level.
This is an improvement respect to previous versions where the operation was only possible with RM set
to “consistency“ run level (i.e. read/only mode).
Two types of consistency audit are available:
– Mark :
differencies are “marked” permanently in a way that cannot be distinguished from the marking
performed in case of changes driven by configuration changes at RM level. These differencies are
taken into account automatically and downloaded during the operation of enabling the download and
isolation recovery.
– Notify:
differences are “marked” in a special way not taken into account during the operation like enabling
download or isolation recovery.
The consistency audit is available on :
– Node
– NE
Consistency audit on Node / NE
The consistency audit on a Node is available when the NE is not isolated and is in download disabled
mode. The consistency audit type is “Mark” and download disabled is required in order to avoid automatic
download at the end of the audit activity. The download disabled must be set manually by the operator
before audit start.
The consistency audit on Nodes is to be used during “take–over” activities.
Objects in RM MIB not found in NE MIB are marked with “not aligned” consistency status. Please note that
“not aligned” objects are automatically downloaded when the NE is put in “download enabled” mode.
If the communication is lost during download, the operator is informed at user interface. When the
communication is resumed no automatic re–start of the consistency audit is performed.
When a Ne is in consistency audit phase, all configuration changes on the NE are refused if impacting on
the real NE configuration (i.e. the implementation of a subnetwork connection is refused but not the
creation since an allocated connection does not have any image in the NE).
As a consequence of this limitation, an activity on a transport entity (e.g. the path implementation) or on
a topology that has impact on a NE where the consistency download phase is ongoing, will fail.
Consistency audit on transport / topology entities
The consistency audit on transport entities is available not only in download disabled but also in download
enabled. This is required to avoid the stop of activities while performing the consistency on a single
transport entity (e.g. a path).
The consistency audit on transport entities is executed in the “notify” mode because in download enable
1AA 00014 0004 (9007) A4 – ALICE 04.10
mode is not possible to put the consistency status equal to “not aligned” for all the misaligned objects. This
is because “not aligned” objects are automatically downloaded, for example, during an “isolation” recovery
and, for this reason, the audit becomes automatically a download.
957.130.872 H 3AL 61259 AA AA 21 / 146
146
The not aligned objects are marked with a particular value of the consistency status :Config. mismatch.
Objects with this value of the attribute are not automatically downloaded when the NE becomes reachable
or when the download state becomes enabled.

The transport entities affected by a consistency audit are locked with a specific attribute of the working

state (auditing).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 22 / 146
146
2.2.3.1 Consistency audit on objects
The consistency audit can be executed on single TPs, subnetwork connections, NE / Node.
The consistency on the Node can only be performed if the Node is in download disabled state and it is
reachable.
During the audit, all the incoming requests on the same Node are rejected.
In the following table the releationship between the initial value of the consistency Status and the result
of the consistency is reported both for “Mark” and “Notify” mode.
Table 1. Starting and final Consistency status given the consistency results for consistency
audit in Mark Mode
Mark Mode :
Initial Object Found and consistent Object not found or not consistent
Consistency
Status
normal Normal not aligned
not aligned Normal not aligned
failed to align Normal failed to align
config mismatch Normal not aligned
aligning Not valid as initial state
planned Not to be taken into account
Table 2. Initial and final Consistency status given the consistency results for consistency audit
in Notify Mode
Notify Mode :
Initial Object Found and consistent Object not found or not consistent
Consistency
Status
normal Normal Config Mismatch
not aligned Normal not aligned
failed to align Normal failed to align
config mismatch Normal Config Mismatch
aligning Not valid as initial state
planned Not to be taken into account
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 23 / 146
146
2.2.3.2 Consistency download on objects
This operation can be executed on single TPs, subnetwork connections, NE / Node.

During the consistency download on the Node, all the incoming requests are rejected.

2.2.3.2.1 Ne unreachable to reachable transition
All current operations on the NE must be completed before serving the transition. For these operations
the NE has to be considered as still not reachable.
All operations received after the transition are queued and executed after transition completion.
The following table reports the activities to be performed on RM elementary objects related to the
Consistency Status.
RM elementary objects must be taken into account by layer in a server to client order: physical ports, NAPs,
MS–TPs, HO–CTPs, HO connections, HO–TTPs, LO–CTPs, LO connections.
Table 3. Objects to be taken into account when a NE becomes reachable
Initial Activity to be performed

Consistency
Status
normal None
not aligned alignment of all attributes
failed to align none
config mismatch none
aligning Not possible. All pending activities must be closed
planned none
2.2.3.3 Download disabled to enabled transistion

All 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 disabled.
Consistency Status.
RM elementary objects must be taken into account by layer in a server to client order: physical ports,
NAPs, MS–TPs, HO–CTPs, HO connections, HO–TTPs, LO–CTPs, LO connections.
Table 4. Activity to be performed at FEP/CFG startup according to the initial Consistency

Status

Consistency
Status
normal None
not aligned alignment on all the attributes
aligning Not possible.
1AA 00014 0004 (9007) A4 – ALICE 04.10
planned none
957.130.872 H 3AL 61259 AA AA 24 / 146
146
2.2.3.4 Startup / Restart scenario
Consistency Status.
RM elementary objects are taken into account by layers in a server to client order: physical ports, NAPs,
MS–TPs, HO–CTPs, HO connections, HO–TTPs, LO–CTPs, LO connections.
It has to be noted that the alignment of a physical port may start internally the alignment on MS–TP, the
HO–CTPs etc. .
Table 5. Activity to be performed at the FEP/CFG startup according to the initial Consistency
Status

Consistency
Status
normal None
not aligned alignment on all the attributes
aligning Alignment on all the attributes
planned none
2.2.3.5 Ne reachable to unreachable transition
All the current operations on the NE must be completed considering the NE unreachable even if the state
change again before the end of the current operations.
2.2.3.6 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 25 / 146
146
2.2.3.7 Consistency attributes
The following table gives an overall mapping of the values of consistency status and consistency activity.

Table 6. Values of Consistency Status attribute

Consistency Semantic
Status
Normal The object in the RM MIB is fully aligned with the equivalent object(s) in the NE – MIB.
Not aligned RM MIB and NE MIB are different because the RM operator has requested a change
in RM MIB causing a non–alignment.
This is a semi permanent state when the Node is in Download disabled Mode or Iso-
lated.
If the Node is moved to the appropriate state (i.e. download enabled and NE reach-
able), the system forces a download (automatic download).
If the Node is Reachable and in Download enables the object is in the aligning state
The RM MIB and the NE MIB are not in line because an audit activity detects a non–
alignment in download disable mode.
As in previous state, objects in this state are automatically downloaded when the NE
is reachable and in download enabled.
If the consistency audit is executed on transport entities and in download enabled

mode, the consistency status is set to config. mismatch
N.B. The NE comes out of the isolation state and during the isolation the object
has been modified inside the NE. RM using the NE event logger detects
the problem and “marks” the objects in order to avoid a global consistency
audit.
Failed to align The object in the RM MIB is not aligned with the equivalent objects in the NE MIB
as a result of a failure in the downloading performed from the “Not aligned” state.
Objects in this state are not automatically downloaded unless a new change is per-
formed on the object or during a consistency download.
Planned The object exists only in the RM MIB in a planned state.
This is the case for example of allocated subnetwork connections, virtual CAP’s etc.
Aligning This is a temporary value that is present only when forcing of attributes on NE is exe-
cuted.
Config Mismatch The object has been found not consistent during a consistency audit performed on
transport entities while in download enabled.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 26 / 146
146
2.2.3.7.1 Functional Agents triggering
In RM, attributes on transport entities may be updated

– following requests started by the functional Agents on TPs or connections (e.g. the implementation
of a path that is the result of a set of connection implementations). This is the case of the normal
activities supported by the FEP.
– following changes on one or more NE (completely or partially) mastered attributes on TPs or

connections. This is the case for example of the loop–back attribute on PDH ports.
2.2.3.7.2 Reporting
A specific alignment information table is used to improve reporting during alignment phase.
Contained information
This table contains the following Information for each object with a consistency status
different from normal:
• phase where the problem was detected: Consistency audit (Mark or Notify),
Consistency download, Change attribute, Isolation recovery, download enabling.....
• [ time stamp ]
• problem or info
• problem parameter (i.e. the RM attribute qualifying the problem or information).
Example :
• Change attribute: (Info–code) The attribute <xy> has not been update in the NE due
to consistency download disabled (or Ne isolation .....)
• Cons.Audit–Notify: (info–code) The TP or connection does not exist in the NE
• Change attribute: (error–code) Failure in alligning the attribute <xyz>
• Change attribute: (error–code) Failure in alligning one or more client objects

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 27 / 146
146
2.2.4 Reporting during consistency
This feature allows to present the list of RM objects not consistent with the NE one’s.

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 in–consistency
– 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
– ctp–ho
– port (pdh)
– nap
– au4RTM
– cap
– ctp–lo
– connInTopol
– pmTp
The restricted list comprises only traffic affecting attributes:
– ne (only if it is not reachable)

– msCtpCap (au4Structure, removeFromProtSchema, allAttributes)
– msProtBlock4f (msProtConfState, allAttributes)
– ctp–ho (disconnectOnNe, allAttributes)
– nap (disconnectOnNe, allAttributes)
– au4RTM (consistSt, allAttributes)
– cap (virtual, tug1Cfg, tug2Cfg, tug3Cfg, allAttributes)
– ctp–lo (disconnectOnNe, allAttributes)
The allAttributes value is used when it is not possible to determinate the attribute that caused the in–
consistency.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 28 / 146
146
2.2.5 Linear MS – Protection
1641SX – 5.3.2 manages the linear MS–protection. This is a new feature.

The protection can only be defined off–line on the NE (i.e. not through the TSD–IM interface) and only
if the involved ports (main and spare) are not carrying traffic.
For this reason, it is recommended to define the protection before assigning the port to RM.
If the port is already assigned, it has to be released (all paths must be removed).
RM presents only the main port and the related MS–TP. The MS protection block is not uploaded in RM
and therefore it cannot be managed at NML: the user should use the EML or the craft terminal.
Alarm management
Alarms on physical ports and MS–TPs are correlated to physical links and MS–Trails without taking into
account the protection at MS level.
The propagation to the HO–LCs is always performed even if the protection exists. This is because at RM
level is not possible to correlate together alarms and MS protection switch position.
The underlying protection degraded alarm is not generated neither on MS–Trails nor on physical
connections because the “low reliability alarm” is received only on SEN–IM equipments and the equivalent
alarm (SSF on protected ttp) is not available.
When the main physical connection is created, the ports at both ends are assigned to RM. Considering
for semplicity only one port, this produces the creation of the MS–TP, of the HO–CTP, of the MS protection
block and of the protected TTP in the RM MIB. The MS protection block points to two MS–TTP’s: the one
related to the spare port usually is not present in the RM MIB.
Adding protection to existing physical links / MS–Trails
The functional agent has to remove the HO–LC’s on the spare MS–Trail and has to create the MS
Protection block in a virtual state. This block is related to the involved MS–TP’s and is created in a second
step in the NE through the FEP. The FEP creates also the protected MS–TP. The functional agent creates
the protected MS–Trail
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 29 / 146
146
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.2: DESCRIPTIONS
146
3AL 61259 AA AA
30 / 146
2.3 Topology Management
The network is composed of the following topological objects in compliance with the partioning concept
(see ITU–T G.803):
– Subnetworks
– Elementary topologies
• SNCP ring
• MS–P ring (MS P ring)
• Second level subnetwork (meshed topologies)
– Nodes
The node is the lower partitioning level and corresponds to a Network Element.
The topologies contains SDH connections and are connected by means of SDH connections (Physical
connections) as defined in the following.
2.3.1 Subnetwork
A subnetwork may contain rings or nodes.
2.3.1.1 SNCP ring
It only contains nodes in a ring configuration. A ring can be managed as a whole for payload operation
purposes.
2.3.1.2 Meshed ET
It has no limits as regards topology.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 31 / 146
146
2.3.2 2–Fibre MS Spring
MS–SPRINGs can be created on maps. A special ET type and symbol are available. Checks are
performed during the validation and the activation phase in order to allow only 1661SMC and 1664SM in

the ring.

The implementation, de–implementation and removing can only be performed on the complete ring and
not on single connections.
During the implementation, RM creates, in addition to normal unprotected objects :
– the MS–Spring protection block

– protected MS–TPs
– protected MS–Trails
and sets the Node Identifier in the MS–SPRING.
The protection block and the related ports, physical connections, MS–Trails, MS–TPs can be displayed
from the Browser in graphical form.
The payload configuration activity after ring implementation creates only 8 AU4s.
Any change performed on the payload configuration of the ring requires the specification of 8 AU4s.
On the protection block, the following operations are available:
– synchronize
– release
– force east, west
– lockout east, west
– manual east, west
– change Wait To Restore time (5, 300, 600, 900 sec)
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.
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.
A view of all the MS Protection Blocks in a MS–SPRing is available in the browser. The view allows a better
understanding of the global functionality of the ring.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 32 / 146
146
2.3.2.1 Squelching Info
All the HO SbnConn’s belonging to HO–Paths and HO–Trails in MS–SPRING 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 HO–TTP and HO–CTP.
For broadcast paths, the squelching information related to legs is evaluated run time during the
implementation (when multiple legs and pass–through are merged into a single broadcast connection).
2.3.2.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.
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 SEN–IM level also when a failure on a single fiber will occur. This will
warn the operator on the reduced degree of protection.
2.3.3 4–Fibre Transoceanic MS Spring
The detailed description of the functionalities provided by 4–Fibre Transoceanic MS Spring can be found
in Section 3 . NPE ( Network Protection Equipment ) of this Handbook.
The detailed description of the procedures related to the above mentioned functionalities can be found
in Section 5 ( Operation ) and Section 6 ( Maintenance )
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 33 / 146
146
2.3.4 SDH Network Layer Map Management (NETVIEW)
This functional area manages the Network maps and their contents.

The following functions are available:

• Create map. Creates a new map in the local Map DB;
• Select a map application. A map application is an application interacting with HP–OVW in order
to modify the behaviour of OVW. Just one map application is currently selectable by the user
of the 1354RM;
• Describe/Modify map. Allows to show and modify the current map parameters;
• Save map. Saves the current map;
• Delete map. Deletes a saved map;
• List maps. Displays a list of maps available in the local Map DB;
• Open map. Opens a map available in the local Map DB;
• Close map. Closes an opened map.
– Submap navigation. A map will probably contain several submaps. An operator has the following
possibilities to navigate through the submaps and to perform submap maintenance:
• Open submap. Opens a submap ”clicking” on the associated symbol in its parent submap (see
Create submap functionality);
• Close submap. The submap will not be on the desktop anymore;
• Zoom a given submap.
• Move to parent submap. The parent submap will be placed at the top of the desktop;
• Move to root. The root submap of the current submap will be placed at the top of the desktop;
• Create submap. Creates a submap and connects it to a symbol in the parent submap;
• Modify submap. Modifies the characteristics of an existing submap;
• Delete submap. Deletes an existing submap while maintaining the symbol to which the submap
is connected.
– Object management. The following functionalities allow the operator to manage the topological
entities.
• Create object. An object instance (with associated attributes) is added in the OVW DB and in
RM–MIB.
• Delete object. Removes an object from the current submap, from the associated submap and
from RM–MIB.
• Hide object. Hides the selected object in the map;

1AA 00014 0004 (9007) A4 – ALICE 04.10
• Show hidden objects. Permits to display again the objects hidden in the map;
957.130.872 H 3AL 61259 AA AA 34 / 146
146
– Display operations. The following functions are available:
• Move symbol. Moves a symbol to another position on the submap. Connections between the
symbol with other symbols will be maintained. Thus moving a symbol (e.g. representing an NE)
might cause other symbols to be changed (e.g. link connected to the NE);
• Create background. Places a background available as graphics file on the background of a

submap;
• Remove background. The background will become blank;
• Locate object. Locates objects by attributes, by selection name.....etc.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 35 / 146
146
2.3.5 Map Management
A Network map is a graphical view of a managed network.

There are two different types (the type has to be specified upon creating the map):

Logical representation provides a network view partitioned in subnetwork, ET and nodes. It
reflects the SNML DB organization and is created by means of the
Network Construction Process .
Geographical representation provides a network view partitioned in terms of sites, NEs and inter/
intra sites connections.
– Map: Redo: Store. This command allows to store the commands required to create all topological
objects contained in the map, on both ovwdb and mibdb.
– Map: Redo: Execute. This command allows to execute all the commands previously stored by issuing
the menu Map: Redo: Store.
– Supervision: Placement: Store. This command allows to store in MIB data base the coordinates of
the topological objects, for the entire map, for the current submap or for the current submap including
the related child submaps.
– Supervision: Placement: Retrieve: Map This command allows to retrieve from MIB data base the
coordinates of all topological objects, for the entire map.
– Supervision: Placement: Retrieve: Not Placed This command allows to retrieve from MIB data base
the coordinates of all topological objects actually displayed in the New Object Holding Area. This
could apply for a user working in Read–Only modality.
– Map Distribution. It includes:
• Store map image. Stores the current map in the central DB as a map–image. When a map is
being stored, the administrator can specify the list of users (user name list) who are enabled
to load the map. It is also possible to send a mail to the users of the list.
• List map images. Lists all the map–image saved in the central Map DB;
• Remove map image. Removes a map–image from the central Map DB. It is also possible to
send a mail to the users of the list.
• Get map images. Retrieves all objects from an existing map–image in order to populate the
current map.
• Lock map image. Locks a map–image in order to prevent other users from accessing it while
the administrator is working on it. This operation also permits to send a mail to the users of the
list.
• Unlock map. Release a map–image that has been previously locked. This operation also
permits to send a mail to the users of the list.
For more detailed information refer to Section 5, Graphical Interface. In particular see paragraph 3.6.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 36 / 146
146
2.3.6 Network Construction
The following functions are provided in order to create the logical representation of the network.
– EML information upload consisting of:

• Upload EMLs. Uploads all the EMLs displayed in the ”Available EMLs” window and places them
in an orphan submap;
• Upload NEs. Uploads all NEs belonging to the selected EML and not yet used in any network
submap. The uploaded NEs are presented in the ”Available NEs” window.
• Upload SDH ports. Uploads all the SDH ports belonging to the selected NE (it can be selected
from the uploaded NEs submap or directly form the network map). Another submap will appear
if the Operator double clicks on the relevant NE icon. It contains the uploaded SDH ports.
– Network management. A network comprises sub–networks, ETs and nodes which are
interconnected. The network is the top topological object. As regards the network, the following
operations can be performed:
• Create/Delete/Modify network object. When a network is being modified, part of the objects may
be already present inside the MIB, if the network has been previously activated through the
command Activate network, other objects can be added additionally.
• Remove network. Removes the network and all its contained topological objects from the SNML
DB. This operation is enabled only for not implemented networks.
• Implement network. This command resets the involved NEs and only creates HO connectivity
objects.
• Deimplement network. This operation is possible only if no path crosses the involved network.
It marks the network as ”activated”.
Generally, the commands that can be utilized for the topological object are the same of those cited
above: they are used for the network object.
In addition, the following operations are available:
• Operators can group together the objects created. Possibilities are NEs into ETs, NEs and ETs
into sub–networks and sub–networks into networks. The operator will be able to create all
objects (ETs, Physical Connections) required for this grouping;
• An operator is able to add not managed symbols (e.g. site, room, software...) in a map ;
• When a submap is displayed, all physical connections to other submaps in the same level
(visible in higher order submaps) will be shown as external connections with a label referencing
the destination;
• An operator can organize objects according to either logic or geographic criteria (logical or
geographical maps)
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 37 / 146
146
2.3.7 Network Access Point Management
Network Access Point (NAP) management is used to manage SDH network access. A NAP is the union
between an access point and a trail termination function associated with a PDH port.

A NAP can be removed, for example if it will not be used in a path;

NAPs are uploaded from a node, ET, sub–network.
2.3.7.1 Functions
– NAP management. The following functions are available:
• Upload NAPs. RM assumes the NAP management, these NAPs are marked as ”NML assigned”
at EML level.
• Remove NAP. The NAP is deleted by RM DB and is marked as ”observed” at EML level.
• List NAPs. It presents a list of NAPs belonging to the selected topological entity.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 38 / 146
146
2.3.8 Payload Configuration Management
The payload configuration management is applied to:

– Physical Layer Network (MSL)

– Higher Order Path Layer Network (HOPL)
– Lower Order Path Layer Network (LOPL)
When implementing a network (or a part of it), the MSL entities and a default HO path layer configuration
are created. Payload configuration enables the operator to further modify the contents of HO and LO
layers.
2.3.8.1 Functions
A default HO payload configuration is created through the Implement Network/Sub–network/ET/Physical

Connection function (see SNLMAP area). It is possible to create a different configuration. The following
operations are allowed:
– Configure HO Link Connection
– Configure Physical Connection
– Configure ET. It configures all physical connections in an ET in an uniform way.
– Setup HO trail. It creates an HO trail and configure it. Information required:

• trail ends
– two nodes of the network,
– two HO–CTPs;
• Trail protection type:
– No protection;
– SNCP;
Specifying ”SNCP,” the user requests to find the best protection by minimizing the number of
overlapping NEs and physical connections.
• the rule for the sequence of the operations:
– User: the HO TTP and the trail are created. The user has to manually request (through
Allocate HO trail, Implement HO trail and Configure HO trail services) the allocation,
implementation and configuration of the trail;
– Automatic: the following steps are executed
• the ending HO– TTP and the trail are created,
• allocation: the Allocate HO trail routine is automatically started,
• implementation: the Implement HO trail service is executed if no error is present
during the allocation phase,
• the LO payload configuration (only if the previous rule is set at ”automatic”).
– Trail constraint management. The user can specify the constraints to use by the allocation algorithm
for either the allocation or the protection activity.
– Remove HO trail. This command removes the HO trail.
– Allocate HO trail. It allocates the resources for a HO Trail.
– Deallocate HO trail.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Implement HO trail. The HO trail is implemented using the same procedure used for a path.
– Deimplement HO trail.
957.130.872 H 3AL 61259 AA AA 39 / 146
146
– Configure HO trail. It configures, modifies or removes the LO path layer of the specified HO trail. The
payload structure must be indicated in the same way of HO link connections.
– Display Physical Connection Configuration. Displays the payload structure of the selected physical

connection.

– HO trail Protection/Unprotection management. For an implemented HO trail the following functions
are available:
• Protect HO trail. The procedure is the same of that described for the path. Refer to the Protect
Path function inside the PPMAP area.
• Un–protect HO trail keeping main. The procedure is the same of that described for the path.
Please refer to the Un–protect Path keeping main function inside the PPMAP area.
• Un–protect HO trail keeping spare. The procedure is the same of that described for the path.
Please refer to the Un–protect Path keeping spare function inside the PPMAP area.
– Examine ET Configuration. Displays the payload structure of all the physical connections contained
in an ET.
– Examine HO Trail Route. Displays the connections (both link connections and subnetwork
connections) composing the trail.
– Display HO Trail Configuration. Displays the lower order payload structure of a specific HO Trail.
When a HO link connection is configured to carry VC–3s or VC–12s, the corresponding HO–TTP (VC–4),
LO–CTPs (TU–3 and TU–12), HO trail and LO link connection will be created .
– Display HO Trail path usage. Displays the lower order paths using a specific HO Trail.
2.3.8.2 Support of protection at VC4 level with LO grooming
On a 1661SMC it is possible to define protected HO–Trails in which the payloaded HO–TTP is connected
via an SNCP with 2 HO–CTPs.
For all the other equipments it is still not possible to have the payloadable TTP and the HO–Trail SNCP
in the same NE.
The usage of enhanced connectivity in NEs where the feature is available is automatically selected both
during the complete allocation and during the adding of protections.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 40 / 146
146
HO–Trail protected with enhanced connectivity
SPARE
LO–LCs
LO–CTPs
LO–CTPs
MAIN
HO–Trail protected without enhanced connectivity
SPARE
LO–LCs
LO–CTPs LO–CTPs
MAIN
Figure 4. HO–Trail with and without enhanced connectivity

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 41 / 146
146
2.4 Transport Management
2.4.1 Path Management

Path management concerns the process of searching paths in the network, implementing them and setting
protection.
A path may exist between two or more NAPs;

A NAP belongs to only one path.
The following path types are:
• Unidirectional
• Bidirectional
• Broadcast
The following protection types are available:
• None
• SNCP
• D&C SNCP
• High Ord. D & C
The following bit–rates for path are provided:
• 2 Mb/s (VC–12).
• 34 Mb/s (VC–3);
• 45 Mb/s (VC–3).
• 140 Mb/s (VC–4);
• AU4–4C concatenated
SDH routing will be performed on a cost basis. This means that a route having the least cost will be used
when setting up a path.
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:
• specify the involved resource,
• indicate if the path has to cross the specified resource or not,
• specify if the constraint has to be applied to the path main route or to the spare one or both;
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 42 / 146
146
2.4.2 Path Create
• The following parameters should be provided:

– Path type
– Protection type
Specifying ”SNCP,” the user requests to find the best protection by minimizing the number
of overlapping NEs and physical connections.
– Rate
– 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
– Allocation Rule: it specifies if the path has to be allocated automatically after its definition
or subsequently upon user’s command.
– Implementation Rule: it specifies if the path has to be implemented automatically after

having been allocated or following an user’s request.
• Delete path definition. Remove a defined path. This function is not available for an allocated or
implemented or commissioned path;
2.4.3 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 sub–networks, 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
957.130.872 H 3AL 61259 AA AA 43 / 146
146
2.4.4 Path allocation and protection index
• Allocate path. It allocates a defined path and locks the resources involved.
SDH routing is performed on a cost basis (eventually respecting the constraints on path route

specified by the user). This means that a route with the lowest cost will be used when setting

up a path. Components that will influence the cost of a path are:
– Cost of resources. Each physical connection has an associated cost value, that can be
modified by the operator.
In order to provide the user with the allocation result, some indexes are calculated and
presented in a text field to be shown in the ”path list” application:
a) ”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.
NSP=(A–B)/A.
NSP is 100% if no node is used for both main and spare routes.
b) ”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.
LSP=(C–D)/C
LSP is 100% if no crossed arch is used for both main and spare routes.
M M=main; S=spare
NSP=4/6
LSP=3/5
S
M
NSP=5/6
LSP=5/5
If the achieved result does not satisfy the user, he can examine in details the allocated path retry
to allocate the path after having added the proper ”constraints” (”use main”, ”use spare”, ”not
use main”,.... ).
Anyway, note that the result is the best one that can be achieved (according to the user request)
with the current capability of the routing algorithm. The above described indexes give a ”fast
information” to the user in terms of allocation acceptable/not acceptable.
• Deallocate path. Reset the status of the path thus unlocking the resources.
– Path implementation management. An implemented path can carry traffic. The following actions are
provided:
1AA 00014 0004 (9007) A4 – ALICE 04.10
• Implement path
• Deimplement path
957.130.872 H 3AL 61259 AA AA 44 / 146
146
– Path Protection/Unprotection management. The following actions are provided:
• Protect path. The user can protect an unprotected path along the whole route (by selecting the
path) or he can protect a path inside a topology.
• Un–protect path keeping main. The user can unprotect a protected path, keeping the main
route, either along the whole route (by selecting the path) or inside a topology.
• Un–protect path keeping spare.
• Un–protect (main/spare) with check. This option includes a check of the actual switch positions
before unprotecting the path thus avoiding the active connections removal.
– Scheduled path operation. The operations that can be performed on a path (allocation/deallocation,
implementation/deimplementation) can be booked for a specific time and their execution is deferred
to the indicated time.
When an MS–SPRING is involved, the following considerations are applied.
– Path / Trail setup
LO paths using LO pass–throughs are available in MS–SPRINGs. The drawback of this feature is that,
being the ring administered at HO, a LO path can be lost not only when the end Nodes are lost but also
when intermediate Nodes crossed at LO are lost.
For protected HO paths or Trails not fully contained in an MS–SPRING, a dual ended–connection is used
to cross the MS–SPRING.
During the HO routing, the same payload position is used in all the sections as required by the MS–Spring
protection algorithm.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 45 / 146
146
2.4.4.1 Allocation algorithm
Different algorithms are used to choose link connections in allocating paths and HO trails.

2.4.4.1.1 Choice of link connections in paths

The algorithm used for the choice of the link connections in the paths (both Higher Order and Lower Order)
is the following:
a) first the routing algorithm chooses the path route;
b) for each link of the path, it chooses the first free link connection, i.e. the one with the lowest time slot
no. (e.g. 01/1/1.1), with the following exceptions:
• inside a MSSPRING, the time slot interchange is not possible: the algorithm chooses the first
free time slot ( the same ) for all the links used by the HO path. See Figure 5. herebelow.
1/1/1/1
1/1/1/2 1/1/1/2 1/1/1/2
Figure 5. Example of allocation in a MS–Spring.
• in case of NE constraint (the protected connections in all AMDs except 1664SM 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 links adjacent to that NE.
1/1/1/1
1/1/1/1
NE–1 NE–2
1/1/1/2 1/1/1/2 1/1/1/2 1/1/1/2 1/1/1/2
Figure 6. Example of allocation with B&S NE constraints in NE–1 and NE–2.
2.4.4.1.2 Choice of link connections in HO trails
The algorithm used for the choice of the link connections in the Higher Order trails is the following.
a) the routing algorithm chooses the route of the trail;
b) in each ring crossed by the HO trail, the algorithm chooses the first free time slot ( the same ) in all
1AA 00014 0004 (9007) A4 – ALICE 04.10
the links used by the HO trail.
957.130.872 H 3AL 61259 AA AA 46 / 146
146
2.4.4.1.3 Link Cost
Dynamic cost
The cost of the link depends on the no. of available resources (link connections) inside the link itself:
The link cost C is represented by the following formula:
C C 0(1 kn)
where: n = number of available resources, Co= reference cost (see below) and k is a parameter that can
be changed by the user;default values are k=2 for 2 Mbps paths, k=1 for 34 Mb, 45Mb and 140 Mb paths.
For more detailed information see Chapter Environmental Variables of the Administrator Reference
Guide.
If k is set equal to 0, the cost used by the routing algorithm does not depend on the number of free
resources.
Higher values of k mean that the cost used by the routing algorithm strongly depends on the number of
free resources.
It is possible to use k=–1, in order to force the routing algorithm to prefer links with few free resources.
Reference cost
To determine the reference cost C0 of a link, a default reference cost is assigned to each physical
connection in the network (Co = 5).
The user is able to modify this value, by means of the Set Attribute operation from the user interface.
The reference cost is inherited by HO and LO ”1 hop” links.
The reference cost Ct of a LO link mapped on more than one physical connection (i.e. using a HO trail
longer than 1 hop) is:
max (C i) Ci
C t _______________
2
where Ci are the costs of the physical connections composing the HO trail.
So this cost is lower then the summation of the single link costs along the HO trail; at the same time is
greater then most costly single link.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 47 / 146
146
2.4.4.2 Path configuration main statuses

DEFINED

Allocate
Deallocate
ALLOCATED
Deimplement
Implement
IMPLEMENTED
Commission
Uncommision
COMMISSIONED
Figure 7. Path configuration status flow–chart
As shown in the above flow–chart, the main statuses of path configuration are:
– Defined
– Allocated
– Implemented
– Commissioned
A path assumes the ”defined” status after having been created. Then the Operator has to allocate it. The
path status goes to ”Allocated” . Next step is its implementation on user’s command.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 48 / 146
146
Now the path status becomes ”Commissioned” following the appropriate command.
The reverse operations are:

– Decommissioning
– Deimplementation
– Deallocation
2.4.4.3 Management of revertive / not revertive SNCP and manual control
All the HO–Trails and paths created by RM will use not revertive switches except for drop & continue.
Ability to change SNCP switches from revertive to not revertive and vice–versa is available on :
– paths / HO– trails
– subnetwork connections at all the level of topologies (i.e. including the node level)
The manual control of SNCP (e.g. using the forced command) is available on :
– paths / HO– trails
– subnetwork connections at all the level of topologies (i.e. including the node level).
On the SNCP, the following operations are available:
– synchronization
– release
– lockout
– force main, spare
– set revertive / not revertive
The status of the SNCP is displayed using 4 attributes:
– SNCP Position (displayed on main view) : main, spare, unknown, RM main – NE spare, RM spare
– NE main, RM service – NE main, RM service – NE spare.
– SNCP Switch cause (displayed on main view) : Failure, Operator Request, None, Unknown.
– SNCP Active Command : Release, Lockout, Forced Main or Spare, Manual Main or Spare, None.
– SNCP Pending Command : Release, Lockout, Force Main or Spare, Manual Main or Spare, None,
unknown, Synchronize, Set Revertive, Set Not Revertive. It is the command under execution. It is
set to ”none” when the answer (OK or KO) is received from the EML.
If on a path or a HO–trail at least one SNCP is forced, a related attribute is set in order to inform the operator
on the reduced protection capability. This attribute takes also into account of the pending operations or
unknown states. The used attribute is ”SNCP status” and the values are: unknown, idle SNCP, Forced
SNCP, Manual SNCP, not Meaningful (see Note 1)
Alignment of the SNCP positions
Upon starting up the managing processes, all the ”SNCP statuses” of protected paths or HO–Trails
implemented are set to unknown, the SNCP positions are not updated. After a parametric time T1, the
managing process performs a synchronization for a parametric number N of protected paths and
HO–Trails with the ”SNCP status” attribute set to unknown (i.e. not yet synchronized manually or through
1AA 00014 0004 (9007) A4 – ALICE 04.10
an event). After another parametric time T2, the operation is repeated with another set of N ”unknown”
paths or HO–Trails. During this automatic synchronization, the pending command of the switches under
operation is set to Synchronize.
957.130.872 H 3AL 61259 AA AA 49 / 146
146
2.4.4.4 PATH & HO–TRAIL DROP & CONTINUE protection
A D&C protection is achieved by adding one or more Service routes ”cross–connecting” Main and Spare
(see figure below).

Service Connections are implemented by means of D&C connections.
During allocation phase, RM first finds the main and the spare routes as in the case of SNCP protection
and then tries to add service connections in all the rings crossed by both main end spare routes.
Service Connections added on the path
A Z
Service connections can be added to

single topologies
Figure 8. D&C SNCP – Examples
Service connections can also be added/removed for an allocated or implemented path or HO–Trail.
Service connections can be added not only for the complete path/trail but also specifying a given topology.
The topology is specified referring to a subnetwork connection already used by the path/trail (e.g. the
subnetwork connection in a SNCP Ring). The subnetwork connections related to the path/trail can be
1AA 00014 0004 (9007) A4 – ALICE 04.10
found using the appropriate navigation in the browser.
957.130.872 H 3AL 61259 AA AA 50 / 146
146
The adding of Service connections doesn’t report any failure if only a limited number of service
connections can be allocated according to network limitations. This behavior applies also in the case of
single topology protection i.e. only a single direction / side can be protected if no resources are found.
In order to use the constraints, the user has to :

– add constraints for the first service connection

– perform a protect command on the topology producing the allocation of the first service connection
(the second will fail)
– add constraints for the second service connection
– perform a protect command producing the allocation of the missing service connection
It is not possible to add service connections across the topological boundaries i.e. a service
connection cannot originate in a subnetwork and end in another one.
3 4 5 16 17 18 19 32
12 13 MAIN 28 29
2 33
6 34
SERVICE 20 26 SERVICE 39
1 38
Z 7 21 27 40
35 A
8 37
14 15 SPARE 30 31
9 10 11 22 23 24 25 36
Figure 9. D&C SNCP a 3 rings detailed example
Figure 10. details the MIB structure for the path of Figure 9.
%!&'

! " ! ! "
$#

()%!&' "*!+,&) "*!+,&) ()%!&' ()%!&' "*!+,&)
" #

!

! ! "! " "! ! ! "! "

()%!&' ()%!&' ()%!&' ()%!&' ()%!&' ()%!&' ()%!&' ()%!&' ()%!&' ()%!&'

MIB structure

Figure 10. D&C SNCP protection – MIB Structure

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 51 / 146
146
Figure 11. shows in detail the service connections.
32 xmitRecMain A 32xmit A

xmitMainRec Z29 rec Z29
34xmitServRecServ AZ 34xmitServRecServ AZ
xmitRec AZ 39 xmitRec AZ 39
xmitRec AZ 40 xmitRec AZ 40
35xmitServRecServ AZ 35xmitServRecServ AZ
xmitSpareRec Z31 rec Z31
36 xmitRecSpare A 36 xmit A
bidirectional path/trail unidirectional path/trail
Figure 11. D&C SNCP protection – Details for service connections
A Add protection
unprotected R Remove protection
AE Add D&C
A
protection
RE Remove D&C SNCP
R protection
R
R
ring A R SNCP
protected A
RE
AE
AE D&C
SNCP
Figure 12. D&C SNCP – State diagram for protection type

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 12. shows the status diagram for protection type.

The interconnection of SNCP Rings and MS–SPRING is possible.
957.130.872 H 3AL 61259 AA AA 52 / 146
146
2.4.4.5 Broadcast Path end points add & remove
It is possible to add or remove NAPs to/from a given broadcast or unidirectional path.

The add/remove operation is performed acting on the single NAP the operator wants to add/remove.
As end points of a broadcast path, the user can specify not only a Nap but also a Node (real or virtual)
After adding a Nap, it is possible to define constraints and then allocate and implement the path.
The added ”leg” of the broadcast can be unprotected or protected. A specific option is present in the Add
Nap form of the Browser.
An attribute describing the global connectivity status of a path is defined (values none, full, partial). This
attribute is set to partial when at least one Nap is not connected as when a new NAP is added and a new
allocation has not yet been performed or has failed.
When a NAP is removed, the involved connections are automatically deimplemented/deallocated.
From the MIB point of view, a broadcast path is represented in this RM release by means of separate legs
mapped in subnetwork connections.
SINK 1
SOURCE
unprotected unprotected SINK 2
broadcast point–to–point
SINK 3
MAIN
Figure 13. Broadcast path

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 53 / 146
146
2.4.4.6 Broadcast path protection
The protection / unprotection for broadcast paths can be performed :

– on the whole path: the legs that cannot be protected are not allocated. The connectivity status of the

path is set to partial.
– on single leg(s) both at definition time (add leg) or later when the leg is already allocated or
implemented.
In the following are given examples of protected broadcast path:
SINK 1
SOURCE
protected unprotected SINK 2
broadcast switch
SINK 3
MAIN
Figure 14. Protected broadcast

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 54 / 146
146
8
6 7
5
9
2
18 19 10 11
1 3
12
4
3
16
13 14 15
17
Figure 15. A protected Broadcast example
-

#

DataBase structure
Figure 16. DB representation

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 55 / 146
146
2.4.4.7 Path / HO trail route disjunction and overlap
A path (or a HO trail) can be used as a constraint of another path (or another HO trail); the constraint type
can be either completely disjointed (not use same route) or overlapped. The overlap can be on the same

server trail or on the same routing links. A routing link is the link connection group between two NEs having

the same route.
The constraint to overlap a given path can be the only one specified for a given path.
The constraint to be disjointed from a given path can coexist with other constraints (e.g. don’t use another
physical connection).
A constraining path must be at least allocated, otherwise allocation of the constrained one fails.
The constraint to overlap a given path (or HO trail) is allowed only at allocation time; if this constraint is
present during an add protection or add leg, the operation will fail.
The following restriction applies: the constraint to overlap a given path (or HO–Trail) is accepted only if
the 2 paths (or Trails) have the same characteristics in term of end Nodes, type (i.e. bidirectional or
broadcast or ...), rate, protection type ( SNCP or none or ....)
2.4.4.8 Path test using loopback
The loopback can be performed either on PDH ports or on NAPs (the operation is executed on the relevant
PDH ports). The loopback is not supported on SDH ports and their related TPs (i.e. CTP).
If a loopbacked PDH port is involved in a path, the loopback status is propagated to the path using a
specific attribute. The same propagation method is applied when a path is created involving loopbacked
PDH ports.
While a path has a loopback on its PDH ports it is not possible to put it into Commissioned state. On the
other hand the loopback request will be rejected for PDH ports or NAPs involved in a commissioned path.
The reporting in case of allocation failure have been partially improved.

Additional Info sent through events are now available directly in the browser for objects already displayed
in the browser: the user is no more required to access to the Event Logger.
When an event of this type is received, a specific icon in the Browser tool bar is ”animated” and the user
can display additional information by clicking on the icon itself. The list of additional info and the icon are
reset when the displayed list of information is closed by the User
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 56 / 146
146
2.4.5 OS driven restoration for HO paths & trails
Transport Manager
Restoration Manager Supervisor

Restoration
Command
Allocation Implementation
Manager Manager
Transport Alarms
Alarm Manager
Correlator RM Mib Commands to the network
Alarm Front End
Elementary alarms (UPA...)
Figure 17. Restoration architecture
The feature allows the automatic restoration of HO transport entities (path or trails) in case of network
failures.
The restoration activity has the target to provide the operation in a time interval ranging from 10 minutes
to 20 minutes.
Restoration is performed using ”add protection” mechanism and it is basically only possible on networks
composed by 1664SM and 1641SX because of the restrictions on the other NE’s about SNCP time slot
usage. It is available both on not protected and on protected transport entities.
Restoration does not use resources allocated for other paths or trails.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 57 / 146
146
2.4.5.1 Architecture
The Restoration subsystem is constituted by :

– Alarm processor and correlator

– Restoration manager
– Transport manager
The above listed blocks are described in the following.
2.4.5.1.1 Alarm processor & correlator
The Alarm processor & correlator performs collection of elementary alarms and propagates them to a
transport alarm. The functionality of this block is not suspended during the restoration activity.
2.4.5.1.2 Restoration Manager
The Restoration Manager performs the following tasks:
– it receives the alarms on transport entities. Only “SDH failure” alarm is taken into account.
– If the related transport is involved in a restoration rule, it waits the Hold Off Time time before starting;
if the alarm is still pending at the end of the “wait” time, it performs the analysis on restorable alarms.
– If the alarm is restorable, the Transport Manager is triggered by sending an appropriate action.
2.4.5.1.3 Transport Manager
The Transport Manager (TrsMng) performs the tasks of definition, allocation, de–allocation, protection,
un–protection, implementation and de–implementation of the transport entities.
TrsMng is triggered by the Restoration Manager when restoration is needed and performs the restoration
making use of the add / remove protection, implementation / de–implementation functions.
The user can select if the constraints associated to the transport entity are to be taken into account during
restoration; as default they are ignored.
The user can choose if restoration will use only not alarmed resources (default) or all resources.
TrsMng uses a specific algorithm to restore not terminated paths because only boundary CTP’s must be
used. ( See paragraph 2.4.5.1.3.1)
TrsMng uses a priority mechanism, i.e. a restoration request has greater priority than an allocation or
implementation request.
During the “wait” time, the user can manually start operations on the transport entity (e.g. add protection).
Pass – through inside virtual NEs are disabled during restoration.
If the status of the transport to be restored is not idle i.e., if some operations are in progress, retries are
automatically performed.
For broadcast paths the restoration is performed on all legs and not only on the faulty ones; only
1AA 00014 0004 (9007) A4 – ALICE 04.10
end–to–end protection is applied.
957.130.872 H 3AL 61259 AA AA 58 / 146
146
2.4.5.1.3.1 Analysis on restorable alarms
The analysis has the target to evaluate if the alarm condition can be recovered or not within the RM domain.
The following conditions are possible:
– the path is not fully terminated within RM.
a failure condition detected by RM could be related to an external problem (i.e. generated in a

part of the network which is not under RM control )
The algorithm considers the fault as internal if, along the path route, at least one disabled LC
is present on all path routes (the link connections out of boundary nodes are not taken into
account, i.e the boundary ctp is re–used by the restoration).
– the path is fully terminated within RM.
• if an SDH failure is present because of an URU ( underlying resource unavailable) alarm on one
of the PDH end ports, no restoration is possible.
• if an URU is not present the restoration is possible .
When a transport is protected and a switch has been forced by the user, no restoration is
possible.
2.4.5.1.3.2 Restoration on not terminated paths
For not terminated paths the boundary CTP’s existing on the route of the original path are used as
constraint for the allocation of the restoration rule.
In other words, if the original path is not protected the boundary CTP’s are set as “use main and spare”.
If the original path is protected and the restoration strategy is “remove protection + add protection”, then
the boundary CTPs of the spare route are temporary saved in the RM database when removing protection
and used again in the new spare.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 59 / 146
146
2.4.5.2 Information Model

Ntw Domain
Network
Rule
Domain
Topology
Put a path/trail under

restoration
Restoration Path HO–Trail
Rule
Figure 18. Restoration Info Model
In order to put a HO–Trail or a HO–Path under automatic restoration, the user selects the transport and
issues the ”Create Restoration Rule” command. See Handbook OPERATION, paragr. 2.5.
As a consequence of this command, the Restoration Rule creation dialog box is displayed. The user must
fill–in the requested attributes and confirm the creation.
The Restoration Rule related to a deleted transport is deleted too.
The Restoration Rule contains the following information:
– transport (name of the transport and type)
– Restoration hold Off time : time the system waits before starting the restoration after receiving a
transport alarm (default 5 minutes). This time is required in order to avoid un–needed restoration
commands (e.g. at path setup time).
– Restoration strategy :
• end–to–end add protection;
• optimized add protection (available only for point–to–point transport entities):
RM adds the protection at the lowest topology level common to all the disabled link connections;
• remove protection + add protection (available only for point–to–point transport entities)
RM removes all the protections from the transport entity (drop and continue, end–to–end spare,
internal spares, ...) and adds an end–to–end protection (only spare).
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Working Status : normal, hold off active, wait to restore, restoring.
957.130.872 H 3AL 61259 AA AA 60 / 146
146
– Last restoration result: none, successful, failed (when the restoration failed because of allocation
problems), not performed (when other reasons blocked the restoration process before the allocation
step e.g.: no disabled LC has been found on the path route, wrong configuration state..)
– Last restoration date: date of the last restoration (see Last restoration result to see the result of the
operation)
– constraint rule: The user can select if the constraints associated to the transport entity are to be
taken into account during restoration; as default they are ignored.
– used resources: The user can choose if restoration will use only not alarmed resources (default)
or all resources.
normal
path/trail alarm
clear alarm REST
REST
path/trail alarm
holdOffActive REST
(timer is restarted)
restoration action received waitToRestore timer expired

checks KO REST
TRS
waiting another operation in progress

TRS
restoration completed restoration action received

(successfull or not) checks OK
TRS TRS
REST = Restoration manager
restoring TRS = Transport manager
Figure 19. Restoration Rule working states
In addition the path/trail Restoration State attribute can assume the following values :
– none: a path/trail is not under restoration: no Restoration Rule is associated to the path/trail;
– supervised: a path/trail is under restoration (there is an associated Restoration Rule) but the
transport is not restored;
– restored: a path/trail is under restoration (there is an associated Restoration Rule) and has been
restored. The information for the operator is that the route has been modified by the restoration
activity; the operator must take the appropriate actions.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 61 / 146
146
The relationship between external activities and the value of the attribute is displayed in Figure 20.
remove restorationRule
none

add restorationRule
supervised
operator Acknowledge successful restoration
restored Other restorations
Figure 20. Transport Restoration States
In case of failure of the restoration action, no retry is performed.
The protection added by the re–routing activity is not removed automatically when the original fault is
repaired. The user’s intervention can be summarized as follows:
a) manually remove the protection or, in general, modify the route of transport in order to revert to the
normal route
b) modify the Restoration State from restored to supervised
In order to find out when the fault (the one causing the restoration) on the path or trail has been solved,
the operator can use the navigation command that shows the alarmed objects on the route (see Handbook
Maintenance).
If, after the restoration, the alarm on the transport rises again, a new restoration is started not taking into
account the value of the Restoration State.
For commissioned paths, a successful restoration leaves the path in the commissioned state, even if the
route of the path has been modified. In case of unsuccessful restoration, the final state of the path can be
different (e.g. partially implemented): a manual operator activity is required to revert to commissioned.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 62 / 146
146
2.4.6 Joint / Split HO–Trails
The Split / Joint Physical Connections and HO–Trails are part of a suit of tools for Network Modification.
2.4.6.1 Split a HO–Trail

A given HO–Trail 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 HO–Trail 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 HO–Trail is deleted
– two new HO–Trails are created
– The LO–Paths ”crossing” the splitting Node are modified by adding LO pass–through 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 LO–Paths 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.
2.4.6.2 Join two HO–Trails
Two HO–Trails entering in a given NE can be joined in order to reduce the LO usage of resources.
Inputs to the procedure are :

– the HO–Trails 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 LO–paths using the original HO–Trails are crossing with pass–through connections the
intermediate NE without LO time–slot interchange.

– the old HO–Trails are deleted
– the new HO–Trail is created
1AA 00014 0004 (9007) A4 – ALICE 04.10
– the LO–Paths ”crossing” the original HO–Trails are modified by removing the pass–through
connections in the intermediate NE. The related protection indexes are updated.
957.130.872 H 3AL 61259 AA AA 63 / 146
146
intermediate node.

The operation reduces the impacts on the existing traffic: LO–Paths 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.
2.4.6.3 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.
A
disconnect client paths connect client paths
from 1W to 4 E from 1W to 4E
B
deconfigure trail A configure trail A
deconfigure trail B configure trail B
C
deimplement conn 2 of trail A implement trail A
deimplement conn 2 of trail B implement trail B
D
JOIN join trails A,B into C split trail C into A,B SPLIT
E
implement trail C deimplement conn 2 of trail A
F
configure trail C deconfigure trail C
G
connect client paths disconnect client paths
from 1W to 4 E from 1W to 4E
H
Figure 21. 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.
– 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 point–to–point connections in topology without time–slot interchange; these
connections can be allocated or implemented;
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 64 / 146
146
NAP LO CTP LO CTP LO CTP B1 LO CTP B2 NAP
A1 LO LC A A2 LO LC B
HO trail A HO trail B
HO LC A HO LC B1 HO LC B2
1 2 3 4
W E W E W E
Figure 22. 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 CTP–CAP 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 NAP
LO CTP A1 LO LC C LO CTP B2
HO trail C
HO LC A HO LC B1 HO LC B2
1 2 3 4
W E W E W E
Figure 23. state H: 1 HO trail (C)
Note: in every state there is no difference in nodes 1 and 4.
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
1AA 00014 0004 (9007) A4 – ALICE 04.10
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 ...).
957.130.872 H 3AL 61259 AA AA 65 / 146
146
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:

a) to continue, performing the following steps:
1) implement trail B;
2) configure trail B;
3) connect client paths from 1W to 4E;
b) to go back, executing the join trails (A, B) or performing the following steps:
1) deimplement connection in node 2 of trail B;

2) deconfigure trail A;
3) deimplement connection in node 2 of trail A;
4) 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.
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 LO–Paths impacted by the operation (supported by the involved
HO–Trails) are reported too.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 66 / 146
146
2.4.6.4 Path connectivity
The path management activities are impacted by the introduction of join and split operations because,
during a join / split HO Trail, the client paths are temporary disconnected between 2 CTPs.
The “connectivity” attribute of paths is used to keep into account the interruption.
It can have the following values:

– notConnected: the path is not allocated;
– disconnectedNAPs: some legs allocated (meaningful only for broadcast paths);
– interrupted: disconnected between 2 CTPs;
– disconnectedNAPs and interrupted: disconnected between 2 CTPs and some legs allocated
(meaningful only for broadcast paths);
– fullyConnected: all legs allocated and no interruptions.
The following figure reports a state diagram of this attribute.
dealloc not dealloc

connected
remove leg
add leg automatic release NAP
dealloc dealloc
alloc alloc
(some legs allocated) (all legs allocated)
remove leg keep NAP, add leg user fully
disconnected connected
NAPS alloc, add leg automatic
connect, connect,
disconnect disconnect
remove leg remove leg
keep interrupted NAP keep interrupted NAP
disconnected
NAPS and interrupted
interrupted
state meaningful for every path
state meaningful for broadcast paths only
Figure 24. Path connectivity state diagram

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 67 / 146
146
2.5 Contiguous Concatenated AU4’s
In this chapter it will be used the AU4–nC notation (n=4, 16, 64), even if only the n=4 value
is managed in 1354RM5.2 release.

The following notation is used in this paragraph:
– HO–CTP: AU4 which transports payload requiring normal capacity;
– AU4–nC CTP: AU4 which transports payload requiring greater capacity;
– HO–LC: Link Connection between two HO–CTP’s;
– AU4–nC LC: Link Connection between two AU4–nC CTP’s.
2.5.1 Introduction
Contiguous Concatenated AU4’s management is implemented with the following functionalities:
– The user constructs the network inserting Virtual NEs or reusing the existing Virtual NEs in order to
describe the Physical Connections leaving the network managed by RM and supporting the AU4–nC.
Currently no Alcatel equipment is able to terminate AU4–nC paths.
– The user configures the network link by link in order to move resources from the HO layer to the
AU4–nC layer.
– The concatenation/deconcatenation activities are performed at User Interface by selecting the

MS–trail containing AU4s/AU4–nCs and issuing Payload configuration; a view is presented, to
configure the structure (concatenating AU4s or deconcatenating AU4–nCs).
As a consequence of the above activities HO/AU4–nC Link Connections are created/deleted.
The HO/AU4–nC Link Connections are visible from the Payload configuration view of the physical
links/MS trails.
– The user can create paths terminated on virtual NEs. The equivalent virtual NA’s and PDH ports are
created.
– The user can allocate the AU4–nC path.
During the allocation only AU4–nC LC’s are taken into account. If no AU4–nC LC is available, the
allocation fails.
– The AU4–nC path can be implemented, de–implemented, de–allocated.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 68 / 146
146
2.5.2 AU4 C attributes
The following classes are modified in order to manage the Contiguous Concatenated AU4’s feature.
– Path
New values are added for the following attribute:
– Rate. AU4–4C, AU4–16C, AU4–64C values are added.
– MS Trail
New attributes:
– “au4Structure”: it is a string that describes the structure of the MS trail in terms of AU4 and AU4–nC.
The attribute is stored in the RM MIB as a string;
– “supportedConcatenatedAU4”: it is a set of the possible types of concatenation supported by the

MS–trail. The concatenation types are those supported, at the same time, by the two MS–TP’s ending
the MS–trail. The possible types of concatenation are: “null”, AU4–4C, AU4–16C, AU4–64C and
“unknown”. The value “unknown” is used to indicate that, due to a problem, it is not possible to retrieve
the information of the concatenation types supported by the two MS–TP ending the MS–trail and so
it is not possible to calculate the concatenation types supported by the MS–trail.
New values for the following attributes:
– The working state. “AU4 configuring”, “failed to AU4 structuring” and “synchronizing” values are
added.
New actions:
– AU4 configuration. The provided information are:
• “au4Structure”.
– MS–trail synchronization. The provided information are:
• the list of the attribute to be synchronized (only the “supportedConcatenatedAU4” can be

specified).
– Link Connection
New values are added for the following attributes:
– The rate. AU4–4C, AU4–16C, AU4–64C values are added.
– Routing Link
– MS–TP
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 69 / 146
146
New attributes are added:
– supportedConcatenatedAU4: it is a set of the possible types of concatenation supported by the port.

The possible types of concatenation are: “null”, AU4–4C, AU4–16C, AU4–64 and “unknown”;

– au4Structure: it is a string that describes the structure of the MS–TP in terms of AU4 and AU4–nC.
The attribute is stored in the RM MIB as a string; a conversion is performed to show it to the operator
in a more suitable way.
– CTP
– Connections
– Port (belonging to virtual NE)
– The physical port type. c4–4C, c4–16C, c4–64C values are added.
– NAP (belonging to virtual NE)
– The rate. c4–4C, c4–16C, c4–64C values are added.
– The “supportedConcatenatedAU4” attribute of the MS–trail has to be set in according to the values
of the two MS–TP’s ending the MS–trail. In particular, if the value of one (or both) the MS–TP’s ending
the MS–trail is “unknown”, the “supportedConcatenatedAU4” attribute of the MS–trail has to be set
to the “unknow” value.
– If one of the two ports ending the physical connection to implement is a “virtual” one, the related
MS–TP has to be created with the following attribute values:
• “supportedConcatenatedAU4” equal to all allowed concatenation types;
• “au4Structure” equal to all HO–CTP’s (no concatenation).
N.B. The creation of the MS–TP, and the related HO–CTS’s, is performed in the Implementation
activity as the EML–IM that manages the virtual NEs is a QB3* one.
– The command fails in the following cases:
• for physical connection: the physical connection contains one or more AU4–nC link
connections;
• for ring and physical connection: the Working State of the related MS–trail has to be “normal”.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– creation of the HO/AU4–nC link connections according to the situation described by the array;
– updating of the MS–trail, setting the Working State=”normal”.
957.130.872 H 3AL 61259 AA AA 70 / 146
146
N.B. A positive response is sent by the TSD–IM Front End Processor in one of the following cases:
– NE reachable and modification OK (Consistency State of the MS–TP’s equal to “normal”);

– NE not reachable (Consistency State of the MS–TP’s equal to “not aligned”);

– NE in download disabled state (Consistency State of the MS–TP’s equal to “not aligned”).
– updating of the MS–trail, setting the Working State=”failed to AU4 structuring”.
– remove the problem and then perform the “AU4 configuration” activity again confirming the
previous request;
– come back to the situation before the problem.
N.B. Take into account that, in case of “virtual NE”, no request is sent to the TSD–IM Front End
Processor. So the deletion/creation of the HO–CTP’s/AU4–nC CTP’s and the related
HO–LC’s/AU4–nC LC’s is in charge to the Topology Management process.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 71 / 146
146
2.5.2.1 MS–trail synchronization Activity
The user, on the User Interface, has to select the MS–trail to be synchronized.

The following checks are performed:

– the Working State of the MS–trail must be “normal”.
The “MS–trail synchronization” action on the MS–trail with the “supportedConcatenatedAU4” is sent to the
Topology Management.
2.5.2.2 Topology Management MS–trail synchronization
The following checks are performed:
– the Working State of the MS–trail has to be “normal”.
The following steps have to be performed by the Topology Management process:
– updating of the MS–trail, setting the “supportedConcatenatedAU4”=”unknown” and the Working

State=”synchronizing”;
– requesting of the synchronization of the “supportedConcatenatedAU4” of the MS–TP to the TSD–IM

Front End Processor (via a “synchro” request on the “supportedConcatenatedAU4” attribute of the
MS–TP’s for each MS–TP ending the MS–trail).
Receiving the two TSD–IM Front End Processor responses (positive or negative), the following steps have
to be performed by the Topology Management process:
– updating of the “supportedConcatenatedAU4“ attribute of the MS–trail according to the values of the
“supportedConcatenatedAU4” attributes retrieved with the “synchro”’s;
– updating of the MS–trail, setting the Working State=”normal”.
N.B. A positive response is sent by the TSD–IM Front End Processor in one of the following cases:
– NE reachable and modification OK (Consistency State of the MS–TP’s equal to “normal”);
– NE not reachable (Consistency State of the MS–TP’s equal to “not aligned”);
– NE in download disabled state (Consistency State of the MS–TP’s equal to “not aligned”).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 72 / 146
146
2.6 D & C Interconnection with 1664SX
2.6.1 SNCP Dual Node Interconnection with D&C in 1664SX

This feature allows to support D&C in network configuration where two Cross–Connects are closing two
(or more) SNCP rings.
It is an evolution of the D & C interconnection between SNCP rings.
2.6.2 Network topology
The two nodes interconnecting the SNCP rings are grouped in a meshed ET’s the remaining nodes
of the ring meshed ET’s).
An example of the resulting topologies is given in the following figure.
Only STM–1 or STM–16 rings are allowed. ( 1664SX limitation ).
ET2 2–N D&C
tpZ
tpA
tpA tpZ
tpAZ tpZA
tpA tpZ tpZA tpAZ
tpA tpZ
ET1
ET4
ENHANCED SNCP ET3
ET5
Figure 25. Topologies for Enhanced SNCP and 2 NE’s D&C
Payload configuration activity cannot be applied on the rings as a whole (it is applicable to the single
physical connection) and path / trail protection (or add protection) at ring level is not available (only the
SNCP end to end protection with or without the D&C can be applied).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 73 / 146
146
2.6.3 Protection at path / trail level
Upon path allocation, the system evaluates, as in case of basic D & C:

– main route

– spare route
– two service routes
As in the case of the normal D&C, it is not possible from the User Interface to select the tp’s involved in
the D&C but they are automatically selected by the algorithm. The tp’s can be selected from the command
mode because this is needed to support the “redo–log” 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 NE’s are included (e.g. the ET2 of the figure) or to the
whole path.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 74 / 146
146
2.6.4 Connections in a 2 N–D&C Node
The implementation of the SNCP Dual Node Interconnection with D&C includes the creation of 2
unidirectional SNCP connections and two unidirectional connections.
For ET 2 in Figure 25. the resulting connections are: ( see Figure 26. ):
– 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. Figure 26. shows the involved connections only for one route (conventionally the main one ).
The connections for the spare route are mirrored respect to the ones shown in Figure 26.
Figure 26. 2–Node D & C connections.
The default switch type is NOT revertive.
The representation of the path/trail routing view includes also an additional level view to display the actual
position of the switches.
The new navigation is available only for this type of connections and is performed by clicking on a icon
displayed in place of the SNCP status.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 75 / 146
146
2.6.5 Enhanced SNCP protection in 1664SX
This connection is usefull to increase the protection level when a single NE is interconnecting multiple
rings.

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 27. herebelow.
A Z
1664SX cross connect equipment
Figure 27. Double failure for a SNCP path (w/o enhanced)
ET2 2–N D&C
tpZ
tpA
tpA tpZ
tpAZ tpZA
tpA tpZ tpZA tpAZ
tpA tpZ
ET1
ET4
ENHANCED SNCP ET3
ET5
Figure 28. Topology view.
By using an enhanced SNCP in the NE common to rings ET1 and ET 3, the protection level of the path
1AA 00014 0004 (9007) A4 – ALICE 04.10
increases.
The default switch type is not revertive .
957.130.872 H 3AL 61259 AA AA 76 / 146
146
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:
• 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
2.6.6 Connection scheme
The implementation of the enhanced SNCP causes the creation of 4 unidirectional SNCP in the NE. See
Figure 29.
Figure 29. Enhanced SNCP connection scheme.
The handling of the macro–connection has impacts on the path/tail implementation process, on the T–FEP
(this includes the algorithm to compare the connection at RM level and at NE level during the
consistencies), on the routing display etc.
The representation of the path/trail routing view includes also an additional level view to display the actual
position of the switches.
The new navigation is available only for this type of connections and is performed by clicking on a icon
displayed in place of the SNCP status.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 77 / 146
146
2.7 Fault Management
2.7.1 Alarms on Physical Connections, Trails, HO Link Connections, Paths, Nodes.

Alarms are generated not only on paths but also on Physical Connections, Trails (both HO and MS).
The details on probable cause, modified behavior, inventories etc. is given in the following.
2.7.1.1 Physical connection
2.7.1.1.1 Generated Alarms
The alarms with the listed probable causes are generated:
Table 7. Physical Connection – Probable Cause
RM Probable RM Object Operational Elementary Elementary

Cause Severity State Object Alarms
MediaEqFail Major Disabled SDH LOS / LOF
Port URU / TrD / TrF
rxF / txF
UnderProtDeg Warning Unchanged SDH lowReliability
Port
N.B. If the RM Probable Cause is MediaEqFail, for a non–protected MS–Trail the supported
HO–LCs are put disabled.
2.7.1.1.2 Processing
Disabled objects
When the alarms ”Media or Equipment failure” is generated, the Physical Connection, the supported
MS–Trail are put disabled.
For non protected MS–Trail, the supported HO–Lc’s are disabled
Unlike paths, the alarms on Physical Connections are managed independently from the configuration
state (defined, implemented, de–implemented).
When the Physical Connection is created (activation phase), the alarm propagation function is started in
order to propagate the already existing alarms on ports.
When the Physical Connection is removed, the alarm propagation function is started in order to invalidate
the existing alarms.
2.7.1.1.3 User Interface
From an alarmed physical connection it is possible to visualize the correlated elementary alarms.
On OVW the color of the Physical Connection is related to the alarm status of the object (and not to the
worst severity of the connected ports.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The list of all the physical connections can be displayed by means of the browser. This list is refreshed
upon object creations.
957.130.872 H 3AL 61259 AA AA 78 / 146
146
2.7.1.2 MS–trail
2.7.1.2.1 Probable Causes

The alarms with the listed probable causes are generated :

Table 8. MS–trail – Probable Causes
N.B. If the RM Probable Causes are MediaEqFail, ExBer, RS Failure for a non–protected
MS–Trail, the supported HO–LCs are put disabled.
Disabled objects
The MS–Trail is set disabled when Media Equipment failure, RS failure and EX–BER alarms are received.
Object creation / deletion
Unlike paths, the alarms on MS–Trails are managed independently from the state of the related topological
objects / physical connection (i.e. implemented or de–implemented).
When the MS–Trail is created (implementation phase), the alarm propagation function is started in order
to propagate the already existing alarms on MS–Tp’s and on physical connections (disable the MS–Trail).
When the MS–Trail is removed, the alarm propagation function is started in order to invalidate the existing
alarms.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 79 / 146
146
From an alarmed MS–Trail it is possible :

– to visualize the correlated elementary alarms at the same layer.

– to visualize alarmed objects existing on the route of the MS–Trail.
In the browser, the list of all the MS–Trails in the network is available. This list is not refreshed upon object
creation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 80 / 146
146
2.7.1.3 HO–trail


Table 9. HO–Trail – Probable causes
UNEQ_In
FERF_In RDI
Disabled objects
When the alarm SDH failure is generated, the operational state is set disabled on the HO–Trail and is also
propagated to LO–LC’s.
Object creation / deletion
The alarms on HO–Trails are managed only when the object is implemented
When the HO–Trail is implemented the alarm propagation function is started in order to propagate the
already existing alarms on end HO–TTPs.
When the HO–Trail is de–implemented, the alarm propagation function is started in order to invalidate the
existing alarms.
1AA 00014 0004 (9007) A4 – ALICE 04.10
When the HO–Trail changes the payload configuration, the propagation to LO–Lc’s is performed in order
to update the operational State.
957.130.872 H 3AL 61259 AA AA 81 / 146
146
From an alarmed HO–Trail is possible :


– to visualize the alarmed objects existing on the route of the HO–Trail (on server layers).
In the browser, the list of all the HO–Trails in the network is available. This list is not refreshed upon object
creations .(as a particular condition, HO–Trails between non adjacent Nodes are automatically inserted
in the list).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 82 / 146
146
2.7.1.4 HO Link Connections


Table 10. HO–Link Connection – Probable causes
Note: for a non–protected MS–Trail the supported HO–LCs are put disabled.
2.7.1.5 LO Link Connections
Table 11. LO–Link Connection – Probable causes

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 83 / 146
146
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
2.7.1.6 Path
957.130.872 H
Table 12. Path – Probable causes
SC.2: DESCRIPTIONS
146
3AL 61259 AA AA
84 / 146
UNEQ_IN
FERF_In RDI
2.7.1.6.2 Modified behaviors
Alarm in route
The ”Alarm in Route” alarm was generated in the previous RM versions when at least one alarm was
received on a used resource at path or server layer.
This alarm was very heavy to be produced because of the amount of DB accesses and because of the
number of events produced.
For fault location, this alarm is totally replaced by the new alarms on Physical Connections and Trails.
For the previous reasons, this alarm is no more generated.
It has to be noted that, with the ”alarm in route” alarm, it was possible to know when a protected path has
lost (partially or completely) its protection. The operator can now retrieve the same information by mean
of the navigation from the alarmed physical connection or trail.
Disabled objects
When SDH failure or Ex–Ber alarm is generated, the path operational state is set to disabled.
Object creation / deletion, change of configuration state
On paths, the alarm propagation function can be configured to start according to the path configuration
state. By default, the path correlation function is started when the path is implemented.
From an alarmed path is possible:
– to visualize the elementary alarms existing on the route of the path.
In the browser, the list of all the paths in the network is available.
2.7.1.6.5 Unidirectional paths
In the Sink ports only URU and Low Reliability alarms are taken into account. The remaining alarms are
1AA 00014 0004 (9007) A4 – ALICE 04.10
not propagated since they are not significant for the unidirectional path.
957.130.872 H 3AL 61259 AA AA 85 / 146
146
2.7.1.7 MS– Spring


Table 13. NPE Ring. Generated Alarms
2.7.1.8 Node
Table 14. Node. Generated Alarms

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 86 / 146
146
2.7.2 Alarm processing according to priorities
Elementary alarms are processed according to a priority in order to give more emphasis on root problems
and less priority to effects (inclusing problems on LO paths).
2.7.2.1 Alarms priority
The Elementary Alarms are processed according to the following different priorities:
– High Priority : HO–TTP, HO–CTP, MS–TP, PDH Ports and SDH Ports.
– Low Priority : LO–TTP and LO–CTP
– two threshold alarm rates are defined in order to have different values for priority 1 alarms and priority
2 alarms.
If the rate of incoming alarms from a given EML exceeds these values (number of alarms in a time period),
the alarm processing function stops accepting new alarms from the EML, declares the EML ”out of
synchronization” (as in the case of counter mismatch), sets a specific EML attribute and rises an alarm
on the EML (probable cause ”Alarm Flooding”).
When the rate of received alarms becomes again lower than the predefined value, the EML is still “alarm
misaligned” and the user has to perform a manual synchronization.
2.7.2.2 Q3 Alarm Enabling/Disabling
Q3 alarms can be enabled/disabled for a certain path.
– On path creation. The user can modify the following attributes:
• Q3 PDH Alarm Enabling Rule ( On Implementation/On Commissioning/Manual ). For TSD–IM

equipments.
• Q3 SDH Alarm Enabling Rule ( On Implementation/On Commissioning/Manual ) . For TSD–IM

equipments.
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.
– After path creation, from the Path List the user can modify the PDH/SDH alarm enabling rule by
selecting the menu Actions: SDH/PDH Alarms: Set enabling rule, as in the case of path creation.
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 Q3 Alarm Enabling rule= on Implementation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 87 / 146
146
2.7.3 QB3* Enabling UPA on specific CTP/CAP
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 prevent 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.
2.7.4 Enable / Disable frame supervision alarm
This feature allows enabling and disabling frame supervision on bulk or structured PDH flows.
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.
By default the frame supervision alarm and the consequent action (AIS) are disabled.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 88 / 146
146
2.7.5 System Management Features
The following are provided:

2.7.5.1 Management of system processes

A tool is provided in order to manage the RM processes (included the ones related to the relational DB)
and all the OS processes on RM (Alarm Surveillance and proxy agents of managed EMLs). All these
processes are automatically started; in case of down f crashed they can also be manually started by the
user.
2.7.5.2 Management of trace files
The trace files are deleted when they overflow a given size.
– Management of RM and EML systems.

The system is able to manage (start/stop) both the RM and the managed EML systems.
– System back–up/restore.
It is possible to perform the back–up and subsequently the restore of the whole system (RM plus
EMLs)
– Monitoring the status of RM and EML systems.

A check is performed on the processes status of the RM and EMLs. The user is informed on the status
by properly colouring the system icon representation.
– Add/Remove Users.
A user administrator is allowed to add/remove users.
2.7.5.3 Recovery from system crashes and migration between NML systems services
– Batch Utility Management.
The aim of this utility is to allow the operator to execute operations in ”batch” mode. The batch utility
permits to read commands to execute from a command file. Commands are written in a command
mode language able to cover all the operations on both paths (create, allocate, de–allocate,
implement, de–implement, define constraints, change values, change protection...) and trails (same
operations as for path plus define and modify payload configuration) and based on the user labels
of the involved objects (paths, trails, ctps, naps).
The service, together with Redo Log File Management and Dump DB Utility Management service
is utilized to:
• recover the system after a crash. The following steps must be executed:
a) put the EML in download disable mode
b) perform the DB restore for both EML and RM at the aligned mibs
c) execute the redo log file using the batch utility

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 89 / 146
146
• allow migration from generic NML systems to RM. The following steps must be executed:
a) dump the NML system DB

b) install the RM version

c) construct the network map, activate and implement
d) execute the dump files using the batch utility
– Redo Log File Management.

RM automatically saves the operations performed on paths/trails.
– Dump DB Utility Management.

This utility extracts the content of the RM MIB in command mode format.
– Display/Save/Filter Event Log (SNML–IM).

RM is able to retrieve information from the HPevent log file and format them according to the SNML
Info Model.
Retrieved information can be filtered according to class, event type, object instance, date
(since/before). Information can be stored in a file for later analysis and can be used to start (using
the FDN) a navigation on the real object in the Mib.
2.7.5.4 SNML – EML Network Layer Data Consistency Check
– Global Audit. Through this function the user can start an audit activity towards a specific EML in order
to check the consistency between SNML and EML network layer data. Functionalities are:
• check consistency for MSTPs (EML DB should be consistent with SNML DB according to the
applied network implementation activity) (Audit of MSTPs)
• check consistency for PDH NAP PORTs (EML DB should be consistent with SNML DB
according to the applied network implementation activity) (Audit of PDH PORTs)
• check consistency for Subnetwork Connections (EML DB should be consistent with SNML DB
according to the applied path/trail implementation activity) (Audit of Subnetwork Connections)
• check consistency for HO CTPs, HO TTPs, LO CTPs (EML DB should be consistent with SNML
DB according to the applied payload configuration) (Audit of Payload Configuration)
– Global Download. The user can start a download activity towards a specific EML in order to force the
alignment of EML network layer data to the SNML ones.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 90 / 146
146
2.7.5.5 RM 2.2 to 2.4 DB conversion
This feature allows the conversion of a RM 2.2 MIB into an RM 2.4 MIB
2.7.5.6 RM 2.3 to 2.4 DB conversion

This feature allows the conversion of a RM 2.3 MIB into an RM 2.4 MIB
2.7.5.7 Year ”2000” compliance
The year is now displayed in YYYY format.
2.7.5.8 Operator Command Log
All the commands received by the IMs are logged together with the operation time, the user name and the
workstation. The result of the operation is not logged.
2.7.5.9 System Access Security Log
All the successful and failed login operations can be retrieved from the relevant Unix files on all the
work–stations belonging to RM.
2.7.5.10 HP–UX 10.20, HP–OV 5.03
RM 2.4 has been designed to be installed on HP systems using the operating system version 10.20 and
OV 5.03. This enables the usage of more powerful hardware and the availability of the symmetric
multi–processor option.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 91 / 146
146
2.7.6 RM to RM navigation, Multi server support
ÉÉÉÉÉÉ
ÉÉÉÉÉÉ
RM
ÉÉÉÉÉÉ

Client
ÉÉÉÉÉÉ

RM RM RM
Server <n> Server <m> Server <x>
Network Domain <n> Network Domain <m> Network Domain <x>
Figure 30. RM client to multiple RM servers
One RM client workstation can now be connected to more than one RM server.
The configuration is MULTI–Master: each work–station does not share the Communication Infrastructure
MIB but is only remotely registered for Manager–Agent messages and events.
From the application point of view :
– in OVW RM applications, starting from an empty map (before synchronizing), it is possible to select
the RM network domain and proceed as usual with the selection of the network.
– in OVW RM applications, working with a pre–populated map, the RM Network Domain is already
defined according to the associated / displayed network
– in OVW RM applications, loading a new map saved with DSM, the Network Domain is automatically
defined as in the previous point
– in the Browser, working from OVW, the Network Domain is retrieved from the objects displayed on
the map.
– in a stand–alone Browser it is possible to visualize all the Network Domains and work in parallel (e.g.
listing the paths on the different RM servers).
Among the RM servers, one is considered as Master. The other ones are not allowed to access the AS
and to navigate towards SH.
In a Multi–master network configuration it is possible to display the alarm list of a certain Network Domain
by activating the Alarm Surveillance icon from the vertical palette and subsequently selecting the involved
Network Domain from the AS dialogue box.
2.7.7 OS–OS Interface
The OS–OS interface, resident on RM–IM, allows to transfer information relevant to alarms to a generic
workstation which has the task of collecting and displaying alarms.
1AA 00014 0004 (9007) A4 – ALICE 04.10
For more detailed information refer to OS–OS Installation Guide.
957.130.872 H 3AL 61259 AA AA 92 / 146
146
2.8 Quality Domain and Performance Activity
2.8.1 General
One of the main functional areas of a TMN is the one providing the Performance Monitoring service on
the managed network; this functional domain will be referred as the Quality Domain (or Performance
Domain).
In order to provide a good network performance monitoring service, RM uses the measurement concept:
i.e. objects, whose performance level has to be controlled, are put under measurement.
The Performance Monitoring activity works on the basis of performance data coming from the
equipments via EML; data concern some standardized performance events, as the errored seconds (ES
and the far end one, FEES), the background block errors (BBE and the far end one, FEBBE), the severely
errored seconds (SES and the far end one, FESES), the unavailability seconds (unidirectional: UASuni
and bidirectional: UASbidi), the pointer justification counters (PJC) and the pointer justification counters
high (PJChigh) and low (PJClow).
The main performance activity consists of:
• configuring the monitoring activity

• activating the performance activity
• storing in the RM DB all the performance data collected from the equipments
• providing the report generation service in order to propagate the result of the monitoring action
• enabling the generation of alarms according to too high number of error events on the
monitored points
The monitored objects are the transports (paths and HO trails), which are monitored in one or more
termination points, belonging to the specified network elements; these are the main network objects
involved in the performance activity. Some new specific objects have been introduced just for the Quality
Domain.
Figure 31. shows the main items in the Quality Domain Object Containment Tree.
1354RM
Network Management
System
Q
Quality Domain Domain
Q Q
Q 15m Q 24h
Measure Counter Archiviation
Q Report Profile Session
Q VCn Q 15m Q
Q
24h Pm Network
Pm Transport
Element
Threshold
Report Profile
Q Threshold
Q Q Q
15m
Crossing
Q Alarm
Pm Tp 24h Profile
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 31. The PM fragment containment tree
957.130.872 H 3AL 61259 AA AA 93 / 146
146
2.8.2 Quality Domain objects at the graphical interface
The specific objects for Performance management are:

– Quality Domain (pm Domain)

– Measures
– PmTransports
– PmTps
– PmNes
– Threshold Crossing Alarm (TCA) Profiles
– Threshold Report Profiles
– Counter Report Profiles
– Archive Session
Navigation between all these objects is provided by using the browser.
2.8.2.1 Pm Domain
2.8.2.1.1 Definition
The Pm Domain is the root of the performance monitoring containment subtree. It is automatically created
by RM.
2.8.2.1.2 Functionalities
From the quality domain it is possible to run the RMP (Regional Manager Performance) application,
in order to display all the possible collected data for all the measures under the quality domain.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 94 / 146
146
2.8.3 Measure
2.8.3.1 Definition
A measure is the elementary working session for PM inside the 1354RM. It groups together a set of
transport entities (paths and trails) having a common performance goal.

A measure object allows to collect the counters belonging to specific TPs, in order to control the behavior
of the related transport entities and / or to enable, on the equipments, the threshold crossing alarm
functionality.
Since the managed equipments do not provide, both an homogenous behavior and the same standard
functionalities, RM provides a generic Performance service, called QoT (Global Quality of Transport).
2.8.3.1.1 QoT (Global Quality of Transports)
The monitored points can be termination points at the end of the transport entities (NAPs and CAPs). In
order to provide the end to end monitoring; the operator can also enable the measuring on a set of
termination points belonging to the route of Transport entities (CTPs).
For each monitored point, it is possible:
• to require all the enabled counter values only

• to set a Threshold Crossing Alarm profile only
• the two previous possibilities, together
The basic functionalities for the Measure objects are:
• Creation
• Attribute Setting
• Correlation to Transport Entities (paths or HO–Trails)
• Uncorrelation from correlated Transport Entities
• Correlation to Termination points (NAPs, CAPs and CTPs)
• Uncorrelation from correlated Termination points
• Correlation to Report Profiles
• Uncorrelation from Report Profiles
• Activation (Start and Restart)
• Consistency
• Stop
• Merging of several Measures
• Deletion
• Display collected data
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 95 / 146
146
2.8.3.1.3 Creation
By means of the creation operation, a new instance of the Measure class is inserted in the PM Domain.
For the creation of a Measure, the user has to specify the following attributes:

• user label (user Label): it is a friendly name associated to the measure
• granularity (pmGranularity): it is the granularity of the service provided by the measure, i.e. the
period the collected data will be retrieved from the monitored network elements; allowed values
are: 15 minutes and 24 hours
• monitored layer (pmLayer): it indicates which network layer must belong to the monitored
objects (transports and termination points); it can be lower order, higher order or both.
• start time (pmStartTime): it is the desired date on which the measure should be activated; not
specified means that the measure will start upon manual intervention.
• end time (pmEndTime): it is the desired date for the measure to be stopped; not specified
means that the measure will stop upon manual intervention.
• collect counters: if true, the collection of the performance counters is required for all the
monitored termination points; if false, measure won’t collect counters: it will be useful only for
threshold crossing alarm generation.
• default tps (defaultEnd): if it is set to true, some termination points of the monitored transports
will be automatically chosen as monitored points (they will be naps or caps); for paths some
NAPs, for HO trails some CAPs and, in any case, all the possible boundary CTPs
At the end of a successful creation, the measure is present in the RM Domain having the Measure State
(pmMeasureState) equal to planned. Anyway no transport neither termination point is related to the
created measure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 96 / 146
146
2.8.3.1.4 Attribute
Some measure attributes can be set (updated) by the user, under certain conditions.
When the measure is planned, the modifiable attributes are:

• user label (userLabel): can always be set
• collect counters: (pmCollectCounter): can always be set
• granularity (pmGranularity): can be set only if no transport has already been correlated to the
measure
• monitored layer: (pmLayer), can be set only if no transport has already been correlated to the
measure
• default tps (defaultEnd): can be set only if no transport has already been correlated to the
measure
• desired start and end times (pmStartTime & pmEndTime): can be set only if the new values
do not cause a conflict with another measure, with the same granularity, trying to monitor the
same tp at the same time.
When the measure is activated, the modifiable attribute is only the desired end time (pmEndTime), if the
new value doesn’t cause a conflict with another measure, with the same granularity, trying to monitor the
same tp at the same time.
Finally, if the measure is stopped, no attribute value can be set.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 97 / 146
146
2.8.3.1.5 Correlation between Measures and Transports (Paths and Trail)
It is possible to correlate several transports (i.e. paths and/or trails) to a measure; being a transport
correlated to a measure means that, when the measure will be activated, that transport will be monitored

in some tp by the measure.

Transport can be correlated only to planned measures having the right value of the monitored layer
attribute (pmLayer: lower order, higher order or both). If the measure has the default tps attribute value
set to true, some termination points will be automatically chosen as monitored points (they will be naps
or caps):
– for paths:
• for unidirectional paths, the sink NAP, if non virtual, will be monitored
• for bidirectional paths, only one NAP, if non virtual, will be monitored
• for broadcast paths, all the non virtual sink NAPs will be monitored
– for HO trails:
• a CAP will be monitored
– for paths and HO trails:
• all the possible boundary CTPs will be monitored
By means of the correlation between termination points and measure action, it will be then possible to add
more monitored termination points for the transport.
When a transport has been correlated to a measure, a new object, child of the measure, is created: the
pmTransport, image of the transport in the Quality Domain.
For the possible automatically chosen monitored points of the transport, some new objects, child of the
pmTransport, are generated: the pmTps, image of the termination points in the Quality Domain.
The first time a termination point belonging to a network element has an image in the Quality Domain, the
network element too has an image in the Quality Domain: the pmNe.
2.8.3.1.6 Uncorrelation between Measures and Transports (Paths and Trails)
It is also possible to uncorrelate transports from a measure they were correlated to; when a transport is
uncorrelated from a measure, the pmTransport is removed and the contained pmTps are removed too.
It is possible to uncorrelate transports only from a planned measure.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 98 / 146
146
2.8.3.1.7 Correlation between Measures and Terminal Points (Naps/Caps and Ctps)
It is possible to correlate a termination point to a measure, so that the termination point will be monitored
by that measure. When a termination point is correlated to a measure, an instance of the pmTp class is
created, to show that the termination point has an image in the Quality Domain.
A termination point can be correlated to a measure if:
• the termination point belongs to a transport already monitored by the measure
• the termination point is not virtual
• the termination point is not already monitored by an other measure, having the same granularity
and going to be activated for at least one instant together with the measure the tp is going to
be correlated; in this case the correlation will fail because of ’time overlap’
The correlation is possible in three different cases:
• planned measure: the created pmTp and the measure are consistent
• activated measure: the newly created pmTp and the measure are not consistent and the
measure will require a manual consistency action
• stopped measure: the just created pmTp and the measure are not consistent and the
measure will require a manual consistency action
2.8.3.1.8 Uncorrelation between Measures and Termination points
It is also possible to uncorrelate termination points from a measure they were correlated to; when a
termination point is uncorrelated from a measure, the pmTp is removed.
To uncorrelate termination points from a measure, the measure must be planned.
2.8.3.1.9 Correlation to reports
By means of this action, it is possible to correlate one or more report to a measure. Required conditions
are:
• the measure is not stopped
• the report window is compliant with the measure granularity (the smallest window values
match with a 15 minute granularity, the greatest ones with a 24 hour granularity)
• threshold reports have the same granularity of the measure
When a report is correlated to an activated measure, reports will be generated with a frequency
corresponding to the report window.
2.8.3.1.10 Uncorrelation from reports
By means of this action, it is possible to uncorrelate one or more reports from a measure they were
correlated to. This operation can be executed for both planned and activated measures. When a report
is no more correlated to an activated measure, reports will not be generated.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 99 / 146
146
2.8.3.1.11 Activation (start and restar)
By means of the activation action, it is possible to manually start a measure.

Required conditions are:

• the measure status must be planned (start) or stopped (restart)
• no start time specified or start time set to a date already passed
• the measure is populated, i.e. contains at least one tp correlated for an implemented
transport
• not time overlapped on the monitored tps, i.e. no conflicts with other measures trying to
monitor the same tp at the same time, while having the same granularity
If the activation succeeds, the state of the measure and the state of the pmTps become activated.
PmTps and measure can be not consistent or consistent according to EML response.
When the measure is activated, the performance activity must be on (it depends on the consistency
attribute), so that:
• threshold crossing alarms (if pmTps are correlated to threshold crossing alarm profiles) will
be generated
• counter values (if the measure has the collect counter attribute set to true) will be collected
from the EML
• reports (counters and thresholds, if correlated to the measure) will be sent to their destination
at each window period
The activation of a measure can be also automatically run by the performance monitoring agent when
the desired start time of a measure is specified, upon reaching that instant (scheduled activation
activity).
A transport monitored by an activated measure will have the pm15 or pm24 attribute set to true (according
to the measure granularity).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 100 / 146
146
2.8.3.1.12 Consistency
By means of the measure consistency, it is possible to check, if the situation presented by RM for the
monitored object is the same at EML side. This means to ask the equipments for:
• performance activity start/stop time
• threshold crossing alarm profiles
Generally this action will be run on measures which have some pmTp not consistent and, so, are not
consistent, but it could be run also on consistent measures. After running the consistency action, the
measure and the pmTps could become:
• consistent
• not consistent: equipments cannot follow RM directives
Having to interact with EML, the consistency action works on the network elements which have at least
a termination point monitored by the measure; for each network element the following steps are
performed:
• retrieve of EML information
• compare of the retrieved information with the RM DB information
• sending of the opportune action to the EML (only in case of misalignment)
2.8.3.1.13 Stop
By means of the stop action it is possible to manually stop an activated measure.
If the stop action succeeds, the measure pmMeasure State and the pmTpState of the pmTps become
stopped.
PmTps and measure will be not consistent or consistent according to EML response.
When the measure is stopped, the performance activity is off (it depends on the consistency attribute), so
that:
• threshold crossing alarms (if pmTps had been correlated to threshold crossing alarm profiles)
are no longer generated
• counter values (if the measure has the collect counter attribute set to true) are no longer
collected from the EML
• reports (counters and thresholds, if correlated to the measure) are no longer sent to their
destination at each window period
The stopping of a measure can be also automatically run by the performance monitoring agent when the
desired end time is reached (scheduled stop activity).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 101 / 146
146
2.8.3.1.14 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 instance.

This action does not loose possible previously collected data, neither looses possible correlated
counter or threshold reports, or threshold crossing alarm profiles.
Only homogeneous measures can be merged; measures are homogeneous when they have the same
state (pmMeasureState) and the same granularity (pmGranularity) values.
Measures generated automatically on path implementation/commissioning cannot be merged.
The merged measure has the following attributes:
• user label (userLabel): the one of the target measure
• identifier (pmMeasureId): the one of the target measure
• granularity (pmGranularity): the one of the target measure
• state (pmMeasureState): the one of the target measure
• consistency (pmConsistency): it will be equal to consistent if and only if all the involved
measures are consistent
• default ends (defaultEnd): it will be equal to true if no involved measure has a false value
• collect counters (pmCollectCounter): it will be equal to true if at least one involved measure
has a true value
• monitored layers (pmLayer): it will be given by the union of the layers monitored by the involved
measures
• start time (pmStartTime): it will be equal to the lowest value between the specified ones of the
merging measures; it will be unspecified only if no input measure has a specified start time
• end time (pmEndTime): it will be set as the greatest value found in the involved measures
The merging of the measures fails:
• if one or more merging measures are synchronizing
• if the new start and end times are too large for some monitored termination points, i.e. any
termination point has already been inserted in another measure which will be activated during
the new activity interval
• if two merging measures (in case of measures which have been already activated) have
monitored the same termination point, but while belonging to two different transports (i.e. there
has been a transport routing redefinition)
• if the merging measures have monitored at different times the same tp, but with different counter
profiles (i.e. bidNePlusFeADM and uniNeADM)
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 102 / 146
146
2.8.3.1.15 Deletion
This function deletes a measure instance in the RM database. This implies to:
• delete all the possible historical data collected for the objects monitored in the measure
• delete all the objects contained in the sub–tree of the measure (i.e. pmTransports and pmTps)
The operation can be executed only on non active and consistent measures
2.8.3.1.16 Display collect data
From a measure it is possible to run the RMP application, in order to display possible collected data for
all the pmTps belonging to the measure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 103 / 146
146
2.8.3.1.17 Measure state transitions

Creation
PLANNED
Activation (Start)
Consistency
Activation (Restart)
STOPPED ACTIVATED
Stop
Deletion
Consistency
The above figure shows the measure state transitions graph.. The ellipses represent the measure states:
• planned: a measure is planned when it is created by the user; at that time it can be populated,
by correlating to it transports and termination points, and no performance monitoring activity is
working
• activated: the measure has been activated: the required performance monitoring activities
(counter value collection, Threshold crossing alarm generation, report sending) should be
working
• stopped: in a stopped measure performance monitoring services are no longer provided.
As already explained, for the last two states the measure can be both:
• consistent: EML is aligned with RM
• not consistent: there is some misalignment between EML and RM

1AA 00014 0004 (9007) A4 – ALICE 04.10
The measure consistency action does not change the pmTp state.
957.130.872 H 3AL 61259 AA AA 104 / 146
146
In the represented states, the measure working state is normal. On the arcs, the measure has a working
state equal to synchronizing.
State transitions occur on activation (start and restart) and stop, while the consistency action does not
change the measure state.

The measure can be deleted only when planned or stopped (but consistent).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 105 / 146
146
2.8.3.2 Pm Transport

The pmTransport is the image, in the Quality Domain, of a monitored transport; for a certain transport, it

is possible to have more pmTransports: in fact, there will be a pmTransport for each measure monitoring
the transport. PmTransports are automatically generated by the performance activity agent, when the
termination point is correlated to the measure.
The basic functionalities for the pmTransports are:
• Deletion
2.8.3.2.3 Attribute Setting
A pmTransport user label (userLabel) can always be set by the user, in order to follow the settings of the
monitored transport user label. No other attribute can be set by the user.
2.8.3.2.4 Deletion
To delete a pm transport, it must belong to:
• a planned measure
• a stopped but consistent measure
When a pmTransport is deleted, all its pmTps are deleted too, together with their possible stored
performance data.
Deleting a pm transport in a planned measure is the same of uncorrelating the relevant transport from the
measure.
2.8.3.2.5 Display collect data
From a pm transport it is possible to run the RMP application, in order to display possible collected data
for all the pmTps belonging to the pm transport.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 106 / 146
146
2.8.3.3 Pm Termination Point
The pmTermination Point is the image, in the Quality Domain, of a monitored termination point. For a
certain termination point, it is possible to have more pmTps: in fact, there will be a pmTp for each measure
monitoring the termination point. PmTps are automatically generated by the performance activity agent,
when the termination point is correlated to the measure.
The basic functionalities for the PM TP are listed in the following:
• Correlation to a threshold crossing alarm profile

• Uncorrelation from a threshold crossing alarm profile
• Deletion
2.8.3.3.3 Correlation to a threshold crossing alarm profile
See threshold crossing alarm profile, correlation to a monitored termination point
2.8.3.3.4 Uncorrelation from a threshold crossing alarm profile
See threshold crossing alarm profile, uncorrelation from a monitored termination point
2.8.3.3.5 Deletion
To delete a pm tp, it must belong to:
• a planned measure
• a stopped but consistent measure
• in any case, if the pmTp has never collected data
When a pmTp is deleted, the stored performance data are deleted.
2.8.3.3.6 Display collected data
From a pm tp it is possible to run the RMP application in order to display all its possible collected data.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 107 / 146
146
2.8.3.3.7 PmTp state transitions
pmTp states are:

• planned: a pmTp is planned when it belongs to a planned measure; no performance monitoring

activity is working
• unavailable: it is the case of a termination point which cannot be managed in performance

monitoring operations (because of equipment constraints), inside an activated measure
• activated: a pmTp can be activated if it is inside an activated measure; performance monitoring

activities (counter value collection, Threshold crossing alarm generation, report sending) must
be working
• stand by: in an activated measure a pmTp can be stand by if it belongs to a termination point
that, for whatever reason, is no more in the monitored transport or if its transport is no longer
implemented: no performance monitoring activity in progress on that termination point.
• stopped: in a stopped measure all the pmTps are stopped, i.e. they should no longer provide
performance monitoring services
As already explained, for the last three states the pmTp can be both:
• consistent: EML is aligned with RM
• not consistent: there’s some misalignment between EML and RM
while the first two states are always consistent.
The measure consistency action does not change the pmTp state.
In the cited states the pmTp working state is normal. On the transitions, the pmTp working state is
synchronizing.
State transitions occur at measure activation (start and restart), at measure stop, or at transport
configuration state changes.
PmTps are planned or activated at their creation, i.e. at the correlation of the termination point to the
measure (or at the correlation of the transport to the measure, if the pmTp is created as a default monitoring
point for the transport),
PmTps can be explicitly deleted only when planned, unavailable, stand by or stopped, if consistent, by
means of a pmTp deletion or of a termination point uncorrelation from the measure, or implicitly deleted,
as a consequence of a transport uncorrelation (or pmTransport deletion) or of a measure deletion.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 108 / 146
146
2.8.3.4 Pm Network Element
When one or more termination points belonging to a network element are correlated to some measures,
an image in the Quality Domain of that network element is generated: it is the pm network element. The
pm network element is automatically created by the performance monitoring agent.
The basic functionality for the pmNes is the Consistency.
2.8.3.4.2 Consistency
This functionality has the objective of aligning EML–MIB to RM–MIB, as far it is concerned about
performance data
The macro steps of this functionality are :
• for all pmTps contained in the pmNe, RM retrieves from EML their performance state
• RM compares its information with EML information, in order to fix the misalignment (at level
of PmTp)
• RM tries to align the EML–MIB to RM–MIB, sending to EML start and stop commands, as
stated in RM–MIB.
• when all EML answers are received, pmTps and pmNe can be consistent or not consistent
The consistency operation on the pmNes is strongly recommended after an SH restart, due to
the fact that SH (EML) does not provide PM data persistency at restart.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 109 / 146
146
2.8.3.5 Threshold Crossing Alarm Profile

Threshold Crossing Alarm Profile allows to state when equipments have to send threshold crossing

alarm. TCA profile attributes are granularity and thresholds values for the following counters: Background
Block Errors, Errored Seconds, Severely Error Seconds and their Far End counters.
Threshold specification differs according to the profile granularity:
– 15 minutes: for each counter two threshold values are required:
• upper value, threshold for alarm generation
• lower value, threshold for alarm clearing
– 24 hours: for each counter only one threshold value is required:
• upper value, threshold for alarm generation
For the 24 hours profile the alarm clearing is automatically performed at the end of the alarmed day.
In order to apply a threshold crossing alarm profile to a certain termination point, the termination point
must be monitored by a measure; in this case it is possible to correlate the profile to the pmTp: at this
time the threshold crossing alarm profile is set on the termination point.
If the measure is planned, the alarm generation process does not work till the measure will enter the
activated state. If the measure is activated, the alarm generation process will work as soon as the
measure monitoring the termination point succeeds in the consistency action.
The threshold crossing alarm profile concerns more thanone termination point: in fact, when the profile
is correlated to a given pmTp, it is applied to the network element the termination point belongs to.
Because of restrictions due to ADM equipments, termination points can be correlated to only one
Threshold Crossing Alarm Profile for each tp rate / granularity pair of values
TCA Profile functionalities are:
• Creation
• Deletion
• Correlation to a monitored termination point
• Uncorrelation from a termination point

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 110 / 146
146
2.8.3.5.3 Creation
RM provides a set of default TCA profiles; anyway, the user may want to define a new, different profile.
During the Creation of a Profile, the following attributes can be specified:
• user label (userLabel): it is a friendly name associated to the Profile
• granularity (pmGranularity): it is the granularity of the TCA Profile instance; possible values
are 15 minutes and 24 hours
• threshold values (bBeLow. bBeHigh, eSLow, eSHigh, ...): the values for the alarm generation
and clearing, for each counter type
2.8.3.5.4 Deletion
This function deletes a TCA Profile from RM database.

In order to be deleted, a profile must not be correlated to any pmTp.
2.8.3.5.5 Correlation to a monitored termination point
By means of this action, it is possible to apply a Threshold Crossing Alarm Profile to a pmTp (and, so,
to the pmNe the pmTp belongs to). In order to do this, it is necessary for the pmTp and the profile to have
the same granularity value.
2.8.3.5.6 Uncorrelation from a termination point
By means of this action, it is possible to clear a Threshold Crossing Alarm Profile on a pmTp.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 111 / 146
146
2.8.3.6 Threshold Report Profile

Threshold report Profiles are used for periodic generation (and sending) of threshold reports; in order

to do this, a threshold report profile must be correlated to a measure; when the measure will be in
activated state, threshold reports will be sent.
Threshold reports hold the information about those counters (Background Block Errors, Errored
Seconds, Severely Error Seconds, UnAvailability Seconds and their Far End versions) which
exceeded some specified threshold values; they will be generated with a period corresponding to the
threshold report profile window attribute, so that, being generally the window longer than the granularity
period, the report will contain information about several granularity periods.
The basic functionalities provided are:
• Creation
• Deletion
• Correlation to a measure (see the measure action: correlation to reports)
• Uncorrelation from a measure (see the measure action: uncorrelation from reports)
2.8.3.6.3 Creation
The user can create threshold report profiles.

The following parameters have to be specified:
• user label (userLabel): it is a friendly name associated to the profile
• destination type (pmReportDestType): it is the medium for the report generation: printer,
terminal (E–mail), file
• estination name (pmRepDestName): it is the actual identifier of the report destination
• granularity (pmGranularity): the granularity by which are grouped the collected data from the
equipments; data exceeding threshold values are shown per granularity period.
• window (pmReportWindow): it is the period of threshold report generation; it must be not

smaller neither too greater than the granularity period
• threshold values (pmThreBBE, pmThreEs, pmThreFEBBE, ...): threshold values for each
counter type
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 112 / 146
146
The following attributes can be set by the user, provided that the report is not correlated to an activated
measure:
• user label (userLabel)
• destination type (pmReportDestType)
• destination name (pmRepDestName)
• window (pmReportWindow)
• threshold values (pmThreBBE, pmThreEs, pmThreFEBBE ...)
2.8.3.6.5 Deletion
This function deletes a Threshold Report Profile

Condition: the profile is not correlated to any measure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 113 / 146
146
2.8.3.7 Counter Report Profile

Counter Report Profiles are used for the periodic generation (and sending) of counter reports; in order

to do this, a counter report profile must be correlated to a measure, so when the measure is activated,
counter reports are sent. Counter reports hold the information about all collected values for the following
counters: Background Block Errors, Errored Seconds, Severely Error Seconds, UnAvailability
Seconds and their Far End versions; they will be generated with a period corresponding to the counter
report profile window attribute. Since the window is bigger than the granularity period, the report will
contain information about several granularity periods.
The basic functionalities provided are:
• Creation
• Deletion
• Correlation to a measure (see the measure action: correlation to reports)
• Uncorrelation from a measure (see the measure action: uncorrelation from reports)
2.8.3.7.3 Creation
The user can create counter report profiles.

The following parameters have to be specified:
• user label (userLabel): it is a friendly name associated to the profile
• destination type (pmReportDestType): it is the medium for the report generation: printer,
terminal (E–mail), file
• destination name (pmRepDestName): it is the final identifier of the generated reports
• window (pmReportWindow): it is the periodicity for the threshold report generation; when
correlating the profile to a measure, the window must be not smaller neither too bigger than the
measure granularity period
All the following attributes of can be set by the user, provided that the report is not correlated to an activated
measure:
• user label (userLabel)
• destination type (pmReportDestType)
• destination name (pmRepDestName)
• window (pmReportWindow)
2.8.3.7.5 Deletion
This function deletes a Counter Report Profile

1AA 00014 0004 (9007) A4 – ALICE 04.10
Condition: the profile is not correlated to any measure.
957.130.872 H 3AL 61259 AA AA 114 / 146
146
2.8.3.8 Archive Session
The archive session is an object identifying a session of performance data archive on a tape medium.
The archive session is uniquely identified by means of:
• a 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”)
• the tip dates (from date and to date)of the data period
• the 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.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 115 / 146
146
2.8.4 Performance activites on objects out of Pm Domain
There are some objects, not belonging to the Quality Domain, which can undergo some performance
actions:

• transports (Paths and HO–Trails)
• termination points (naps, caps and ctps)
• nodes
• EML domains
2.8.4.1 Transport
Transports can enter/exit a monitoring activity by means of the correlation/uncorrelation to measures (see
correlation between measures and transports).
Paths can also enter the monitoring activity automatically, if they have the pm automatic
attribute set to true: at their implementation they will be automatically correlated to a measure
which will be automatically activated.
Furthermore, when a monitored transport changes its configuration state from/to:
• deimplementation
• reimplementation
• leg remove
• protection remove
if the monitoring measure is activated, the corresponding involved pmTps will change their state in order
to follow the new transport configuration state: their pmTpState attribute will switch between activated
and stand by and the performance activity on the equipments will start/stop.
2.8.4.2 Termination points
Termination points can enter/exit a monitoring activity by means of the correlation/uncorrelation to

measures (see correlation between measures and termination points).
2.8.4.3 Nodes
Nodes can enter a performance consistency activity as described for pm network elements (consistency).
2.8.4.4 EML domain
Consistency can be run on an EML domain; this is the same of running the consistency on the network
elements composing the EML domain
2.8.5 Redo Log Management
All the operations performed by the user service also are traced in the Redo Log file.
2.8.6 Dedicated Performance Data Backup

1AA 00014 0004 (9007) A4 – ALICE 04.10
Separate data base backup services are now available for Network Configuration Tables (included
started termination points) and for Performance Tables.
957.130.872 H 3AL 61259 AA AA 116 / 146
146
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.2: DESCRIPTIONS
2.9 FAD / NAD – Functional Access Domain
See Handbook System Management Features, in particular see Chapter 8.
146
3AL 61259 AA AA
117 / 146
2.10 Backup and Restore
The backup/restore functions, permit to save/restore the following data types:

– Network configuration data (and HPOV maps saved into DNM repository);

– Alarm data;
– PM data;
– OS data: Operating System configuration data (i.e. /etc/hosts) – Third party software (HPOV ORS
DB) – Application configuration data (i.e. us_nodes, im_host_conf);
– Operator data.
N.B. The previous data types could be saved all together or in separate way selecting the relevant
data on user interface.
The first three subsystems backup/restore procedure are based on the Oracle import/export features, so
only table data are saved and not the table structure. This imply to recreate the Oracle DB (see the
Administrator Guide Handbook).
Figure 32. illustrates the information distributed in the two disks.
EXTERNAL DISK INTERNAL DISK

APPLICATION / OP. SYS. BACKUP / MIRROR
Operating System /backup
Base Software archives files

( /mirror/arch )
Application SW ( RM ) reference base
( /mirror/db_ref_base )
Oracle DB
redologs & control redologs & control
( /mirror/mirror )
Figure 32. Distribution of files in two application disks

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 118 / 146
146
The detailed procedure is described in the SMF Handbook, in particular Chapter 8.
Prior to execute the backup / restore feature for NR2 EMLs (SH and WX) it is necessary to
execute the following manual workaround procedure:
1) For each installed EML the relevant directory should be created:

$ mkdir –p /backup/1353<sys>_<nn>
where <sys> is SH or WX according to the managed EML and <nn> is the
logical number of EML (EML Domain Id).
2) Create the link with the NR2 backup directory structure:

$ ln –s /backup/<sys> /backup/1353<sys>_<nn>/Ntwk
3) Run Restore Procedure and ignore the warning message.
During the backup the RM system is switched in read only run level, so it is guaranteed the saved data
integrity.
The network backup function is available both as a periodical action and on user request via user interface.
The files originated by a backup are stored onto a disk (other than the one in which resides the Oracle
database) and optionally on a tape (see Figure 32. ).
Different snapshot backups are stored on an unique tape.

The suggested frequency is once per day.
2.10.1 Procedures
The detailed procedure is described in the handbook System Administrator Reference Guide.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 119 / 146
146
2.11 RM objects
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 sub–networks.
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 EML–domain 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 sub–network 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
The path defines a connection between ends (NAPs) of the network.
ET
1AA 00014 0004 (9007) A4 – ALICE 04.10
The elementary topology is the ring. It contains nodes.
957.130.872 H 3AL 61259 AA AA 120 / 146
146
Sbn
The subnetwork is a partitioning of the NML network. It contains Elementary topologies and
interconnected Nodes.
A sub–network is a grouping of nodes and ETs.

A sub–network 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
sbn1 sbn2
connInTopol
Nap1 Nap2
Connection in topology at netwok level. Connection between Nap1 and Nap2

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 121 / 146
146
sbn
Nap1
Ctp1
connInTopol
Connection in topology at subnetwork level. Describes the connection Nap1 to Ctp1
ctp ctp
ntw
nap connInTopol ctp1
ctp ctp
Note: If the ring is located on the network boundary, it describes the connection between Nap1 and Ctp1
N.B. connInTopol at ring level (case 1)

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 122 / 146
146
ctp ctp
ntw
ctp ctp
ctp1 ctp2
connInTopol
ctp
ctp ctp
Note: If the ring is located in the inner of the network, it describes the connection between ctp1 and ctp2
N.B. connInTopol at ring level (case 2)
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
It represents both the Msctp and the mscap entities related to an SDH physical port at MS layer.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 123 / 146
146
NE 1641 SM

Nap PDH
2 Mb This ctp contains
connInTopol the LOPL adaptation
function
ctp ctp
LOPL
VC–4
cap
This is a 1 to 1
connInTopol
connInTopol This ctp contains the

HOPL adaptation
function
ctp
HOPL
MSL
msctpcap STM–1 port
LOPL=low order path layer ; HOPL=high order path layer; MSL=multiplex section layer
Figure 33. Simplified representation of the 1641 SM

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 124 / 146
146
NE 1651 SM
nap
connInTopol
ctp ctp
time division
multiplexing LOPL
HOPL
cap1 cap4
connInTopol connInTopol
ctp1 ctp4
MSL
msctpcap
STM–4
The connection between cap and ctp at HOPL is a connInTopol inside the NE
Figure 34. Schematic representation of the 1651 SM

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 125 / 146
146
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
nap
nap
01
957.130.872 H
connInTopol
SC.2: DESCRIPTIONS
tdm
msctpcap
connInTopol
NE
Figure 35. Schematic representation of the NE

msctpcap
146
3AL 61259 AA AA
HOPL
MSL
LOPL
126 / 146
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
ctp ctp LO
HOtrail
cap cap
HO
HO link connection
ctp ctp
ms trail
MS
msctpcap msctpcap
Figure 36. Trail and link connections
The trail corresponds to the logical generation/check of OH/SOH info, in the G803 layer structure (peer
to peer arrangement).
Link Connection
The link connection describes the connectivity between two CTPs in any partitioning level and in any layer.
The figure which follows describes the objects involved in the structure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 127 / 146
146
NE NE
nap nap

ctp3rd ord
LOlc(TU3#1)

LOPL tdm tdm LOPL
140cap1
(VC4) 140cap1
HOtrail(VC4S1) (VC4) #1
#1
ctp16
HOlc ( AU4#16) ctp1
HOlc ( AU4#1)
HOPL HOPL
MSL MSL
ms trail
mstp mstp
mstp mstp
physConn
nap nap
ctp3rd ord LOlc(TU3#1)
140cap1
(VC4) 140cap1
HOtrail(VC4S1) (VC4) #1
#1
ctp16 ctp16 ctp16

HOlc ( AU4#16) HOlc ( AU4#16)
ctp1 ctp1
ctp1
HOlc ( AU4#1) connInTopol HOlc ( AU4#1)
ms trail ms trail
mstp
mstp mstp mstp
physConn physConn
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 37. Objects involved in the structure
957.130.872 H 3AL 61259 AA AA 128 / 146
146
2.12 Trail Monitor
The Trail Monitor function allows to monitor, along a path (in an intermediate NE), the HO(LO) Path
Overhead.
This function provides path segment monitoring capabilities by use of POH.
It can be inserted to monitor the signal before the matrix or after the matrix. It is used to monitor
unidirectional or bidirectional paths. The Trail Monitor can be used in the following applications:
–SNCP/N with Path Overhead Monitoring ( POM ) at the incoming signal (before matrix)
– Protected Trail Monitoring with POM at the outgoing signal (after matrix)
– Unidirectional and Bidirectional Trail Monitoring
In the following paragraphs these applications are described by figures: the upper part of the figure shows
the functional view and the lower part represents the Managed Object view.
Figure 43. to Figure 45. show examples of trail monitor application for fault localization.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 129 / 146
146
2.12.1 SNCP/N with POM at the incoming signal (before matrix)
TT

Client
TSF MC TSF layer
TSD TSD
POM POM
MCp MCp
SSF SSF
A A Server
layer
SNCP/N Functional Model (HOP or LOP)
vc4TTPSinkR1
dcp rrp
ucp
CP CP
CPG urp
au4CTPSinkR1 au4CTPSinkR1
Signal Flow
Containment/naming relationship
trailMonitor trailMonitor
SNCP/N Information Model (HOP)
Figure 38. POM in SNCP/N (I)
The non–intrusive monitoring function is realized by a trailMonitor (high order for HPOM in the example)
associated to the CTP (au4CTPSnkR1) that performs the adaptation to the server layer. Note that in this
figure the vc4TTPSinkR1 can be replaced by an au4CTPSource.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 130 / 146
146
2.12.2 SNCP/N with POM at the outgoing signal (after matrix)
POM
Client
MC layer
MCp MCp
Server
layer
A A A
SNCP/N Functional Model (HOP or LOP)
au4CTPSource
rrp
trailMonitor
CP CPG CP
urp
Signal Flow
dcp au4CTPSinkR1 au4CTPSinkR1

ucp
SNCP/N Information Model (HOP)
Figure 39. POM in SNCP/N (II)
In this example the non–intrusive monitoring function realized by the trailMonitor, performs after matrix
(protection) monitoring (The trailMonitor instances at au4CTPsinkR1 points necessary for SNCP/N are
not drawn in this figure).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 131 / 146
146
2.12.2.1 Trail monitoring unidirectional
Signal Flow
Trail

TT POM TT
NOTE.1
MC MC MC
A A A A
Link Connection Link Connection
Trail monitoring Functional Model (HOP or LOP)

vc4TTPSource
Signal Flow vc4TTPSinkR1
Trail
Snk
au4CTPSinkR1 au4CTPSource
au4CTPSource au4CTPSinkR1
Link connection Link connection

Signal Flow
dcp
ucp
Trail monitoring Information Model (HOP)
Figure 40. POM in Trail Monitoring (before and after)
NOTE .1 The POM duplication has been abstracted to highlight the Information Model view.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 132 / 146
146
2.12.2.1.1 Trail monitoring bidirectional
Signal Flow
Trail
TT NOTE.1 POM TT
Signal Flow
MC MC MC
A A A A
Link Connection Link Connection

vc4TTPBidirectionalR1 Signal Flow vc4TTPBidirectionalR1

Trail
Signal Flow
au4CTPBidirectionalR1 au4CTPBidirectionalR1
au4CTPBidirectionalR1
au4CTPBidirectionalR1
D
A Link connection B C Link connection
trailMonitor trailMonitor trailMonitor

B1 C1 C2
Signal Flow Trail monitoring Information Model (HOP)

Bidirectional
dcp
ucp
Figure 41. POM in Trail Monitoring (bidirectional before and after)
In this example, at point C, two non–intrusive monitoring functions modelled by trailMonitor have been
instantiated for monitoring of the ingress/egress trails at that point. The afterMatrixSignal attribute permits
to differentiate them.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 133 / 146
146
2.12.2.1.2 Trail monitoring bidirectional (view in detail)

au4CTPBidirectionalR1 au4CTPBidirectionalR1
au4CTPSinkR1 au4CTPSource
Signal Flow
B1
au4CTPSource au4CTPSinkR1
trailMonitor
Signal Flow
C1 C2
Before matrix After matrix

B C
Signal Flow
Bidirectional
dcp Containment/naming relationship
ucp
Figure 42. POM in Trail Monitoring (detailed view of bidirectional before and after)
The trailMonitor at C1, monitoring the outgoing trail, has the afterMatrixSignal attribute set to egress,
whereas the ones at B1 and C2 monitoring the incoming trails have them set to ingress.
The setting of the afterMatrixSignal attribute is done at instantiation time.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 134 / 146
146
2.12.2.1.3 TrailMonitor application for fault localization(1/3)

Trail
Distur-
Distur- bance
POM
TT
NOTE.1
bance TT detected
TCP TCP detected TCP
MC MC MC MC
CP CP CP CP CP CP
A A A A A A
Link Connection Link Connection Link Connection
Trail monitoring Information Model (HOP) for Fault localization

Trail
vc4TTPSource au4CTPSinkR1 au4CTPSource au4CTPSinkR1 au4CTPSource vc4TTPSinkR1

A B C D E F Distur-
bance
detected
Distur-
bance
detected
Link connection Link connection Link connection
trailMonitor
Signal flow
ucp
The example shows a disturbance detected by the vc4TTPSinkR1 at the terminating end. As may not be
obvious where this disturbance is located, the trail is viewed as a series of link connections. Starting at
the trail sink end (point F) and going towards the source trail end(point A), a trailMonitor is selectively
instantiated, one point at a time, (E in the example). The point E also has the disturbance present.
Figure 43. trailMonitor for fault localization example( I )

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 135 / 146
146
2.12.2.1.4 trailMonitor application for fault localization(2/3)

Trail
Distur-
Distur- bance
POM
TT bance TT detected
TCP NOTE.1
TCP detected TCP
MC MC MC MC
CP CP CP CP CP CP
A A A A A A
Trail

A B C D E F
Distur-
bance
detected
trailMonitor
trailMonitor
Link connection Link connection
Distur- Distur-
bance bance
detected detected
supervisedUnequippedSi
Signal flow
ucp
The process continues upstream. The next point (D, a before matrix one) when supervised by means of
an instantiated trailMonitor, is found also with the disturbance present.
Figure 44. trailMonitor for fault localization example( II )

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 136 / 146
146
2.12.2.1.5 trailMonitor for fault localization(3/3)

Trail
Distur-
Distur- bance
POM Distur-
TT POM bance TT detected
NOTE.1 bance NOTE.1
TCP TCP free TCPdetected TCP
MC MC MC MC
CP CP CP CP CP CP
A A A A A A

Trail

A B C D E F
Distur-
bance
detected
trailMonitor
trailMonitor
trailMonitor
Link connection Distur- Link connection
bance Distur- Distur-
free bance bance
detected detected
Signal flow
ucp
The next point upstream ( C) is found disturbance free. The fault is so located between those two points
(C–D) in which the trailMonitor reports disturbance free performance for one (C) while the other(D) reports
the disturbance condition.
Figure 45. trailMonitor for fault localization example( III )

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 137 / 146
146
2.13 Path/Trail Allocation Failures
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.
Selecting the involved path/trail and clicking on the Show Failure Information Tool button, the Netscape
browser application starts and displays the Netscape Path/Trail allocation failure window.
The Netscape Path/Trail allocation failure window contains the following frames:
• Window title: Netscape Path/Trail allocation failure.
• Failed object frame. It contains:
– path/trail userlabel
– type ( point to point or broadcast )
– failure date
– failure time
– no. of failed legs ( for broadcast paths only )
• Problem Summary frame. It contains:
– frame title: PATH: path type or TRAIL
– one row per each failed leg. The relevant leg number is shown in the left–hand column.
Each leg is described as:
• End1 label (node+port) and End2 label (node+port)
• PROBLEM TYPE, reference to the html Problem Detail frame. The following problem
types are possible:
– 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.
Two columns are displayable: MAIN (problems on the main route) and SPARE (problems
on the spare route, only for protected paths/trail)
Clicking on the reference to the html Problem Detail frame ( named OBSTACLES and CONSTRAINTS
1AA 00014 0004 (9007) A4 – ALICE 04.10
PROBLEMS), the Problem Detail frame view will display the selected leg.
957.130.872 H 3AL 61259 AA AA 138 / 146
146
• The Problem Detail frame contains:
– header ( upper left–hand side), constituted by:

• Leg no. ,i.e. the selected leg number. This field is not present for point to point paths
• ROUTE: End1 (node+port) and End2 (node+port)
• route type: Main or Spare, followed by the PROBLEM TYPE
– Failed routing display (left–hand side). It shows, per each row:
• 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.
• END 1 name and END 2 name.
• Problem Type ( yellow string which is the html reference to the Path/Trail allocation
failure description window
From the Problem Detail frame select the problem type. The Path/Trail allocation failure description
window is displayed.
• 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.
• Generic Help on Allocation Failure. 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.
• Problem description. It contains the detailed problem description (Title and Explanation) of
the problem and suggestions ( Hints ) how to solve the problem.
The different problem types are:
– NE Connection Problems
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.
– Infinite Cost
Explanation: The routing algorithm has found a route which uses a routing link with 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
1AA 00014 0004 (9007) A4 – ALICE 04.10
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.
957.130.872 H 3AL 61259 AA AA 139 / 146
146
– 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 140 / 146
146
3 OBJECT NAMES
RM object names characters used are:

– A–Z, a–z, 0–9, all special characters except: tilde (~), backslash (\), pipe (|), double quote (”), TAB
The maximum object username lenght is:
– path 46
– ne 32
– port 58
– physical Conn 44
– routing link 46
– network 24
– subnetwork 24
– et (ring) 24
– node 32
– link connection 46
– trail 46
– tgTop 24
– network domain 24
– perf. measure 58
– pmTransport 46
– TCA Profile 48
– pmNE 46
– pmTp 68
– pmCountRep 24
– tcRProfile 24
– pmTranStProfile 24
– pmRatioProfile 24
– pmQpgProfile 24
– aSSAProfile 32
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 141 / 146
146
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.2: DESCRIPTIONS
146
3AL 61259 AA AA
142 / 146
4 ACRONYMS AND ABBREVIATIONS
ADM Add and Drop Multiplexer

AIS Alarm Indication Signal

ALS Automatic Laser Shutdown
ASAP Alarm Severity Assignment Profile
AU Administrative Unit
AU PJC Administrative Unit Pointer Justification Counter
BER Bit Error Rate
CD–ROM 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

1AA 00014 0004 (9007) A4 – ALICE 04.10
HP Hewlett Packard
HP–OV Hewlett Packard OpenView
957.130.872 H 3AL 61259 AA AA 143 / 146
146
HP–OVW Hewlett Packard OpenView Windows
HP–UX Hewlett Packard Unix

HP–VUE 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
MS–SPRING 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 Equipment–4 fibre MS Spring
NSAP Network Service Access Point

1AA 00014 0004 (9007) A4 – ALICE 04.10
OFS Out of Frame Seconds
957.130.872 H 3AL 61259 AA AA 144 / 146
146
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
STM–N 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 Cross–Connect
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 145 / 146
146
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.2: DESCRIPTIONS
END OF DOCUMENT
146
3AL 61259 AA AA
146 / 146
TABLE OF CONTENTS
1 TRANSOCEANIC MS–SPRING: MAIN CONCEPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Architectural description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4.2 Why Transoceanic MS–SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4.3 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 TRANSOCEANIC MS_SPRING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1.1 Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1.2 Span protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1.3 Ring protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.1.4 Multiple protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3 BROADCAST CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1.2 Failure affecting all drop points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.1.3 Failure affecting some drop points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.1.4 Broadcast connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4 TRANSOCEANIC MS_SPRING RESTORING ALGORITHM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.1 Path restoring algorythm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.1.1 Ring path restoring algorythm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.1.2 Span path restoring algorythm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.1.3 Transoceanic MS–SPRing manager data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.1.4 Traffic maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5 DROP & CONTINUE INTERCONNECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.1.2 Secondary circuit on HP channels: fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

E.CORRADINI
E.CORRADINI
1AA 00014 0004 (9007) A4 – ALICE 04.10
1354RM REL.5.2B
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 1 / 188
188
5.1.3 Secondary circuit on LP channels: fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.1.4 Failure cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.1.5 Span failure on span adjacent Service Selector of primary node . . . . . . . . . . . . . . . . . . . 51
5.1.6 Primary node failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.1.7 Ring failure on span included between primary and termination nodes (HP case) . . . . 53

5.1.8 Ring failure on span included between primary and termination nodes (LP case) . . . . 54
6 D&C INTERCONNECTION DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.1.1 D&C data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.1.2 Traffic map/D&C interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.1.3 Commands data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.1.4 Report data to OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.1.5 Data bus for TRANSOCEANIC MS–SPRing/D&C IN 1664SM SYSTEM . . . . . . . . . . . . 57
6.1.6 Alarm Management Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.1.7 Operations executed by NPE actuator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7 APS BYTES FOR TRANSOCEANIC MS_SPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.1.1 Span Switching example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7.1.2 Span Restoring example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.1.3 Multiple Span Switching on ADJacent spans example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
7.1.4 Span Restoring On Failed ADJacent spans example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.1.5 Ring Switching example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.1.6 Ring Restoring example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.1.7 Node Failure Ring Switching example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
7.1.8 Span Switching On Ring Switching example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
8 FEATURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.1.1 General description of MS–SPRING protection scheme . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.1.2 MS shared protection rings – Transoceanic application . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9 THE 4–F MS SPRING RM SIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
9.1.1 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
9.1.2 4f MS–Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
10 DISPLAY OF THE PROTECTION BLOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

10.1 Display of the Protection blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 2 / 188
188
FIGURES
Figure 1. 4 Fibre Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Figure 2. Transoceanic connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 3. Connection protection (no–transocanic MS_SPRing protocol) . . . . . . . . . . . . . . . . . . . . . . 12
Figure 4. Connection protection (Transoceanic MS_SPRing protocol). . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 5. Span switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 6. 4F MS–SPRing connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 7. Non–Transoceanic ring protection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 8. Transoceanic ring protection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 9. Example of connection management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 10. Ring Fault Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 11. Ring Segmentation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 12. Broadcast connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 13. Failure affecting all drop nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 14. Failure included between drop nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 15. D&C protection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 16. Secondary circuit on LP channels preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 17. D&C protection management: span failure on link adjacent Service Selector . . . . . . . . . 51
Figure 18. D&C protection management: failure on primary node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 19. D&C protection management: ring failure on link between P and T nodes (HP case) . . 53
Figure 20. D&C protection management: ring failure on link between P and T nodes (LP case) . . 54
Figure 21. HP and LP initial connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 22. SF span failure detected on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 23. SF span request short path on node A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 24. Span bridge acknowledgement short path on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 25. Span bridge & switch acknowledgement short path on node A . . . . . . . . . . . . . . . . . . . . . 68
Figure 26. SF span failure clearing on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 27. WTR timeout expiration on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 28. No Request code received on node A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 29. No Request code with Idle status received on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 30. No Request code with Idle status received on node A . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 31. Initial status of HP and LP connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 32. SF span condition detected on A and B nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 33. SF span bridge request received on A and B nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 34. SF span bridge acknowledgement received on A and B nodes . . . . . . . . . . . . . . . . . . . . . 76
Figure 35. SF span failure clearing on node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 36. WTR timeout expiration on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 37. No Request code received on node B: first step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 38. No Request code received on node B: second step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 39. No Request code with Idle status received on node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 40. No Request code with Idle status received on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 42. SF condition detected on F node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 43. SF request short path on node E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 44. SF request long path on node A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 45. SF request long path on node D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 46. SF request long path on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 47. SF request long path on node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 48. second SF request long path on node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Figure 49. second SF request long path on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 50. second SF request long path on node D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 3 / 188
188
Figure 51. second SF request long path on node A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 52. SF request long path on node E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 53. SF request long path on node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 54. SF Ring switching initial condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Figure 55. SF Ring clearing detected by node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Figure 56. WTR times expiration on nodes C, B, D, A, F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 57. No Request code on node E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 58. No Request code on node C from both sides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 59. No Request code on node B from both sides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 60. No Request code on node D from both sides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 61. No Request code on node A from both sides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 62. No Request code arrives on node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 63. No Request code arrives on nodes A, B, C, D, E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 65. SF condition detected on node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 66. SF condition detected on node D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 67. SF request long path on node A from node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 68. SF request long path on node C from node D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 69. SF request long path on node B from node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 70. second SF request long path on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 71. second SF request long path on node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 72. second SF request long path on node A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 73. SF request long path on node D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 74. SF request long path on node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 75. Br & Sw status on node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 76. Br & Sw status on nodes A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 77. SF Ring switching initial condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 78. SF span condition detected on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Figure 79. Span request short path on node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 80. Span bridge status on node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 81. Span bridge and switch status on node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Figure 82. Multiply dropped unidirectional path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 83. Dual–node ring interconnection with D&C/working mechanism: unidirectional path . . . 129
Figure 84. Dual–node ring interconnection with D&C/working mechanism: bidirectional path,
outgoing direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 85. Dual–node ring interconnection with D&C/protection architecture: bidirectional path,
outgoing direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 86. Dual–node ring interconnection with D&C/working architecture: bidirectional path,
incoming direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
incoming direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 88. Dual–node ring interconnection with D&C/working mechanism: outgoing direction
(insert node = Primary node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 89. Dual–node ring interconnection with D&C/protection architecture: outgoing direction
(insert node = Primary node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 90. Dual–node ring interconnection with D&C/working architecture: incoming direction
(drop node = Primary node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 91. Dual–node ring interconnection with D&C/protection architecture: incoming direction
(drop node = Primary node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
1AA 00014 0004 (9007) A4 – ALICE 04.10

Figure 95. Transoceanic drop & continue/working: failure–free state . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 96. Transoceanic drop & continue/protection: failure–free state . . . . . . . . . . . . . . . . . . . . . . . . 140
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 4 / 188
188
Figure 97. Transoceanic drop & continue/working: failure of the primary node . . . . . . . . . . . . . . . . . 141
Figure 98. Transoceanic drop & continue/protection: failure of the primary node . . . . . . . . . . . . . . . 142
Figure 99. Transoceanic drop&c/working:failure outside of the termination, primary, or secondary
node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 100. Transoceanic drop&c/protection: failure outside of the termination, primary, or

secondary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 101. Transoceanic drop & continue/working: failure between primary and secondary . . . . . 145
Figure 102. Transoceanic drop & continue/working: failure of the secondary node . . . . . . . . . . . . . 146
Figure 103. inside, (a) unidir (b) bidir (c) broadcast, unprotected, no prot. in NPE, HP . . . . . . . . . . 148
Figure 104. inside, (a) unidir (b) bidir (c) broadcast, SNCP, no prot. in NPE, HP . . . . . . . . . . . . . . . 149
Figure 105. boundary (2 NPE rings), bidir, D&C, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 106. boundary, bidir, D&C, no prot. in NPE, HP (add/drop node = Primary) . . . . . . . . . . . . . 151
Figure 107. boundary, bidir, D&C, no prot. in NPE, HP (add/drop node between P and S) . . . . . . . 152
Figure 108. boundary, unidir, D&C, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 109. crossing, unidir, unprotected, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 110. crossing, biidir, unprotected, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 111. crossing, broadcast, unprotected, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 112. crossing, broadcast, SNCP, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 113. crossing, unidir, SNCP, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 114. crossing, unidir, D&C, no prot. in NPE, HP (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 115. crossing, unidir, D&C, no prot. in NPE, HP (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Figure 116. crossing, bidir, SNCP, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 117. crossing, bidir, D&C, no prot. in NPE, HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 118. bidirectional protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 119. unidirectional protected path (using working resource between nodes E and D) . . . . . 167
Figure 120. unidirectional protected path (using protection resource between nodes E and D) . . . 167
Figure 121. broadcast protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 122. Selection box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 123. 4–F Protection blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Figure 124. Manage switch menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
TABLES
Table 1. Traffic map: initial provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 2. Traffic map: new HP connections on protection channels . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 3. Traffic map: preempted LP connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 4. Traffic map: mantained LP connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 5. Traffic map: final HP and LP connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 6. Aggregate Alarms + Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 7. Encoding of Sync_A and Sync_B bits of Aggregate Alarms + Sync . . . . . . . . . . . . . . . . . . . 57
Table 8. K1 byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 9. K2 byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 10. K0 byte + Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 11. Commands byte 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Table 12. Commands byte 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Table 13. Fault localization byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Table 14. Summary of supported path types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Table 15. Transition of the three states during MS–Spring implementation (case virtual –> active) 178
Table 16. 0.Transition of the thre states during MS–Spring topology removal . . . . . . . . . . . . . . . . . . 180
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 5 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
188
3AL 61259 AA AA
6 / 188
1 TRANSOCEANIC MS–SPRING: MAIN CONCEPTS
1.1 Introduction
The aim of this document is to describe the operations related to the operation and maintenance of the
4–F Transoceanic MS–Spring controlled by the 1354RM.
1.2 Target audience
The Introduction Manual is intended for all NPE users.
– Architecture
– MS–Spring Main Concepts
– Broadcast Connections
– Restoring Algorithm
– Drop & Continue Management
– Drop & Continue Interconnection
– APS Bytes for Transoceanic MS–Spring
– NPE Features
– NPE in 1354RM
– Protection Block Display

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 7 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
188
3AL 61259 AA AA
8 / 188
1.4 Architectural description
1.4.1 Introduction
Transoceanic MS–SPRing is constituted by a four fibre MS shared protection ring (”4F MS–SPRing”)
managing a different MS–SPRing protocol respect to the standard one.
4F MS–SPRing 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 MS–SPRing supports ring switching and span switching.

On 4F MS–SPRing 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 MS–SPRing 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 MS–SPRing 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 MS–SPRing 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 pass–through channels to allow other nodes to be connected.
Alcatel implementation foresees rings made up by more than 16 nodes (64 maximum).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 9 / 188
188
ÉÉ
ÉÉ ÀÀ
Node 1
ÀÀ HP Traffic
ÉÉ
ÉÉ À
Node 2
À
ÉÉ
ÉÉ ÀÀ ÉÉ À
ÍÍ
ÍÍ
ÀÀ
ÁÁ
ÁÁ
ÉÉ
ÍÍ
ÍÍ
À
Á
Á
ÍÍ
ÍÍ ÁÁ
ÁÁ LP Traffic ÍÍ
ÍÍ Á
Á
ÁÁ
ÁÁ ÍÍ
ÍÍ LP Traffic ÁÁ
ÁÁ Í
Í
ÁÁ ÍÍ ÁÁ Í
ÀÀ
ÀÀ ÉÉ
ÉÉ ÀÀ
ÀÀ É
É
ÀÀ ÉÉ
Node 3
HP Traffic ÀÀ É
Node 4
É
É ÍÍ
ÍÍ À
À Á
Á
É Agg East Main ÍÍAgg East Spare À Agg West Main Á
Figure 1. 4 Fibre Ring

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 10 / 188
188
1.4.2 Why Transoceanic MS–SPRing
Transoceanic MS–SPRing is a different type of MS_SPRing protocol in order to avoid triple ocean cross-
ing. The following figures show an example of failure management in a transoceanic link, comparing
MS_SPRing and Transoceanic MS_SPRing protocols.

MS–SPRing ring
Chicago–London link
Figure 2. Transoceanic connection.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 11 / 188
188
MS_SPRing ring
Failure between Lisbona and Paris
New connection (protection)

Loop at Lisbona and Paris Nodes
Figure 3. Connection protection (no–transocanic MS_SPRing protocol)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 12 / 188
188
MS_SPRing ring
Failure between Lisbon and Paris
New connection (protection)

Bridge & Switch on LP at Chicago and London Nodes
Figure 4. Connection protection (Transoceanic MS_SPRing protocol).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 13 / 188
188
1.4.3 Acronyms and abbreviations
2F 2 Fibres

4F 4 Fibres

AIS Alarm Indication Signal
AU4 Administrative Unit
AU–AIS Administrative Unit Alarm Indication Signal
AU–LOP Administrative Unit Loss Of Pointer
ADM Add Drop Multiplexer
BR&SW Bridge and Switch
CT Craft Terminal
D&C Drop and Continue
DCC Data Communication Channel
DCI Drop and Continue Interconnection
EC Equipment Controller
HP Higher Path traffic
HPC Higher order Path Connection
HW Hardware
LOF Loss Of Frame
LOS Loss Of Signal
LP Lower Path traffic
MS–AIS Multiplex Section Alarm Indication Signal
MS–EXBER Multiplex Section Excessive BER
MS–RDI Multiplex Section Remote Defect Indication
MS–SIGDEG Multiplex Section Signal Degrade
MS–SPRing Multiplex Section Shared Protection Ring
NE Network Element
OS Operating System
OKKO Integrity signal of the card

1AA 00014 0004 (9007) A4 – ALICE 04.10
SD Signal Degrade
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 14 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
SF
SM
SW
STM
SOH
WTR
01
957.130.872 H
Software
SC.3: NPE
Signal Failure
Section Overhead
Wait Time to Restore

Synchronous Multiplexer
Synchronous Transfer Mode
188
3AL 61259 AA AA
15 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
188
3AL 61259 AA AA
16 / 188
TSD ITALIA
2 TRANSOCEANIC MS_SPRING MANAGEMENT
2.1 Introduction
Transoceanic ring nodes have different behaviour in MS_SPRing protocol respect to non–Transoceanic
application.
2.1.1 Fault management
Transoceanic 4F MS–SPRing 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 (opto–electronic component failures);
2.1.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
c ) MS–AIS
d ) MS–EXBER
e ) 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 MS–SPRing 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 17 / 188
188
TSD ITALIA
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.
2.1.1.2 Protection switching protocol
Transoceanic 4F MS–SPRing 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).
APS switching sequences follow ITU Rec. G.841 for 4F MS_SPRing protocol for transoceanic
application. (Annex A)
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 Pass–Through 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.
The main operations performed during switching are:

– bridge;
– switch.
1AA 00014 0004 (9007) A4 – ALICE 04.10
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.3: NPE
957.130.872 H 3AL 61259 AA AA 18 / 188
188
TSD ITALIA
2.1.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 AU–AIS 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 passed–through by the
node, AIS is forced on the opposite aggregate side of the node.
ÍÍ
ÍÍ ÁÁ ÍÍ ÁÁ
ÁÁ
ÁÁ
ÁÁ
ÍÍ
ÍÍ
ÍÍ
ÁÁ
ÁÁ
ÁÁ
ÍÍ
ÍÍ
ÍÍ
ÍÍ ÁÁ ÍÍ ÁÁ
ÁÁ
ÁÁ
ÁÁ
ÍÍ
ÍÍ
ÍÍ
ÁÁ
ÁÁ
ÁÁ
ÍÍ
ÍÍ
Node 1 Node 2
Node 4 Node 3
ÍÍ
ÍÍ ÁÁ ÍÍ ÁÁ
ÁÁ
ÁÁ
ÁÁ
ÍÍ
ÍÍ
ÍÍ
ÁÁ
ÁÁ
ÁÁ
ÍÍ
ÍÍ
ÍÍ
ÍÍ ÁÁ ÍÍ ÁÁ
ÁÁ
ÁÁ
ÁÁ
ÍÍ
ÍÍ
ÍÍ
ÁÁ
ÁÁ
ÁÁ
ÍÍ
ÍÍ
ÍÍ
ÍÍ
ÁÁ
Tx block Working channel
ÁÁ Rx block Protection channel
Figure 5. Span switching

1AA 00014 0004 (9007) A4 – ALICE 04.10
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.3: NPE
957.130.872 H 3AL 61259 AA AA 19 / 188
188
TSD ITALIA
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.
In Transoceanic application the span protection does not involve all channels, but it is performed on a

AU–4 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.
2.1.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 (SF–S code or SD–S 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).
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 k–byte Pass–Through 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
So all these nodes know the presence of a span switching, even if they are not directly involved.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 20 / 188
188
TSD ITALIA
2.1.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 Wait–To–Restore 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:
condition);
• sending the Reverse Request on the short path.
b) the other node detects clearing of SF or SD condition.

It may enter in Wait–To–Restore state performing the following actions:
condition);
• signal the new state (WTR code) in both directions;
• remains in Wait to restore for the configured WTR time.
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 pass–through sides). Now
1AA 00014 0004 (9007) A4 – ALICE 04.10
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.3: NPE
957.130.872 H 3AL 61259 AA AA 21 / 188
188
TSD ITALIA
2.1.3 Ring protection
Nodes belonging to a Transoceanic ring have a different behaviour respect to a non–Transoceanic ring.

The below figure shows an example of ring connection.

1 2 3
4 5 6
HP traffic
LP traffic
Connection under evaluation

it is carried via NE 5–6–3–2 in HP channels
Figure 6. 4F MS–SPRing connection management

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 22 / 188
188
TSD ITALIA
2.1.3.1 Non–Transoceanic 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.
Figure which follows shows a ring protection switching involved in a non–Transoceanic ring.
1 2 3
4 5 6
HP traffic
LP traffic
The connection protection is carried via:

NE 5–6 on HP channels,
NE 6–5–4–1–2–3 on LP channels,
NE 3–2 on HP channels.
Figure 7. Non–Transoceanic 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Intermediate nodes are not involved in switching operations.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 23 / 188
188
TSD ITALIA
2.1.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.
1 2 3
4 5 6
HP traffic
LP traffic
The connection protection is carried via:

NE 5–4–1–2 on LP channels
Figure 8. Transoceanic ring protection management
This protection mechanism allows to mantain part of the low priority traffic when a fault occurs (differently
from normal MS–SPRing 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 non–transoceanic application all span protection channels are managed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– in transoceanic application also intermediate nodes are involved in bridge and switch operations.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 24 / 188
188
TSD ITALIA
2.1.3.3 Transoceanic ring connections
The next figures show how the connections are managed in a Transoceanic ring.
1 2 3
4 5 6
HP Traffic West Aggregate (M+S)

LP Traffic
Hp Connection Au4#6 East Aggregate (M+S)
Lp1 Connection Au4#11
Figure 9. Example of connection management.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 25 / 188
188
TSD ITALIA
After the fault event between Node 6 and Node 3, the LP3 Connection is lost (the AU–4 is used to carry
the HP Traffic), the LP1 Connection is lost however for the failure, but instead the LP2 Connection is not
lost.

1 2 3
4 5 6
HP Traffic West Aggregate (M+S)

LP Traffic
Hp Connection Au4#6 East Aggregate (M+S)
Figure 10. Ring Fault Event

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 26 / 188
188
TSD ITALIA
2.1.3.4 Ring switching/restoring algorythm
According to ITU–T 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 MS–SPRing 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.
Alcatel transoceanic ring performances surpass ITU requirements, since in presence of failure a
significant part of the LP traffic neither is 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 27 / 188
188
TSD ITALIA
2.1.3.5 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.
The two phases are constituted by:
– first phase:
1 ) on the HP path AIS insertion also in the protection time slot.
So if the involved time slot carries a LP path, AIS is detected and the path is preempted.
2 ) on the intermediate nodes of the new HP path execution of pass–through connections.
3 ) on the drop termination node of all LP paths to preempt, execution of squelching operation (AIS
forcing to tributary channel).
– second phase:
After that all the drop termination nodes of the preempted LP paths have inserted AIS it is possible
to use the protection time slots for carrying the HP path.
4 ) on the HP path insertion node execution of bridge operation and then remove of previously
inserted AIS.
If in the drop node switch operation was already executed, the HP path is restored.
5 ) in the HP path drop node execution of the switch operation.
If on the correspondent insertion node bridge operation was not yet executed the connection
will receive AIS forced by the insertion node itself. When also bridge operation is performed,the
HP path is restored.
Pass–through operation executed in intermediate nodes may occur before AIS forcing action performed
on insertion node or squelching on drop node. Thus a pass–through operation may inter–connect two LP
paths without presence of AIS on the flow causing temporary misconnection on a LP path.
To avoid misconnection pass–through operation on intermediate nodes are preceded by an AIS forcing
action on transmission side.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 28 / 188
188
TSD ITALIA
2.1.3.6 Ring restoring mechanism
Ring restoring of a HP path in transoceanic application consists in the reconnection of the provisioned HP
path and re–building 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.
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.
The operations performed are:
– first phase:
• on HP path drop node execution of drop switch operation reusing the provisioned HP path
received on working channels.
HP path is reconstituted. Restored HP path is disconnected and the protection channels can
be reused to carry LP paths.
– second phase:
• on HP path insertion node execution of drop bridge operation and on the intermediate nodes
of drop pass–through operation.
In both cases the operation consists into reconnecting on protection channels the provisioned
LP connection on the node (insertion, pass–through or not equipped). Provisioned LP paths
are re–built from insertion until drop nodes.
– third phase:
• on LP paths drop node removing of squelching action (AIS unforced on tributary side).
Now LP paths are completely restored.
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.
The operations performed are:

– first phase:
• on the HP path drop node execution of drop switch operation reusing the provisioned HP path
received on working channels.
HP path is reconstituted.
• on the HP path insertion node execution of drop bridge operation and on the intermediate nodes
of drop pass–through operation.
In both cases the operation consists into reconnecting on protection channels the provisioned
LP connection the node (insertion, pass–through or not equipped).
• on the insertion and intermediate nodes execution of AIS forcing transmission side.
Provisioned LP connection operation executed before drop switch operation may cause tempo
rary misconnection on HP path.
To avoid misconnection this operation of insertion and intermediate nodes must be preceded
by an AIS forcing action on transmission side. Although the path on protection channels is
changed this action avoids the reception of a non valid path.
– second phase:
• on the restored HP path insertion and intermediate nodes removing of AIS previously inserted.
Restored HP path is disconnected and provisioned LP paths are re–built from insertion until
1AA 00014 0004 (9007) A4 – ALICE 04.10
drop nodes. To allow the flowing of provisioned LP paths AIS must be eliminated.
• on the LP paths drop node removing of squelching action (AIS unforced on tributary side).
Now LP paths are completely restored.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 29 / 188
188
TSD ITALIA
2.1.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.

2.1.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.
2.1.4.2 Span and Ring Failures
In non–Transoceanic 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) HP path crosses only span in ring failure

2) HP path crosses one or more spans in span failure
3) 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 re–established
(provisioned HP path crosses the ring failed span and then it results still interrupted).
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
– 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).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 30 / 188
188
TSD ITALIA
2.1.4.3 Multiple Ring Failures
In Transoceanic application multiple ring failures does not split the ring into multiple subrings as occurs
in non–Transoceanic 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 re–obtain 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 re–connected 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 re–constituted).
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 31 / 188
188
TSD ITALIA
2.1.4.4 Ring Segmentation
The presence of two (or more) ring failures on a ring causes ring segmentation on APS protocol signalling.
The nodes located between two failures on a side of the ring cannot reach the nodes located on the other

side.

Next figure reports an example of a segmented ring.
In the ring initially are present two ring failures on the span between A and B nodes and on the span
between F and G nodes. A, G, H nodes cannot communicate with B, C, D, E, F nodes and viceversa.
The occurrence and clearing of another failure between C and D nodes is known only at B, C, D, E and
F nodes.
In this condition ring restoring operation during appearance of ring failure and ring switching operation
during clearing of ring failure can be executed only on a portion of the nodes.
Ring switching and restoring operations generally involve all ring nodes. First nodes crossed by the
restored HP path that execute bridge, switch, pass–through, AIS insertion actions during ring switching
and homologous dropped actions during ring restoring. But also other nodes not carrying restored HP path
may be involved to execute the specific AIS insertion and remove tributary side actions (squelching action
to preempt or restore LP connections).
Figure 11. Ring Segmentation example

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 32 / 188
188
TSD ITALIA
On ring segmentation example the appearance and clearing of a ring failure between C and D nodes cause
respectively the elimination or building of restored HP paths that are all located on nodes on which protocol
signalling arrives (B, C, D, E and F nodes in the example).
But it may occur that a LP path to be restored or to be preempted has as drop point a node on the
isolatedside of the ring (A, G and H nodes in the example). In this case squelching tributary side, remove
and insertion actions cannot be executed.
The lack of squelching would cause a misconnection on preempted LP path, so appropriate

counteractions are executed:
a) in SF unidirectional failure (multiple ring failures in SD are not allowed) force AIS on all 16 time slots
received from protection fibre also on the side not detecting failure upon reception of bridge request
on short path from adjacent node.
In this case all the LP paths travelling the failed span receive AIS and are all preempted. Thus with
ring segmentation also LP paths for which the drop points is unreachable result already preempted.
Then, the failure clears AIS on all the protection channels is removed; but now the node
that must execute squelching action can be reached and then preemption of LP path can be main
tained.
As counteraction this solution determines in unidirectional case the loss of all LP paths crossing the
failed span also in the direction not affected by the failure.
b) on the nodes interfacing ring failure insert AIS only on the protection channels transmitted toward
failed span carrying LP paths preempted to restore HP paths. This action allows to squelch LP path
to be preempted also if AIS forcing action was not possible on provisioned LP drop point. The action
is necessary only during ring switching mechanism activated in presence of ring segmentation.
The impossibility to remove AIS does not allow to restore LP path. LP path crosses one of the existing
failures and it is however lost if it travels along failed span direction.
Then when the failure interrupting LP path clears, squelching action can be removed because now the
node can communicate through protocol signalling and execute ring switching operations. Thus LP path
results correctly restored.
2.1.4.5 Multiple Switching Operations
Alcatel implementation provides:

– to follow standard protocol signalling among ring nodes
– to optimize the use of available bandwidth in case of failures executing:
• operations on the signals different from those indicated by standard;
• modification of the priority list of events according to ITU–T Recommendation.
Alcatel implementation allows:

– coexistence of multiple span switchings for multiple SD span and SF span failures (according to
ITU–T).
All nodes adjacent to the failed spans are in Switching state.
– ring switching for unique SD ring failure (according to ITU–T).
– ring switching for multiple SF ring failures (according to ITU–T)
All the nodes adjacent the failed spans are in Switching state.
– coexistence of ring switching and multiple span switchings for multiple SF ring failures and multiple
SD span and SF span failures (different from ITU–T).
Node adjacent spans detecting ring failure are in Switching state; all node adjacent spans detecting
span failure are in k–byte Pass–Through state.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 33 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
TSD ITALIA
188
3AL 61259 AA AA
34 / 188
TSD ITALIA
3 BROADCAST CONNECTIONS
3.1 Introduction
A broadcast connection is an unidirectional point–multipoints 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
pass–through 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 – pass–through;
– node 2 and 3 – bridge (pass–through and drop);
– node 1 – drop.
1 2 3
4 5 6
HP traffic
LP traffic
Broadcast connection
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 12. Broadcast connection
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 35 / 188
188
TSD ITALIA
4F Transoceanic MS–SPRing ring protection mechanism is used also to restore broadcast paths.

3.1.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.
1 2 3
4 5 6
HP traffic
LP traffic
Protected broadcast connection
Figure 13. 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:
– ring bridge on insertion node;

– pass–through LP channel on intermediate nodes of the protected connection;
– ring switch and pass–through LP channel on all the drop nodes except the nearest one;
– ring switch on nearest provisioned drop node.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 36 / 188
188
TSD ITALIA
3.1.3 Failure affecting some drop points
If the ring failure occurs on a span included between two sink nodes, the signal still reaches some drop
points.
1 2 3
4 5 6
HP traffic
LP traffic
Protected broadcast connection
Figure 14. Failure included between drop nodes
To restore the connection, the actions to perform are:
– ring bridge on insertion node;

– pass–through LP channel on intermediate nodes of the protected connection;
– ring switch and pass–through LP channel on the unreachable drop nodes;
– ring switch on the last unreachable drop node.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 37 / 188
188
TSD ITALIA
3.1.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:
– pass–through operation to build the path for the subsequent nodes;
– ring switch operation to sink the signal on the drop termination.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 38 / 188
188
TSD ITALIA
4 TRANSOCEANIC MS_SPRING RESTORING ALGORITHM
4.1 Path restoring algorythm

During both span and ring protection mechanisms the node determines the time slots of the LP channels
involved in a particular action.
4.1.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 re–route 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.
The following table shows a typical traffic map for HP and LP paths. The example illustrates only the first
8 time slots of both working and protection channels.
Table 1. Traffic map: initial provisioning

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 39 / 188
188
TSD ITALIA
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.
The following table describes the traffic map relevant to Step 1) for HP and LP paths. For the working
channels the table report the remaining connections not affected by the failure. For the protection
channels the table reports only the new HP connections.
Table 2. Traffic map: new HP connections on protection channels
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 pass–througed 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
1AA 00014 0004 (9007) A4 – ALICE 04.10
connections not involved in protection and then that are mantained on the ring.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 40 / 188
188
TSD ITALIA
Table 3. Traffic map: preempted LP connections

Table 4. Traffic map: mantained LP connections
ÁÁÁÁ
NODES
ÁÁÁÁ
AU_number A B C D E F
1 Pt –––––––
2 Pt
3 Pt
4 Pt
5 Pt
6 Pt
7 Pt –––––––
8 Pt
........
........
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
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 41 / 188
188
TSD ITALIA
Table 5. Traffic map: final HP and LP connections

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 pass–through, pass–through 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.
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 re–build (and consequent LP paths to preempt) and other LP paths to restore
1AA 00014 0004 (9007) A4 – ALICE 04.10
when one of the ring failure conditions is cleared.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 42 / 188
188
TSD ITALIA
4.1.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 pass–through 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:
– transmitted LP time slots for span bridge on aggregate spare side.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 43 / 188
188
TSD ITALIA
4.1.3 Transoceanic MS–SPRing manager data
4.1.3.1 Ring data

Transoceanic MS–SPRing manager needs a set of configuration information to execute:

a) Enabling It enables the transoceanic ring software
b) Node Id NE identifier inside the ring
c) Ring Map sequence of nodes (node identifier) where the ring is crossed in a specific direction
d) Ring WTR WTR time used to restore normal state after a span or ring switch
4.1.4 Traffic maps
Traffic maps data are subdivided for HP and LP path connections.
HP traffic maps data are subdivided in two distinct tables for clockwise and counter–clockwise
transmission direction.
Each table is organized as a matrix having as rows and columns:

– the 16 time slots;
– the nodes of the ring.
The value of a single element reports the status of the configured connection: NOT CONNECTED,
INSERT, PASS–THROUGH, DROP, DROP & INSERT, BRIDGE.
About LP traffic map the node is interested at the paths involving only the node itself.
For clockwise and counter–clockwise transmission direction two distinct tables.
For each of the 16 time slots they report:
– source node
– destination node.
4.1.4.1 HP and LP connections
HP and LP connections are subdivided in transmit connections and receive connections and they are
provisioned for each node side.
For everyone of the 16 time slots the transmit connection reports the type (NOT USED, PASS–THROUGH,
INSERTION).
For everyone of the 16 time slots the receive connection reports the type (NOT USED, PASS–THROUGH,
DROP).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 44 / 188
188
TSD ITALIA
4.1.4.2 Commands data
Transoceanic MS–SPRing manager can receive from OS a set of commands to execute:

a) Command type:
4) Lockout of protection
5) Force Span Switch
6) Force Ring Switch
7) Manual Span Switch
8) Manual Ring Switch
9) Exercise Span
10 ) Exercise Ring
11 ) Clear Command
b) Side:
1) East
2) West
4.1.4.3 Report data to OS
OS must get informations concerning the Node status in order to provide a feedback about the ring status.
These informations are:
a) Command type received and actuated:
1) Lockout protection
2) Force Span Switch
3) Force Ring Switch
4) Manual Span Switch
5) Manual Ring Switch
6) Exercise Span
7) Exercise Ring
8) Clear Command
9) Side:
East
West
b) Node Status: Idle, Pass–Through, 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 K1–K2–K3 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 45 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
TSD ITALIA
188
3AL 61259 AA AA
46 / 188
TSD ITALIA
5 DROP & CONTINUE INTERCONNECTION MANAGEMENT
5.1 Introduction
A Transoceanic 4F MS–SPRing may be interconnected to another ring in a dual node interconnection

architecture, according to ITU–T Recommendation G 842.
With this architecture the Transoceanic nodes may be used as primary and secondary node of a inter–ring
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.
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 15. 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.
D&C functionality associated with Transoceanic MS–SPRing protection mechanism causes a completely
different interaction respect to not–Transoceanic application, particularly in consequence of the bridge
and switch operations performed by intermediate nodes.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 47 / 188
188
TSD ITALIA

T T
P S P S
S P S P
T T
P: Primary node Service circuit

S: Secondary node Secondary circuit
T: Termination node Service Selector
Figure 15. D&C protection management

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 48 / 188
188
TSD ITALIA
5.1.2 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 MS–SPRing
ring protection mechanism by interacting with D&C function.
D&C function together with Transoceanic MS–SPRing 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 49 / 188
188
TSD ITALIA
5.1.3 Secondary circuit on LP channels: fault management
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 16. 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
ÍÍÍ
ÍÍÍ
ÍÍÍ
D&C Selector
LP channels
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 16. Secondary circuit on LP channels preemption
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 50 / 188
188
TSD ITALIA
5.1.4 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).
5.1.5 Span failure on span adjacent Service Selector of primary node
T T
P S P S
S P S P
Service Selector
Figure 17. D&C protection management: span failure on link adjacent Service Selector
For secondary circuit carried on HP channels , the secondary circuit is selected executing a
cross–connection operation because the signal comes from opposite side working line.
For secondary circuit carried on LPchannels, the secondary circuit is selected executing a pass–through
connection operation because the signal comes from opposite side protection line.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 51 / 188
188
TSD ITALIA
5.1.6 Primary node failure

T T
P S P S
S P S P
Service Selector Bridge connection
Figure 18. 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.
This case is managed only by Transoceanic MS–SPRing manager. The D&C path is represented on traffic
map as HP connection having secondary and termination nodes as drop/insert points.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 52 / 188
188
TSD ITALIA
5.1.7 Ring failure on span included between primary and termination nodes (HP case)
Figure 19. reports the behaviour of D&C function together with Transoceanic MS–SPRing when a failure
occurs on a span or node included between primary and termination node of a D&C path.
T T
P S P S
S P S P
Service Selector
Figure 19. 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 MS–SPRing 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.
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
1AA 00014 0004 (9007) A4 – ALICE 04.10
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.3: NPE
957.130.872 H 3AL 61259 AA AA 53 / 188
188
TSD ITALIA
5.1.8 Ring failure on span included between primary and termination nodes (LP case)
The following figure reports the behaviour of D&C function together Transoceanic MS–SPRing when
occurs a failure on a span or node included between primary and termination node of a D&C path.

T T
P S P S
S P S P
Service Selector Bridge connection
Figure 20. 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 re–route 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.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 54 / 188
188
6 D&C INTERCONNECTION DATA
6.1 Introduction
This chapter contains the description of D & C for 2–fibre and 4–fibre arrangement.
6.1.1 D&C data
D&C information required are:
a) Enabling enable or disable the overall DCI protection
b) Connection for every one of 16 AU4 flows:
• used or not used in D&C protection (and if used the type of secondary circuit: HP or
LP);
• connection side (local or opposite): the provisioned D&C connections for which the
selector is located on the same side are local; the provisioned D&C connections for
which the selector is located on the other side of the equipment are opposite;
• preferential circuit: the selection to perform when both circuits are not affected by
failure (insertion from tributary or pass–through from aggregate).
c) Revertive for every AU4 D&C protected if the protection is revertive or not;
d) WTR for every AU4 D&C protected in revertive way the WTR time to expire after which
the preferential circuit is restored.
Other data involved in the function are the provisioned connections on aggregate and tributary cards.
Node identifier and ring map information are also required.
6.1.2 Traffic map/D&C interaction
A D&C protected connection with service and secondary circuits is described by general traffic maps used
for ring protection.
On transmission direction D&C path is originated on termination node, configured in bridge on primary
node and in drop on secondary node.
On receiving direction a service circuit is inserted on primary node and a secondary circuit is inserted on
secondary node. Then only one of them reaches the termination node.
With the aim of rebuilding the connection during ring switching a D&C flow may be considered in the
following way:
– on Tx side as a broadcast path;
– on Rx side as a normal path inserted on primary node and dropped to the termination node
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 55 / 188
188
6.1.3 Commands data
D&C function can receive from OS a set of commands to execute.

For each D&C path the operator is allowed to modify the status of the selector. Two types of commands

are available: the ’manual switch’, which has lower priority than the alarm status, the ’forced switch’ , which

overcomes any alarm status.
These commands must be explicitely cleared by the operator.
a) Command type:
1) Manual Switch
2) Forced Switch
3) Clear Switch
6.1.4 Report data to OS
The informations received by the OS are:
a) Command type received and actuated:
1) Manual Switch
2) Forced Switch
3) Clear Switch
b) Selector status (Tributary or Pass–Through).

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 56 / 188
188
6.1.5 Data bus for TRANSOCEANIC MS–SPRING/D&C IN 1664SM SYSTEM
6.1.5.1 Aggregate alarms + Sync

This is the alarm byte sent by an aggregate card (main or spare) toward Transoceanic MS–SPRing
manager.
The least significant bits (bit 0 and 1) are used only by aggregate spare cards in which is resident the
manager to synchronize the operation of the two managers. In this case the byte is transmitted by an
Aggregate Spare and received by the other Aggregate Spare.
Each Aggregate Spare transmits the status of its manager (master or slave) at regular interval time.
Table 6. Aggregate Alarms + Sync
Table 7. Encoding of Sync_A and Sync_B bits of Aggregate Alarms + Sync
Sync bits encoding is listed in the table below.
6.1.5.2 K1 byte
Byte K1 is transmitted within multiplex section overhead carrying the protection channels.
Bits 1–4 carry bridge request codes, bits 5–8 carry the destination node identifier (least significant part).
The meanings are defined and reported on Recommendation G.841.
Table 8. K1 byte
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 57 / 188
188
6.1.5.3 K2 byte
Byte K2 is transmitted within multiplex section overhead carrying the protection channels.

Bits 1–4 carry source node identifier (least significant part), bit 5 carries long/short indication, bits 6–8 carry

status code. The meanings are defined and reported on Recommendation G.841.
Table 9. K2 byte
6.1.5.4 K0 byte + Sync
Alcatel Transoceanic MS–SPRing manages up to 64 nodes. Another byte of the multiplex section
overhead (called K0) is used, to identify source and destination nodes.
This byte is also used to communicate the information regarding the status of the Manager (active or
standby) to the Transoceanic Actuators. Then the byte is transmitted by two Aggregate Spare and
received by two Aggregate Main and all Tributary cards.
Table 10. K0 byte + Sync

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 58 / 188
188
6.1.5.5 Commands
Commands byte may be distinct in two parts: command for span protection and command for ring
protection.
The most significant bit (bit 7) of the Commands establishes if the commanded actions refer to span
switching or ring switching procedure.
Bit 6 and bit 7 of the Commands to value 0 establishes that the command byte has no action to drive.
Table 11. Commands byte 1
Commands for span protection describe the action .

The commands are for each side (west or east):
– AIS: AIS DROP, AIS TRANSMISSION
– BRIDGE: SPAN BRIDGE
– SWITCH SPAN SWITCH.
These commands may be simultaneously present for both sides because the equipment can be involved
in span protection operations for both sides.
The basic operations for span protection are:

– AIS DROP : for aggregate spare card
– AIS TRASMISSION : for opposite side aggregate spare card
– SPAN BRIDGE : for aggregate spare card
– SPAN SWITCH for aggregate main opposite side and tributary cards
– DROP AIS DROP : for aggregate spare card
– DROP AIS TRASMISSION : for opposite side aggregate spare card
– DROP SPAN BRIDGE : for aggregate spare card
– DROP SPAN SWITCH : for aggregate main opposite side and tributary cards.
Table 12. Commands byte 2
Commands for ring protection is organized in macro–commands: a single command bit signals the
execution of a group of operations that can be performed together at the same time.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 59 / 188
188
The commands are six plus an option. At each macro–command corresponds the following operations:
– FIRST STEP SWITCHING : AIS DROP, AIS TRASMISSION, PASS–THROUGH
– SECOND STEP SWITCHING : BRIDGE, DROP AIS TRASMISSION
– SWITCH: SWITCH

– DROP SWITCH DROP SWITCH

– FIRST STEP RESTORING: DROP BRIDGE, DROP PASS–THROUGH (if COMPRESSED bit
is setted is added AIS TRANSMISSION)
– SECOND STEP RESTORING: DROP AIS DROP (if COMPRESSED bit is setted is added DROP
AIS TRANSMISSION).
The basic operations for ring protection are:

– AIS DROP : for both aggregate spare cards
– AIS TRASMISSION : for both aggregate spare cards
– PASS–THROUGH : for both aggregate spare cards
– RING BRIDGE for both aggregate spare cards
– RING SWITCH : for tributary cards
– DROP AIS DROP : for both aggregate spare cards
– DROP AIS TRASMISSION : for both aggregate spare cards
– DROP PASS–THROUGH : for both aggregate spare cards
– DROP RING BRIDGE : for both aggregate spare cards
– DROP RING SWITCH : for tributary cards.
Multiple protection mechanisms (ring + span, span + ring, ring + ring) will cause the alternation of
Commands byte 1 and Commands byte 2.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 60 / 188
188
6.1.5.6 Fault localization
The position of a failure in the ring (span between two nodes) may be signalled via the node identifier of
only one of the two nodes and the side (west or east) .
Ring failure is communicated via:
– WEST side
– node identifier of the node adjacent the failed span on the west side.
Clearing of the same ring failure is communicated via:
– No failure indication
– same node identifier.
Table 13. Fault localization byte
The code fault may assume the following values:
– 00 : RESET
– 01 : WEST
– 10 : EAST
– 11 : NO_FAIL
RESET value identifies the initial situation without failures on the ring; WEST (or EAST) value associated
to a node identifier reports the presence of ring failure; NO_FAIL value associated to the same node
identifier reports the clearing of the previous corresponding ring failure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 61 / 188
188
6.1.6 Alarm Management Function
6.1.6.1 MS–SPRing Alarm management

Span or ring failure detection is provided.

Ring failure condition occurs when a section alarm is detected on the Aggregate main and spare cards
of the same side simultaneously.
When an alarm coming from a main card interfacing the working fibre is detected, a timeout is started to
detect a potential alarm from the spare card of the same side. So the manager is able to declare span
failure or ring failure condition.
6.1.6.2 D&C Alarm management
For Transoceanic D&C management this function provides Signal Fail or Signal Degrade detention of the
AU4 time slots involved in D&C protection coming from the two available path (from tribuatary side and
from aggregate opposite side).
The SF and SD condition of the AU4 received from tributary side is detected by the tributary card.
The SF and SD condition of the AU4 received from aggregate opposite side is detected by the aggregate
card.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 62 / 188
188
6.1.7 Operations executed by NPE actuator
The basic operations performed by Transoceanic MS–SPRing Actuator are:

– AIS FORGING RECEIVING side (for both span and ring protection)
– AIS FORGING DROP side (for both span and ring protection)
– AIS FORGING TRANSMISSION side (for both span and ring protection)
– AIS CROSS–CONNECTION side (interaction between Transoceanic and D&C functions)
– AIS PASS–THROUGH side (interaction between Transoceanic and D&C functions)
– SPAN BRIDGE (West or East)
– SPAN SWITCH (West or East)
– RING PASS–THROUGH
– RING BRIDGE
– RING SWITCH
6.1.7.1 AIS Forcing Receiving side
This action is executed during both SF span and SF ring protection.
The action is performed by the Aggregate card (Main and/or Spare) receiving the signal when an alarm
is detected causing a signal failure condition.
The action is done internally without need of command by Transoceanic MS–SPRing manager forcing
AU–AIS on all 16 AU4 flows.
AIS indication crosses both drop tributary flows and pass–through flows.
6.1.7.2 AIS Forcing on dropped LP channels (AIS DROP SIDE)
This action is executed during both span and ring protection mechanisms.
The action is performed by the Aggregate Spare card acting only on the flows sent toward tributary cards
In span protection the action regards only the spare card of the side interfacing the failure; in ring protection
the action may regard both spare cards(West/East)
6.1.7.3 AIS Forcing on transmitted LP channels (AIS Transmission Side)
This action is executed during both span and ring protection mechanisms.
In span protection the action concerns only the spare card of the side opposite to the one interfacing the
failure to signal AIS on the LP channels travelling toward the other nodes that are preempted to restore
HP channels.
In ring protection the action may regard one of the two spare cards of the equipment: the card of the side
acting as insertion point of a HP connection to restore.
This action allows to have AIS on the LP connections to preempt during the instauration of the new HP
path avoiding misconnection before, AIS forging on drop termination nodes (drop side)
The action is temporary; as soon as the new HP path is completed AIS forcing is removed to allow the
flow signal between insert and drop points of the connection.
With multiple ring failures ring switching and restoring mechanisms provide the insertion of temporary AIS
on transmission side on all nodes carrying the new HP paths on protection channels (during ring switching)
or involved in restore of previously preempted LP paths (during ring restoring).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 63 / 188
188
6.1.7.4 AIS Forcing on LP channels sent toward Aggregate Main (AIS Cross–Connection Side)
This action is executed during both span and ring protection mechanisms interacting on protected D&C
paths that have secondary circuit carried on LP channels.

The action is performed by the Aggregate Spare card.
AIS is selectively inserted on the time slots received from own section and sent toward opposite side
aggregate main.
During span and ring protection, for every protected D&C path on the node, the action regards only the
spare card of the side opposite to the one hosting provisioned D&C selector.
The operation allows to squelch secondary circuit going toward D&C selector when this is preempted to
restore HP paths travelling on the same corrisponding working channels.
6.1.7.5 AIS Forcing on LP channels received from Aggregate Spare (AIS Pass–Through Side)
This action is executed in presence of double span protection mechanism interacting with protected D&C
paths that have secondary circuit carried on LP channels.
The action is performed by the Aggregate Spare card.

AIS is selectively inserted on the time slots received from the other aggregate spare.
During second span switching mechanism, for every protected D&C path on the node, the action regards
only the spare card of the same side hosting provisioned D&C selector.
The operation allows to squelch secondary circuit coming from opposite side aggregate spare before that
arrives on active D&C selector moved on the card itself. This is done when secondary circuits are
preempted to restore HP paths travelling on the same corrispondent working channels on adjacent span.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 64 / 188
188
TSD ITALIA
7 APS BYTES FOR TRANSOCEANIC MS_SPRING
7.1 Introduction
Since the no. of nodes of the ring are greater than 16, source and destination node identifier codes on K1
and K2 bytes are not sufficient; another byte (kobyte) must be used.
It is to be noted that K1 and K2 bytes must carry also MS–AIS and MS–RDI indications.
Besides, the ring could be constituted by node apparatus of different vendors and the extension to 64
nodes (16x4) is a proprietary need in consequence of the use of a NPE station.
The NPE station may be composed by a 1664SM equipment cascade (up to 4).
Instead standardized Transoceanic MS–SPRing foresees ring constituted by 16 nodes maximum.
A single equipment is identified through a couple of numbers (Es.: 15.3). The first number is coded as
source and destination identifiers on assigned bits of K1 and K2 bytes; the second number is coded on
K0 byte.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 65 / 188
188
TSD ITALIA
7.1.1 Span Switching example
In the following figures are reported the steps of an unidirectional SF span protection switching.
The example reports the connections of two nodes of the ring that will be involved in span protection.

The HP and LP connections are represented for only the first 8 time slots.

7,8 3,6,7 1,4,6 1,6,8
W E W E
1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
A B
1,2,3,5,6,8 2,3,5,8 2,3,5,6,7,8 2,5,7 1,2,4,5,6,7
1,6 6,7 3,6,8 1,4,6
Working channels (HP)
Protection channels (LP)
Figure 21. HP and LP initial connections
Step 1) A SF span condition is detected on node B.
The node performs:
– AIS forcing on 1,3,4,5,6,7 received HP channels;
– AIS forcing on 3,6 dropped LP channels to preempt;
– AIS forcing on 5,7 passed–through LP channels to preempt transmitted on the opposite side.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 66 / 188
188
TSD ITALIA
7,8 3,6,7 1,4,6 1,6,8

W E W E
1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,6,8, 3,5,7
A B 1,2,4,5,6,7
1,2,3,5,6,8 2,3,5,8 2,3,5,6,7,8 2,5,7 1,2,4,6, 5,7
1,6 6,7 3,6, 8 1,4,6
Working channels (HP) x AIS forcing on received channels

x AIS forcing on dropped channels
Protection channels (LP) x AIS forcing on transmitted channels
Figure 22. SF span failure detected on node B
Step 2) A SF span short path request is detected on node A.
7,8 3,6,7 1,4,6 1,6,8

W E W E
1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,6,8, 3,5,7
1,2,6,8, 3,5 2,3,5,8

A 2,3,5,6,7,8 B 1,2,4,5,6,7
1,2,3,5,6,8 2,8 1,2,3,4,5,6,7,8 2,5,7 1,2,4,6, 5,7
1,6 6,7 3,6, 8 1,4,6
x AIS forcing on received channels

Working channels (HP) x AIS forcing on dropped channels
x AIS forcing on transmitted channels
Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 23. SF span request short path on node A
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 67 / 188
188
TSD ITALIA
The node performs:

– AIS forcing on 3,5 pass–throughed LP channels to preempt transmitted on the opposite side;
– bridge on 3,6,7 inserted HP channels and 1,4,5 pass–throughed HP channels.

Step 3) A span bridge acknowledgement on the short path arrives on node B.
7,8 3,6,7 1,4,6 1,6,8

W E W E
1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,6,8, 3,5,7
1,2,6,8, 3,5 2,3,5,8 A 1,2,3,4,5,6,7,8B 2 1,2,4,5,6,7
1,2,3,5,6,8 2,8 1,2,3,4,5,6,7,8 2,5,7 1,2,4,6, 5,7
1,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 24. Span bridge acknowledgement short path on node B
The node performs:

– bridge on 1,4,6 inserted HP channels and 3,5,7 pass–throughed HP channels;
– switch on 1,4,6 dropped HP channels and 3,5,7 pass–throughed HP channels.
Step 4) A span bridge & switch acknowledgement on the short path arrives on node A.
The node performs:

– switch on 3,6,7 dropped HP channels and 1,4,5 pass–throughed HP channels.
7,8 3,6,7 1,4,6 1,6,8

W E W E
1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,6,8, 3,5,7
1,4,5
1,2,6,8, 3,5 2,3,5,8 A 1,2,3,4,5,6,7,8B 2 1,2,4,5,6,7
1,2,3,5,6,8 2,8 1,2,3,4,5,6,7,8 2,5,7 1,2,4,6, 5,7
1,6 6,7 3,6, 8 1,4,6

Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 25. Span bridge & switch acknowledgement short path on node A
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 68 / 188
188
TSD ITALIA
7.1.2 Span Restoring example
In the following figures are reported the steps of an unidirectional SF span protection restoring starting
from the final conditions of the previous example.
Step 1) SF span condition clearing detected on node B.
The node performs:

– AIS removing on 1,3,4,5,6,7 received HP channels.
7,8 3,6,7 1,4,6 1,6,8

W E W E
1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,6,8, 3,5,7
1,4,5
1,2,6,8, 3,5 2,3,5,8

A B 1,2,4,5,6,7
1,2,3,4,5,6,7,8 2
1,2,3,5,6,8 2,8 1,2,3,4,5,6,7,8 2,5,7 1,2,4,6, 5,7
1,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 26. SF span failure clearing on node B

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 69 / 188
188
TSD ITALIA
Step 2) WTR timeout expiration on node B.
The node performs:

– drop span switch on 1,4,6 dropped and 3,5,7 passed–through HP channels restoring the HP

connections.

7,8 3,6,7 1,4,6 1,6,8
W E W E
1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,6,8, 3,5,7
1,4,5
1,2,6,8, 3,5 2,3,5,8 A 1,2,3,4,5,6,7,8B 2 1,2,4,5,6,7
1,2,3,5,6,8 2,8 1,2,3,4,5,6,7,8 2,5,7 1,2,4,6, 5,7
1,6 6,7 3,6, 8 1,4,6

Protection channels (LP) Bridge & Switch
Figure 27. WTR timeout expiration on node B
Step 3) No Request code detected on node A.
7,8 3,6,7 1,4,6 1,6,8

W E W E
1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,6,8,3,5,7
1,2,6,8,3,5 2,3,5,8 A 1,2,3,4,5,6,7,8B 2 1,2,4,5,6,7
1,2,3,5,6,8 2,3,5,8 2,3,5,6,7,8 2,5,7 1,2,4,6,5,7
1,6 6,7 3,6, 8 1,4,6

Protection channels (LP) Bridge & Switch
Figure 28. No Request code received on node A

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 70 / 188
188
TSD ITALIA
The node performs:
– drop span switch on 3,6,7 dropped and 1,4,5 passed–through HP channels restoring the HP
connections;
– drop span bridge on 3,6,7 inserted and 1,4,5 passed–through HP channels reconnecting the inserted
and pass–throghed LP channels;
Step 4) No Request code with Idle status detected on node B.
The node performs:
– drop span bridge on 1,4,6 inserted and 3,5,7 passed–through HP channels reconnecting the inserted
(3,6 time slots) and pass–throghed (5,7 time slots) LP channels;
– AIS removing on 3,6 dropped LP channels restoring 3,6 LP paths;
– AIS removing on 5,7 passed–through LP channels restoring 5,7 LP paths.
7,8 3,6,7 1,4,6 1,6,8

W E W E
1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,6,8, 3,5,7
1,2,6,8, 3,5 2,3,5,8

A 2,3,5,6,7,8 B 2,5,7 1,2,4,5,6,7
1,2,3,5,6,8 2,3,5,8 2,3,5,6,7,8 2,5,7 1,2,4,5,6,7
1,6 6,7 3,6,8 1,4,6

Figure 29. No Request code with Idle status received on node B

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 71 / 188
188
TSD ITALIA
Step 5) No Request code with Idle status detected on node A.
The node performs:


– AIS removing on 3,5 passed–through LP channels restoring 3,5 LP paths.
7,8 3,6,7 1,4,6 1,6,8

W E W E
1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,6,8, 3,5,7
1,2,3,5,6,8 2,3,5,8
A 2,3,5,6,7,8 B 2,5,7 1,2,4,5,6,7
1,2,3,5,6,8 2,3,5,8 2,3,5,6,7,8 2,5,7 1,2,4,5,6,7
1,6 6,7 3,6,8 1,4,6

Figure 30. No Request code with Idle status received on node A

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 72 / 188
188
TSD ITALIA
7.1.3 Multiple Span Switching on ADJacent spans example
In Transoceanic 4F MS–SPRing multiple span failures have as counteraction multiple span switching
executed on different spans.
A singular case is represented by multiple span failures occurring on adjacent spans. In this case a node
is involved in span protection on both sides of the equipment.
The following figures shows an example: a previous span failure occurred between B and C nodes has
caused a span switching to restore HP paths travelling on failed span.
Subsequently a bidirectional span failure occurs between A and B nodes.
2,3,6 1,4,7 7,8 3,6,7 1,4,6 1,6,8

W E W E W E
2,3,5,6,8 5,8 1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
1,4,5 3,5,7
1,4,6,7, 5 1,6, 5 A 1,2,6,8, 3,5 B C
1,2,4,5,6,7
2,3,5,8 1,2,3,4,5,6,7,8 2
1,4,5,6,7 1,5,6 1,2,3,5,6,8 2,8 1,2,3,4,5,6,7,8 2,5,7 1,2,4,6, 5,7
4,7 2,8, 3 1,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 31. Initial status of HP and LP connections
Step 1) A SF span condition is detected on A and B nodes.
For the second span failure 1,5,8 LP paths must be preempted. On node B LP path1 is dropped and LP
paths 5,8 are passed–through. Span switching processing foresees AIS forcing action on these time slots.
About passed–through flows time slot 5 is already involved in previous span switching and the insertion
of AIS on this flow should cause loss of the restored HP path.
Then AIS forcing action on transmitted LP channels must be executed only on the provisioned LP in
pass–through connection not already involved in previous span failure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 73 / 188
188
TSD ITALIA
Node A performs:
– AIS forcing on 1,4,5,7,8 received HP channels;

– AIS forcing on 8 dropped LP channels to preempt;

– AIS forcing on 1,5 passed–through LP channels to preempt transmitted on the opposite side.

The node B performs:

– AIS forcing on 1 dropped LP channel to preempt;
– AIS forcing only on 8 pass–throughed LP channel to preempt transmitted on the opposite side.
2,3,6 1,4,7 7,8 3,6,7 1,4 ,6 1,6,8

W E W E W E
2,3,6, 5,8 5,8 1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,3,6,7,8, 5
1,4,5 3,5,7
4,6,7, 1,5 1,6, 5 A 1,2,6,8, 3,5 B 1,2,3,4,5,6,7,8
C
1,2,4,5,6,7
2,3,5,8 2
1,4,5,6,7 1,5,6 1,2,3,5,6,8 2,8 2,3,6,7, 8, 1,4,5 2,5,7 1,2,4,6, 5,7
4,7 2, 8, 3 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 32. SF span condition detected on A and B nodes
Step 2) A SF span short path bridge request is received on A and B nodes.
For the second span failure span switching processing foresees bridge action on 1,4,5,7,8 HP time slots:
7,8 in insertion and 1,4,5 in pass–through connection on node B. This operation is normally performed
by the card interfacing the protection fibre connecting the inserted flows from tributary and the
passed–through flows from the aggregate working opposite side.
On node B for the presence of adjacent span failure the passed–through flows must be taken from
aggregate protection opposite side.
Only on node B, after soon bridge operation, AIS forcing action on transmitted LP channels executed for
the first span failure must be dropped on the time slots that results to be preempted also for the second
span failure (among the bridged one time slots both in insertion and pass–through connection).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 74 / 188
188
TSD ITALIA
Node A performs:
– bridge on 1,4,7 inserted HP channels and 5,8 passed–through HP channels from working opposite
side fibre.
– bridge on 7,8 inserted HP channels and 1,4,5 pass–through HP channels from protection opposite
side fibre;
– AIS removing on 5 pass–through LP channel already preempted for the first span failure.
2,3,6 1,4,7 7,8 3,6,7 1,4 ,6 1,6,8

W E W E W E
2,3,6, 5,8 5,8 1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,3,6,7,8, 5
1,4,5 3,5,7
A B C
4,6,7, 1,5 1,5,6 1,2,4,5,6,7,8, 3 2,3,1,4,5 1,2,3,4,5,6,7,8 1,2,4,5,6,7
2
1,4,5,6,7 6 1,2,3,4,5,6,7,8 2,8 2,3,6,7, 8, 1,4,5 2,5,7 1,2,4,6, 5,7
4,7 2, 8, 3 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 33. SF span bridge request received on A and B nodes
Step 3) A SF short path bridge acknowledgement is received by A and B nodes.
For the second failure switching processing foresees switch action on 1,4,5,7,8 HP time slots.
This operation is normally performed by the card interfacing the working fibre for the passed–through flows
and by the tributary card for the dropped flows.
On node B because of adjacent span failure, pass–through flows must be switched by aggregate
protection instead of aggregate working.
Add on aggregate working, normally executing this operation in single failure case, executes also in this
situation switch action. The operation seems useless, but it may be important when occurs clearing of
adjacent span failure. In this situation consequent drop switch action allows the immediate
re–establishment of the HP paths travelling from the remaining failed span toward the reconstituted span.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 75 / 188
188
TSD ITALIA
The node A performs:
– switch on 1,4,7 dropped HP channels executed by tributary cards;

– switch on 5,8 pass–throughed HP channels executed by working opposite side card.

– switch on 7,8 dropped HP channels executed by tributary cards;
– switch on 1,4,5 pass–throughed HP channels executed by protection opposite side card taking them
from opposite protection fibre;
– switch on 1,4,5 pass–throughed HP channels executed by working opposite side card taking them
from opposite protection fibre.
2,3,6 1,4,7 7,8 3,6,7 1,4,6 1,6,8

W E W E W E
2,3,6, 5,8 5,8 1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
5,8 1,4,5 3,5,7

A B C
4,6,7, 1,5 1,5,6 1,2,4,5,6,7,8, 3 2,3,1,4,5 1,2,3,4,5,6,7,8 1,2,4,5,6,7
2
1,4,5,6,7 6 1,2,3,4,5,6,7,8 1,2,3,4,5,6,7, 8 2,5,7 1,2,4,6, 5,7

2,8,1,4,5
4,7 2, 8, 3 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 34. SF span bridge acknowledgement received on A and B nodes

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 76 / 188
188
TSD ITALIA
7.1.4 Span Restoring On Failed ADJacent spans example
A singular case is represented by clearing of span failure in one of the adjacent spans involved in multiple
span switching.
In this case a node was involved in span protection on both sides of the equipment.
In the following figures are reported the steps of a span protection restoring starting from the final
conditions of the previous example. The reconstituted span is between B and C nodes.
Step 1) SF span condition clearing detected on node C.
The node performs:
– AIS removing on 1,3,4,5,6,7 received HP channels.
2,3,6 1,4,7 7,8 3,6,7 1,4,6 1,6,8

W E W E W E
2,3,6, 5,8 5,8 1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
5,8 1,4,5 3,5,7

A B C
4,6,7, 1,5 1,5,6 1,2,4,5,6,7,8, 3 2,3,1,4,5 1,2,3,4,5,6,7,8 1,2,4,5,6,7
2
1,4,5,6,7 6 1,2,3,4,5,6,7,8 1,2,3,4,5,6,7, 8 2,5,7 1,2,4,6, 5,7

2,8,1,4,5
4,7 2, 8, 3 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 35. SF span failure clearing on node C
Step 2) WTR timeout expiration on node C.
The node performs:
– drop span switch on 1,4,6 dropped and 3,5,7 pass–through HP channels restoring the HP
connections.
Since previous span switching operation executed by working card on node B the pass–throughed
HP flows 1,4,5 will be transferred toward node C without AIS and then result correctly received.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 77 / 188
188
TSD ITALIA
2,3,6 1,4,7 7,8 3,6,7 1,4,6 1,6,8

W E W E W E

2,3,6, 5,8 5,8 1,4,5,7,8 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
5,8 1,4,5 3,5,7

A B C
4,6,7, 1,5 1,5,6 1,2,4,5,6,7,8, 3 2,3,1,4,5 1,2,3,4,5,6,7,8 1,2,4,5,6,7
2
1,4,5,6,7 6 1,2,3,4,5,6,7,8 1,2,3,4,5,6,7, 8 2,5,7 1,2,4,6, 5,7

2,8,1,4,5
4,7 2, 8, 3 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 36. WTR timeout expiration on node B
Step 3) No Request code received on node B.
2,3,6 1,4,7 7,8 3,6,7 1,4,6 1,6,8

W E W E W E
2,3,6, 5,8 5,8 1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
5,8 1,4,5 3,5,7

A B C
4,6,7, 1,5 1,5,6 1,2,4,5,6,7,8, 3 2,3 1,2,3,4,5,6,7,8 1,2,4,5,6,7
2
1,4,5,6,7 6 1,2,3,4,5,6,7,8 1,2,3,4,5,6,7, 8 2,5,7 1,2,4,6, 5,7

2,8,1,4,5
4,7 2, 8, 3 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 37. No Request code received on node B: first step
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 78 / 188
188
TSD ITALIA
Span restoring processing foresees drop span switch and bridge operation on node B. These operations
are analyzed in two steps: the first explains drop switch action and the second explains the drop bridge
action.
Drop switch action is performed on 3,6,7 dropped time slots and on 1,4,5 pass–through time slots.
The operation involves tributary cards for dropped channels and both working and protection aggregate
cards for pass–through channels.
On working card the action is similar at single failure case and consists in selecting the pass–through flows
from working fibre of the opposite side and no more from protection fibre opposite side executing a direct
connection.
On protection card the action consists in selecting the pass–through flows from working fibre opposite side
and no more from protection fibre opposite side executing a cross–connection.
2,3,6 1,4,7 7,8 3,6,7 1,4,6 1,6,8

W E W E W E
2,3,6, 5,8 5,8 1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
5,8 1,4,5 3,5,7

A 2,3 B C
4,6,7, 1,5 1,5,6 1,2,4,5,6,7,8, 3 1,2,3,4,5,6,7,8 1,2,4,5,6,7
2
1,4,5,6,7 6 1,2,3,4,5,6,7,8 2,3,5,8 2,3,6,7, 5,8 2,7, 5 1,2,4,6, 5,7
4,7 2, 8, 3 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 38. No Request code received on node B: second step
Drop bridge action involves 3,6,7 inserted time slots and 1,4,5 pass–throughed time slots.
The operation includes protection aggregate card: the action consists into disconnecting the HP paths and
reconnecting the provisioned LP paths (similar as single span restoring).
About LP pass–through flows reconnection it is necessary to force AIS on the flows that are involved in
remaining span failure before the execution of the provisioned LP connections to avoid misconnection
(these flows are involved in HP restoring and then do not carry LP traffic).
Among 2,3,5,8 LP pass–through flows 5,8 time slots are involved in remaining span protection (it is to be
noted that time slot already has AIS forcing).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 79 / 188
188
TSD ITALIA
The node performs:
– drop span switch on 3,6,7 dropped time slots executed by tributary cards;
– drop span switch on 1,4,5 pass–through HP channels executed by both aggregate working and

protection cards restoring the HP connections on reconstituted working fibre;

– drop span bridge on 3,6,7 inserted and 1,4,5 pass–through HP channels reconnecting the inserted
(6,7 time slots) and pass–through (3,5 time slots) LP channels;
– AIS forcing on 5,8 transmitted time slots even involved in HP restoring.
Step 4) No Request code with Idle status received on node C.
The node performs:
– drop span bridge on 1,4,6 inserted and 3,5,7 pass–throughed HP channels reconnecting the inserted
(3,6 time slots) and pass–throgh (5,7 time slots) LP channels;
– AIS removing on 5,7 pass–through LP channels restoring only 7 LP path (time slot 5 has still AIS
forcing deriving from the previous node).
2,3,6 1,4,7 7,8 3,6,7 1,4,6 1,6,8

W E W E W E
2,3,6, 5,8 5,8 1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
5,8 1,4,5 3,5,7

A 2,3 B C
4,6,7, 1,5 1,5,6 1,2,4,5,6,7,8, 3 2,3,5,6,7,8 2,5,7 1,2,4,5,6,7
1,4,5,6,7 6 1,2,3,4,5,6,7,8 2,3,5,8 2,3,6,7, 5,8 2,7, 5 1,2,4,6,7, 5
4,7 2, 8, 3 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 39. No Request code with Idle status received on node C

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 80 / 188
188
TSD ITALIA
Step 5) No Request code with Idle status received on node B.
The node performs:

– AIS removing on 6,7 dropped LP channels restoring 6,7 LP paths (as for single span failure);
– AIS removing on 3,5 pass–through LP channels (as for single span failure): time slot 5 already not
had AIS forcing because involved in remaining span failure and then the action restores only 3 LP
path.
2,3,6 1,4,7 7,8 3,6,7 1,4,6 1,6,8

W E W E W E
2,3,6, 5,8 5,8 1,4,5,7,8 1,4,5 1,3,4,5,6,7 3,5,7 1,3,5,6,7,8
5,8 1,4,5 3,5,7

A 2,3 B C
4,6,7, 1,5 1,5,6 1,2,3,4,5,6,7,8 2,3,5,6,7,8 2,5,7 1,2,4,5,6,7
1,4,5,6,7 6 1,2,3,4,5,6,7,8 2,3,5,8 2,3,6,7, 5,8 2,7, 5 1,2,4,6,7, 5
4,7 2,3, 8 1 ,6 6,7 3,6, 8 1,4,6

Bridge & Switch
Figure 40. No Request code with Idle status received on node B

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 81 / 188
188
TSD ITALIA
7.1.5 Ring Switching example
In the following figures are reported the steps of an unidirectional SF ring protection switching.
The ring is composed by six nodes. HP and LP connections reflect the traffic map already seen for ”Path

restoring algorythm” paragraph that reports the ring connection for only the first 8 time slots.

1,2 1,4,5 1,3,6 3,6,7 4,6 1,6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6 1,3,5,6,7,8
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
2,8 2,3,8 1,7,8 6,7 3,6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7,8 5,7,8
F E D
1,2,3,5,8 1,3,6,7,8
2,3 1,8 1,3,6

1,2,5,7,8 1,2,4,5,6,7
F E D
7,8 6,7,8 6 1,5,6 1,6
1,2,5 6 7,8 1,5 5 2,4,5,7

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 82 / 188
188
TSD ITALIA
Step 1) A SF ring condition is detected on node F. The node performs:

– AIS forcing on 1,2,3,5,8 received HP channels and on 6,7,8 received LP channels;
– AIS forcing on 1,5,8 transmitted LP channels away from the failure used for HP connections
restoring.
1, 2 1,4,5 1,6, 3 3,6,7 4,6 1, 6,8
A B C
1,4,5,6,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6, 2,3 1, 3,5,6,7,8
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5, 7 1,5 ,2,3,8, 7 2,3, 5 2,3,6,7, 5 2,7, 5
2, 8 2,3,8 1, 7 ,8 6,7 3,6 1,4, 6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

2, 1,5,8, 7 1,2,4,6,7, 5
1,2,5,7,8
F E D 1,2,4,5,6,7
7,8 6,7,8 6 1,5,6 1, 6
7,8 6,7,8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,4,7, 5

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 42. SF condition detected on F node
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 83 / 188
188
TSD ITALIA
Step 2) A SF ring short path request arrives on node E. The node performs:
– AIS forcing on 5,8 dropped LP channels to preempt from both sides;
restoring.

1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1,6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3 1,3,5,6,7,8
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5, 7 1,5 ,2,3,8, 7 2,3, 5 2,3,6,7, 5 2,7, 5
2, 8 2,3,8 1, 7 ,8 6,7 3,6 1,4, 6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

2, 1,5,8, 7 1,2,4,6,7, 5
1,2,5,7,8 F E D 1,2,4,5,6,7
7,8 6,7,8 6 1,5,6 1, 6
7,8 6,7,8 6 1, 2,3,5, 6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,4,7, 5

Figure 43. SF request short path on node E

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 84 / 188
188
TSD ITALIA
Step 3) A SF ring long path request arrives on node A. The node performs:
– AIS forcing on 2,3,8(both sides) dropped LP channels to preempt;
– AIS forcing on 2 transmitted LP channel away from the failure used for HP connections restoring;
– pass–through of 1,5,8 LP channels used for HP connections restoring on both sides.
1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1,6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3 1,3,5,6,7,8
A B C
1,5,7,8 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5,8, 7 1,2,5,8 ,3, 7 3, 2,5 3,6,7, 2,5 2,5, 7
2, 8 2,3,8 1,8, 7 6,7 3,6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

2, 1,5,8, 7 1,4,6,7,2,5
1,2,5,7,8 F E D 1,2,4,5,6,7
7,8 6,7,8 6 1,5,6 1, 6
7,8 6,7,8 6 1, 2,3,5, 6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

Figure 44. SF request long path on node A

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 85 / 188
188
TSD ITALIA
Step 4) A SF ring long path request arrives on node D originated by node E. The node performs:
– AIS forcing on 2,5(both sides) dropped LP channels to preempt;

1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1,6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
1,6 ,2,3 3, 6 4,5 3,5,7

1,3,5,6,7,8
A B C
1,7,8, 5 1,3,7,8,2,5 3, 2,5 3,6,7, 2,5 2,5, 7
1,5,8, 7 1,2,5,8 ,3, 7 3, 2,5 3,6,7, 2,5 2,5, 7
2, 8 2,3,8 1,8, 7 6,7 3,6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

2, 1,5,8, 7 1,4,6,7,2,5
1,2,7,8, 5 F E D 1,4,6,7,2,3,5,8
7,8 6,7,8 6 1,3,6, 2,5 1,3,6, 2,5
7,8 6,7,8 6 2,3,5,1,6 2,3,5,1,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

Figure 45. SF request long path on node D

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 86 / 188
188
TSD ITALIA
Step 5) A SF ring long path request arrives on node B originated by node F. The node performs:
– pass–through of 1,2,5,8 LP channels used for HP connections restoring on both sides.
1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1,6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1,3,5,6,7,8
A B C
1,7,8, 5 1,3,7,8,2,5 1,3,8, 2,5 3,6,7, 2,5 2,5, 7
1,5,8, 7 1,2,5,8 ,3, 7 1,2,5,8 ,3 1,2,3,5,8, 6,7 2,5, 7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

2, 1,5,8, 7 1,4,6,7,2,5
1,2,7,8, 5 F E D 1,4,6,7,2,3,5,8
7,8 6,7,8 6 1,3,6, 2,5 1,3,6, 2,5
7,8 6,7,8 6 2,3,5,1,6 2,3,5,1,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

Figure 46. SF request long path on node B

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 87 / 188
188
TSD ITALIA
Step 6) A SF ring long path request arrives on node C originated by node E. The node performs:
– AIS forcing on 3 dropped LP channels to preempt;

1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1,6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1,3,5,6,7,8
A B C
1,5,8, 7 1,2,3,5,8, 7 1,2,3,5,8 1,2,3,5,8, 6,7 2,3,5,8, 7
1,5,8, 7 1,2,5,8 ,3, 7 1,2,5,8 ,3 1,2,3,5,8, 6,7 2,3,5,8, 7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,5,8, 2, 7 1,4,6,7,2,3,5,8
F E D 1,4,6,7,2,3,5,8
1,5,8, 2,7 7,8 6,7,8 6 1,6, 2,3,5 1,6, 2,3,5
7, 8 6,7, 8 6 1,6, 2,3,5 1,6, 2,3,5
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

Figure 47. SF request long path on node C

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 88 / 188
188
TSD ITALIA
Step 7) A SF ring long path request arrives on node C originated by node F. The node performs:
– bridge and switch on 1 restored HP channel;
– AIS removing on 1 transmitted LP channel carrying the new HP connection.
1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1, 6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1 1,3,5,6,7,8
A B C
5,8, 1,7 2,3,5,8, 1,7 1, 2,3,5,8 2,3,5,8, 1,6,7 2,3,5,8, 7
1,5,8, 7 1,2,5,8 ,3, 7 1,2,5,8 ,3 1,2,3,5,8, 6,7 2,3,5,8, 7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,5,8, 2, 7 1,4,6,7,2,3,5,8
F E D 1,4,6,7,2,3,5,8
5,8, 1,2,7 7,8 6,7,8 6 1,6, 2,3,5 1,6, 2,3,5
7, 8 6,7, 8 6 1,6, 2,3,5 1,6, 2,3,5
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 48. second SF request long path on node C
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 89 / 188
188
TSD ITALIA
Step 8) A SF ring long path request arrives on node B originated by node E. The node performs:

1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1, 6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1 1,3,5,6,7,8
3
A B C
5,8, 1,7 2,5,8, 1,7 1, 2,5,8 2,3,5,8, 1,6,7 2,3,5,8, 7
1,5,8, 7 1,2,5,8 ,3, 7 1,2,5,8 1,2,5,8, 3,6,7 2,5,8,3,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,5,8, 2, 7 1,3,4,6,7, 2,5,8
F E D 1,4,6,7,2,3,5,8
5,8, 1,2,7 7,8 6,7,8 6 1,3,6, 2,5 1,3,6, 2,5
7, 8 6,7, 8 6 1,6, 2,3,5 1,6, 2,3,5
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 49. second SF request long path on node B
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 90 / 188
188
TSD ITALIA
Step 9) A SF ring long path request arrives on node D originated by node F. The node performs:
1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1, 6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1 1,3,5,6,7,8
3
A B C
1,7,8, 5 2,5, 1,7,8 1,8, 2,5 2,3,5, 1,6,7,8 2,3,5,7,8
1,5,8, 7 1,2,5,8 ,3, 7 1,2,5,8 1,2,5,8, 3,6,7 2,5,8,3,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,5,8, 2, 7 8 1,3,4,6,7, 2,5,8
F E D 1,4,6,7,8, 2,3,5
1,2,7,8, 5 7,8 6,7,8 6 1,3,6, 2,5 1,3,6, 2,5
7, 8 6,7, 8 6 1,6, 2,3,5 1,6, 2,3,5
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
Figure 50. second SF request long path on node D

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 91 / 188
188
TSD ITALIA
Step 10) A SF ring long path request arrives on node A originated by node E. The node performs:

1, 2 1,4,5 1,6 ,3 3,6,7 4,6 1, 6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
2 1 1,3,5,6,7,8
3
A B C
1,7,8, 5 2,5, 1,7,8 1,8, 2,5 2,3,5,1,6,7,8 2,3,5,7,8
1,5,8, 7 1,5,8, 2,3, 7 2, ,1,5,8 1,5,8,2,3,6,7 5,8, 2,3,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,5,8, 2, 7 8 1,2,3,4,6,7, 5,8
F E D 1,4,6,7,8, 2,3,5
1,2,7,8, 5 7,8 6,7,8 6 1,2,3,6, 5 1,2,3,6,5
7, 8 6,7, 8 6 1,6, 2,3,5 1,6, 2,3,5
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
Figure 51. second SF request long path on node A

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 92 / 188
188
TSD ITALIA
Step 11) A SF ring long path request arrives on node E originated by node F. The node performs:
– bridge and switch on 2,3,5 restored HP channels;
– AIS removing on 2,3,5 transmitted LP channel carrying the new HP connections.
The 2,3 HP connections now are completely restored in both directions.
1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
1,5,8, 7 1,5,8, 2,3, 7 2, ,1,5,8 1,5,8, 2,3,6,7 5,8, 2,3,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,5,8, 2, 7 2,3,5 8 1,2,3,4,6,7, 5,8
1,2,5,7,8
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7,8 6,7,8 6 1,2,3,6, 5 1,2,3,6, 5
7, 8 6,7, 8 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 52. SF request long path on node E
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 93 / 188
188
TSD ITALIA
Step 12) A SF ring long path request arrives on node F originated by node E. The node performs:
– bridge and switch on 1,5,8 restored HP channels;
– AIS removing on 1,5,8 transmitted LP channel carrying the new HP connections.
Also the 1,5,8 HP connections now are completely restored in both directions. HP traffic is all restored.

1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,8, 7 8 1,2,3,4,5,6,7,8
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 53. SF request long path on node F
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 94 / 188
188
TSD ITALIA
7.1.6 Ring Restoring example
The following figures show the steps of an unidirectional SF ring protection restoring, starting from the final
conditions of the previous example.
1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,8, 7 8 1,2,3,4,5,6,7,8
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 54. SF Ring switching initial condition
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 95 / 188
188
TSD ITALIA
Step 1) SF ring condition clearing detected from node F. The node performs:
– AIS removing on 1,2,3,5,8 received HP channels and on 6,7,8 received LP channels.

1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
1,5,7,8 1,2,3,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 8 1,2,3,4,5,6,7,8
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
Figure 55. SF Ring clearing detected by node F

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 96 / 188
188
TSD ITALIA
Step 2) WTR/2 interval expires on node C. The node drops ring switch on 1 HP channel.
Step 3) WTR/2 interval expires on node B. The node drops ring switch on 3 HP channel.
Step 4) WTR/2 interval expires on node D. The node drops ring switch on 8 HP channel.
Step 5) WTR/2 interval expires on node A. The node drops ring switch on 2 HP channel.
Step 6) WTR interval expires on node F. The node drops ring switch on 1,5,8 HP channels.
1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
1,5,7,8 1,2,3,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 8 1,2,3,4,5,6,7,8
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 56. WTR times expiration on nodes C, B, D, A, F
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 97 / 188
188
TSD ITALIA
Step 7) No Request code arrives on node E. The node performs:

– drop ring switch on 2,3,5 HP channels;
– drop ring bridge on 2,3,5 HP channels;
– restoring provisioned 5 LP channel in insertion.

1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,5,7,8 1,5,8 1,5,6,7,8 5,7,8
1,5,7,8 1,2,3,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 8 1,2,3,4,5,6,7,8
1,5,8
F E D 1,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,5,6 1,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 57. No Request code on node E
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 98 / 188
188
TSD ITALIA
Step 8) No Request code arrives on node C from both sides. The node performs:
– drop ring bridge on 1 HP channel;
– restoring provisioned 3 LP channel in insertion and 2 LP channel in pass–through.
1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1,3,5,6,7,8
2 3
A B C
5,7 5,7 5 2,3,5,6,7 2,5,7
1,5,7,8 1,2,3,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,5,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 8 1,2,4,5,6,7
1,5,8
F E D 1,4,5,6,7,8
2,5,7 7 6,7,8 6 1,2,5,6 1,2,5,6
7 6,7 6 1,5,6 1,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 58. No Request code on node C from both sides
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 99 / 188
188
TSD ITALIA
Step 9) No Request code arrives on node B from both sides. The node performs:
– restoring provisioned 1,8 LP channels in insertion and 2,3 LP channels in pass–through.

1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1,3,5,6,7,8
2
A B C
5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5,7,8 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 8 1,2,4,5,6,7
1,5,8
F E D 1,4,5,6,7,8
2,5,7 7 6,7,8 6 1,2,5,6 1,2,5,6
7 6,7 6 1,5,6 1,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
Figure 59. No Request code on node B from both sides

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 100 / 188
188
TSD ITALIA
Step 10) No Request code arrives on node D from both sides. The node performs:
– restoring provisioned 5 LP channel on a side and 2,5 LP channels on the other side in insertion.
1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1,3,5,6,7,8
2
A B C
5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5,7,8 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 1,2,4,5,6,7
1,5,8
F E D 1,2,4,5,6,7
2,5,7 7 6,7,8 6 1,5,6 1,6
7 6,7 6 1,5,6 1,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
Figure 60. No Request code on node D from both sides

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 101 / 188
188
TSD ITALIA
Step 11) No Request code arrives on node A from both sides. The node performs:
– restoring provisioned 8 LP channel on a side and 2,8 LP channels on the other side in insertion and
1 LP channel in pass–through both directions.

1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1,3,5,6,7,8
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 1,2,4,5,6,7
1,5,8
1,2,5,7,8 F E D 1,2,4,5,6,7
7 6,7,8 6 1,5,6 1,6
7 6,7 6 1,5,6 1,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 61. No Request code on node A from both sides
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 102 / 188
188
TSD ITALIA
Step 12) No Request code arrives on node F. The node performs:

– drop ring bridge on 1,5,8 HP channels;
– restoring provisioned 1,5 LP channels in insertion and 8 LP channel in pass–through both directions;
– AIS drop side removing on 1,5 LP channels.
1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1,3,5,6,7,8
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 1,2,4,5,6,7
1,2,5,7,8 F E D 1,2,4,5,6,7
7,8 6,7,8 6 1,5,6 1,6
7,8 6,7,8 6 1,5,6 1,6
1,2,5 6 7, 8 1, 5 5 2,5, 4,7

Figure 62. No Request code arrives on node F

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 103 / 188
188
TSD ITALIA
Step 13) Second Idle code arrives on node A. It removes AIS on 8 and 2,3,8 LP channels.
Step 14) Second Idle code arrives on node B. It removes AIS on restored 1,8 LP channels.
Step 15) Second Idle code arrives on node C. It removes AIS on restored 3 LP channel.
Step 16) Second Idle code arrives on node D. It removes AIS on 5 and 2,5 LP channels.

Step 17) Second Idle code arrives on node E. It removes AIS on restored 8 and 5 LP channels.

1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6
1,3,5,6,7,8
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
2,8 2,3,8 1,7,8 6,7 3,6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,7,8 1,2,4,5,6,7
1,2,5,7,8 F E D 1,2,4,5,6,7
7,8 6,7,8 6 1,5,6 1,6
7,8 6,7,8 6 1,5,6 1,6
1,2,5 6 7,8 1,5 5 2,4,5,7

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 63. No Request code arrives on nodes A, B, C, D, E
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 104 / 188
188
TSD ITALIA
7.1.7 Node Failure Ring Switching example
In the following figures are reported the steps of a node failure ring switching protection.
The ring is composed by six nodes. HP and LP connections reflect the traffic map already seen for ”Path
restoring algorythm” paragraph that reports the ring connection for only the first 8 time slots.
1,2 1,4,5 1,3,6 3,6,7 4,6 1,6,8
A B C
1,3,4,5,6 3,4,5,6,7
3,6 4,5 3,5,7

1,2,3,6 1,3,5,6,7,8
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
2,8 2,3,8 1,7,8 6,7 3,6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7,8 5,7,8
F E D
1,2,3,5,8 1,3,6,7,8
2,3 1,8 1,3,6

1,2,5,7,8 1,2,4,5,6,7
F E D
7,8 6,7,8 6 1,5,6 1,6
1,2,5 6 7,8 1,5 5 2,4,5,7

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 105 / 188
188
TSD ITALIA
The failed node is node E.

Step 1) A SF ring condition is detected on node F. The node performs:


restoring.
1, 2 1,4,5 1,6, 3 3,6,7 4,6 1, 6,8
A B C
1,4,5,6, 3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6, 2,3 1, 3,5,6,7,8
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6,7 2,5,7
1,5, 7 1,5 ,2,3,8, 7 2,3, 5 2,3,6,7, 5 2,7, 5
2, 8 2,3,8 1, 7 ,8 6,7 3,6 1,4, 6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

2, 1,5,8, 7 1,2,4,6,7, 5
1,2,5,7,8
F E D 1,2,4,5,6,7
7,8 6,7,8 6 1,5,6 1, 6
7,8 6,7,8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,4,7, 5

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 65. SF condition detected on node F
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 106 / 188
188
TSD ITALIA
Step 2) A SF ring condition is detected on node D. The node performs:

– AIS forcing on 7 dropped LP channel to preempt;
– AIS forcing on 7,8 transmitted LP channels away from the failure used for HP connections restoring.
1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1,6, 8
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
1,6, 2,3 5,7,8, 1,3,6
A B C
1,5,7 1,2,3,5,7,8 2,3,5 2,3,5,6, 7 2,5, 7
1,5, 7 1,5 ,2,3,8, 7 2,3, 5 2,3,6,7, 5 2,7, 5
2, 8 2,3,8 1, 7 ,8 6, 7 3,6 1,6 ,4
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

2, 1,5,8, 7 1,2,4,6,7, 5
1,2,5,7,8
F E D 1,6 ,2,4,5, 7,8
7,8 6,7,8 6 1,5,6 1, 6
7,8 6,7,8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,4, 5, 7

Figure 66. SF condition detected on node D

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 107 / 188
188
TSD ITALIA
Step 3) A SF ring long path request arrives on node A originated by node F. The node performs:
– AIS forcing on 2,3,8(both sides) dropped LP channels to preempt;

1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1,6, 8
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
1,6, 2,3 5,7,8, 1,3,6
A B C
1,5,7,8 1,2,3,5,7,8 2,3,5 2,3,5,6, 7 2,5, 7
1,5,8, 7 1,2,5,8 ,3, 7 2,5 ,3 3,6,7, 2,5 2,5 ,7
2, 8 2,3,8 1,8, 7 6, 7 3,6 1,6 ,4
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

2, 1,5,8, 7 1,4,6,7, 2,5
1,2,5,7,8
F E D 1,6 ,2,4,5, 7,8
7,8 6,7,8 6 1,5,6 1, 6
7,8 6,7,8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,5, 4, 7

Figure 67. SF request long path on node A from node F

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 108 / 188
188
TSD ITALIA
Step 4) A SF ring long path request arrives on node C originated by node D. The node performs:
– AIS forcing on 3,6(both sides) dropped LP channels to preempt;
– AIS forcing on 1,6 transmitted LP channels away from the failure used for HP connections restoring;
– pass–through of 7,8 LP channels used for HP connections restoring on both sides.
1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1,6, 8
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
1,6, 2,3 5,7,8, 1,3,6
A B C
1,5,7,8 1,2,3,5,7,8 2,3,5 2,3,5, 1,6,7,8 2,5, 7,8
1,5,8, 7 1,2,5,8 ,3, 7 2,5 ,3 3,6,7, 2,5 2,5 ,7,8
2, 8 2,3,8 1,8, 7 6,7 3,6 1 ,4, 6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

2, 1,5,8, 7 1,4,6,7,8, 2,5
1,2,5,7,8
F E D 1,6 ,2,4,5, 7,8
7,8 6,7,8 6 1,5,6 1, 6
7,8 6,7,8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,5, 4, 7

Figure 68. SF request long path on node C from node D

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 109 / 188
188
TSD ITALIA
Step 5) A SF ring long path request arrives on node B originated by node F. The node performs:

It is to be noted that after the first bridge request turns around more LP connections was preempted respect

the case of SF ring switching because the nodes individuate different fault localization and consequently
they preempt different LP connections to rebuild the new HP paths.
1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1,6, 8
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
1,6, 2,3 5,7,8, 1,3,6
A B C
1,8 ,5,7 2,3,5,7, 1,8 2,3,5, 1,8 2,3,5, 1,6,7,8 2,5, 7,8
1,5,8, 7 1,2,5,8 ,3, 7 1,2,5,8 ,3 1,2,3,5,8 ,6,7 2,5,8 ,7
2, 8 2,3,8 1,8, 7 6,7 3,6 1 ,4, 6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

2, 1,5,8, 7 1,4,6,7, 2,5,8
2,5,7, 1,8
F E D 1,6 ,2,4,5, 7,8
7,8 6,7,8 6 1,5,6 1, 6
7, 8 6,7, 8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,5, 4, 7

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 69. SF request long path on node B from node F
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 110 / 188
188
TSD ITALIA
Step 6) A SF ring long path request arrives on node B originated by node D. The node recognizes a node
E failure; the HP connections dropped and inserted by the node E (2,3,5 time slots on a side and 3,6,7
on the other side) are however lost and there is no more need to restore. The node performs:
– confirming provisioned 6,7 LP channels in drop/insert toward node C (no more used for node failure);
– no bridge & switch action;

– AIS removing on 3 transmitted LP channel toward node C (no more used for node failure).
1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1,6, 8
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
2,3 5,7,8, 1,3,6
A B C
1,8 ,5,7 2,3,5,7, 1,8 2,3,5, 1,8 2,3,5, 1,6,7,8 2,5, 7,8
1,5,8, 7 1,2,5,8 ,3, 7 1,2,5,8 ,3 1,2,5,8, 3,6,7 2,5,8 ,7
2, 8 2,3,8 1,8, 7 6,7 3,6 1 ,4, 6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

2, 1,5,8, 7 1,4,6,7, 2,5,8
F E D 1,6 ,2,4,5, 7,8
2,5,7, 1,8 7,8 6,7,8 6 1,5,6 1, 6
7, 8 6,7, 8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,5, 4, 7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 70. second SF request long path on node B
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 111 / 188
188
TSD ITALIA
Step 7) A SF ring long path request arrives on node C originated by node F. The node recognizes a node
E failure. The node performs:
– confirming provisioned 3,6 LP channels in drop/insert toward node B and 6 LP channel toward node
D (no more used for node failure);


– AIS removing on 1,6 transmitted LP channels toward node B (6 no more used for node failure).
1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1 ,6 ,8
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
2,3 1
A B C 5,7,8, 1,3,6
1,5,7, 8 1,2,3,5,7, 8 1,2,3,5, 8 1,2,3,5,6, 7,8 2,5, 7,8
1,5,8, 7 1,2,5,8 ,3, 7 1,2,5,8 ,3 1,2,5,8, 3,6,7 2,5,8 ,7
2, 8 2,3,8 1,8, 7 6, 7 3,6 1 ,4, 6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

2, 1,5,8, 7 1,4,6,7, 2,5,8
1,2,5,7, 8
F E D 1,6 ,2,4,5, 7,8
7,8 6,7,8 6 1,5,6 1, 6
7, 8 6,7, 8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,5, 4, 7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 71. second SF request long path on node C
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 112 / 188
188
TSD ITALIA
Step 8) A SF ring long path request arrives on node A originated by node D. The node recognizes a node
– confirming provisioned 2,3 LP channels in drop/insert toward node B (no more used for node failure);
– no bridge & switch action;
– AIS removing on 2 transmitted LP channel toward node B (no more used for node failure).
1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1 ,6 ,8
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
2,3 1
A B C 5,7,8, 1,3,6
1,5,7, 8 1,2,3,5,7, 8 1,2,3,5, 8 1,2,3,5,6, 7,8 2,5, 7,8
1,5,8, 7 1,5,8 ,2,3, 7 1,5,8 ,2,3 1,5,8 ,2,3,6,7 2,7, 5,8
2, 8 2,3,8 1,8, 7 6, 7 3,6 1 ,4, 6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

2, 1,5,8, 7 1,2,4,6,7, 5,8
1,2,5,7, 8
F E D 1,6 ,2,4,5, 7,8
7,8 6,7,8 6 1,5,6 1, 6
7, 8 6,7, 8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,4, 5, 7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 72. second SF request long path on node A
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 113 / 188
188
TSD ITALIA
Step 9) A SF ring long path request arrives on node D originated by node F. The node recognizes a node
– AIS removing on 7,8 transmitted LP channels toward node C (7 no more used for node failure);

– AIS removing on 7 received LP channel tributary side (no more used for node failure).

1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1 ,6 ,8
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
2,3 1
A B C 5,7,8, 1,3,6
1,5,7,8 1,2,3,5,7,8 1,2,3,5,8 1,2,3,5,6,7,8 2,5,7,8
1,5,8, 7 1,5,8 ,2,3, 7 1,5,8 ,2,3 1,5,8 ,2,3,6,7 2,7, 5,8
2, 8 2,3,8 1,8, 7 6,7 3,6 1 ,4, 6
1,6 2,3,5 3,6,7 7, 8 5,7,8

1,5,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

2, 1,5,8, 7 8 1,2,4,6,7, 5,8
1,2,5,7,8
F E D 1,6 ,2,4,5,7,8
7,8 6,7,8 6 1,5,6 1, 6
7,8 6,7,8 6 1,5,6 1, 6
2, 1,5 6 7, 8 1, 5 5 2,4,7, 5

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 73. SF request long path on node D
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 114 / 188
188
TSD ITALIA
Step 10) A SF ring long path request arrives on node F originated by node D. The node recognizes a node
– bridge and switch on 1,8 restored HP channels;
– AIS removing on 1,5,8 transmitted LP channels toward node C (5 no more used for node failure);
– AIS removing on 5 received LP channel tributary side (no more used for node failure).
Now only 1,8 HP channels are restored.
1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1,8, 6
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
2,3 1
A B C 5,7,8, 1,3,6
1,5,7,8 1,2,3,5,7,8 1,2,3,5,8 1,2,3,5,6,7,8 2,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,3,5,8 1,2,3,5,6,7,8 2,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3,6 1 ,4, 6
1,6 7, 8 5,7,8
1,8, 5 2,3,5 3,6,7
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

1,2,5,8, 7 8 1,2,4,5,6,7,8
1,8
1,2,5,7,8
F E D 1,6 ,2,4,5,7,8
7 6,7,8 6 1,5,6 1, 6
7 6,7 6 1,5,6 1, 6
1 ,2,5 6 7, 8 1, 5 5 2,4,5,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 74. SF request long path on node F
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 115 / 188
188
TSD ITALIA
Step 11) Bridge & Switch status arrives on node C originated by node D.
The node performs:
– AIS removing on 3,6(both sides) received LP channels tributary side (no more used for node failure).

1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1,8, 6
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
2,3 1
A B C 5,7,8, 1,3,6
1,5,7,8 1,2,3,5,7,8 1,2,3,5,8 1,2,3,5,6,7,8 2,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,3,5,8 1,2,3,5,6,7,8 2,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3,6 1,6 ,4
1,6 7, 8 5,7,8
1,8, 5 2,3,5 3,6,7
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

1,2,5,8, 7 8 1,2,4,5,6,7,8
1,8
1,2,5,7,8
F E D 1,6 ,2,4,5,7,8
7 6,7,8 6 1,5,6 1, 6
7 6,7 6 1,5,6 1, 6
1 ,2,5 6 7, 8 1, 5 5 2,4,5,7

x Bridge & Switch
Figure 75. Br & Sw status on node C

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 116 / 188
188
TSD ITALIA
Step 12) Bridge & Switch status arrives on node A originated by node F. The node performs:
– AIS removing on 2,3 received LP channels tributary side (no more used for node failure).
Step 13) Bridge & Switch status arrives on node B originated by node D. The node performs:
– no action.
– LP channels no more used HP channels are restored. Only LP channels 1 and 8 are preempted.
1, 2 1,4,5 1,6, 3 3 ,6,7 4,6 1,8, 6
A B C
1,4,5,6, 3 3 ,4,5,6,7
3, 6 4,5 3 ,5,7
2,3 1
A B C 5,7,8, 1,3,6
1,5,7,8 1,2,3,5,7,8 1,2,3,5,8 1,2,3,5,6,7,8 2,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,3,5,8 1,2,3,5,6,7,8 2,5,7,8
2, 8 2,3, 8 1,8, 7 6,7 3,6 1,6 ,4
1,6 7, 8 5,7,8
1,8, 5 2,3,5 3,6,7
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8 1, 3,6
2,3 1,8 1,3,6

1,2,5,8, 7 8 1,2,4,5,6,7,8
1,8
1,2,5,7,8
F E D 1,6 ,2,4,5,7,8
7 6,7,8 6 1,5,6 1, 6
7 6,7 6 1,5,6 1, 6
1 ,2,5 6 7, 8 1, 5 5 2,4,5,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 76. Br & Sw status on nodes A and B
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 117 / 188
188
TSD ITALIA
7.1.8 Span Switching On Ring Switching example
The following figures describe the steps of an unidirectional SF span protection coexisting with ring
switching protection already present.

The example refers to previous ring switching example and span failure occurring on B and C nodes.

1, 2 1,4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
1,4,5,6 ,3 3,4,5,6,7
3, 6 4,5 3,5,7
1,6 ,2,3
1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,8, 7 8 1,2,3,4,5,6,7,8
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 77. SF Ring switching initial condition
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 118 / 188
188
TSD ITALIA
Step 1) A SF span condition is detected on node B. The node performs:

– among 3,4,5,6,7 channels: 3,5 are used for ring protection and then only 4,6,7 channels are involved
in span switching;
– AIS forcing on 6,7 provisioned dropped LP channels to preempt.

1, 2 1, 4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
3,6 1,3,6, 4,5 4,5 3,4,5,6,7
1,2,3,6 1,4,5,6, 3
3, 6 4,5 3,5,7
1,6 ,2,3 1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,5,8 1,2,3,5,6,7,8 2,3,5,7,8
2, 8 2,3,8 1,8, 7 6,7 3, 6 1,4,6
1,6 1,5,8 2,3, 5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,8, 7 8 1,2,3,4,5,6,7,8
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, 4,7

x Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 78. SF span condition detected on node B
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 119 / 188
188
TSD ITALIA
Step 2) A SF span short path request arrives on node C. The node performs:
– among 3,4,5,6,7 channels: 3,5 are used for ring protection and then only 4,6,7 channels are involved
in span switching;
– AIS forcing on 6 provisioned dropped LP channel to preempt;

– AIS forcing on 7 provisioned pass–through LP channels to preempt;

– span bridge on 4,6,7 LP channels.
1, 2 1, 4,5 1,3,6 3,6,7 4,6 1, 6,8
A B C
3,6 1,3,6, 4,5 4,5 3,4,5,6,7
1,2,3,6 1,4,5,6, 3
3, 6 4,5 3,5,7
4,6,7
1,6 ,2,3 1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,4,5,6,7,8 2,3,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,5,8 1,2,3,5,6,7,8 2,3,5,8, 7
2, 8 2,3,8 1,8, 7 6,7 3,6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,8, 7 8 1,2,3,4,5,6,8, 7
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, ,4, 7

x Ring Bridge & Switch
x Span Bridge & Switch
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 79. Span request short path on node C
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 120 / 188
188
TSD ITALIA
Step 3) A span bridge status arrives on node B. The node performs:

– span bridge and switch on 4,6,7 LP channels.
1, 2 1,4, 5 1,3,6 6,7, 3 4,6 1, 6,8
A B C
3,6 1,3,4,6, 5 4, 5 3,4,5,6,7
1,2,3,6 1,4,5,6, 3
3, 6 4,5 3,5,7
4,6,7
1,6 ,2,3 4,6,7 1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,4,5,6,7,8 2,3,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,5,8 1,2,3,4,5,6,7,8 2,3,5,8, 7
2, 8 2,3,8 1,8, 7 6,7 3,6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,8, 7 8 1,2,3,4,5,6,8, 7
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, ,4, 7

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 80. Span bridge status on node B
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 121 / 188
188
TSD ITALIA
Step 4) A span bridge and switch status arrives on node C. The node performs:
– span switch on 4,6,7 LP channels.
At the end all the HP connections lost for ring failure are mantained and other 3 HP connections affected
by span failure are restored; only 3,5 HP paths carried on failed span are lost. The 7 LP path from B to

D is also lost.

1, 2 1,4, 5 1,3,6 6,7, 3 4,6 1, 6,8
A B C
3,6 1,3,4,6, 5 4, 5 3,4,5,6,7
1,2,3,6 1,4,5,6, 3
3, 6 4,5 3,5,7
1,6 ,2,3 4,6,7 4,6,7 1 1,3,5,6,7,8
2 3
A B C
1,5,7,8 1,2,5,7,8 1,2,5,8 1,2,3,4,5,6,7,8 2,3,5,7,8
1,5,8, 7 1,2,3,5,8, 7 1,2,5,8 1,2,3,4,5,6,7,8 2,3,5,8, 7
2, 8 2,3,8 1,8, 7 6,7 3,6 1,4,6
1,6 1,5,8 2,3,5 3,6,7 7, 8 5,7,8
F E D
2,3 1,2,3,5,8 1,8 1,3,6,7,8
2,3 1,8 1, 3,6

1,2,5,8, 7 8 1,2,3,4,5,6,8, 7
1,5,8 2,3,5
F E D 1,2,3,4,5,6,7,8
1,2,5,7,8 7 6,7,8 6 1,2,3,5,6 1,2,3,5,6
7 6,7 6 1,2,3,5,6 1,2,3,5,6
2, 1,5 6 7, 8 1, 5 5 2,5, ,4, 7

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 81. Span bridge and switch status on node C
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 122 / 188
188
8 FEATURES
This Chapter is in accordance with ITU–T Recommendation G.841; explanations have been for better
understanding.
DEFINITIONS
ITU–T Recommendation G.841 definitions apply. In addition, more definitions are suggested hereafter.
path: according to ITU–T Recommendation G.803, a path is a transport entity (i.e., architectural
component) used to transfer information. Nevertheless, this name will be used throughout this document
to indicate the information carried either unidirectionally or bi–directionally between two access points of
a ring on either a path link connection (if the two points are both PDH) or trail segment.
bridge&switch node: the node that performs the bridge and switch function for a protection event. Where
the bridge and switch is performed on a per AU–4 basis, the node executing a bridge and switch of at least
one AU–4 is referred to as a bridge and switch node. Note that with a Transoceanic application, a node
in the switching status may not be a bvridge&switch node, whereas a node in the pass–through state may
be a bridge&switch node. With the Classic application, only a request node (see below) may be a
bridge&switch node.
protocol request: a message sent by a node to another node via K1/K2 bytes with the purpose of settling
a certain behavior. All the K1 request codes represent protocol requests, but not all of them are bridge
requests. For example, a SF–R is a bridge request, but LP–S is not: both of them are protocol requests.
Even NR is a protocol request.
protocol reply: a message sent by a node to another node via K1/K2 bytes with the purpose of
acknowledging a received protocol request.
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 pass–through state. If such
a node executes bridge and switch of at least one AU–4 it is also a bridge&switch node.
commanded span: is either the span involved in a couple of crossing protocol requests (or protocol
request and protocol reply) being exchanged by tail/head end nodes, or the span involved by an externally
initiated command, even if this requires no specific signaling on the ring (i.e., LOW).
MSSPRING channels: The range of channels that are part of the MSSPRING operation (i.e. the whole
of the working and protection channels).
protection section: the full set of both protection and (lower) unprotected channels in a multiplex section.
protection semisection: the part of multiplex section (i.e. the N/2+1..N channels in a 2–fiber STM–N NE)
consisting of protection channels.
unprotected channels: see non–preemptible unprotected channel. Each pair of unprotected

channels is made up on one in the working (semi)section plus one in the protection (semi)section.
unprotected traffic: see non–preemptible unprotected traffic.
working section: the full set of both working and (upper) unprotected channels in a multiplex section.
1AA 00014 0004 (9007) A4 – ALICE 04.10
working semisection: the part of multiplex section (i.e. the 1..N/2 channels in a 2–fiber STM–N NE)
consisting of working channels.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 123 / 188
188
8.1 Introduction
This document covers the management of MSSPRING with the following characteristics:
– ring access: 140 Mbit/s, STM–1, STM–4;

– switched entity: VC4, VC4–4c;

– connectivity: VC4, VC4–4c;
– protection selectivity (NUT);
– misconnections: avoided permanent and transitory by means of squelching and unsquelching;
– low–priority extra–traffic on protection channels
– both Classic and Transoceanic (G.841 Annex A) applications
– TSI on low–priority (i.e., ET) thru traffic;
8.1.1 General description of MS–SPRING protection scheme
Multiplex Section Shared Protection Ring (MSSPRING) is an SDH trail protection scheme, as it is
described in ITU–T 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 124 / 188
188
8.1.2 MS shared protection rings – Transoceanic application
The application is fully compliant with G.841, Annex A.
8.1.2.1 Application
The application is fully compliant with G.841, Annex A section A.1

8.1.2.2 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, pre–empted extra traffic can be re–established 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 auto–provisions 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 per–AU–4 basis. In this way, an unloaded
Normal AU–4 will not be bridged & switched, and the corresponding ET AU–4 will not be pre–empted.
8.1.2.3 Application architecture

The application is fully compliant with G.841, Annex A section A.3.
An MS shared protection ring in a transoceanic application uses SDH multiplex section layer indications
to trigger the protection switching. Switching action is performed only on AU–4 tributaries affected by the
failure. Multiplex section indicators include MS failure conditions, and signalling messages that are sent
between nodes to affect a coordinated MS protection switch.
In the event of a failure, ring switches are established at any node whose traffic is affected by the failure.
Unlike the general purpose approaches described earlier, no loopbacks are established. Loopbacks and
switching only at the nodes adjacent to a failure are the cause of triple ocean crossing encountered by the
traffic restoration path mentioned above. Therefore, in the transoceanic approach, all nodes are allowed
to switch and use the existing protocol in conjunction with ring maps. As in the general purpose cases
described in Sections 7.2.1.1 and 7.2.1.2, the affected traffic is rerouted away from the failure over the
protection channels.
The problem of misconnection is eliminated for the transoceanic ring application because there are no
loopbacks at the switching nodes. It is the looping at switching nodes that sets up the potential for
misconnections.
Single and multiple failures resulting in ring switching are executed in the same manner, by simply bridging
1AA 00014 0004 (9007) A4 – ALICE 04.10
and switching and taking advantage of the ring map information .
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 125 / 188
188
8.1.2.4 Switching criteria
Full compliance to , Annex A, section A.4 is required.

The criteria found in Section 7.2.4 applies, with the following additional interpretations:

forced switch to protection–ring (FS–R): This command performs the ring switch of normal traffic signals
from working channels to the protection channels for the span between the node at which the command
is initiated and the adjacent node to which the command is destined. This switch occurs regardless of the
state of the protection channels, unless the protection channels are satisfying a higher priority bridge
request, or a signal failure (or a K–byte failure) exists on the long path protection channels. For
transoceanic applications, the FS–R is meant to prompt the same switching response as that for a cable
cut on the span between the node at which the command is initiated and the adjacent node to which the
command is destined. As in the behaviour for cable cuts, however, no loopbacks are established. Normal
traffic between any two nodes that had been using the affected span is now rerouted away from this span
via the protection channels.
manual switch to protection–ring (MS–R): For transoceanic applications, the note under the FS–R
description also applies here.
£exercise–ring (EXER–R): For transoceanic applications, no extra traffic is affected either.
exercise–span (EXER–S): For transoceanic applications, no extra traffic is affected either.
As described in Section 7.4.2, the SF bridge request is used to protect normal traffic affected by a
hard–failure, while the SD bridge request is used to protect against a soft failure. The bridge requests are
transmitted on both the short and long paths. Each intermediate node verifies the destination node ID of
the long path bridge request and relays the bridge request. The destination node receives the bridge
request, performs the activity according to the priority level, and sends the bridged indication. For
transoceanic applications, this activity occurs at both the switching nodes and the intermediate nodes.
As described also in Section 7.4.2, the WTR bridge request is used to prevent frequent oscillation between
the protection channels and the working channels. The intent is to minimize oscillations, since hits are
incurred during switching. The WTR bridge request is issued after the working channels’ BER meets the
restoral threshold. The WTR is issued only after an SF or an SD condition and, thus, does not apply for
externally initiated bridge requests. For ring switches in a transoceanic application, a WTR bridge request
received bidirectionally by an intermediate node with bridged and switched traffic results in the following.
The intermediate node initiates a local WTR whose time interval is one half that of the switching node WTR
interval. For transoceanic applications, the WTR interval is set to the same value at all nodes.
8.1.2.5 Protection switch protocol
The Protection switch protocol is as described in G.841, Annex A, section A.5.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 126 / 188
188
8.1.2.6 Additional requirements
The following additional requirements dealing with particular paths other than uni– or bi–directional
point–to–point shall be met.
8.1.2.6.1 Unidirectional multiply dropped paths
A unidirectional multiply dropped path (also called broadcast or point–to–multipoint, see Figure 82. ) shall
be protected as follows: the capability for the insert node to reach all drop nodes must be preserved upon
occurrence of single (ring/span) failure (exception: insert node failure).
8.1.2.6.2 Dual–node ring interconnection
Interworking between the Transoceanic MS–SPRING and another ring is achieved as follows:
– the “continue” portion of the drop& continue (all spans between Primary and Secondary node, that
may not be adjacent) uses working channels; this methos will be referred to as drop &
continue/working herein;
– the “continue” portion of the drop& continue (all spans between Primary and Secondary node, that
may not be adjacent) uses protection channels; this methos will be referred to as drop &
continue/protection herein.
The latter option provides a lower lever of survivability, but on the other hand avoids using up working (i.e.,
premium) channels for redundancy purposes.
The method shall be programmable by the manager on a per–au4 basis.
The following objectives shall apply:
– the dual–node interconnection capability shall be preserved upon a single ring failure occurring
between the termination node and the Primary node (not including node failures of both termination
and Primary); this means that the interconnection is still redundant after the occurrence of such a
failure; the above only applies to drop & continue/working method; if the drop & continue/protection
method is used, the loss of dual–node interconnection capability is tolerated upon occurrence of the
mentioned failure.
– The dual–node interconnection capability shall be preserved upon multiple span failure, even
occurring on span(s) between the Primary and Secondary node.
– The dual–node interconnection capability is obviously lost in case of failure of either Primary or
Secondary node. The interconnection shall however be preserved via the available interconnection
node.
– The loss of dual–node interconnection capability is tolerated upon occurrence of any (span/ring)
failure between the Primary and Secondary node; in this case, only the Primary interconnection
remains available and guarantees interconnction.
– the dual–node interconnection capability shall be applicable to:
• unidirectional paths;
• broadcast paths;
1AA 00014 0004 (9007) A4 – ALICE 04.10
• bidirectional paths with add/drop node different from Primary node (see Figure 84. through
Figure 87. );
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 127 / 188
188
• bidirectional paths with add/drop node is the Primary node (see Figure 88. through Figure 91. ),
namely the path enters the ring at the Primary node to reach the other ring through the Primary
itself as well as the Secondary;

• bidirectional paths with add/drop node is located between the Primary and the Secondary

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 128 / 188
188
C B A R Q
D P
working channels
protection channels
E N
F G H L M
Figure 82. Multiply dropped unidirectional path
C B A R Q
D P
working channels
protection channels
E N
F G H L M
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 83. Dual–node ring interconnection with D&C/working mechanism: unidirectional path
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 129 / 188
188
C B A R Q
D P
working channels
protection channels
E N
F G H L M
Figure 84. Dual–node ring interconnection with D&C/working mechanism: bidirectional path, outgoing
direction
C B A R Q
D P
working channels
protection channels
E N
F G H L M
1AA 00014 0004 (9007) A4 – ALICE 04.10
outgoing direction
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 130 / 188
188
C B A R Q
D P
working channels
protection channels
E N
F G H L M
= selector
Figure 86. Dual–node ring interconnection with D&C/working architecture: bidirectional path, incoming
direction
C B A R Q
D P
working channels
protection channels
E N
F G H L M
= selector
1AA 00014 0004 (9007) A4 – ALICE 04.10
incoming direction
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 131 / 188
188
C B A R Q
D P
working channels
protection channels
E N
F G H L M
Figure 88. Dual–node ring interconnection with D&C/working mechanism: outgoing direction (insert
node = Primary node)
C B A R Q
D P
working channels
protection channels
E N
F G H L M
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 89. Dual–node ring interconnection with D&C/protection architecture: outgoing direction (insert
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 132 / 188
188
C B A R Q
D P
working channels
protection channels
E N
F G H L M
= selector
Figure 90. Dual–node ring interconnection with D&C/working architecture: incoming direction (drop
C B A R Q
D P
working channels
protection channels
E N
F G H L M
= selector
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 91. Dual–node ring interconnection with D&C/protection architecture: incoming direction (drop
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 133 / 188
188
8.1.2.7 Protection algorithm operation
Full compliance to G.841, Annex A, section A.6 is ensured, with the following additions.

8.1.2.7.1 Handling coexistence Signal Fail – Ring + Forced Switch Ring

SF–R and FS–R do not coexist. If a SF–R + FS–R combination affects a ring on different spans – whatever
the sequence over time –
– the nodes do not reroute and save the premium paths affected by both.
– the nodes do not reroute and lose the premium paths affected by FS–R only.
– the nodes do not reroute and save the premium paths affected by SF–R only.
8.1.2.7.2 Handling coexistence Signal Fail – Ring + Signal Fail – Ring
If a SF–R + SF–R combination affects a ring on different spans
– the nodes reroute the premium paths affected by both;
– the nodes do not reroute the premium paths affected by one SF–R only.”
8.1.2.7.3 Handling coexistence Forced Switch – Ring + Forced Switch Ring
“If a FS–R + FS–R combination affects a ring on different spans
– the nodes reroute the premium paths affected by both;
– the nodes do not reroute the premium paths affected by one FS–R only.”
8.1.2.7.4 Handling unidirectional multiply dropped paths
Figure 82. shows a generic ring and a normal point–to–multipoint cicuit being inserted at node A and
broadcast to nodes G, H, and L.
With the Transoceanic MS–SPRING, the ring traffic map shall describe a point–to–multipoint path
according to the following rules:
– the insert node for the given path (see Figure 82. , node A) shall see the outgoing point–to–multipoint
path as being inserted locally and dropped at the farthest drop node (L);
– each node dropping the incoming point–to–multipoint 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 pass–through connection. Every such node shall also be aware that the drop
connection is part of a point–to–multipoint 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 92. ), shall be 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 134 / 188
188
– Node L realizes that the failure is affecting the point–to–multipoint path it is receiving from A (because
the ring traffic map declares the path as A⇒L, and the failure is in between) and, knowing to be the
farthest drop node for that path, drops the extra–traffic according to the usual rules and converts its
drop/West connection of the failed point–to–multipoint 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 point–to–multipoint path it is receiving from
A (because the ring traffic map declares the path as A⇒G, 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 point–to–multipoint 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 point–to–multipoint path
a good signal as a substitute for the failed one.
A failure between the first drop node and the farthest drop node (see Figure 93. ), 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 point–to–multipoint path it is receiving from
A and does no switching at all.
The original point–to–multipoint path is therefore split into
• a point–to–multipoint path on the working channel, from the insert node through the farthest
unaffected drop node (G), and
• a point–to–multipoint path on the corresponding protection channel in the opposite direction,
from the insert node through the first affected drop node (H).
A failure of the farthest drop node (see Figure 94. ) is handled as follows:
– Node A does no switching because the node being declared by its ring traffic map as destination of
the point–to–multipoint 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 135 / 188
188
C B A R Q
D P
working channels
protection channels
E N
F G H L M
C B A R Q
D P
working channels
protection channels
E N
F G H L M
F
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 136 / 188
188
C B A R Q
D P
working channels
protection channels
E N
F G H L M
8.1.2.7.5 Ring interworking with a transoceanic MS–SPRING
Figure 95. (drop & continue/working method) and Figure 96. (drop & continue/protection method) show
the nominal failure–free state of a simple MS–SPRING and illustrates a particular tributary handed–off at
two ring interconnection nodes (D, E) and to be terminated at node A. The two ring interconnection nodes
are referred to as the Primary node and the Secondary node. Primary and secondary nodes are defined
on a per–tributary (AU–4) basis.
Each bi–directional path going from an MS–SPRING ring to another ring through a dual–node
interconnection is therefore a combination of a point–to–multipoint path and a multipoint–to–point path
traveling in the opposite direction and traversing the same spans.
8.1.2.7.5.1 Failure of the primary node
The same behavior recommended for Classic MS–SPRING applies:
a failure of the Primary node in the [Transoceanic] MS–SPRING results in a secondary connection of the
tributary. Failure of the Primary node is illustrated in Figure 97. (drop & continue/working method) and
Figure 98. (drop & continue/protection method). All traffic traversing the failed node is recovered by
bridging & switching the affected paths onto the protection capacity at each termination node (node A in
the example) as well as at the secondary node (node D).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 137 / 188
188
8.1.2.7.5.2 Failure outside of the termination, Primary, or Secondary nodes
A cable cut failure is illustrated in Figure 99. (drop & continue/working method) and Figure 100. (drop &
continue/protection method).

As the termination node A bridges and switches the path onto the protection channel away from the failure,
the two interconnection nodes shall behave as follows (drop & continue/working method):
– the Primary node shall loop 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 dual–node interconnection capability is preserved, still allowing the ring self–healing when
a potential additional fault affects the secondary path (the hand–off to the Secondary node).
As for the drop & continue/protection method, the loopback is not applicable as the “continue” portion is
pre–empted 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.
8.1.2.7.5.3 Failure of the secondary node
The same behavior recommended for Classic MS–SPRING applies to both drop & continue/working and
/protection methods:
for a failure of the secondary node, the tributary at the terminating node (see node A in Figure 102. ) 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.
8.1.2.7.5.4 Failure between the interconnection nodes
A failure occurring between the two interconnection nodes (see Figure 101. ), 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
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 138 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Working
Protection
957.130.872 H
SC.3: NPE
E
A
F
B
188
3AL 61259 AA AA
D
Figure 95. Transoceanic drop & continue/working: failure–free state
139 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Working
Protection
957.130.872 H
SC.3: NPE
E
A
F
B
188
3AL 61259 AA AA
D
Figure 96. Transoceanic drop & continue/protection: failure–free state
140 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Working
Protection
957.130.872 H
SC.3: NPE
A
E
F
B
188
3AL 61259 AA AA
D
Figure 97. Transoceanic drop & continue/working: failure of the primary node
141 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Working
Protection
957.130.872 H
SC.3: NPE
A
E
F
B
188
3AL 61259 AA AA
D
Figure 98. Transoceanic drop & continue/protection: failure of the primary node
142 / 188
Working
Protection
(f. pass–through) B
A (f. pass–through)
Protocol
request
F (f. pass–through)
C (f. pass–through)
Protocol
reply
E(switching) (switching) D
Figure 99. Transoceanic drop&c/working:failure outside of the termination, primary, or secondary nod
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 143 / 188
188
Working
Protection

Protocol
request
Protocol
reply
Figure 100. Transoceanic drop&c/protection: failure outside of the termination, primary, or secondary
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 144 / 188
188
Working
Protection
Protocol
request
Protocol
reply
Figure 101. Transoceanic drop & continue/working: failure between primary and secondary
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 145 / 188
188
Working
Protection


Figure 102. Transoceanic drop & continue/working: failure of the secondary node
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 146 / 188
188
8.1.2.7.6 Path types and traffic map
This section lists a set of paths that are supported by networks that include an NPE ring.
Table 14. Summary of supported path types

path scope path direction path protection path bandwidth class in

protection MS–SP ring
in MS–
SP ring
1 inside unidir unprotected no HP
2 inside bidir unprotected no HP
3 inside broadcast unprotected no HP
4 inside unidir unprotected no LP
5 inside bidir unprotected no LP
6 inside broadcast unprotected no LP
7 boundary unidir unprotected no HP
8 boundary bidir unprotected no HP
9 boundary broadcast unprotected no HP
10 boundary unidir D&C no HP
11 boundary bidir D&C no HP
12 boundary unidir unprotected no LP
13 boundary bidir unprotected no LP
14 boundary broadcast unprotected no LP
15 crossing unidir unprotected no HP
16 crossing bidir unprotected no HP
17 crossing broadcast unprotected no HP
18 crossing unidir SNCP no HP
19 crossing bidir SNCP no HP
20 crossing broadcast SNCP no HP
21 crossing unidir D&C no HP
22 crossing bidir D&C no HP
23 crossing unidir unprotected no LP
24 crossing bidir unprotected no LP
25 crossing broadcast unprotected no LP
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. In all traffic map bits k = i+N, where N comes from STM–N.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 147 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
F
A
957.130.872 H
SC.3: NPE
F
A
F
A
E
B
NPE
E
B
E
B
NPE
NPE
D
C
D
C
D
C
188
3AL 61259 AA AA
Figure 103. inside, (a) unidir (b) bidir (c) broadcast, unprotected, no prot. in NPE, HP
148 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
F
A
957.130.872 H
SC.3: NPE
F
F
A
A
E
B
E
B
E
B
D
C
D
C
D
C
188
3AL 61259 AA AA
Figure 104. inside, (a) unidir (b) bidir (c) broadcast, SNCP, no prot. in NPE, HP
149 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
F
F
A
957.130.872 H
SC.3: NPE
E
B
E
B
NPE
NPE
D
C
D
C
F
A
F
A
E
B
E
B
NPE
NPE
188
3AL 61259 AA AA
Figure 105. boundary (2 NPE rings), bidir, D&C, no prot. in NPE, HP
D
C
D
C
150 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
F
F
A
957.130.872 H
SC.3: NPE
E
B
E
B
NPE
NPE
D
C
D
C
F
A
F
A
E
B
E
B
NPE
NPE
188
3AL 61259 AA AA
D
C
D
C
Figure 106. boundary, bidir, D&C, no prot. in NPE, HP (add/drop node = Primary)
151 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
F
F
A
957.130.872 H
SC.3: NPE
E
B
E
B
NPE
NPE
D
C
D
C
F
A
F
A
E
B
E
B
NPE
NPE
188
3AL 61259 AA AA
D
C
D
C
Figure 107. boundary, bidir, D&C, no prot. in NPE, HP (add/drop node between P and S)
152 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
F
A
F
A
957.130.872 H
SC.3: NPE
E
B
E
B
NPE
NPE
D
C
D
C
F
A
E
B
188
3AL 61259 AA AA
Figure 108. boundary, unidir, D&C, no prot. in NPE, HP
NPE
D
C
153 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
F
A
E
B
NPE
D
C
188
3AL 61259 AA AA
Figure 109. crossing, unidir, unprotected, no prot. in NPE, HP
154 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
F
A
E
B
NPE
D
C
188
3AL 61259 AA AA
Figure 110. crossing, biidir, unprotected, no prot. in NPE, HP
155 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
F
A
E
B
NPE
D
C
188
3AL 61259 AA AA
Figure 111. crossing, broadcast, unprotected, no prot. in NPE, HP
156 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
F
A
E
B
NPE
D
C
188
3AL 61259 AA AA
Figure 112. crossing, broadcast, SNCP, no prot. in NPE, HP
157 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
F
A
E
B
NPE
D
C
188
3AL 61259 AA AA
Figure 113. crossing, unidir, SNCP, no prot. in NPE, HP
158 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
F
A
E
B
NPE
D
C
188
3AL 61259 AA AA
Figure 114. crossing, unidir, D&C, no prot. in NPE, HP (1)
159 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
F
A
E
B
NPE
D
C
188
3AL 61259 AA AA
Figure 115. crossing, unidir, D&C, no prot. in NPE, HP (2)
160 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
F
A
957.130.872 H
SC.3: NPE
E
B
NPE
D
C
F
A
E
B
188
Figure 116. crossing, bidir, SNCP, no prot. in NPE, HP
3AL 61259 AA AA
NPE
D
C
161 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
F
A
957.130.872 H
SC.3: NPE
E
B
NPE
D
C
F
A
E
B
Figure 117. crossing, bidir, D&C, no prot. in NPE, HP
188
3AL 61259 AA AA
NPE
D
C
162 / 188
9 THE 4–F MS SPRING RM SIDE
9.1 Introduction
This chapter contains:
Glossary
4f MS–Spring
9.1.1 Glossary
– Tail(–end) node: the node that detects a failure or receives an external command from the manager
and then initiates the K1K2 protocol sending a protocol request (a bi–directional failure is detected
by two adjacent nodes, that for this reason are both Tail nodes).
– Head(–end) node: the node that receives a K1K2 protocol request from a Tail node and
acknowledges it (via a protocol reply) to complete the protocol process.
– Served request (trigger): a request for which some consequent action takes place according to the
MS–SPRING rules.
– Pending request (trigger): those triggers that are not served due to the presence of higher priority
triggers. Also the simultaneous presence of the equal priority triggers may lead to a pending
condition.
– 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.
– MS–SPRING request (trigger): any kind of valid input to the MS–SPRING 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 node’s 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 (LW–R): 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 (LW–S): 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Lockout of Protection channels – span (LP–S): command that preventes 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.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 163 / 188
188
9.1.2 4f MS–Spring
9.1.2.1 Introduction

The four fibers MS–Spring is a new type of ring supported by RM.

The ring can be made up of a maximum of 64 ADM’s of type 1664SM. Only STM16 ports can be used to
build the ring. The usage of 1664SM R3.1 inserts constraints on the usage of aggregate (main and spare)
ports for protected and protecting fibers.
For Paths and Trails a new attribute is defined, enabling 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.
Ring traffic maps are fully managed by RM.
The “component” of the ring traffic map related to each path and trail is evaluated and sent to all NEs in
the ring.
In order to avoid misconnections, RM, during the implementation phase, sends the update of the ring traffic
maps before the creation of connections, and viceversa, during the de–implementation 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 AU4s between Service Nodes according to NE implementation.
As a consequence of limitations existing on equipment side:
– add / remove protection is not supported when involving NPE 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 add / remove of legs of broadcast paths is not supported
– the time–slot interchange on protecting resources is not available

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 164 / 188
188
9.1.2.2 Impacted classes
The following classes are modified in order to manage the MS–Spring .

9.1.2.2.1 Path
The following new attribute is added:
– 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 (default)
When crossing 4 Fibers MS–Spring, 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.
as a result, in the segment between service nodes:
– if the path is bidirectional (Figure 118. ), 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 point–to–point (Figure 119. ), 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 120. );
– if a path is broadcast (Figure 121. ), the used resource is:
• protection if the signal flows into the service nodes (B, C) like in a unidirectional
point–to–point path: a unidirectional D&C IC on protection is performed in the primary
node;
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
point–to–point path can become broadcast only if the working resources are used between
service nodes (nodes E, D in Figure 121. ).
• Protecting resources preferred

When crossing a 4 Fibre MS–Spring, the path uses protecting (low priority) resources.
If the routing algorithm must use the working resource in one span of the 4F MS–spring (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 MS–Spring, 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 MS–Spring, if the protected HO path is completely inside a 4f MS–Spring, the allocation
will always fail.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 165 / 188
188
9.1.2.2.2 Trail
The following new information is added:

– Server Ms protection usage profile is added to HO trails (see the description given for paths).

working
protection
A B C
NPE
F E D
G H I
NPE
N M L
Figure 118. bidirectional protected path

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 166 / 188
188
working
protection
SNCP
A B C
NPE
F E D
SNCP
Figure 119. unidirectional protected path (using working resource between nodes E and D)
working
protection
SNCP
A B C
NPE
F E D
SNCP
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 120. unidirectional protected path (using protection resource between nodes E and D)
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 167 / 188
188
working
protection
SNCP

A B C
NPE
F E D
SNCP
Figure 121. broadcast protected path
9.1.2.2.3 Physical Connection
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 or, if, e.g. in the 2f MS–Spring, the LP traffic is not allowed). This
attribute is automatically built in case of usage of the 1664SM where Main and Spare aggregate ports are
clearly defined. For Second generation NEs the information has to be inserted manually by the user during
network construction.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 168 / 188
188
9.1.2.3 New classes
The following new classes (the grayed ones) are inserted in order to manage the MS–SPRING topologies.
4f MS–Spring
path / trail (ET)
Node
AU4
Map
4f MS
Protection Block
end node
AU4 RTM
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 169 / 188
188
9.1.2.3.1 4f MS Protection Block
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 / TSD–IM Front End
Processor and can assume the following values:
• virtual.
The MS–SPRING 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 MS–SPRING et topology is “enabled” inside the NE, i.e. all the relevant objects are created
inside NE but the MS–Spring mechanism is not active; the NE transmits idle code on the K1/K2
channel (see also Transition State)
• active.
The MS–SPRING 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 MS–SPRING 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 extra–traffic) and the MS–Spring mechanism
is active
The Configuration State attribute “active” is consistent with the NE ’status’ if the 4–F 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
east–west 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
1AA 00014 0004 (9007) A4 – ALICE 04.10
sequence y, z, w, where x,y,z,w are the identifiers of the nodes).
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 170 / 188
188
– 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 re–alignment procedure,
either automatic or manual, has failed, normal if the re–alignment 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 MS–Spring
provisioning phase.
– West Span WTR (Wait To Restore time): it contains the value (west side) to provide to the NE during
the MS–Spring provisioning phase.
– East Span WTR (Wait To Restore time): it contains the value (east side) to provide to the NE during
the MS–Spring 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 Ring Active Condition

This attribute indicates the ring command that is currently stored to and served by the NE on the West
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. 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.
– East Ring Active Condition

This attribute indicates the ring command that is currently stored to and served by the NE on the East
side of the node. The same values as described for the West Ring Active Condition are valid
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 171 / 188
188
– West 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:


• Ring forced switch: forced
• Ring manual switch: manual
– East Ring Pending Command

This attribute indicates the ring command that is currently stored to but not served by the NE on its
East side. The same values as foreseen for the West Ring Pending Command are valid
– West Span Active Condition

This attribute indicates the span command that is currently stored to and served by the NE on the
West side of the node. The following values shall apply:
• Span forced switch: forced
• Span manual switch: manual
• Span Lockout of Protection: lockoutProtection
• Span WTR running: wtrRunning
– East Span Active Condition

This attribute indicates the span command that is currently stored to and served by the NE on the
East side of the node. The same values as foreseen for the East span Active Condition are valid.
– West 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:
• Span forced switch: forced
• Span manual switch: manual
– East Span Pending Command

This attribute indicates the span command that is currently stored to but not served by the NE on its
East side. The same values as foreseen for the West Span Pending Command are valid.
– East Lockout Working Ring ( not supported by the current NE version )

This attribute indicates whether a Lockout of Working Channels Ring command is currently stored
to the NE on its East side. It can assume the following values: none, lockoutWorking.
– West Lockout Working Ring ( not supported by the current NE version )

This attribute indicates whether a Lockout of Working Channels Ring command is currently stored
to the NE on its West side. It can assume the following values: none, lockoutWorking.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– East Lockout Working Span ( not supported by the current NE version )

This attribute indicates whether a Lockout of Working Channels Span command is currently stored
to the NE on its East side. It can assume the following values: none, lockoutWorking.
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 172 / 188
188
– West Lockout Working Span ( not supported by the current NE version )
This attribute indicates whether a Lockout of Working Channels Span command is currently stored
to the NE on its West side. It can assume the following values: none, lockoutWorking.
– West Failure of Protocol

This attribute indicates the K1K2 protocol failure detected on the West side of the node. The following
values shall apply:
• no protocol failure detected: none
• default APS code detected: defaultKBytes
• improper APS code detected: improperCode
• node Id mismatch detected: nodeIdMismatch
– East Failure of Protocol

This attribute indicates the K1K2 protocol failure detected on the east side of the node. The same
values as foreseen for the West Spare Failure Condition are valid.
– 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 MS–SPRING is enabled (configured) but not active (protection mechanism not running) at
the node: standby
• the MS–SPRING 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 MS–SPRING 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
– West Protocol Role

channel in order to serve either a local or remote trigger regardiiing its West 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 command–ring or failure/degrade–ring that involves its West
side: tailHeadRing ( interruption RING )
• the node is serving an external command–span or failure/degrade–span that involves its West
side: tailHeadSpan ( interruption SPAN )
• the protection MS on the West side of the node is unavailable or locked out (via LP–S only):
protUnav
• the node is serving an external command–ring or failure/degrade–ring that involves its West
side, the protection MS on the West side is unavailable or locked out: ( ext ) RingProtUnav
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 173 / 188
188
– East Protocol Role
channel in order to serve either a local or remote trigger regarding its 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 command–ring or failure/degrade–ring that involves its East
side: tailHeadRing ( interruption RING )
• the node is serving an external command–span or failure/degrade–span that involves its East
side: tailHeadSpan ( interruption SPAN )
• the protection MS on the East side of the node is unavailable or locked out (via LP–S only):
protUnav
• the node is serving an external command–ring or failure/degrade–ring that involves its East
side, protection MS on the East side is unavailable or locked out: thRingProtUnav
9.1.2.3.2 AU4 map
The AU4 Map is not visible at the user interface; it represents the “piece of row” of the ring traffic map
contained in a path or trail.
It contains the following information:
– AU4 Map identifier;
– et identifier;
– pointer to the related path or trail (belongTrailId);
– target state (allocated, implemented);
– current state (allocated, implemented, partially implemented);
– flow (unidirectional, bidirectional);
– Au4 #; for a STM–16 ring, the following rule is applied:

Au4 # <= 16 for working resources, Au4 # > 16 for protection resources;
– rate (AU–4, concatenated AU–4);
– ring direction: clock wise, counter clock wise;

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 174 / 188
188
9.1.2.3.3 End node
The End node is not visible at the user interface; it represents one end of a Au4 map.

– AU4 MapId;
– node Id;
– role:
(dropInsert, passThrough, drop, insert, pointToMultiP, dropContinueW, dropContinueP, continue,
lastDropContinue, concatenated, firstPointToMultiP, lastPointToMultiP);
– end type (A, Z);
– connected Au4 # (with the same rules described for the same attribute in the AU4 map class);
it is used for time slot interchange only, included the drop & continue on a protection channel.
9.1.2.3.4 AU4 RTM ( Ring Traffic Map )
The AU4 RTM is visible at the user interface; it represents a whole row of the ring traffic map.
– containment information (network Id, subnetwork Id, ET id, node Id, 4FmsProtBlock Id);
– Au4 # (with the same rules described for the same attribute in the AU4 map class);
– Au4 role (working / protection);
– Consistency Status (normal, aligning, not aligned, failed to align).
No identifier is needed (an instance of this class can be identified by nodeId and AU4 #).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 175 / 188
188
9.1.2.4 RM behaviour during 2f/4f MS–SPRING topology Activation
For 4–F MS SPRING the following check has been added :

• the node type must be 1664 SM

• the fiber type must be STM–16
• the number of nodes must be less equal 64
• the involved ports have to be connected in a consistent way in the whole et (main–west to
main–east, spare–west to spare–east).
If one of the above checks fails, the Activation of the MS–SPRING topology fails (the user has to re–build
the et topology in the correct way)
9.1.2.5 RM behavior during 2f/4f MS–SPRING topology implementation
The RM behavior during MS–SPRING topology implementation is distinguished in topology

implementation process behavior and TSD–IM Front End Processor behavior.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 176 / 188
188
9.1.2.6 Topology Implementation
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:
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 TSD–IM 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.
9.1.2.6.1 TSD–IM Front End Processor process
If the submitted request is to change on a MS Protection Block the Configuration State attribute from
“virtual” to “active” and the ring map info to the provided value, the TDS–IM Front End Processor executes
the following steps:
a) it sets the Configuration State and the ring map info to the requested value (active) and the
Consistency Status to “aligning”
b) it applies the consistency to the NE, i.e. it sends to the NE the proper commands in order to achieve
on NE side the ’status’ consistent with the transition “virtual” to “active” of the MS Protection Block
Configuration State. Three consecutive phases are accomplished on the NE (ring provisioning info,
map with topological info and ring activation). The Transition State of the MS Protection Block keeps
the mapping with the final state inside the NE of each phase: supposing that the Transition State
starting value is “idle”, the proper command (establish action on Ring Protection Manager MOC) is
sent in order to achieve the “defined” state. If the first phase is successful, the Transition State is set
to “defined” and the next command is sent (populate ring map action on Ring Coordinator MOC). If
the second phase is successful, the Transition State is set to “populated map” and the last command
is sent (activate action on Ring Coordinator MOC). If also the last phase is successful, the NE ’status’
is consistent with the value “active” of the Configuration State attribute, so the Consistency Status
of the MS Protection Block is changed from “aligning” to “normal”, the Transition State is set
“activated” and a positive response is sent back to the Topology Implementation process.
If one of the three phases fails, the NE ’status’ is not consistent with the value “active” of the
Configuration State attribute, so the Consistency Status of the MS Protection Block is changed from
“aligning” to “failed to align”, a KO response is sent back to the Topology Implementation process
and the Transition State keeps the value corresponding to the state associated to the last successful
phase (in this way, upon reception of the same request from the Topology Implementation process,
the TSD–IM Front End Processor knows the failed phase from which starting to re–execute)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 177 / 188
188
If the submitted request is to change the ring map info only, the TSD–IM Front End Processor executes
the following steps:
a) it sets the ring map info attribute to the requested value and the Consistency Status to “aligning”

b) it applies the consistency to the NE, i.e. it sends to the NE the proper command (populateMap action
on Ring Coordinator MOC) in order to update the topology info contained in both the ring map and
the ring traffic map.
c) if step b ) is ok, the Consistency Status is set “normal” and a positive response is sent back to the
Topology Implementation process otherwise it is set “failed to align” and a ko response is sent back.
The following table shows the possible combined values assumed by the three represented states during
a MS–Spring topology implementation .
Table 15. Transition of the three states during MS–Spring implementation (case virtual –> active)
Configuration State Consistency Status Transition State Description
virtual normal idle Starting condition
active aligning idle Transient condition
defined Transient condition:

establish phase ok
populated map Transient condition:

map populat. phase ok
normal activated Implementation OK:

activate phase also ok
failed to align idle Implementation KO:

establish phase failed
defined Implementation KO:

map popul. phase failed
populated map Implementation KO:

activate phase failed
9.1.2.7 RM behavior during node removal inside a 2f/4f MS–SPRING topology
The remove node functionality, when the node belongs to a MS–Spring topology, updates the maps in the
remaining NEs.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 178 / 188
188
9.1.2.8 RM behavior during 2f/4f MS–SPRING topology removal
The RM behavior during MS–SPRING topology removal is distinguished in topology implementation

process behavior and TSD–IM Front End Processor behavior.
9.1.2.8.1 Topology Implementation process
If the topology to remove is a MS–Spring et, before executing the usual operations, common to each type
of topology, the Topology Implementation process performs the following specific steps:
a) for each node of the et, it submits to the proper TSD–IM Front End Processor (in charge of the node)
the request to change the Configuration State of the MS Protection Block (contained in the node) to
the “virtual” value.
b) if the TSD–IM Front End Processor gives back a positive response for each change request
submitted at the previous step, the topology implementation process performs the further following
steps:
1) for each node contained in the et, it removes the MS Protection Block object.
2) starts the usual deimplement topology needed operations
Otherwise, if at least one negative response is received, the ring topology removal activity requested
by the user fails, i.e. the ring topology working state is set to “failed to remove”.
9.1.2.8.2 TSD–IM Front End Processor process
If the submitted request is to change on a MS Protection Block the Configuration State attribute to “virtual”,
the TDS–IM Front End Processor executes the following steps:
a) it sets the Configuration State to “virtual” and the Consistency Status to “aligning”
b) it applies the consistency to the NE, i.e. it sends to the NE the proper commands in order to achieve
on NE side the ’status’ consistent with the transition of the MS Protection Block Configuration State
to “virtual”. To do this, two consecutive phases are accomplished in the NE (de–activate the
MS–Spring so that MS–Spring mechanism is stopped, the failure condition released inside the ring
but all the provisioned info are kept and then dismissed it so that all the rlevant MOCs are destroyed).
The proper command (de–activate action on the Ring Coordinator MOC) is sent. If successfull, the
Transition State is set “populated map” and the dismiss action on the Ring Coordinator MOC is sent.
If also the second phase is successfull, the Transition State is set “idle”, the NE ’status’ is consistent
with the value “virtual” of the Configuration State attribute, so the Consistency Status of the MS
Protection Block is changed from “aligning” to “normal”.
If one of the two phases fails, the NE ’status’ is not consistent with the value “virtual” of the
Configuration State attribute, so the Consistency Status of the MS Protection Block is changed from
“aligning” to “failed to align”, a ko response is sent back to the Topology Implementation process and
the Transition State keeps the value corresponding to the state associated to the last successfull
phase (in this way, upon reception of the same request from the Topology Implementation process,
the TDS–IM Front End Processor knows the failed phase from which starting to re–execute)
The following table shows the possible combined values assumed by the three represented states during
a MS–Spring topology removal.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 179 / 188
188
Table 16. 0.Transition of the thre states during MS–Spring topology removal
Configuration State Consistency Status Transition State Description

active normal activated Starting condition
virtual aligning activated Transient condition
populated map Transient condition:

de–activate phase ok
normal idle Removal OK:

dismiss phase also ok
failed to align activated Removal KO:

de–activate phase failed
populated map Removal KO:

dismiss phase failed
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 180 / 188
188
9.1.2.9 RM behavior during path or trail implementation
The RM behavior during path/trail implementation is constituted by the behavior of the path/trail
implementation process and the behavior of the TSD–IM Front End Processor.
9.1.2.9.1 Path / trail Implemention
If the transport entity (path/trail) to implement crosses a MS–Spring et topology, the path/trail
Implementation process performs the following further steps, before interacting with the TSD–IM Front
End Processor:
a) it creates, contained in the involved MS–Spring et MOC, the AU4 Maps (more than one, if a drop and
continue on protecton is in the path), filling the pointer to the related path/trail and the map
information; it creates also the related end nodes. The target state is set to implemented, the current
state is set to allocated.
b) before requesting the modification of the Configuration State from “allocated” to “implemented” of
each cross connection belonging to the path/trail, for each node belonging to the et (not only the
nodes involved in the path/trail) it submits to the TSD–IM Front End Processor the request to align
the Au4 RTM ( Ring Traffic Map )
If the TSD–IM Front End Processor gives back a positive response for each change request
submitted at the previous step, the path/trail implementation process starts the usual implement
path/trail needed operations; otherwise the path/trail implementation activity requested by the user
fails, i.e. the path/trail working state is set to “failed to implement”.
c) The current state of the Au4 map is updated after the reception of the last response from T–FEPs;
this state is used in order to propagate the correct configuration state to the path and to upper level
connections in topology:
• the current state is set = target state (i.e. implemented) if all the responses are OK (the
responses are OK also in case of notAligned objects).
• the current state is set = partially implemented if at least one response is KO;
9.1.2.10 TSD–IM Front End Processor
According to the request received by the Path/trail Implementation process, the TSD–IM Front End
Processor performs the following steps:
a) it sets the Consistency Status of the Au4 RTM to the proper value: “notAligned” in case of download
disabled mode, “aligning” if it is allowed the operation towaards the NE.
b) if notAligned, a positive response is sent back to the path/trail implementation process, else it applies
the consistency with the NE, i.e. it sends to the NE the proper commands (compose traffic map or
update squelch table) in order to update the Ring Traffic Map (or the Squelch Table in 2 fiber
MS–Spring) according to the AU4 Map info and related end nodes (e.g., if the ring is a 4f MS–Spring,
starting from the source node, supposing one source node and one end node, and moving according
to the given “ring direction”, all the cross–connections of the starting, crossed and ending nodes are
provided with their type: insert–drop/pass–through/drop&continue....)
c) if step b ) is successfull, the Consistency Status of the involved AU4 RTM is set “normal” and a
positive response is sent back to the path/trail implementation process; otherwise it is set “failed to
align” and a ko response is sent back.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 181 / 188
188
9.1.2.11 RM behavior during path or trail de–implementation
The RM behavior during path/trail de–implementation is distinguished between the behavior of the
path/trail implementation process and the behavior of the TSD–IM Front End Processor.

9.1.2.11.1 Path / trail Implementation process
If the transport entity (path/trail) to de–implement crosses a MS–Spring et topology, after having
successfully requested the modification of the Configuration State from “implemented” to “allocated” of
each cross connection belonging to the path/trail, the path/trail Implementation process performs the
following steps:
a) the state of the Au4 map is set = allocated;
b) for each node belonging to the et (not only the nodes involved in the path/trail) it submits to TSD–IM
Front End Processor the request to align the Au4 RTM.
c) The current state of the Au4 map is updated after the reception of the last response from T–FEPs;
this state is used in order to propagate the correct configuration state to the path and to upper level
connections in topology.
• the current state is set = target state (i.e. allocated) if all responses are OK (the responses are
OK also in case of notAligned objects). As a result, the Au4 map is deleted and the path is set
to allocated;
• the current state is set to partially implemented if at least one response is KO. As a result, this
AU4 map is not deleted from database at this point, in order to take it into account in the
successive calculations of the ring traffic map; the path is set partially implemented.
The general rule is: an AU4 map is deleted when both target state and current state are allocated.
This behavior is necessary, in order to take into account that an action to T–FEP can be lost (e.g. the
T–FEP is down): in this case, no misalignment information can be stored in the AU4 RTM object.
9.1.2.12 TSD–IM Front End Processor process
It is applied the same algorithm as in case of the path/trail implementation.
9.1.2.13 RM behavior during consistency/recovery download
Due to the fact that the consistency is applied at node level and not at ring level, the presence of a failure
inside the ring can lead to “misconnections” while consistency is on–going.
The only way available to the user to avoid “misconnections” is to manually perform for each node inside
the ring the “lockout of protection” command, before applying the Consistency Download activity.
This activity is performed by TSD–IM Front End Processor process.
9.1.2.13.1 TSD–IM Front End Processor
It is applied the same algorithm as in case of the path/trail implementation/deimplementation; the only
difference is that the activity is internal and not triggered by the Path / trail Implementation process.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 182 / 188
188
9.1.2.14 RM behavior during consistency audit
This activity is performed by TSD–IM Front End Processor process.

9.1.2.14.1 TSD–IM Front End Processor

It checks the differences between RM mib and NE, using the read Traffic Map row action defined in
TSD–IM; if there are differences in an Au4, the related Au4 RTM object is set to
notAligned/consistencyMismatch.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 183 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
188
3AL 61259 AA AA
184 / 188
10 DISPLAY OF THE PROTECTION BLOCKS
10.1 Display of the Protection blocks

A view of all the MS Protection Blocks in a MS–SPRing is available in the browser. To display this view,
execute the following procedure:
a) From the browser point with the mouse at the 4–F MS–Spring and open the pop–up menu. Select
item Display all related items...
b) From the selection box select item All Protection blocks in MS Spring 4–F and click on No Filter
button. The Protection block drawing window is displayed. See Figure 123.
Figure 122. Selection box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 185 / 188
188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
Protection blocks
Figure 123. 4–F Protection blocks.
188
3AL 61259 AA AA
186 / 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.3: NPE
Figure 124. Manage switch menu.
The figure which follows show the commands available to manage switches.
188
3AL 61259 AA AA
187 / 188
INDEX
H P

Head(–end) node, 163 Pending request (trigger), 163

protocol message, 163
protocol reply, 163
I protocol request, 163
Intermediate nodes, 163
S
L Served request (trigger), 163
Serving nodes, 163
Lockout of Protection channels – span, 163
Lockout of Working channels – ring (LW–R), 163
Lockout of Working channels – span , 163 T
Tail(–end) node, 163

M
MS–SPRING request (trigger), 163

END OF DOCUMENT
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01 SC.3: NPE
957.130.872 H 3AL 61259 AA AA 188 / 188
188
TABLE OF CONTENTS
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 REGIONAL MANAGER GRAPHICAL USER INTERFACE PRINCIPLES . . . . . . . . . . . . . . . . . . 7

2.1 Generalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.1 Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.2 Location and insertion cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.3 Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.1 Dimensions and layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.2 Client area and Window titles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.3 Window menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.4 Scroll bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.5 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2.6 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2.7 Entry boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.8 Dialogue boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3 GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4 PRELIMINARY OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.1 Logging in to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2 Workspace description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3 Locking the screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.4 Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5 ACCESS TO THE MAIN FUNCTIONALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.1.1 The Tool Subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.1.2 Alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6 VIEWS DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

E.CORRADINI
E.CORRADINI
1AA 00014 0004 (9007) A4 – ALICE 04.10
1354RM REL.5.2B
ED 01 SC.4:GETTING STARTED
957.130.872 H 3AL 61259 AA AA 1 / 58
58
7 SDH NETVIEW : MAP NAVIGATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
8 NAVIGATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

9 ON–LINE DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 2 / 58
58
Figure 1. Mouse configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 2. Mouse pointer representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 3. Example of a window layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 4. Window menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 5. Scroll bar components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 6. Examples of push buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 7. Examples of radio buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 8. Example of Option Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 9. Window view showing the menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 10. Window view with Pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 11. Window view with Cascading menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 12. Unselectable menu items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 13. Highlighted menu item indicating selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 14. Example of a dialogue box having Entry Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 15. Single List box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 16. Multiple List box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 17. Error dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 18. Warning dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 19. Work in progress dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 20. Question dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 21. Information dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 22. Confirmation Dialogue Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 23. Login panel view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 24. The SDH Manager workspace Front Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 25. Locking the screen using a manual lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 26. Screen lock Password: entry box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 27. Logging out using the front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 28. HP–CDE Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 29. 1354RM Tool subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 30. 1354RM main windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 31. OVW Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 32. Root Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 33. Network map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 34. Objects belonging to a subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 35. Objects belonging to a ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 36. Objects belonging to a ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 37. Dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 3 / 58
58
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.4:GETTING STARTED
58
3AL 61259 AA AA
4 / 58
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.
• User Interface Principles
• Windows
• Glossary
• Logging Operation
• Workspace description
• Locking the screen
• Logout
• Access to the Main Functionalities
• View Description
• Map Navigation
• Navigation
• Help System
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 5 / 58
58
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
58
3AL 61259 AA AA
6 / 58
2 REGIONAL MANAGER GRAPHICAL USER INTERFACE PRINCIPLES
2.1 Generalities
The Regional Manager user interface is based on the Hewlett Packard Open View Windows (HP–OVW)
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 window’s 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 7 / 58
58
2.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 text–formatting 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.
2.1.2 Location and insertion cursor
This cursor takes the form of an I–beam pointer (see Figure 2. ). It indicates where the text is going to be
entered. This cursor is frequently met when using Entry boxes (see chapter 2.2.7). The cursor can be
moved horizontally and vertically using the Navigation keys.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 8 / 58
58
2.1.3 Mouse
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.

2.1.3.1 Mouse buttons
There are 3 Mouse buttons. The actions that are undertaken using the different mouse buttons depends
on their configuration. The following figure shows a right handed mouse configuration.
Drag button
Select button
Custom button
Figure 1. Mouse 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 pop–up menus (mouse button 3).
With a left handed mouse configuration, button 3 becomes the select button.
2.1.3.2 Select/Deselect/Drag–and–Drop 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.
– Drag–and–drop 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 9 / 58
58
2.1.3.3 Mouse pointer signification
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.

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 I–beam pointer is usually associated with windows and entry boxes.
They indicate that a written entry can be performed here.
x 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 pro-
gress.
The cross pointer is used to select a window to be printed as part of a screen
hardcopy process.
The 4–directional arrow pointer indicates a move operation or a resizing op-

eration can be undertaken on a window.
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 2. Mouse pointer representations
2.1.3.4 Double clicking
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 (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 symbol’s submap should open.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 10 / 58
58
2.2 Windows
This section defines the attributes of windows and describes their general aspects.
2.2.1 Dimensions and layout
The figure below indicates the standard window layout.
Maximize
Window menu button Window title button
Iconify
button
Menu Bar
Client area
Resize borders
Figure 3. Example of a window layout
2.2.2 Client area and Window titles
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 11 / 58
58
2.2.3 Window menu
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 4. 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
2.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
1AA 00014 0004 (9007) A4 – ALICE 04.10
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,
957.130.872 H 3AL 61259 AA AA 12 / 58
58
2.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.
There are vertical and horizontal scroll bars as shown in the figure below.
Slider
Stepper
arrows
Scroll Region
Figure 5. 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 but-
ton. 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 direc-
1AA 00014 0004 (9007) A4 – ALICE 04.10
tion desired. The contents in the client area are displaced as long as the slider moves.
957.130.872 H 3AL 61259 AA AA 13 / 58
58
2.2.5 Buttons
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.

2.2.5.1 Push buttons
Push buttons are identified by two characteristics:
– 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 6. Examples of push buttons.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 14 / 58
58
2.2.5.2 Radio buttons
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
Figure 7. Examples of radio buttons.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 15 / 58
58
2.2.5.3 Option buttons
When you click on an option button, you open an option menu from which you choose a single item. Option
buttons are used when a list of items are mutually exclusive.

Option button
Figure 8. Example of Option Button
N.B. The example given above enables you to choose the zooming factor for a submap. To open the
option menu, click on the option button with the ”Select” mouse button. Select an item from the
list that opens.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 16 / 58
58
2.2.6 Menus
In this section we describe an important aspect of the user interface. The user constantly has to open win-
dows, 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,
– pop–up menus.
These types of menus are described in detail below. The details concern a view of the menu types on real
windows.
2.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 me-
nus and cascading menus are opened.
Menu Bar
Window title
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 9. Window view showing the menu bar
957.130.872 H 3AL 61259 AA AA 17 / 58
58
2.2.6.2 Pull down menus
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.

Pull–down menu
Selected menu item
Figure 10. Window view with Pull down menu
N.B. A menu option followed by ”...” means that selecting this option opens another view.
For example the Open... or Save As... menu options in the File pull down menu.
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 ”Ctrl+E”
in Figure 10. can be used as a shortcut for accessing the Close option.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 18 / 58
58
2.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.
In Figure 11. the Distribute Maps... > menu option is selected.
2.2.6.4 Pop–up menus
Pop–up menus appear when you click, using the ”Custom” mouse button, in the following cases:
– 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
pop–up menu opens. Select an item from the menu by clicking on it using the ”Custom” mouse but-
tons.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 19 / 58
58
2.2.6.5 Unavailable menu items and Menu item Selection
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.
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.
Selected menu
item ”highlighted”
Figure 13. Highlighted menu item indicating selection.
2.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 corre-
sponding to the mnemonic of the option.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 20 / 58
58
2.2.7 Entry boxes
2.2.7.1 Description and Definition

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.
Title of the window
Label of the Entry box
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.
N.B. 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 21 / 58
58
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 I–beam 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.
2.2.7.2 Syntactic guidelines
This concerns the use of upper case and lower case characters when entering text.
The text entered is re–displayed 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 22 / 58
58
2.2.8 Dialogue boxes
2.2.8.1 Generalities
Dialogue boxes provide an interface between the SDH Manager and the user. They enable to confirm op-
erations 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 de-
scribed previously (scroll bars, push buttons...). The principal dialogue boxes are described below.
2.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.
Item
selected Push
from list. buttons:
actions
on List
List of
existing
Sub-
maps.
Entry Box
Push buttons
Figure 15. Single List box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 23 / 58
58
a) Single column lists.
As the name suggests, they enable you to select elements from a single list. An example is shown
below.

As seen in the figure above, List boxes contain:
• A Title: specifying the context of the List box.

• A List: from which an item or items are selected.
• Options: used to undertake actions on the items in the list. For example, ”Open Submap”.
• Entry boxes: in which you can enter text. For example the Find Submap (press return): entry
box in which you give the name of the submap you are looking for.
• Push buttons: to undertake actions on the elements in the list, to get help (Help push button)
or to close the list box (Close push button).
b) Multiple columns lists.
They display the data in the form of multiple columns. An example is given below.
Figure 16. 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 24 / 58
58
2.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.
The different types are shown in the figures below:
Figure 17. Error dialogue box
These dialogue boxes inform you of an illegal command or action.
Figure 18. Warning dialogue box
These dialogue boxes are displayed to warn you about future events pertaining to the action you have
launched.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 19. Work in progress dialogue box
957.130.872 H 3AL 61259 AA AA 25 / 58
58
These 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 20. Question dialogue box
A question dialogue box requests additional confirmation following a command previously launched. The
Cancel push button cancels the operation.
Figure 21. Information dialogue box
They inform you on the action you have undertaken. In Figure 21. 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 22. Confirmation Dialogue Box

1AA 00014 0004 (9007) A4 – ALICE 04.10
They enable you to confirm or cancel an action previously launched.
957.130.872 H 3AL 61259 AA AA 26 / 58
58
3 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 STM–N 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.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 27 / 58
58
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.

Cross–connect (XC)

Cross–Connects 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.
High Order Matrix:

Defines the ports of an NE handling transmission rates greater than 140 Mbit/s.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 28 / 58
58
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 ITU–T (International Telecommunication
Union).
Kilobits per 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.
Loss Of Signal:
Alarm linked to the physical interfaces, associated with the absence of a received signal.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Loss Of Tributary Signal:

Alarm linked to the PDH physical interface, indicating the loss of a tributary signal.
957.130.872 H 3AL 61259 AA AA 29 / 58
58
Low Order Path Adaptation:
Function of the 21x2Mbit/s, 3x34Mbit/s and the 140 Mbit/s tributary boards that maps (or de–maps) the
tributary signal to (or from) the virtual containers used in the synchronous transport domain.

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 STM–N 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:

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 STM–N signal in case of channel failure or low transmission quality.
Multiplex Section Termination:

Function of the 140 Mbit/s and the STM–1 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.
Network Management Level:

Designates the management functions performed on networks elements assembled in a network.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 30 / 58
58
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 1353SH 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 end–user 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 STM–1 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 STM–1 signal to the
outgoing STM–1 frame or the outgoing high order virtual container.
Severity:
Linked to alarms, severities indicate the magnitude related to the failure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 31 / 58
58
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.

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 STM–1 signal has a transmission rate of 155 Mbit/s while an
STM–16 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 STM–N frame.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 32 / 58
58
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 33 / 58
58
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
58
3AL 61259 AA AA
34 / 58
4 PRELIMINARY OPERATIONS
4.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 23. 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.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 35 / 58
58
4.2 Workspace description
Your workspace is described as the functionalities that appear on your workstation screen after login.
The workspace Front Panel is described below.

WS
Clock activity Text
Padlock Workspaces Editor
Date
Exit Letter
Printer Terminal
Netstation applications
File Regional
Manager Manager
Figure 24. 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 Netstation applications allows to select among the netstation applications.
• 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 four available
workspaces (workspaces One to Four)
• 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 Regional Manager 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
957.130.872 H 3AL 61259 AA AA 36 / 58
58
4.3 Locking the screen
This utility enables you to lock the screen to prevent other users from using your working environment.
Padlock
icon
Figure 25. 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 26. Screen lock Password: entry box
To resume work type in your password in the Password: entry box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 37 / 58
58
4.4 Logging Out
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 27. Logging out using the front panel
A dialogue box opens from which you can confirm or cancel the ”Logout” operation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 38 / 58
58
5 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.
5.1 Introduction
The 1354RM graphical interface is based on:
– HP Common Desktop Environment (HP-CDE)
– HP OpenView Windows (HP-OVw)
– OSF Motif applications (Browser, RM Configuration Tools, Monitor tool, System Management
Functions, etc.).
The HP_CDE Tool panel ( See Figure 28. ) has been customized to contain the 1354RM Logo (right–hand
side).
WS
Clock activity Text
Padlock Workspaces Editor
Date
Exit Letter
Printer Terminal
Netstation applications
File Regional
Manager Manager
Figure 28. HP–CDE Panel
Clicking on the small arrow above the 1354RM logo you can open the Tool Subpanel. ( See Figure 29. )
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 39 / 58
58
5.1.1 The Tool Subpanel
The HP_CDE Tool Subpanel (See Figure 29. ) has been customized to contain the icons that follow (click
on the small arrow above the 1354 RM logo to open the Tool Subpanel )

Figure 29. 1354RM Tool subpanel
– Logo 1354 RM Network Management System. Clicking twice on it, the informa
tion on RM version is displayed.
– TMN OSs This icon, if selected, opens the supervision of the various OSs.
– Administration This icon, if selected, opens the System Management functions ( SMF ).
– Alarms Starts the Alarm surveillance user interface.
– Browser Starts the Generic Browser
– Network View Starts the netview application.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 40 / 58
58
5.1.1.1 TMNOSs
By clicking on the TMNOSs icon opens a window containing all the OSs icons, i.e. all the network SHs and
RMs. 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 pull–down menu bar comprising the following menus:
– File containing the only option ”Close” to close the window
– Actions 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:
• Start/Stop/Stop + Start. This submenu is present both for RM and SH.
The Start option is available if the selected OS is in the Stop state.

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).
• Monitor. This submenu is available both for RM and SH. It opens the
Process Monitor window.
• SMF. This submenu is present both for RM and SH. It permits to launch
the System Management Features application.
• Alarms. This submenu is only available for SH. It permits to launch the AS
application.
• PNM. This submenu is only available for SH. It permits to launch the OVW
application relevant to the selected SH and displayed on the 1354RM
di–splay. This feature is called zoom–in or plug–in.
• Version. This menu is only available for SH. The SW version installed is
indicated.
• SH–P Log. This submenu is only present for RM. It permits to display the
messages relative to the SH application presented on the 1354RM display.
• SH–P Version. This submenu is only available for the 1354RM. It permits
to display the SH release that has been installed.
– Global Actions It permits to launch the entire system actions. It contains the following
sub–menus:
• Network Start. It sequencely starts the network processes.

1AA 00014 0004 (9007) A4 – ALICE 04.10
• Network Stop. It sequencely stops the network processes.
• Check. Its purpose is to refresh the TMN–OSs window.
957.130.872 H 3AL 61259 AA AA 41 / 58
58
5.1.2 Alarm management
From your workspace front panel click on the Alarm icon shown in Figure 29. on page 40.
The Counter summary window is opened from which the operations on alarms can be carried out.

A customized sublist is presented. This sublist contains the following rows:
1) PHYSICAL LINK
2) MS TRAIL
3) HO TRAIL
4) PATH
5) PROCESSING
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).
5.1.2.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 ( PHYSICAL LINK, MS TRAIL, HO TRAIL, PATH, PROCESSING). As an
alternative select the row and issue the Sublist: Open pull–down menu item.
The Alarm sublist is presented.
b) Select the alarm from the sublist and navigate it by selecting the Navigation: AS_EXT_Tool
pull–down 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 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
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 42 / 58
58
6 VIEWS DESCRIPTION
The main 1354RM applications are Netview and Browser: See Figure 30. on page 45
Netview is based on HP–Open View which permits to manage the map and the submap. Moreover it 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:
– Root submap
– Network submap
– Subnetwork submap
– Ring submap
– Node submap
Two additional submaps are utilized when the map is being constructed: i.e.:
– Available EML submap
– Available NEs submap
The Browser application includes:
– a main view which allows to navigate among all the topological and connectivity objects;
– several views denominated:
• Payload configuration of a Physical connection
• HO–TRAIL configuration (LO lc in HOtrail)
• LO Paths in a HO–TRAIL
• Payload Configuration of a SDH port
• MS–SPRING protection block view
• Single MS–SPRING Protection Block
• Path Routing view
• Node view
• Nap view
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 43 / 58
58
– several lists. They are:
• Path List

• Trail List

• NAP List
• CTP List
• CAP List
• Port List
• Performance Measure List
• Alarmed Object List
• Alarm Profile List
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
Setup Trail It is used to create a trail.
Path Create It is used to create a path (end–to–end 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)
Connectivity matrix It is utilized to display the main connectivity objects.
Event logger It allows to display the events.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 44 / 58
58
BROWSER WINDOWS NETVIEW WINDOWS
browser list 1 view 1 root

main netw
subn
ring
................ ................
node
list m view n
EMLs
NEs
MANAGEMENT TOOL WINDOWS
payload config setup trail path create path constraints
PM:measure create PM:measure correlate path/trail PM:measure correlate tp
connectivity matrix Event Logger
Figure 30. 1354RM main windows

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 45 / 58
58
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
58
3AL 61259 AA AA
46 / 58
7 SDH NETVIEW : MAP NAVIGATION
Navigating Between Submaps

You can navigate between submaps of an open map in several ways:

– Explodable Symbol
You can open a submap by double clicking on a symbol
– Submap Navigation Buttons
You can navigate between submaps using the submap navigation tools, located in the Toolbar of
each submap window. The following navigation tools are available (see Figure 31. on page 49):
• Close. To close the current submap.
• Parent. Displays the primary parent of this submap. This is the submap that is defined in the
Submap Description dialog box as the Parent of the current submap.
• Root. Displays the root submap. This submap is at the top of the hierarchy.
• Home. Displays the home submap. The home submap is the first submap that appears when
you open a map
• Panner. Displays the Panner. The panner lets you zoom in on details within a submap window
and pan from area to area in the submap window.
To use the panner:
– Click on the panner icon (lens) or select View: Pan and Zoom.
– In the panner window use button 1 to draw a box around the area to zoom in. Use button
2 to move the box.
– Click All to reset the view to the full submap window.
• Browser. This button is context–sensitive, i.e. it is available if you first select an object from the
map. When clicking this button, the browser application starts from the selected object.
• EML Navigation. You first select a node, then clicking on this icon you can open the 1353SH
Equipment View of that node.
• Path Create. This button is context–sensitive, i.e. it is available if you first select a node from
the map. When clicking this button, the Path Create application starts from the selected node.
• Path Constraints. This button is context–sensitive, i.e. it is available if you first select a
node/et/subnetwork/port/physical connection from the map from the map. When clicking this
button, the Path Constraints application starts and a message asks the user to insert the
trail/path to constraint.
In case the Path Constraints was previously opened, clicking this button the selected object is
automatically added as a constraint.
• Add Leg. This button is context–sensitive, i.e. it is available if you first select a node from the
1AA 00014 0004 (9007) A4 – ALICE 04.10
map. When clicking this button, the Add Leg application starts from the selected node.
957.130.872 H 3AL 61259 AA AA 47 / 58
58
• Payload Configuration This button is context–sensitive, i.e. it is available if you first select a
ring/Physical connection from the map. When clicking this button, the Payload Configuration
application starts from the selected object.

• Setup Trail. This button is context–sensitive, i.e. it is available if you first select a node from

the map. When clicking this button, the Setup Trail application starts from the selected node.
• Path List in Topology. This button is context–sensitive, i.e. it is available if you first select a
topological object from the map. When clicking this button, the Path List application starts,
giving then the paths related to the selected topological object.
• Path List in Physical Connections. This button is context–sensitive, i.e. it is available if you
first select a Physical Connection from the map. When clicking this button, the Path List
application starts, giving then the paths crossing the selected Physical Connection.
• Nap List . This button is context–sensitive, i.e. it is available if you first select a topological
object from the map. When clicking this button, the browser application starts, giving then the
list of the Naps belonging to the selected topological object.
• Ctp List . This button is context–sensitive, i.e. it is available if you first select a topological object
from the map. When clicking this button, the browser application starts, giving then the list of
the Ctps belonging to the selected topological object.
• Alarmed Objects . This button is context–sensitive, i.e. it is available if you first select a
topological object from the map. When clicking this button, the browser application starts, giving
then the list of the alarmed objects belonging to the selected topological object.
• Trail List . This button is context–sensitive, i.e. it is available if you first select a topological
object from the map. When clicking this button, the browser application starts, giving then the
list of the trails belonging to the selected topological object.
• About OVW. Displays the About OpenView Windows dialog box. This dialog box provides
information about the copyright date, session ID, server name, and provides access to
information about registered applications.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 48 / 58
58
CLOSE ROOT PANNER EML
NAVIGATION
GET HOME BROWSER

PARENT PATH LIST
PATH PAYLOAD IN TOPOLOGY PATH LIST IN
CONSTRAINTS CONFIG. PHYSICAL CONNECT
PATH SETUP
CREATE ADD LEG TRAIL
NAP LIST ALARMED

OBJECTS ABOUT OVW
CTP LIST TRAIL LIST
Figure 31. OVW Toolbar
– Define User Options
The following is a list of option you can set up.
• The Home submap is the first submap that appears when you open a map. To define the Home
submap do as follows:
– Open the submap you want to be displayed each time you open the current map.
– Select Map: Submap: Set This Submap as Home.
• The map that OVW first displays when started, is called the user default map. To define the
user default map do as follows:
– Select Map: Maps: Open/ List.
– Highlight a map name.
– Click on Set User Default.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 49 / 58
58
EXAMPLE
An example of submap navigation is shown in the figures that follow.

a) Figure 32. shows the Root submap. The Root submap contains the icon of the network.

Figure 32. Root Map
b) Clicking twice on the network icon, the network map is opened. It contains the subnetwork symbols
along with their physical connections (see examples in Figure 33. on page 51)
c) Clicking twice on the subnetwork icon, the submap of the objects belonging to that subnetwork is
opened (see examples in Figure 34. on page 52 and Figure 37. on page 53)
d) Clicking twice on the icon of the ring, the submap of the objects belonging to that ring is presented
(see examples in Figure 35. on page 53)
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 50 / 58
58
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
Figure 33. Network map
58
3AL 61259 AA AA
51 / 58
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
Figure 34. Objects belonging to a subnetwork
58
3AL 61259 AA AA
52 / 58
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
to a node
957.130.872 H
External connection
Figure 35. Objects belonging to a ring
58
3AL 61259 AA AA
to a
External
connection
subnetwork
53 / 58
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
to a ring
957.130.872 H
External connection
to a subnetwork
External connection
Figure 37. Dialog box.
Figure 36. Objects belonging to a ring
58
3AL 61259 AA AA
54 / 58
8 NAVIGATION
Some applications can be utilized together in the following modes:

– from Netview to Browser

Select an object in the map and enter command Browse:object.
– from Netview to Path Create
Select one node/more nodes or nap and enter command Path Create from toolbar.
– from Netview to Path Constraints
Select a node/physical connection/ lc / ctp / path / trail and enter command Path Constraints
from toolbar.
– from Netview to Payload Configuration
Select a physical connection or a ring and enter command Payload Configuration from toolbar.
– from Netview to Setup Trail
A node can be selected from the map. Enter command Setup Trail
The applications relative to the PM measures and the Event Logger can be obtained again from the
Brow–ser.
– Navigation from Browser to Netview
As regards ”Navigation from Browser to Netview”, the only function available is ”Locate”. It
allows to visualize a ctp, ttp, nap on the map ( at level of node ) or a trail / path , displaying the
route.
– by using Tool Talk
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 ( PHYSICAL LINK, MS TRAIL, HO TRAIL, PATH, PROCESSING). As an
alternative select the row and issue the Sublist: Open pull–down menu item.
The Alarm sublist is presented.
b) Select the alarm from the sublist and navigate it by selecting the Navigation: AS_EXT_Tool
pull–down menu item. A confirmation dialog box appears. Click on OK to confirm.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 55 / 58
58
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 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
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.
capability to receive ToolTalk message from OVw application.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 56 / 58
58
9 ON–LINE DOCUMENTATION
9.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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 57 / 58
58
INDEX
B Pointer, 10

Buttons

Push buttons, 14 N
Radio buttons, 15
Navigation to/from, Alarms, 42
C
P
Cascading menus, 19
Pop–up menus, 19
Pull down menus, 18
L
List dialogue boxes, 23 S

Login, 35
Screen, Lock, 37
Logout, Front panel, 38
SDH Manager, Main functionalities, 39
M
U
Menu bar, 17
Upper case/Lower case characters, 22
Menus
User Interface, Standard elements, 7
Cascading menu, 19
item, 20
Menu bar, 17 W
Mnemonics, 20
Pop–up menu, 19 Windows
Pull down menu, 18 Layout, 11
Mnemonics, 20 Menu, 12
Mouse Scroll bars, 13
Actions, 9, 10 Workspace, Types of, 36
Buttons, 9
END OF DOCUMENT
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 58 / 58
58
TABLE OF CONTENTS
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Document description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4 Interrelationships with 1353SH during Network Construction . . . . . . . . . . . . . . . . . . . . . 14
1.5 System Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2 NETWORK CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1 Network Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 Create a new Map in HP-OV data base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3 Populate the new Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4 Creating the 4–F MS–SPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.4.1 Creating the Nodes and the ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.4.2 Creating the Connections between Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.5 Create Network for D & C in ADMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.6 Creating the Dual Node Interconnection with D & C in 1664SX . . . . . . . . . . . . . . . . . . . . 46
2.6.1 Sequence on SH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.6.2 Sequence on RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.7 Creating the One Node Interconnection with D & C in 1664SX . . . . . . . . . . . . . . . . . . . . . 51
2.7.1 Sequence on SH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.7.2 Sequence on RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.8 Contiguous Concatenated AU4’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.9 Line / Radio System Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.10 Network implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.11 Map Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.12 Payload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.12.1 Configuring the Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.12.2 Payload Configuration monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.12.3 Payload Configuration supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.13 AU4 Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.13.1 AU4 Concatenation SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.13.2 AU4 Concatenation Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.13.3 AU4 Concatenation Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

E.CORRADINI
E.CORRADINI
1AA 00014 0004 (9007) A4 – ALICE 04.10
1354RM REL.5.2B
ED 01 SC.5:OPERATION
957.130.872 H 3AL 61259 AA AA 1 / 334
334
2.14 Setup Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.14.1 Trail remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2.15 Upload NAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

3 TRANSPORT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

3.1 Path Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.2 Path Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.3 Path Allocate,Implement, Commissioning and Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
3.3.1 Path Allocate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
3.3.2 Path Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.3.3 Path Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.3.4 Displaying the path route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
3.4 Path /TrailConstraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.5 Adding a leg to a path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.6 Path in NPE ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
3.7 Drop and Continue path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3.7.1 4–Node Drop and Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3.7.2 D & C path in a 2–Node SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
3.7.3 Path Constraints in a 2–Node SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.7.4 D & C path in a 1–Node Enhanced SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.7.5 D & C path create in a 2–Node SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.7.6 D & C path allocate in a 2–Node SNCP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.8 Add / Remove Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
3.9 OS driven restoration for HO paths & trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.9.1 Create a restoration rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.9.2 Display a restoration rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
3.10 Join/Split Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
3.10.1 Join Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
3.10.2 Split path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
3.11 Join–Split Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
3.11.1 Split a HO–Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
3.11.2 Join two HO–Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
4 PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

4.1 SNCP path layer switch management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
4.2 Multiplex Section Layer switch management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
4.2.1 Automatic Protection Switch in 2–fiber MS–SPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
4.2.2 Squelching in case of isolated nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
4.2.3 MS–SPRING Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
4.2.4 Provisioning of the APS Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
4.2.5 Provisioning of the Service Selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
4.2.6 Commands for the APS Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
4.2.7 Commands for the Service Selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
4.2.8 Reports of the APS Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
4.3 Management of switches at RM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
4.3.1 Display of the Protection blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
4.3.2 4–F NPE RING Switch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
5 NETWORK MODIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
1AA 00014 0004 (9007) A4 – ALICE 04.10
5.1.1 Adding a Network Element in a SCNP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

5.1.2 Removing a Network Element (NE) from a SNCP ring . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
5.1.3 Removing a PDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
957.130.872 H 3AL 61259 AA AA 2 / 334
334
5.2 Network Modification with existing traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
5.2.1 rmList file create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
5.2.2 rmLCmd file play . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
5.3 Add/Remove Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
5.3.1 Removing an SDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

5.3.2 Adding a PDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

5.3.3 Adding an SDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
5.4 Configuration of a Transmux board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
5.4.1 Payload Structure Configuration of a Transmux board . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
5.4.2 Payload Structure Remove of a Transmux board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
6 SPECIAL NETWORK VIEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

6.1 Creating a geographical map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
6.2 Layered Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
6.3 Connectivity Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
6.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
6.3.2 Data Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
7.2 Creating the Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
7.3 Transport object Correlation to the Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
7.4 Tp’s correlation to the Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
7.5 PMTP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
7.5.1 Examples of assignement of the attribute SIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
7.6 Counter Report Profile Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
7.7 Threshold Report Profiles Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
7.8 Report Profile Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
7.9 Measure Activation, Stop and Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
7.9.1 Measure Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
7.9.2 Measure Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
7.9.3 Measure Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
7.10 Threshold Crossing Alarm (TCA) Profile creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
7.11 Threshold Crossing Alarm (TCA) Profile Correlation to the PMTP . . . . . . . . . . . . . . . . 264
7.12 Merging of several Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
7.13 Displaying PM data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
7.14 The pmNE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
7.15 Archive Performance Monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
7.15.1 Archive Performance Monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
7.15.2 Retrieve Performance Monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
7.15.3 Display Performance Monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
7.15.4 Delete Monitored data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
7.16 Archive Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
7.17 Uncorrelate the transport from planned measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
7.18 Uncorrelate the tp from planned measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
7.19 Remove from RM menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
7.20 Uncorrelate the counter/threshold report profile from the measure . . . . . . . . . . . . . . . 281
8 OPERATOR ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
8.1.1 Add Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
1AA 00014 0004 (9007) A4 – ALICE 04.10
8.1.2 Remove Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
9 RESTRICTED OPERATORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

9.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
957.130.872 H 3AL 61259 AA AA 3 / 334
334
9.2 Access of the operator with Initiator restr_pb1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
9.2.1 Browser main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
9.2.2 Browser navigated objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
9.3 Access of the operator with Initiator restr_lo1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

9.3.1 Browser main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

9.3.2 Browser navigated objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
10 EXPORT OF RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

10.1 Global Export of resources at NN startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
10.1.1 NAD global change for the Physical connections terminating to virtual nodes . . . . . . 298
10.1.2 NN assignment of the NAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
10.1.3 NN assignment of the path(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
10.2 Manual export procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
10.2.1 Export of HO and LO link connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
10.2.2 Export of MS trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
10.2.3 Export of HO trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
10.3 Export of resources on ISN interface for 1355VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
10.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
10.3.2 Assignment of the link connection within an RM domain . . . . . . . . . . . . . . . . . . . . . . . . . 332
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 4 / 334
334
FIGURES
Figure 1. Administration icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 2. Startup monitoring window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 3. Process monitoring window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 4. Map pull–down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 5. New map dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 6. Create Network dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 7. Root Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 8. Create Subnetwork dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 9. Network map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 10. Create Ring dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 11. Objects belonging to a subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 12. Construction:Upload EML(s) info:Available EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 13. Uploading EMLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 14. Uploading NEs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 15. Node just created. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 16. Create connection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 17. Connection display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 18. Connection just created. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 19. Create Ring dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 20. 4–F MS–SPRING icon in the Subnetwork map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 21. Construction:Upload EML(s) info:Available EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 22. Uploading EMLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 23. Uploading NEs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 24. NPE Ring submap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 25. Submaps of NPE nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 26. Create Connection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 27. Physical view of the aggregates of 1664SM–NPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 28. Ports belonging to a 1664SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 29. Browse: Object: 4–F MS Spring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 30. Setting Node Position and Node Id. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 31. D & C in ADM subnetwork map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 32. Ring 1 submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 33. Ring 2 submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 34. Ring3 submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 35. Browser: implementation in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 36. Subnetwork and ring submaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 37. Example of dual node interconnection with D & C in 1664SX. . . . . . . . . . . . . . . . . . . . . . . 46
Figure 38. Example of topology with 2 Nodes D&C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 39. Create connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 41. Network submaps of the 3 Meshed ETs for 2 Node D & C . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 42. Example of One Node Interconnection with D & C in 1664SX. . . . . . . . . . . . . . . . . . . . . . 51
Figure 43. Example of topology with 1 Node D&C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 44. Create connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 46. Ring submaps for 1 Node D & C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 47. Subnetwork map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 48. Ring submap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 49. Create Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 50. Example of Path Create command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
957.130.872 H 3AL 61259 AA AA 5 / 334
334
Figure 51. Line System view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 52. Line system details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 53. Implement Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 54. All Protection Blocks in MS–SPRING 4 F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 55. Payload Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 56. Payload Configuration dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 57. Physical connection structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 58. MS trail selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 59. Payload configuration button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 60. Payload Configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 61. Payload selection subwindow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 62. Concatenated payload configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 63. Report Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 64. MS Trail Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 65. AU4 Concatenation Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 66. Concatenation Remove report log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 67. Setup Trail window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 68. Ring Attribute change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 69. Trail Creation report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 70. Paths in trail view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 71. HO–Trail with and without enhanced connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 72. Payload configuration of the trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 73. Trail list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 74. Trail:Actions:Configuration:Deimplement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 75. Trail:Actions:Configuration:Deallocate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 76. Supervision:Upload NAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 77. Topological object: Configuration: Upload NAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 78. NAP upload monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 79. Node: Display: Main related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 80. Selection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 81. NAP list functional button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 82. Filter dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 83. NAP list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 84. Path Creation dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 85. Path List: Actions: SDH/PDH Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 86. Actions: PDH/SDH Alarms: Set Enabling Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 87. Naps view of a bidirectional path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 88. Multi path creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 89. Path In Topology list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 90. Route report example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 91. Actual route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 92. Path Routing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 93. Highlight button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 94. Selection box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 95. Locate display ( unprotected path ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 96. Selection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 97. Locate display ( protected path ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 98. Path Constraints dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 99. CTP as constraint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 100. Use Service Forward/Backward for Dual Node SNCP network . . . . . . . . . . . . . . . . . . . . 106
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 101. Add Leg menu item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Figure 102. Add Leg dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 103. Add Leg (selected node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 104. Add Leg button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
957.130.872 H 3AL 61259 AA AA 6 / 334
334
Figure 105. Routing display of a broadcast path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 106. bidirectional protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 107. unidirectional protected path (using working resource between nodes E and D) . . . . . 111
Figure 108. unidirectional protected path (using protection resource between nodes E and D) . . . 112
Figure 109. broadcast protected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Figure 110. Drop and Continue D/C W INS W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Figure 111. Drop and Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 112. Drop and Continue – 1st failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 113. Drop and Continue – 2nd failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 114. Subnetwork and ring submaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 115. D & C path create. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 116. D & C path allocate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Figure 117. D & C path routing view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 118. Network submaps of the 3 Meshed ETs for 2 Node D & C . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 119. Example Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Figure 120. Path Create dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 121. Locate views on ring 2 submap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Figure 122. Routing view for 2–N D & C path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 123. Status switch subwindows for 2–N D & C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 124. Main route connection view detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 125. CTP name detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 126. Path: Add Protection menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 127. Path: Remove Protection menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 128. Use Service Forward/Backward for Dual Node SNCP network . . . . . . . . . . . . . . . . . . . . 130
Figure 129. Double failure for a SNCP path (w/o enhanced) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 130. Path routing view ( one node D & C ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 131. Enhanced SNCP–one node connection detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 132. Path list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Figure 133. Routing display of an unprotected path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Figure 134. Netview locate (unprotected path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 135. Actions: Add Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 136. Netview locate (protected path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 137. Routing display of a protected path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 138. Path: Remove protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 139. Path locate display: nested topology ( ring ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 140. Routing display: protected path: nested ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 141. Routing display; path protected in its nested topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 142. Restoration:Create Restoration Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 143. Create: Restoration Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 144. Browser: restoration domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 145. Restoration Rule list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 146. Restoration Rule attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 147. Rings to be merged. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 148. Submaps of RING R1 and RING R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 149. Path List containing paths P1 and P2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 150. Locate display of paths P1 and P2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 151. Construction: Create Virtual : Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 152. Virtual Port create dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 153. Construction: Upload EML(s) info...: Available NE PORTs . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 154. Construction: Create: Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 155. Create Connection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Figure 156. Connection between the virtual nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 157. Payload configuration of the virtual physical connection . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 158. Path Create between virtual nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
957.130.872 H 3AL 61259 AA AA 7 / 334
334
Figure 159. Path Create between the two virtual nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 160. P1+PV Join path pull–down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 161. Join path dialog box ( P1+PV=P3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 162. P2+P3 Join path pull–down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Figure 163. Path list after join operation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Figure 164. Locate path P1 on the map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 165. Actions: Manage path: Split path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 166. Split path dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 167. Node selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 168. Manage trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Figure 169. Common node selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 170. Path list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 171. Actions: Manage Trails: Join trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Figure 172. Manage trail: Join trail dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Figure 173. Confirmation dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 174. Trail joining phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 175. Joined trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 176. Path:Manage SNCP menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 177. Connection in topology:Manage SNCP menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 178. Example of display of a B & S connection in topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Figure 179. Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 180. Connection in topology attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 181. HO–Trail with and without enhanced connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 182. Effect of a BRIDGE EAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 183. Effect of a BRIDGE WEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 184. Effect of a SWITCH EAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 185. Effect of a SWITCH WEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 186. :Example of six nodes ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Figure 187. Step 4: Final situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 188. Drop and Continue at the service nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 189. Example of squelching table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 190. MS–Spring: Display All related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 191. Protection blocks in a MS–Spring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Figure 192. Protection block: Manage switch menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Figure 193. Examples of actual position of the switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Figure 194. Protection block: Wait to Restore time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Figure 195. 4–F Protection blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 196. Span Switch pop–up menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Figure 197. Wait to Restore Time set up dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Figure 198. Adding a new Network Element, case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 199. Adding a new Network Element, case 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Figure 200. Reference ring topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 201. View: Report full only selected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 202. .rmList file naming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 203. .rmList file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 204. .rmList file: Create Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 205. Create the Command file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 206. .rmCmd file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 207. Command file: Change Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Figure 208. Change Permissions dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 209. Command file execution dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Figure 210. Command file execution report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Figure 211. Map create dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Figure 212. SDH Network layer configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
957.130.872 H 3AL 61259 AA AA 8 / 334
334
Figure 213. Supervision: Synchronize Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Figure 214. Geogr. map construction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Figure 215. Map: Submap: Describe/Modify. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 216. Adding a graphical background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 217. Submap description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Figure 218. Root geographical map with background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Figure 219. Network submap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Figure 220. Network geographical map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 221. Location submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Figure 222. View: SDH Layer: Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 223. View: SDH Layer: HO–AU4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Figure 224. View: SDH Layer: HO–TU3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Figure 225. View: SDH Layer: LO–TU12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Figure 226. Actions:Get Topologies:all levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 227. Connectivity Inventory : VC4 Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 228. PM functional buttons in the browser window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Figure 229. PM main objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Figure 230. Measure Creation dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Figure 231. PM domain related items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Figure 232. Measure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Figure 233. Measure: Actions pull–down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Figure 234. Transport correlation to a measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Figure 235. Performance Monitoring: Correlate to Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Figure 236. TPs correlated to measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 237. Measure selection dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 238. PMTP Show / Set Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Figure 239. Side of the pmctps in a b&s connection ( signal from NE–A to NE–B ) . . . . . . . . . . . . . 249
Figure 240. Side of the pmctps in a b&s connection ( signal from NE–B to NE–A ) . . . . . . . . . . . . . 249
Figure 241. Side of the ctp/nap for a unidirectional connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Figure 242. Counter Report Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Figure 243. Counter Report profile list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Figure 244. Counter report profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 245. Example of generated counter report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Figure 246. Create: Threshold Report dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Figure 247. Threshold Report Profile list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Figure 248. Measure correlation pop–up menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Figure 249. Correlate report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Figure 250. TCA Profile creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Figure 251. Measure merging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 252. RM db Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Figure 253. Report Request Control Transport selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Figure 254. Graphical Counters Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Figure 255. PM graphical counter report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 256. PM Counter Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Figure 257. TP selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Figure 258. pmNE Show/Set attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Figure 259. Archive data functional buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Figure 260. Archive report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Figure 261. Retrieve confirmation box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Figure 262. Displayed archived data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 263. Object containment tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Figure 264. SMF first level window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Figure 265. Operator Administration feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Figure 266. Operator definition objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
957.130.872 H 3AL 61259 AA AA 9 / 334
334
Figure 267. Browse the virtual connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Figure 268. NAD global change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Figure 269. Change NAD: 1354NN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Figure 270. NAD: Change for NAP(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Figure 271. Network:Display:Main Related Items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Figure 272. Node:Display Main Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Figure 273. Selection of NAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Figure 274. Filter options: rate and idle indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Figure 275. NAP List:NAD:Change of the selected Naps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Figure 276. NAD attribute display in the NAP list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Figure 277. Path list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Figure 278. Naps View: NAD change of the NAPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Figure 279. Node list: display main related items...of a virtual node. . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Figure 280. Selection of paths terminated to a node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Figure 281. List of paths terminated to a node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Figure 282. Export of the real NAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Figure 283. Path NAD change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Figure 284. NN assignment of the path(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Figure 285. Virtual Node:display:main related items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Figure 286. Filter settings:SDH and Assigned. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Figure 287. Filtered ( SDH and Assigned ) port list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Figure 288. Port:Actions:Display;Main related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Figure 289. Browser:Network,Virtual node, SDH port, Physical Connection. . . . . . . . . . . . . . . . . . . . 316
Figure 290. Physical Connection;Display:All related items.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Figure 291. Selection box:Link Connections selected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Figure 292. Link Connection list:Actions:Select All. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Figure 293. All Link Connections: Actions: NAD: Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Figure 294. Link Connection list: NAD=1354NN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Figure 295. Physical Connection: Display All Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Figure 296. Browser: navigated objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Figure 297. MS trail: NAD: Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Figure 298. MS trail: NAD change verify. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figure 299. HO trail: Actions: NAD: Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Figure 300. HO trail: NAD change verify. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
TABLES
Table 1. VC4 squelching table for node A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Table 2. LVC squelching table for node A (no entries) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Table 3. VC4 squelching table for node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Table 4. LVC squelching table for node B (no entries) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Table 5. VC4 squelching table for node C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Table 6. LVC squelching table for node C (no entries) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Table 7. VC4 squelching table for node D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Table 8. VC4 squelching table for node E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Table 9. LVC squelching table for node E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Table 10. VC4 squelching table for node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Table 11. LVC squelching table for node F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Table 12. VC4 squelching table for node G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Table 13. LVC squelching table for node G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Table 14. Commands and their priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Table 15. Reports of the APS Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 10 / 334
334
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:
– 1353SH Operator’s Handbook
– Regional Manager Introduction Manual
– Regional Manager Getting started Manual
1.3 Document description
– MAP CREATE
• Network Configuration
• Create a New Map
• Populate the New Map
• Create the 4–F MS–SPRING
• Create the D&C network with ADMs
• Create the Dual Node D&C in 1664SX
• Create the One Node D&C in 1664SX
• AU4C Topology
• Line/Radio System Creation
– NETWORK IMPLEMENTATION
• Network Implementation
– MAP MANAGEMENT
• Map Management
– CONFIGURATION
1AA 00014 0004 (9007) A4 – ALICE 04.10
• Payload Configuration
• AU4C Payload configuration
957.130.872 H 3AL 61259 AA AA 11 / 334
334
• Setup Trail
• Upload NAPs

– TRANSPORT MANAGEMENT

• Path Provisioning
• Path Create
• Path Allocate
• Path/Trail Constraints
• Add/Leg
• Path in NPE Ring
• Path in D&C network
• Add/Remove Protection
• Restoration for HO paths & trail
• Joint–Split Path
• Joint–Split Trail
– PROTECTION MANAGEMENT
• SNCP path switch management
• 2–F MS–SPRING
• Management of switches at RM interface
– NETWORK MODIFICATIONS
• Add/Remove a Network Element
• Network Modification with existing traffic
• Add/Remove Tributary Board
• Configuration of a Transmux board
– NETWORK VIEWS
• Geographical Map
• Layered Map
• Connectivity Inventory
– PERFORMANCE MONITORING
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
Performance Monitoring
• Create Measure
957.130.872 H 3AL 61259 AA AA 12 / 334
334
• Transport Correlation to Measure
• Tp’s 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
– USER ADMINISTRATION
• Operator Administration
– RESTRICTED OPERATORS
• Restricted Operators Configuration
• Path builder
• Look only
– EXPORT PROCEDURES
• Export for QNN
• Manual Export to NN Procedure
• Export on ISN Interface for CNM
The paragraphs which follow briefly describe the Interrelationships with 1353SH during Network
Construction and System startup.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 13 / 334
334
1.4 Interrelationships with 1353SH during Network Construction
This paragraph summarizes the macroactivities to be executed at SH and RM side during Network
Construction. The detailed description of the operations to be carried out at SH side is contained in the

1353SH Operator’s Handbook, while the paragraphs which follow describe the operations at RM side.

The macroactivities to be executed at SH and RM side are:
– On 1353SH: Create Map
– On 1353SH: Create NE Directory: Create NE. The NE which has been just created appears
brown–colored in the map window
– On 1353SH: Select the NE and then NE: NE Address and OS Address.
– On 1353SH: 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 1353SH: Select Administration: SMF: System Management: Process Monitoring.
– On 1353SH: 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
957.130.872 H 3AL 61259 AA AA 14 / 334
334
1.5 System Startup
a) Execute a login by entering username and password.

b) Select the Administration ( SMF ) icon from the vertical palette: the System Management Features
(SMF) window opens.
Administration icon
Figure 1. Administration icon
c) Select the option System Start/Stop and click on button OK. The system Start/Stop submenu opens.
d) Select the option Start System. A dialog window opens; click on Start button and confirm. A question
box arises: ” Do you want to start countdown?”:
1) If you click on Yes a 60 sec countdown starts including the ”Abort” button to interrupt the startup.
2) If you click on No the startup procedure begins immediately and an additional window
summarizes the main steps:
– ” Starting db instance... ”
– ” Starting nml agents... ”
– ” Starting nml control... ”
– ” 1354RM Subsystem start procedure terminated with success.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 15 / 334
334
Figure 2. Startup monitoring window.
As an alternative:
1) Select Process Monitor Control and click on button OK; the Process Control window opens.
2) Select the Actions:Startup: Database pull–down menu item. Wait until the Database becomes
ON (green colored and ON textstring )
3) Select the Actions:Startup: System pull–down menu item. Wait until the System becomes ON
(green colored and ON textstring )
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 3. Process monitoring window.
957.130.872 H 3AL 61259 AA AA 16 / 334
334
2 NETWORK CONFIGURATION
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 HP–OV and RM–MIB data bases.
The macro–activities are:
– Create a new map;
– Populate the new map;
– Implement the network.
During network construction, the map is automatically checked in order to verify if some errors has been
encountered.
For 4–F MS SPRING the following check has been added :
• the node type must be 1664 SM
• the fiber type must be STM–16
• the number of nodes must be less equal 64
• the involved ports have to be connected in a consistent way in the whole et (main–west to
main–east, spare–west to spare–east).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 17 / 334
334
2.2 Create a new Map in HP-OV data base
a) Start the Netview application by selecting the Netview icon from the vertical palette.

b) In the Root window select Map:Maps:New. A new dialog box appears and the operator has to specify

the following information:
Figure 4. Map pull–down menu.
• Map name
• Layout:None.
• Compound Status:Propagate Most Critical.
Select the application Map Management and click on Configure for This Map... button. The configuration
window is displayed.
Configure For This Map...
Displays a Configuration dialog box for the application. The Configuration dialog box contains
configuration settings that are specific to that application.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 18 / 334
334
The following configuration settings are available:
– Type of SDH network synchronization enabled for this map . Three pop–up options are selectable:
• Unset. If this option is selected the operator will not be able to perform any operations of
alignment of the local (WS) OVW data base to the SNML_IM data base.
• Synchronize Complete Map (Map and Alarm Synchronization) If this option is selected the
operator will be able to perform operations of alignment of the local (WS) OVW data base to
the SNML_IM data base.
• Synchronize Only Alarm on Map .( DEFAULT) If this option is selected, the operator will be
able to perform operations of alarm alignment of the local (WS) OVW data base to the SNML_IM
data base.
– SDH network synchronization by site for this map, (DEFAULT=FALSE) if true, means that the
alignment will be executed geographically. If false will be executed logically. This field is effective only
if SDH map and alarm synchronization is enabled. Note that on geographical map only view
operation can be performed.
– SDH synchronize ports for physical maps (DEFAULT=TRUE) means alignment of the local OVW
data to SNML_IM data for the data relevant to the ports.
– SDH set attribute in creation enabled (DEFAULT=FALSE) means that the application will open the
View/Set attributes for each object added. (Not used)
– SDH delete operation enabled on implemented object (DEFAULT=FALSE), if true means that it is
possible to delete an object implemented. Deletion is only possible in OVwDb.
– SDH Show uselabel on Layered map (DEFAULT=FALSE). If set to Enabled, in the layered maps the
user label is displayed with the payload structure, otherwise only the payload is displayed.
– Enable Synchronization log (DEFAULT=TRUE). If set to Enabled, the Synchronization log is

displayed after each synchronization operation.
• Select the application Map Management and click on Configure for this Map: a dialog box
opens. Select button SDH Synchronization enabled for this Map = TRUE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 19 / 334
334
Figure 5. New map dialog box.
c) Select Verify and then press OK.
d) Press OK again from the New Map dialog box. The new Map is created. A dialog box asks if you want
to open the new map. By clicking on YES the new map is opened.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 20 / 334
334
2.3 Populate the new Map
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, rings, nodes, ports and connections).
The operator can populate the map either manually creating all objects or getting an already created map
from distributed archives.
2.3.1 Populate the Map in a manual mode
The following steps have to be executed:
2.3.1.1 Creating the Network
a) Create the Network object using the command Construction: Create:Network.
b) In the Create dialog box enter the Network name and click on Create button. See Figure 6. The
Network icon appears in the New Object Holding Area. Drag ( holding the middle mouse button) the
icon into the window. Double click on the Network icon to open the Network map.
Figure 6. Create Network dialog box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 21 / 334
334
Figure 7. Root Map
2.3.1.1.1 Creating the Subnetwork
a) The subnetwork objects are created in the Network submap using the command Construction:
Create:Subnetwork.
b) In the Create:Subnetwork dialog box ( see Figure 8. ) 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 9. Double click on the Subnetwork icon to open
the Subnetwork submap.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 22 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 9. Network map
Figure 8. Create Subnetwork dialog box.
334
3AL 61259 AA AA
23 / 334
2.3.1.1.2 Creating the Ring (ET)
a) The ring (Elementary Topology) objects are created in a Subnetwork submap using the command
Construction:Create:Ring. The Create Ring dialog box is presented. See Figure 10.

Enter the following values:

• Ring name
• ET Type:
– SNCP–U Subnetwork Connection Protection–Unidirectional
– 2–F MS–SPRING Multiplex Section Shared Protection
– Meshed open ring
– 4–F MS–SPRING 4–F Transoceanic MS–SPRING.
• STM Type ( STM1, STM 4, STM 16, STM 64 )
• Fiber No. ( 2 / 4 )
Figure 10. Create Ring dialog box.
b) Click on Create button. The Ring icon appears in the New Object Holding Area
c) Drag the icon to the center of the window. Double click on the Ring icon to open the Ring submap.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 24 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 11. Objects belonging to a subnetwork
334
3AL 61259 AA AA
25 / 334
2.3.1.1.3 Creating the Network Elements and the ports
A network element can be inserted either in the Subnetwork submap or in the Ring submap.

a) Using the menu Construction:Upload EML(s) info:Available EML(s), a submap is opened. It does not

belong to the topological structure. It includes all managed EML(s), which have been defined in the
current installation.
Figure 12. Construction:Upload EML(s) info:Available EMLs

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 13. Uploading EMLs.
957.130.872 H 3AL 61259 AA AA 26 / 334
334
b) Select the EML containing the relevant NEs and execute:Construction:Upload EML(s)
info...:Available NEs in an EML. An EML submap containing all the NEs available in that EML is
generated.
Figure 14. Uploading NEs.
c) Select the relevant NE(s) with single or multiple selection and execute the command
Construction:Upload EML(s) info...:Available NE ports. The NE ports are loaded inside a new NE
submap.
Note that the node map is created but is not automatically opened.
d) The uploaded NEs can be moved from the ”Available” maps ( EML data ) to the topological maps.
Select the NE (left click) and holding the mouse button move to the proper submap working area,
then release the mouse button.
– Alternatively this operation is done by selecting the NE and issuing with Edit:Cut:From this submap.
Subsequently enter Edit:Paste into the proper window. The pasted objects appear in the New Object
Holding Area and the operator may drag them to the window work area.
– the NE is pasted to the map and its related node is created in the data base.
• For QB3* NEs the icon of the node is colored in brown, i.e. the node is created and its
1AA 00014 0004 (9007) A4 – ALICE 04.10
Implementation state is defined. See Figure 15.
957.130.872 H 3AL 61259 AA AA 27 / 334
334
• For TSD–IM NEs the icon of the node is colored in green, i.e. the node is created and its
operational state is enabled. See Figure 15.

QB3* NODE
TSD–IM NODE
Figure 15. Node just created.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 28 / 334
334
2.3.1.1.4 Creating the Connections
a) Select View: Overlay Submap: off for all submaps, in order to display more submaps at the same
time.
b) Open the submap of the nodes to be connected. See Figure 16.
c) Select a couple of ports to be connected (use the Control button of the keyboard to select the second
port), then execute Construction: Create:Connection (alternatively press F12). In the Create
Connection dialog box ( see Figure 16. ) enter the connection name and click on Create button. The
connection is hence created and is displayed in the parent submap(s). See Figure 17. on page 30.
Figure 16. Create connection dialog box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 29 / 334
334
Figure 17. Connection display.
• 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 connection is not visible in the Node submap which now contains only the ports not
connected. See Figure 18.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 30 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
d)
01
957.130.872 H
SC.5:OPERATION
Create all the remaining connections as per above point c )
Figure 18. Connection just created.
334
3AL 61259 AA AA
31 / 334
2.4 Creating the 4–F MS–SPRING
Construction:Create:Ring. The Create Ring dialog box is presented. See Figure 19. herebelow.

Figure 19. Create Ring dialog box.
b) In the Create Ring dialog box enter: Ring name, ET Type=4–F MS Spring, STM Type=STM–16, Fiber
No.= 4 , Global Configuration=True and then click on Create button. The Ring icon appears in the
New Object Holding Area.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 32 / 334
334
c) Drag the icon to the center of the window. See Figure 20. on page 33. Double click on the Ring icon
to open the Ring submap.
Figure 20. 4–F MS–SPRING icon in the Subnetwork map.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 33 / 334
334
2.4.1 Creating the Nodes and the ports
Only the network element 1664SM can be inserted in the 4–F MS–Spring Ring submap.

a) Using the menu Construction:Upload EML(s) info:Available EML(s), a submap is opened. It does not

belong to the topological structure. It includes all managed EML(s), which have been defined in the
current installation.
Figure 21. Construction:Upload EML(s) info:Available EMLs

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 22. Uploading EMLs.
957.130.872 H 3AL 61259 AA AA 34 / 334
334
b) Select the EML containing the relevant NEs and execute:Construction:Upload EML(s)
generated.
Figure 23. Uploading NEs.
c) Select the relevant NE(s) with single or multiple selection and execute the command
submap.
Note that the node map is created but is not automatically opened.
d) The uploaded NEs can be moved from the ”Available” maps ( EML data ) to the topological maps.
– This operation is done by selecting the NE and issuing with Edit:Cut:From this submap.
Subsequently enter Edit:Paste into the proper window. The pasted objects appear in the New Object
Holding Area and the operator may drag them to the window work area. See Figure 24. on page 36.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 35 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 24. NPE Ring submap.
334
3AL 61259 AA AA
36 / 334
2.4.2 Creating the Connections between Nodes
a) Open the submap of the nodes to be connected. See Figure 25.

Figure 25. Submaps of NPE nodes.
b) Select a couple of ports to be connected and click on F12. The Create connection dialog box is
presented.
c) Enter the connection name and click on Create button.
Figure 26. Create Connection dialog box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 37 / 334
334
TX
RX
SLOT 17 SLOT 19
AGGR. WEST 1 AGGR. WEST 2
WORKING PROTECTION
SLOT 18 SLOT 20
AGGR. EAST 1 AGGR. EAST 2
WORKING PROTECTION
Figure 27. Physical view of the aggregates of 1664SM–NPE.
N.B. The 1644SM network element, when inserted in a NPE ring is equipped with 4 STM–16
aggregate boards, as shown in Figure 27.
N.B. West 1 and East 1 aggregate ports support the working capacity, West 2 and East 2 aggregate
ports support the protection capacity. In 1354RM node map West 2 and East 2 aggregate ports
icons are marked by a “ S “. See Figure 28.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 38 / 334
334
WORKING
PROTECTION
(MAIN)
(SPARE)
WORKING
(MAIN)
PROTECTION
(SPARE)
Figure 28. Ports belonging to a 1664SM
d) 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. To do this start the browser on the 4–F MS Spring.
Select the ring icon from the map and issue Browse: Object(s) pull–down menu item. The Browser
start on the selected object. See Figure 29.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 29. Browse: Object: 4–F MS Spring.
957.130.872 H 3AL 61259 AA AA 39 / 334
334
e) Select the nodes, one at a time and issue Show/Set Attributes. In the Show/Set Attributes dialog box
enter the values of Node Position and Node Id accordingly. See Figure 30. herebelow.

SET NODE POSITION
SET NODE ID
VALUES PRESENT AT
EML/NE LAYER
Figure 30. Setting Node Position and Node Id.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 40 / 334
334
2.5 Create Network for D & C in ADMs
SEQUENCE
a) Create three rings ( R1, R2 and R3 ) as per Figure 31.

Figure 31. D & C in ADM subnetwork map

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 41 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
b)
01
957.130.872 H
SC.5:OPERATION
Create all connections as in Figure 32. thru Figure 34.
Figure 33. Ring 2 submap

Figure 32. Ring 1 submap
334
3AL 61259 AA AA
42 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 34. Ring3 submap
334
3AL 61259 AA AA
43 / 334
c) Implement the network by issuing the command Supervision: Implement Object. From the browser
you can monitor the implementation in progress.

Figure 35. Browser: implementation in progress
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 44 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
d)
01
957.130.872 H
SC.5:OPERATION
Figure 36. Subnetwork and ring submaps.
334
3AL 61259 AA AA
Subnetwork and ring submaps after implementation are shown in Figure 36.
45 / 334
2.6 Creating the Dual Node Interconnection with D & C in 1664SX
SCOPE

The scope of this procedure is to create the topological objects needed to manage the Dual Node

Interconnection with D & C in 1664SX.
Figure 37. shows an example of dual node interconnection with D & C in 1664SX. The two physical rings
are represented in the 1354 RM by meshed rings, in particular the two nodes interconnecting the SNCP
rings are grouped in a meshed ET.
ET–1 and ET–3 contain only ADM nodes, ET–2 contains the two cross connect equipments.
2–N D&C
ET–3
ET–1
tpZ
tpA
tpZA tpAZ
tpZA tpAZ
tpA tpZ
SIDE A ET–2 SIDE B
Figure 37. Example of dual node interconnection with D & C in 1664SX.
ALLOWED RATES Allowed rates, due to hardware limitations are STM–1 and STM–16.
ADVANTAGES
• the connection between rings is optimized
• no limitations on the no. of rings connectable on both sides: the only limitation is constituted by
the maximum capacity (in terms of ports) of the cross connect equipment.
• Assuming that no traffic is terminated to cross connect equipment and the total traffic flows
through ET–2, i.e. through the cross connect squipment, the total traffic terminated to SIDE A
(see Figure 37. above) should be equal to he total traffic terminated to SIDE B.
• Althogh no limitations exist on the number of rings, it is assumed that the total no. of physical
rings on SIDE A = total no. of physical rings on SIDE B.
• Improved reliability of the connections from SIDE A to SIDE B

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 46 / 334
334
2.6.1 Sequence on SH
a) TBD
b) TBD
For each Cross connect equipment all physical ports associated to the TPs involved in the D & C
scheme must be housed in the same subrack.
The correct connection scheme can be verified at RM side by checking the tp attributes (port
name and payload position) by issuing Show/Set Attributes for the involved tp. The port name
contains the subrack name.
2.6.2 Sequence on RM
a) Create the Network and the Subnetwork.
Construction:Create:Ring.
b) In the Create Ring dialog box enter: Ring name, ET Type=Meshed, STM Type=STM–16 or STM–1,
Fiber No.= 2 , Global Configuration=False and then click on Create button. The Ring icon appears
in the New Object Holding Area.
c) Drag the icon to the center of the window.
d) Execute above points b ) and c ) for the 3 rings, as shown in Figure 38.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 38. Example of topology with 2 Nodes D&C
957.130.872 H 3AL 61259 AA AA 47 / 334
334
e) Double click on the Ring icon to open the Ring submap.
f) Using the menu Construction:Upload EML(s) info:Available EML(s).

g) Select the EML containing the relevant NEs and execute:Construction:Upload EML(s)

generated.
h) Select the relevant NE(s) with single or multiple selection and execute the command
submap.
i) The uploaded NEs can be moved from the ”Available” maps ( EML data ) to the topological maps.
Subsequently enter Edit:Paste into the proper window, according to the scheme described under
SCOPE. The pasted objects appear in the New Object Holding Area and the operator may drag them
to the window work area.
j) Open the submap of the nodes to be connected and select a couple of ports to be connected and
click on F12. The Create connection dialog box is presented.
Figure 39. Create connection.
k) Enter the connection name and click on Create button.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 48 / 334
334
object connected at the other end plus the connection name. See Figure 40.
connected.
l) Create all the remaining connections as per above point j )
m ) Implement the network.
Figure 41. shows the details of the three rings which constitute this small sample network.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 49 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
ET–2
957.130.872 H
SC.5:OPERATION
ET–3
ET–1
334
3AL 61259 AA AA
Figure 41. Network submaps of the 3 Meshed ETs for 2 Node D & C
50 / 334
2.7 Creating the One Node Interconnection with D & C in 1664SX
ET2
tpA tpZ
ET1
ET3
tpA tpZ
SIDE A SIDE B
ENHANCED SNCP
Figure 42. Example of One Node Interconnection with D & C in 1664SX.
SCOPE
The scope of this procedure is to create the topological objects needed to manage the Single Node
Interconnection with D & C in 1664SX.
Figure 37. shows an example of single node interconnection with D & C in 1664SX. The two physical rings
are represented in the 1354 RM by meshed rings, in particular the node interconnecting the SNCP rings
is contained in a meshed ET’s .
ET–1 and ET–3 contain only ADM nodes, ET–2 contains the cross connect equipment.
ALLOWED RATES Allowed rates, due to hardware limitations are STM–1 and STM–16.
ADVANTAGES
• the connection between rings is optimized
• no limitations on the no. of rings connectable on both sides: the only limitation is constituted by
the maximum capacity (in terms of ports) of the cross connect equipment.
• Assuming that no traffic is terminated to cross connect equipment and the total traffic flows
through ET–2, i.e. through the cross connect squipment, the total traffic terminated to SIDE A
(see Figure 42. above) should be equal to he total traffic terminated to SIDE B.
1AA 00014 0004 (9007) A4 – ALICE 04.10
• Althogh no limitations exist on the number of rings, it is assumed that the total no. of physical
rings on SIDE A = total no. of physical rings on SIDE B.
957.130.872 H 3AL 61259 AA AA 51 / 334
334
2.7.1 Sequence on SH
a) tbd

b) tbd

For the Cross connect equipment all physical ports associated to the TPs involved in the D & C
scheme must be housed in the same subrack.
The correct connection scheme can be verified at RM side by checking the tp attributes (port
name and payload position) by issuing Show/Set Attributes for the involved tp. The port name
contains the subrack name.
2.7.2 Sequence on RM
a) Create the Network and the Subnetwork.
b) The ring (Elementary Topology) objects are created in a Subnetwork submap using the command
Construction:Create:Ring.
c) In the Create Ring dialog box enter: Ring name, ET Type=Meshed, STM Type=STM–16 or STM–1,
Fiber No.= 2 , Global Configuration=False and then click on Create button. The Ring icon appears
in the New Object Holding Area.
d) Drag the icon to the center of the window.
e) Execute above points b ) to d ) for the 3 rings, as shown in Figure 43.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 43. Example of topology with 1 Node D&C
957.130.872 H 3AL 61259 AA AA 52 / 334
334
f) Double click on the Ring icon to open the Ring submap.
g) Using the menu Construction:Upload EML(s) info:Available EML(s).

h) Select the EML containing the relevant NEs and execute:Construction:Upload EML(s)
generated.
i) Select the relevant NE(s) with single or multiple selection and execute the command
submap.
j) The uploaded NEs can be moved from the ”Available” maps ( EML data ) to the topological maps.
Subsequently enter Edit:Paste into the proper window, according to the scheme described under
SCOPE. The pasted objects appear in the New Object Holding Area and the operator may drag them
to the window work area.
k) Open the submap of the nodes to be connected and select a couple of ports to be connected and
click on F12. The Create connection dialog box is presented.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 53 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
l)
01
957.130.872 H
SC.5:OPERATION
Enter the connection name and click on Create button.
Figure 44. Create connection.
334
3AL 61259 AA AA
54 / 334
object connected at the other end plus the connection name. See Figure 40.
connected.
m ) Create all the remaining connections as per above point j )
shows the details of the three rings which constitute this small sample network.
ET–1
ET–2
ET–3
Figure 46. Ring submaps for 1 Node D & C.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 55 / 334
334
2.8 Contiguous Concatenated AU4’s
– The user constructs the network inserting Virtual NE’s or reusing the existing Virtual NE’s in order
to describe the Physical Connections leaving the network managed by RM and supporting the

AU4–nC.

Figure 47. shows the Subnetwork map, which includes the two virtual network elements to terminate the
concatenated path.
Figure 48. shows the Ring submap. Notice that the payload structue must be executed on all relevant MS
Trails.
Figure 47. Subnetwork map
Figure 48. Ring submap.
The Create Connection command is executed by selecting the terminating port on the virtual network
element and the terminating port of the node to connect.
N.B. When designing the network which will convey concatenated traffic, it is suggested to verify the
resources needed:
• the Network Elements along the path must support the concatenation feature
• the STM–N physical connections along the path must support the target rate
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 56 / 334
334
Figure 49. Create Connection
The Path Create command is executed by selecting first the terminating virtual network elements. See
Figure 50. on page 57
Figure 50. Example of Path Create command

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 57 / 334
334
2.9 Line / Radio System Creation
a) Create, and implement the connection which physically contains Line/Radio Systems.

b) Create a Subnetwork to contain line/radio systems.

c) Create a meshed ET to contain the two Line Systems included in the Physical connection.
d) Execute Construction: Upload: available EMLs... for the EML which contains Line/Radio System
NEs. (emlfox)
e) Execute Construction: Upload: available NEs... for that EML, select the two line systems and issue
Edit: Cut from this Submap, then Edit: Paste to the meshed dedicated ET.
f) Execute Construction: Upload: available EMLs... for the virtual EML which contains the virtual nodes
to be connected to the Line Systems.
g) Execute Construction: Upload: available NEs... for this EML, select the virtual nodes, cut them and
paste them to the meshed dedicated ET.
NOTE
The name of the Virtual nodes should be related to the name of the physical connection (only for easier
understanding)
h) Create all the connections with Construction: Create: Connection. In the Line/Radio System detail
make use of the port called ”GEN” to create the connection towards the other line/radio system.
In the Virtual Network Element detail connect one STM–1 port.
i) Execute Supervision: Implement of the dedicated Subnetwork.
j) Select the first Physical connection and execute Construction: Link to a Topology: Add. A dialog box
is displayed informing: ” Select the elementary topology ( ET ) to be related to the physical connection
and press OK when done ”
k) Select the meshed ring ET and press OK.

The involved physical connection is marked in the map by a link symbol. This symbol displays the
alarm information received by the line/radio systems. The same information is present in the meshed
dedicated ring window.
NOTE
You can remove the link symbol by means of the command Construction: Link to a Topology: Remove.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 58 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 51. Line System view
Figure 52. Line system details
334
3AL 61259 AA AA
59 / 334
2.10 Network implementation
– 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 MS–Spring 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:
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 TSD–IM 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.
a) To execute the network implementation select the Network/Subnetwork/Ring icon in the

Root/Network/Subnetwork window and issue the command Supervision: Implement.
Figure 53. Implement Network

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 60 / 334
334
N.B. In case of NPE MS–SPRING the operator can excute the following checks:
1) From the Subnetwork map point with the mouse at the NPE ring and issue the pop–up menu
Main Items: All Protection Blocks in MS–SPRING 4 F. The relevant graphical window is
displayed, including all protection blocks.

Figure 54. All Protection Blocks in MS–SPRING 4 F
2) From 1353 SH equipment view select menu MS–Spring: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)
3) From 1354RM 4 F–MS 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 SH interface = VALUE at RM interface + 1
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 61 / 334
334
2.11 Map Management
A Network map is a graphical view of a managed network.

There are two different types (the type has to be specified upon creating the map):

Logical representation provides a network view partitioned in subnetwork, ET and nodes. It
reflects the SNML DB organization and is created by means of the
Network Construction Process .
Geographical representation provides a network view partitioned in terms of sites, NEs and inter/
intra sites connections.
– Map: Redo: Store. This command allows to store the commands required to create all topological
objects contained in the map or submap on both ovwdb and mibdb. It is possible to store the
map/submap without connections. See detailled description in Section Graphical Interface.
– Map: Redo: Execute. This command allows to execute all the commands previously stored by issuing
the menu Map: Redo: Store. See detailled description in Section Graphical Interface.
– Supervision: Placement: Store. This command allows to store in MIB data base the coordinates of
the topological objects, for the entire map, for the current submap or for the current submap including
the related child submaps.
– Supervision: Placement: Retrieve: Map This command allows to retrieve from MIB data base the
coordinates of all topological objects, for the entire map.
– Supervision: Placement: Retrieve: Not Placed This command allows to retrieve from MIB data base
the coordinates of all topological objects actually displayed in the New Object Holding Area. This
could apply for a user working in Read–Only modality.
– Map Distribution. It includes:
• Store map image. Stores the current map in the central DB as a map–image. When a map is
being stored, the administrator can specify the list of users (user name list) who are enabled
to load the map. It is also possible to send a mail to the users of the list.
• List map images. Lists all the map–image saved in the central Map DB;
1AA 00014 0004 (9007) A4 – ALICE 04.10
• Remove map image. Removes a map–image from the central Map DB. It is also possible to
send a mail to the users of the list.
957.130.872 H 3AL 61259 AA AA 62 / 334
334
• Get map images. Retrieves all objects from an existing map–image in order to populate the
current map.
• Lock map image. Locks a map–image in order to prevent other users from accessing it while
the administrator is working on it. This operation also permits to send a mail to the users of the
list.
• Unlock map. Release a map–image that has been previously locked. This operation also
permits to send a mail to the users of the list.
For more detailed information refer to Section 5, Graphical Interface. In particular see paragraph 3.6.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 63 / 334
334
2.12 Payload Configuration
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:
– Ring
– 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.12.1 Configuring the Payload
The payload configuration procedure consists in:
a) FROM NETVIEW
1) Select the object to configure in the relevant Netview submap.
2) Select the command: Tools: Modify Payload or click on the relevant tool button. The Payload
Configuration window is presented.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 55. Payload Configuration window
957.130.872 H 3AL 61259 AA AA 64 / 334
334
b) FROM BROWSER
1) Select the object from the Browser window and launch the Configure Payload application by
selecting the appropriate Tool button.
If the object to be payloaded is a ring or a physical connection, the virtual container fields are shown
on the Payload Configuration window. The operator can write the new configuration into these fields
or he can choose it using the selection box on the right of the VC fields (Dictionary). Enter the
configuration and click on OK.
Figure 56. Payload Configuration dictionaries
If the object to be payloaded is an HO trail or an HO–LC, 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 65 / 334
334
2.12.2 Payload Configuration monitoring
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”.
NOTE
To execute a Payload Configuration on a connection inside a ring, it is required to change the

globalConfiguration attribute of the ring to which belongs the connection from ”true” to ”false”.To do this,
execute Show/Set Attributes on the involved ring. See Figure 68. on page 75
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 66 / 334
334
2.12.3 Payload Configuration supervision
When the payload configuration is successfully completed, the user can supervise it in the following ways:
a) From the map select the Physical Connection and use the pop–up menu Payload Configuration. The
relevant drawing window is opened; the Payload Configuration is represented graphically.
East Aggr Port structure
routing display
West Aggr ms trail HO trail LO link connections
Physical Connection HO link connection LO structure paths in trail
Paths in physical connection
Figure 57. Physical connection structure
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
c) From the browser or from the Physical Connection drawing window you can open the graphical
window on the SDH Port, which displays the payload configuration supported by the port.
957.130.872 H 3AL 61259 AA AA 67 / 334
334
2.13 AU4 Concatenation
2.13.1 AU4 Concatenation SETUP

a) From the browser select the physical connection ( see Figure 58. ) and issue Display: Related Items:
the MS trail to configure and click on Payload Configuration button. See Figure 59. The Payload
Configuration window is presented. See Figure 60.
Figure 58. MS trail selection.
PAYLOAD CONFIGURATION
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 59. Payload configuration button.
957.130.872 H 3AL 61259 AA AA 68 / 334
334
b) The actual payload structure is displayed in the bottom section of the window.
PAYLOAD
STRUCTURE
first AU4
Figure 60. Payload Configuration window.
c) Click on the AU4 which will be the first AU4 of the concatenated stream. A subwindow is displayed
( see Figure 61. on page 70), which allows to select the payload structure. If the operator selects
AU4–4C and presses OK, the concatenated configuration is set up in the Payload Configuration
window. See Figure 62.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 69 / 334
334
Figure 61. Payload selection subwindow.
SETUP BUTTON
MS–TRAIL
CONCATENATED
PAYLOAD
CONFIGURATION
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 62. Concatenated payload configuration.
957.130.872 H 3AL 61259 AA AA 70 / 334
334
d) Click on SETUP button to confirm. The configuration is sent to the Network Elements and a Report
Log is displayed. See below Figure 63.
Figure 63. Report Log
2.13.2 AU4 Concatenation Display
a) Select the relevant Physical Connection and issue Display: Related Items: MS Trail Structure. The
graphical window is displayed in Figure 64. herebelow.
CONCATENATED
AU4–4C
MS–Trail
Figure 64. MS Trail Structure

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 71 / 334
334
2.13.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 60.

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 65. on
page 72 ), 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 65. AU4 Concatenation Remove
d) Click on SETUP button to confirm. The configuration is sent to the Network Elements and a Report
Log is displayed. See below Figure 66.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 66. Concatenation Remove report log.
957.130.872 H 3AL 61259 AA AA 72 / 334
334
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 ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 73 / 334
334
2.14 Setup Trail
A HO–Trail can be created only between nodes external to the NPE MS–Spring.

The Trail Setup function is used to create, allocate, implement and configure an HO–Trail within the SDH
Network. A HO–Trail is a transport connection between HO–TTPs ( HO–CAPs) related to SDH ports. A
HO Trail provides LO resources ( LO–LCs) to carry LO traffic (i.e. LO paths).
a) Select the Trail Termination points to be created on the map and then the Pull–down Supervision:Trail
Setup menu.
The Setup Trail dialog box is presented; it already contains the two selected nodes.
Figure 67. Setup Trail window
b) As an alternative, from the Browser select the HO–CTPs that will support the HO–Trail termination
HO–TTPs and then launch the Setup Trail application by selecting the relevant tool button.
c) The Setup Trail dialog box is presented. It already contains the selected objects.
d) If one or more end–nodes / ctps are in a globally configured ring issue a Show/Set Attributes of the
ring in order to modify the global configuration to False. Select Set, then Apply.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 74 / 334
334
Figure 68. Ring Attribute change
e) In the Setup Trail dialog box enter the Trail name (user label ), the number of trails (only if you have
selected nodes) and select the trail configuration. Click on OK. The Creation Report is presented as
in Figure 69. and the Paths in trail view opens ( see Figure 70. )
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 69. Trail Creation report.
957.130.872 H 3AL 61259 AA AA 75 / 334
334
Figure 70. Paths in trail view.
Note that the number of trails can be specified only for trails between nodes.
The User Label can be:
– not specified it is created according to Rec. M1400.

– specified if you create more trails an ordinal number is added to the User Label.
– Protection type. You can select:
• Not protected
• SNCP protected
• D&C protected
– Setup rule:
• automatic. The trail is allocated and automatically implemented.

1AA 00014 0004 (9007) A4 – ALICE 04.10
• user. The Operator must allocate and then implement the trail in a manual mode.
957.130.872 H 3AL 61259 AA AA 76 / 334
334
N.B. 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. See Figure 71.
SPARE
LO–LCs
LO–CTPs
LO–CTPs
MAIN
SPARE
LO–LCs
LO–CTPs LO–CTPs
MAIN

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 77 / 334
334
2.14.1 Trail remove
A trail can be removed only if it is not crossed by any path. In addition, the trail must be configured at higher
order ( VC–4 ); so it can be deimplemented, deallocated and finally removed.

SEQUENCE
a) Select the trail from the trail list or from a drawing window ( e.g. Paths in Trail, Physical Connection
structure, ..) and issue the command Modify Payload. The payload configuration window is
displayed, already containing in the drop area the selected trail.
Setup button
AU4 configuration
Figure 72. Payload configuration of the trail.
b) Select the configuration at higher order AU4, as in Figure 72. and click on Setup button. Wait...
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 78 / 334
334
c) In the trail list the operator can verify that the payload configuration has been successfully changed
to higher order VC4. See Figure 73.
configuration=AU4
Figure 73. Trail list.
d) Select the trail and issue the command Actions:Configuration:Deimplement from the pull–down
menu bar. The trail configuration state changes to Deimplemented.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 74. Trail:Actions:Configuration:Deimplement.
957.130.872 H 3AL 61259 AA AA 79 / 334
334
e) Select the trail and issue the command Actions:Configuration:Deallocate from the pull–down menu
bar. The trail configuration state changes to Deallocated. ( See Figure 75. )

Figure 75. Trail:Actions:Configuration:Deallocate.
f) Select the trail and issue the command Actions:Remove: Remove from MIB from the pull–down
menu bar. The trail is removed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 80 / 334
334
2.15 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 VC–12, or VC–3, or VC–4.
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.
The following sequences show examples of upload NAPs.
2.15.1 Upload NAPs from Netview
SEQUENCE
a) From Netview map select a topological object and issue the command Supervision: Upload NAPs
from the pull–down menu bar. A dialog box alerts that the action has been correctly started.
Figure 76. Supervision:Upload NAPs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 81 / 334
334
2.15.1.1 Upload NAPs from Browser
SEQUENCE

a) From the browser window point with the mouse at the topological object whose NAPs are to be

uploaded and open the pop–up menu. Select menu item Configuration: Upload NAPs. See
Figure 77. A dialog box alerts that the action has been correctly started.
Figure 77. Topological object: Configuration: Upload NAPs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 82 / 334
334
2.15.1.2 NAP upload monitoring
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 78.
Working state=
uploading
Figure 78. NAP upload monitoring.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 83 / 334
334
2.15.1.3 Verify the Upload of NAPs
a) Verify from the browser

1) From the browser point the mouse at the topological object to verify and open the pop–up menu.

Select menu option Display: Main related items...
2) From the selection dialog box of Figure 80. on page 85 click on option NAPs and click on No
Filter. The NAP list is displayed. See Figure 83. on page 86
Figure 79. Node: Display: Main related items...

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 84 / 334
334
Figure 80. Selection dialog box.
b) Verify from Netview
1) Select from the suitable submap the topological object to verify and click on the functional button
NAP list. See Figure 81. The filter dialog box is presented (see Figure 82. on page 86) Click
on Apply. The NAP list is displayed as in Figure 83.
Nap list
Figure 81. NAP list functional button.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 85 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 83. NAP list.
Figure 82. Filter dialog box.
334
3AL 61259 AA AA
86 / 334
3 TRANSPORT MANAGEMENT

– Path Provisioning and path visualization

– Path Constraints
– OS driven restoration
– Join/Split trail
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
– Path Allocate, Deallocate
– Path Implement, Deimplement
– Path Commission, Decommission
– Setup path constraints
You can then display the path route using the SDH netview or browser application.
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
957.130.872 H 3AL 61259 AA AA 87 / 334
334
3.2 Path Create
3.2.1 Path Create by using the Browser

The Path Create dialog box is opened by selecting the Path Creation tool button.

Figure 84. Path Creation dialog box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 88 / 334
334
You can enter the following selections:
– userlabel
– type (UNIDIR/BROADCAST/BIDIR)
– rate (2Mb/34Mb/140Mb/45Mb/ AU4–4C / AU4–16C / AU4–64C ) . Only the concatenation rate

AU4–4C is supported in Rel. 5.2 B.

– protection (Not protected/In Rings/SNCP/D&C SNCP)
– allocation rule (user/automatic)
– allocation constraints (not alarmed resources/no restriction)
– Propagation Rule (when defined/when allocated/when implemented/when commissioned)
– implementation rule (automatic/user)
– automatic Monitoring (false/true)
– MS Protection Usage Profile (for 4–F MSSpring only). This attribute can allocate the path on the
“protection” or “working” capacity
– Q3 PDH Alarm Enabling Rule ( On Implementation/On Commissioning/Manual ). For TSD–IM
equipments.
– Q3 SDH Alarm Enabling Rule ( On Implementation/On Commissioning/Manual ) . For TSD–IM
equipments. ( in particular SSF alarm on boundary CTP )
N.B. For QB3* equipment the user can enable the UPA alarm by issuing the command Alarm
Enabling: LOP, EXBER, UPA command on the selected CAP. See Section Maintenance for
details.
The system provides defaults values for all attributes except for the userLabel.
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. See Figure 85.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 85. Path List: Actions: SDH/PDH Alarms.
957.130.872 H 3AL 61259 AA AA 89 / 334
334
In addition, after path creation, from the Path List the user can modify the PDH/SDH alarm enabling rule
by selecting the menu Actions: SDH/PDH Alarms: Set enabling rule, as in the case of path creation.
A dialog box is presented, which allows the enabling rule selection by means of a dictionary. See

Figure 86.

CLICK HERE
Figure 86. Actions: PDH/SDH Alarms: Set Enabling Rule
Using the browser application:
a) Select the Network.
b) Open the Network pop–up menu and select Display: Related items.
c) In the selection box select the option All Nodes and click on Apply.
The Nodes belonging to the selected Network are displayed in the node list window.
d) Select the first node involved in the path and execute Actions: Display: Related items: NAPs.
The Nap list is presented.
e) Select the NAP and click on the Path Creation tool button.
f) Repeat steps d) and e) for the other NAPs.
g) Enter the correct values of the attributes.
h) Click on the Create Path button. A dialog box informs: ’ Starting path creation’
If the path is created the browser window of path and used naps is automatically shown; starting from this
window is it possible to perform all actions on path (eg. allocate, implement, ...). In case of Multiple path
creation (see next paragraph) the list of created paths is automatically shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 90 / 334
334
Figure 87. Naps view of a bidirectional path
3.2.1.1 Path Create by using NETVIEW Browse: Nodes
a) Select the relevant nodes from the map.
b) Select menu Path: Create. The Path Create dialog box is open. It contains the already selected
nodes.
c) Click on the Path Creation button. A dialog box informs: ”Starting Path Creation”. The system
chooses the first free NAP from the selected nodes.
A message will inform whether the operation was successful or not.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 91 / 334
334
3.2.1.2 Multipath Create
If the Operator selects the Multipath Create button, a dialog box is displayed. The following values must
be specified:

Figure 88. 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 92 / 334
334
3.2.1.3 Path Create by using NETVIEW Browse: Nap(s)
a) Select the involved nodes from the map and enter Browse:Nap(s):Idle 2Mb/ Idle 34Mb/ Idle140Mb
/ filtered.
The NAP lists of both originating and terminating nodes are displayed.
b) From the NAP list of the originating node select the NAP and press tool button Create Path . The Path
Create dialog box opens, it contains the first selected NAP.
c) From the NAP list of the terminating node select the relevant NAP and press the tool button Create
Path. The selected NAP is added to the NAP list of the Path Create dialog box.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 93 / 334
334
3.3 Path Allocate,Implement, Commissioning and Display
This paragraph describes the commands used to modify path configuration state and to display the path.

3.3.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 89. Path In Topology list
b) From the list select the path to allocate and select the Actions: Configuration: Allocate pull–down
menu.
A warning box alerts: ”Action correctly started...” .
The Path working state changes from allocating to normal at the end of the allocation.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 94 / 334
334
3.3.2 Path Implement
a) From the Path List select the path and the Actions: Configuration: Implement pull–down menu item.
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.3.3 Path Commissioning
a) From the Path List select the path and the Actions: Configuration: Commission pull–down menu item.
When the path is in this state no other operations are possible except for path de–commissioning and
performance monitoring and TCAs enabling/disabling. (Threshold crossing).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 95 / 334
334
3.3.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.3.4.1 Path route from Path List
From the Path List you can display the path route window by selecting the Show the Path Route icon.
From the Routing Display window you can display the Route Report by selecting View: Report: Route
full....
Figure 90. Route report example

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 96 / 334
334
3.3.4.2 Path Routing view
This view displays the complete path route including the main resources dedicated to the selected path.
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 90.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 97 / 334
334
3.3.4.3 Main Route
The Main route graphical representation comprises (in the area relevant to the first column):

– on the upper left–hand 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 right–hand 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 Main The switch is set at ”Main”

– S Spare The switch is set at ”Spare”
– C 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”.
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. 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 91. are given two
examples:
MAIN
M M M M
M M
MAIN
SPARE
SPARE
Figure 91. Actual route

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 98 / 334
334
Naps view
Figure 92. 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 .
Clicking on ’Nap view’ button inside the icon bar (see Figure 92. ) it is possible to open the view to display
all path’s terminations (see Figure 87. ).
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
For a path crossing a NPE Ring, the user can verify the connections on the traffic map.
957.130.872 H 3AL 61259 AA AA 99 / 334
334
3.3.4.4 Path route on SDH netview
The scope of this procedure is to display the path/trail route in the Netview maps. The Highlite 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
a) From the path list select the path to display and click on Highlight button.
Highlight button
Figure 93. Highlight button.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 100 / 334
334
1) If the transport is not protected the dialog box of Figure 94. is presented. The following options
are available:
• Main to display the main route ( square flag )

• Show Payload on Physical Connection ( AU4#, TUG3#,TUG2#,TU12#)
• Show end points ( small blue window icon)
a) Select the options (multiple selections are allowed) and click on Apply button. The path
is highlighted in the netview maps. See an example in Figure 95.
Figure 94. Selection box.
Figure 95. Locate display ( unprotected path ).

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 101 / 334
334
2) If the transport is protected the dialog box of Figure 96. is presented. The following options are
available:
• Main to display the main route ( square flag )

• Spare to display the spare route ( triangular flag )
• Service to display the service spare route, for D & C paths only ( triangular flag )
• Show Payload on Physical Connection ( AU4#, TUG3#,TUG2#,TU12#)
• Show end points ( small blue window icon)
Figure 96. Selection dialog box.
a) Select the options (multiple selections are allowed) and click on Apply button. The path
is highlighted in the netview maps. See an example in Figure 97.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 102 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 97. Locate display ( protected path )
334
3AL 61259 AA AA
103 / 334
3.4 Path /TrailConstraints
This procedure allows to set–up constraints on a path or trail, i.e. to get/exclude the use of certain
resources for a path or trail.

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.
In order to create a new constraint, select the path from Path List and click on the Path Constraints tool
button.
The Path Constraints dialog box is opened. Two possibilities are available:
Path/Trail drop area
Constraint drop area
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 98. Path Constraints dialog box
957.130.872 H 3AL 61259 AA AA 104 / 334
334
1) From Browser select the object to utilize as a constraint. The objects available are:
– topological objects: node, ring, subnetwork

– physical connection
– ctp
– routing link
– lc
– path
– trail
2) From the map (Netview) create the constraint by selecting the object to utilize as a constraint
and the Path: Constraint pull–down menu .
In this manner the object is added in the constraint list.
After having added the constraint/constraints, for each constraint the selection is done between Use
Main and Use Spare for an unprotected path.
If a protected path is involved selection concerns:
– 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
– Use Main as A. This constraint can be applied only to a CTP, used as constraint to a unidirectional
or broadcast path. See Figure 99.
NAP
source
CTP CTP CTP CTP CTP
A Z A Z A Z
Figure 99. 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 99.
– Use Main and Spare as A, if the main and spare route are using the same CTP as A termination.
– Use Service Forwards

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Use Service Backwards
957.130.872 H 3AL 61259 AA AA 105 / 334
334
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 100. herebelow.
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 100. herebelow.
FORWARD
BACKWARD
THIS PHYSCON IS USED THIS PHYSCON IS USED

AS CONSTRAINT: AS CONSTRAINT:
USE SERVICE FORWARD USE SERVICE BACKWARD
Figure 100. Use Service Forward/Backward for Dual Node SNCP network
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 106 / 334
334
3.5 Adding a leg to a path
a) From the Path List select the path (monodirectional/broadcast)

b) Enter the command Add: Leg either by selecting the relevant tool button or by using the menu
Actions: Boadcast Path Modify: Add Leg . See Figure 101. The Add Leg dialog box opens. The path
icon is contained in the path drop area. See Figure 102.
c) Select the node from the node list or the NAPfrom the nap list and enter the command Add: Leg either
by selecting the relevant tool button or by using the menu Actions: Broadcast Path Modify: Add Leg
as shown in Figure 103. The selected node now appears in the Leg drop area of the Add Leg dialog
box.
d) Click on button Add Leg. See Figure 104. The leg is allocated and implemented.
e) Figure 105. shows an example of routing display of a broadcast path.
Add Leg
Figure 101. Add Leg menu item.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 107 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
Leg drop area
Path drop area
SC.5:OPERATION
Figure 102. Add Leg dialog box.
Figure 103. Add Leg (selected node)
334
3AL 61259 AA AA
108 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Add Leg
957.130.872 H
SC.5:OPERATION
Figure 104. Add Leg button.
Figure 105. Routing display of a broadcast path.
334
3AL 61259 AA AA
109 / 334
3.6 Path in NPE ring
For a path crossing a NPE ring the following attribute has been added:

– 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 (default)
When crossing 4 Fibers MS–Spring, 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.
as a result, in the segment between service nodes:
– if the path is bidirectional (Figure 106. ), 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 point–to–point (Figure 107. ), 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);
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 108. );
– if a path is broadcast (Figure 109. ), the used resource is:
• protection if the signal flows into the service nodes (B, C) like in a unidirectional
point–to–point path: a unidirectional D&C IC on protection is performed in the primary
node;
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
point–to–point path can become broadcast only if the working resources are used between
service nodes (nodes E, D in Figure 109. ).
• Protecting resources preferred

When crossing a 4 Fibre MS–Spring, the path uses protecting (low priority) resources.
If the routing algorithm must use the working resource in one span of the 4F MS–spring (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 MS–Spring, 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 MS–Spring, if the protected HO path is completely inside a 4f MS–Spring, the allocation
will always fail.
N.B. The procedure used to create a path crossing a NPE Ring is the same as described at
1AA 00014 0004 (9007) A4 – ALICE 04.10
paragraph 3.2 at page 58 .
957.130.872 H 3AL 61259 AA AA 110 / 334
334
working
protection
A B C
NPE
F E D
G H I
NPE
N M L
Figure 106. bidirectional protected path
working
protection
SNCP
A B C
NPE
F E D
SNCP
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 107. unidirectional protected path (using working resource between nodes E and D)
957.130.872 H 3AL 61259 AA AA 111 / 334
334
working
protection

SNCP

A B C
NPE
F E D
SNCP
Figure 108. unidirectional protected path (using protection resource between nodes E and D)
working
protection
SNCP
A B C
NPE
F E D
SNCP
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 109. broadcast protected path
957.130.872 H 3AL 61259 AA AA 112 / 334
334
3.7 Drop and Continue path
The main topics described in this paragraph are:

4–Node Drop and Continue

D & C path in a 2–Node SNCP network
Path Constraints in a 2–Node SNCP network
D & C path in a 1–Node Enhanced SNCP network
3.7.1 4–Node Drop and Continue
(see Figure 110. on page 114, Figure 111. on page 115, Figure 112. on page 116, Figure 113. on page
116.)
Drop and Continue is a way of protecting a path crossing a number of sub–networks, e.g., rings.
The sub–networks 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 AU–4.
The Drop and Continue feature improves traffic availability as compared with the simple ”end–to–end
SNCP/I”. More subnetworks are connected the further is availability increased.
The Drop and Continue features simultaneously realizes the following on one node:
• unidirectional pass–through
• protected drop
• insertion in the opposite direction with respect tothe passthrough direction.
The configurations achievable are:
• D/C–W INS–W
• D/C–E INS–W
• D/C–E INS–E
• D/C–W INS–E
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 (INS–E or INS–W) indicates the insert side.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The ”Unidirectional pass–through” is always in the direction opposite to that of the ”insert” side (e.g., when
”INS E” the pass–through is from East to West).
957.130.872 H 3AL 61259 AA AA 113 / 334
334
For further information refer to Figure 110. on page 114 which shows the D/C–W INS–W configuration.

WEST AGGREGATES EAST
Rx Tx
Tx Rx
TRIBUTARY
Tx Rx
Figure 110. Drop and Continue D/C W INS W
The ”Drop and Continue” featuring two connected rings (with dual connection) is indicated in
Figure 111. on page 115.
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 112. on page116 ), the link direction
is: 1 , 5 , 4 , 3 , 6 , 7, 8.
Pass–through 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 113. on page 116) the selected
direction on the link is : 1 , 5 , 4 , 10 , 9 , 8.
The operative switch is on node 8 and the previous pass through between nodes 4 and 3 is no more used.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 114 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
2
01
W
W
W
INS
D/CW
D/CW
6
3
957.130.872 H
INSW
INSW
W
INS
TRIB
SC.5:OPERATION
E
E
8
1
Figure 111. Drop and Continue

W
W
E
INS
D/CE
334
D/CE
3AL 61259 AA AA
4
10
INSE
INSE
E
INS
TRIB
E
E
9
5
115 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
2
2
7
7
SC.5:OPERATION
6
3
6
3
8
1
1
8
4
10
10
Figure 112. Drop and Continue – 1st failure
Figure 113. Drop and Continue – 2nd failure

9
9
5
5
334
3AL 61259 AA AA
116 / 334
3.7.1.1 Path create in D & C network with ADMs (4–node D & C network)
a) With reference to the network shown in Figure 114. , select nodes 13 and 17 and issue Tools: Create
Path.
Figure 114. Subnetwork and ring submaps.
b) In the path create dialog box of Figure 115. select protection = D & C SNCP. Click on Create button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 117 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
c)
d)
01
957.130.872 H
SC.5:OPERATION
Allocate the path, as per Figure 116.
The path is created and its NAP view is displayed.
Figure 115. D & C path create.
334
3AL 61259 AA AA
118 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
e)
01
957.130.872 H
SC.5:OPERATION
Figure 116. D & C path allocate.
334
3AL 61259 AA AA
Click on Routing view button. The path routimg view is displayed. See Figure 117.
119 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Active=Main
Figure 117. D & C path routing view.
334
3AL 61259 AA AA
D & C connInTopol
Service connection
120 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
ET–2
957.130.872 H
SC.5:OPERATION
3.7.2 D & C path in a 2–Node SNCP network
ET–3
ET–1
334
3AL 61259 AA AA
Figure 118. Network submaps of the 3 Meshed ETs for 2 Node D & C
121 / 334
2–N D&C

ET–3
ET–1
tpZ
tpA
tpAZ tpZA
tpAZ tpZA
tpA tpZ
SIDE A ET–2 SIDE B
Figure 119. Example Network.
The path create procedure described at para 3.7.2.1 herebelow refers to the example network of
Figure 118. and Figure 119.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 122 / 334
334
3.7.2.1 D & C path create in a 2–Node SNCP network
The Path Create procedure is the same as described at paragraph 3.2 on page 88, with the following
exceptions:
– Rate=140 Mb,
– Protection type=D & C SNCP. ( see Figure 120. )

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 120. Path Create dialog box.
957.130.872 H 3AL 61259 AA AA 123 / 334
334
3.7.2.2 D & C path allocate in a 2–Node SNCP network
Upon path allocation, the system evaluates, as in case of basic D & C ( see Figure 122. )
– main route

– spare route

Figure 121. on page 124 shows the locate view of the D & C path on the ET–2 submap.
MAIN ROUTE SPARE ROUTE

SERVICE ROUTES
Figure 121. Locate views on ring 2 submap.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 124 / 334
334
SWITCH STATUS ICONS 1 2 3 4 5 6
Figure 122. Routing view for 2–N D & C path.
If you click on the icon of the Switch status, the system opens a subwindow which displays the switch
status. Figure 123. shows the subwindows relevant to the routing display view of Figure 122.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 125 / 334
334
Z
Z ZA ZA
A AZ AZ
A
MAIN ROUTE CONNECTION VIEW SPARE ROUTE CONNECTION VIEW
( ref. 1,3,6 of Figure 122. ) ( ref. 2,4.5 of Figure 122. )
Figure 123. Status switch subwindows for 2–N D & C.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 126 / 334
334
Z ZA
A AZ
DASHED LINE=SPARE SWITCH POSITION
LINE=MAIN SWITCH POSITION
= “ the actual switch position is MAIN “
Figure 124. Main route connection view detail
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
1AA 00014 0004 (9007) A4 – ALICE 04.10
turned on spare ). See above Figure 124.
957.130.872 H 3AL 61259 AA AA 127 / 334
334
BOARD
CTP NAME DETAIL NODE NAME
SUBRACK PORT
RACK Channel (N.A.)
PAYLOAD POSITION
Figure 125. 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 123. the connections are:
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 “redo–log”
functionality.
pointing to the topology where the interconnection NE’s are included (e.g. the ET2 of the figure) or to the
whole path.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 128 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 126. Path: Add Protection menu.
Figure 127. Path: Remove Protection menu.
334
3AL 61259 AA AA
129 / 334
3.7.3 Path Constraints in a 2–Node SNCP network
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 128.
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 128.
FORWARD
BACKWARD
THIS PHYSCON IS USED THIS PHYSCON IS USED

AS CONSTRAINT: AS CONSTRAINT:
USE SERVICE FORWARD USE SERVICE BACKWARD
Figure 128. Use Service Forward/Backward for Dual Node SNCP network
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 130 / 334
334
3.7.4 D & C path in a 1–Node Enhanced SNCP network
This connection is usefull to increase the protection level when a single NE is interconnecting multiple
rings.
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 129. herebelow.
A Z
A A Z Z
1664SX cross connect equipment
Figure 129. Double failure for a SNCP path (w/o enhanced)
3.7.5 D & C path create in a 2–Node SNCP network
The Path Create procedure is the same as described at paragraph 3.2 on page 88, with the following
exceptions:
– Rate=140 Mb,
– Protection type=D & C SNCP. ( see Figure 120. )
3.7.6 D & C path allocate in a 2–Node SNCP network
Upon path allocation, the system evaluates, as in case of basic D & C

– main route
– spare route
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 122.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 131 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 130. Path routing view ( one node D & C )
334
3AL 61259 AA AA
132 / 334
Z Z
A
A
DASHED LINE=SPARE SWITCH POSITION
LINE=MAIN SWITCH POSITION
= “ the actual switch position is MAIN “
Figure 131. Enhanced SNCP–one node connection detail.
N.B. Figure 131. 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
1AA 00014 0004 (9007) A4 – ALICE 04.10
turned on spare ). See above Figure 131.
The implementation of the enhanced SNCP causes the creation of 4 unidirectional SNCP in the NE: .
957.130.872 H 3AL 61259 AA AA 133 / 334
334


N.B. As in the case of the normal D&C, it is not possible from the User Interface to select the tp’s
involved in the D&C but they are automatically selected by the routing algorithm. The tp’s can
be selected from the command mode because this is needed to support the “redo–log”
functionality.
pointing to the topology where the interconnection NE’s 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 .
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:
• 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
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 134 / 334
334
3.8 Add / Remove Protection
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 non–overlapped 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.
Paragraph 3.8.1 at page 138 describes the Add Protection command.
Paragraph 3.8.1.1 at page 140 describes the Remove Protection command.
Paragraph 3.8.1.2 at page 142 describes the Add Protection in a nested topology.
The procedure which follows deals about the display of an unprotected path ( see also paragraph 3.3.4.2).
locate routing view
PATH
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 132. Path list.
957.130.872 H 3AL 61259 AA AA 135 / 334
334
a) From the path list select an unprotected path.
1) If you click on routing view button, the routing display is presented. See Figure 133.

2) If you click on locate button, you can display the route in the netview map. See detailed

procedure at paragraph 3.3.4.4 at page 100 . See example in Figure 134.
Naps view
Figure 133. Routing display of an unprotected path.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 136 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 134. Netview locate (unprotected path)
334
3AL 61259 AA AA
137 / 334
3.8.1 Add Protection ( path )
a) Select the path from the path list and issue the command Actions: Add protection. The option items
are:

– Spare. The spare route is allocated and implemented.
– Spare (only allocation). The spare route is allocated.
– Service. This item is selectable only if the path protection type is D & C. The service route is allocated
and implemented.
– Service (only allocation). This item is selectable only if the path protection type is D & C. The service
route is allocated.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 135. Actions: Add Protection.
957.130.872 H 3AL 61259 AA AA 138 / 334
334
b) Select option item Spare. The spare route is allocated and implemented. See locate view in
Figure 136. and routing display in Figure 137.
main route
is used
Figure 136. Netview locate (protected path)
main route
is used
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 137. Routing display of a protected path.
957.130.872 H 3AL 61259 AA AA 139 / 334
334
3.8.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.
2) Remove protection without check. The following options are selectable:
• 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
Figure 138. Path: Remove protection.
957.130.872 H 3AL 61259 AA AA 140 / 334
334
b) Select (this is an example) Remove Protection (no check).
Figure 133. and Figure 134. show respectively the routing display and the locate display.
In some cases a manual refresh of the routing display is needed.

REFRESH button
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 141 / 334
334
3.8.1.2 Add protection in a nested topology
In this example a protected path can be furthermore protected in its nested topology. The locate display
of the path is shown in Figure 139. and the routing display is shown in Figure 140.

a) In the routing display window point with the mouse at the nested connection in topology and issue
the command Add protection: spare.
The routing display is updated, showing the additional spare route within the topology. See
Figure 141.
MAP OF RING R1
nested topology
Figure 139. Path locate display: nested topology ( ring )

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 142 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
connection in topology of the nested topology
334
3AL 61259 AA AA
Figure 140. Routing display: protected path: nested ring.
143 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
334
3AL 61259 AA AA
Figure 141. Routing display; path protected in its nested topology.
144 / 334
3.9 OS driven restoration for HO paths & trails
The OS driven restoration applies to HO paths and trails.

3.9.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 issue the command
Actions:Restoration:Create Restoration Rule. See Figure 142. The Create Restoration Rule is
displayed. See Figure 143. on page 146
Figure 142. Restoration:Create Restoration Rule.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 145 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 143. Create: Restoration Rule.
334
3AL 61259 AA AA
146 / 334
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.
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:
– not alarmed objects ( default )
– all objects. This option will successfully restore the transport upon repair of the related
resources.
4) Constraint Rule. Possible values are:
– do not use constraints ( default )
– 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.
c) Click on the functional button Create. The restoration rule is created. Its name coincides with the
transport name.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 147 / 334
334
3.9.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 144. ) and the restoration rule list opens. See Figure 145.

Figure 144. Browser: restoration domain.
Figure 145. Restoration Rule list.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 148 / 334
334
The displayed attributes are:
– user label. It coincides with the transport name.

– object type. The possible values are path or trail.
– restoration strategy. See paragraph 3.9.1.

– hold off time . See paragraph 3.9.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
b) You can display other attributes by selecting the transport and issuing the command
Actions:Details:Show/Set Attributes. The dialog box of Figure 146. is presented.
Figure 146. Restoration Rule attributes.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 149 / 334
334
For trail or path the attribute Restoration state can assume one of the following values:
– 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 150 / 334
334
3.10 Join/Split Path
Join/Split path are used to merge a pair of paths into one single path or to slit a path into a pair of paths.
3.10.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 RING1 must be merged to a path crossing RING2.
RING R1 2
SUBNETWORK S1
RING R2
SUBNETWORK S2
Figure 147. Rings to be merged.
b) By clicking twice on the icons of RING1 and RING2 it is possible to display the two ring submaps.
See Figure 148.
c) 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 149. 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 149. on page 152

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 151 / 334
334
RING R1
RING R2
Figure 148. Submaps of RING R1 and RING R2
d) Select path P1 and click on Highlight button. In the Locate Objects dialog box choose the desired
options (see detailed description at paragraph xxxx and click on Apply button. The path is displayed
in the map. See Figure 150. Execute the same operation for path P2. See Figure 150.
HIGHLIGHT
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 149. Path List containing paths P1 and P2
957.130.872 H 3AL 61259 AA AA 152 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
RING R1
957.130.872 H
PATH P1 DISPLAY
SC.5:OPERATION
RING R2
Figure 150. Locate display of paths P1 and P2.

PATH P2 DISPLAY
334
3AL 61259 AA AA
153 / 334
SEQUENCE
a) Create a virtual SDH port ( via menu command Construction: Create Virtual: Port ) in node NE–V1
and NE–V2.

1) Select the Virtual NE and issue Construction: Create Virtual : Port. See Figure 151. herebelow.
Figure 151. Construction: Create Virtual : Port.
2) In the Virtual Port create dialog box ( see below figure) enter the required values to create the
virtual port.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 152. Virtual Port create dialog box.
957.130.872 H 3AL 61259 AA AA 154 / 334
334
b) Select from the map virtual node NE–V1 and issue Construction: Upload EML(s) info...: Available NE
PORTs.
Select from the map virtual node NE–V2 and issue Construction: Upload EML(s) info...: Available NE
PORTs. The submaps of NE–V1 and NE–V2 are opened.

Figure 153. Construction: Upload EML(s) info...: Available NE PORTs
c) From the submaps of NE–V1 and NE–V2 select the virtual ports which have just been created and
issue Construction: Create Connection ( F12 button). See below figure.
Figure 154. Construction: Create: Connection.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 155 / 334
334
d) In the Create Connection dialog box enter the connection name and click on Create button. The
connection is created in all related submaps. See Figure 156. on page 156.

Figure 155. Create Connection dialog box.
RING R1 and RING R2 SUBMAPS
Figure 156. Connection between the virtual nodes.
N.B. If the paths to merge are protected, two virtual Physical connections must be created at above
steps a) to d). The redundant SDH virtual ports must be created accordingly.
e) Execute the implementation of the virtual physical connection. Select the virtual physical connection
from the map and issue Supervision: Implement Object
f) Execute the payload configuration of the virtual physical connection: select the object from the map
1AA 00014 0004 (9007) A4 – ALICE 04.10
and issue Tools: Modify Payload. The payload structure must be congruent with the configuration of
R1 and R2.
957.130.872 H 3AL 61259 AA AA 156 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 158. Path Create between virtual nodes.
334
3AL 61259 AA AA
Figure 157. Payload configuration of the virtual physical connection
157 / 334
Figure 159. Path Create between the two virtual nodes.
g) Create a “virtual” path PV between the virtual nodes. This path should have the same attributes as
the two paths P1 and P2 to join. The Path Create dialog box is shown in Figure 159.
h) Allocate and the implement path PV (e.g. selecting the path from the path list and issuing Actions:
Configuration: Allocate and then Actions: Configuration: Implement.
i) From the path list (see Figure 160. herebelow) join first paths P1+PV. Select the paths and issue
Actions: Manage paths: Join path.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 158 / 334
334
Figure 160. P1+PV Join path pull–down menu.
j) In the Join path dialog box enter the name of the joined path (e.g. P3 ) and click on the functional
button Join path. After a few seconds paths P1 and PV are deleted and the new path P3 is created
and implemented.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 161. Join path dialog box ( P1+PV=P3)
957.130.872 H 3AL 61259 AA AA 159 / 334
334
k) From the path list join paths P2+P3. Select the paths and issue Actions: Manage paths: Join path.

Figure 162. P2+P3 Join path pull–down menu.
l) In the Join path dialog box enter the name of the 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. See Figure 163.
Figure 163. Path list after join operation..
Figure 164. shows the locate display of path P on the maps.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 160 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 164. Locate path P1 on the map.
334
3AL 61259 AA AA
161 / 334
3.10.2 Split path
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: Manage path: Split path
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.
Figure 165. Actions: Manage path: Split path

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 162 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 167. Node selection.
Figure 166. Split path dialog box.
334
3AL 61259 AA AA
163 / 334
3.11 Join–Split Trail
Two HO–Trails entering in a given NE can be joined in order to reduce the LO usage of resources or an
HO–Trail crossing at HO a Node can be split in order to perform crossing at LO.

3.11.1 Split a HO–Trail
A given HO–Trail 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 HO–Trail 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;
Figure 168. Manage trail.

1AA 00014 0004 (9007) A4 – ALICE 04.10
b) the user selects the splitting node and the operation can be executed.
957.130.872 H 3AL 61259 AA AA 164 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 169. Common node selection.
334
3AL 61259 AA AA
165 / 334
– the old HO–Trail is deleted
– two new HO–Trails are created
– The LO–Paths ”crossing” the splitting Node are modified by adding LO pass–through connection.

The related protection indexes are updated.

splitting node.
The operation reduces the impacts on the existing traffic: the LO–Paths 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.
3.11.2 Join two HO–Trails
Two HO–Trails entering in a given NE can be joined in order to reduce the LO usage of resources.
SEQUENCE
a) From the trail list select the HO–Trails to join. See Figure 171.
b) Select the command Actions:Manage Trails: Join trail. The Join trail dialog box is presented,
containing the two selected trails, as per Figure 172.
c) Click on button Join trail to start the operation. A confirmation is required. See Figure 173.
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 LO–paths using the original HO–Trails are crossing with pass–through connections the
intermediate NE without LO time–slot interchange.

– the old HO–Trails are deleted
– the new HO–Trail is created
– the LO–Paths ”crossing” the original HO–Trails are modified by removing the pass–through
connections in the intermediate NE. The related protection indexes are updated.
intermediate node.
The operation reduces the impacts on the existing traffic: LO–Paths 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.
Figure 174. and Figure 175. show the joinig of the two trails.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 166 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 171. Actions: Manage Trails: Join trail.
Figure 172. Manage trail: Join trail dialog box.
334
3AL 61259 AA AA
167 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 174. Trail joining phase.
Figure 173. Confirmation dialog box.
334
3AL 61259 AA AA
168 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 175. Joined trail.
334
3AL 61259 AA AA
169 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
334
3AL 61259 AA AA
170 / 334
4 PROTECTION MANAGEMENT
4.1 SNCP path layer switch management

The SNCP switch management commands can be applied to SNCP paths (see Figure 176. ) or to Bridge
& Switch connections in topologies ( see Figure 176. on page 171 )
Figure 176. Path:Manage SNCP menu.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 171 / 334
334
Figure 177. Connection in topology:Manage SNCP menu.
SNCP switch management commands are available at all connectivity layers.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 172 / 334
334
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 pop–up menu. It is possible to obtain this menu by selecting the path icon
and selecting the Actions:Manage SNCP pull–down 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.
Figure 178. shows an example of display of a B & S connection in topology.
switch status
B & S connection in topology Revertive
1AA 00014 0004 (9007) A4 – ALICE 04.10
last operation executed on the switch
Figure 178. Example of display of a B & S connection in topology.
957.130.872 H 3AL 61259 AA AA 173 / 334
334
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
957.130.872 H 3AL 61259 AA AA 174 / 334
334
b) After the execution of a Manage SNCP command a report is forwardedto the operator.
See Figure 179. An example of Connection in topology attributes is shown in Figure 180.
Figure 179. Report.
Figure 180. Connection in topology attributes.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 175 / 334
334
N.B. For a SNCP path the attribute SNCP status can be:
– 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.
– forced SNCP. At least one switch is set to forced.
– manual SNCP. At least one switch is set to manual.
N.B. 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 176 / 334
334

SPARE
LO–LCs
LO–CTPs
LO–CTPs
MAIN
SPARE
LO–LCs
LO–CTPs LO–CTPs
MAIN

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 177 / 334
334
4.2 Multiplex Section Layer switch management
4.2.1 Automatic Protection Switch in 2–fiber MS–SPRING

4.2.1.1 Bridge and Switch
In case of fiber breaks, the APS for 2F MS–SPRING 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 co–exist (this is the typical case,
indeed): since they affect different class of connections, the final configuration is given by the sum of the
two.
W E W E
W E W E
protection
BEFORE working AFTER
Figure 182. Effect of a BRIDGE EAST

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 178 / 334
334
W E W E
W E W E
protection
Figure 183. Effect of a BRIDGE WEST
W E W E
W E W E
protection
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 184. Effect of a SWITCH EAST
957.130.872 H 3AL 61259 AA AA 179 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
W
957.130.872 H
BEFORE
SC.5:OPERATION
E
working
protection
W
Figure 185. Effect of a SWITCH WEST
334
3AL 61259 AA AA
AFTER
E
180 / 334
4.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 K1–K2 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.
7) 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
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 mis–connections, all of the tributaries that terminate a low–priority connection output
an AIS signal (this operation is called ’squelching’).
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).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 181 / 334
334
4.2.1.3 Example of ring switch in a 6–nodes 2f MS–SPRING
The following diagrams depict the sequence of operations that occur in a six–nodes 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 186. 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
e w w
w e
1 2 3
6 5 4
e w
w e w e
Tributary
Working Channels
Protection Channels
Figure 186. :Example of six nodes ring
a failure affects the connection from node ’2’ to node ’3’.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 182 / 334
334
Tributary
e w w
w e
1 2 3
6 5 4
e w
w e w e
Bridge
Working Channels Tributary
Switch
Protection Channels
Figure 187. Step 4: Final situation
A squence of bridge and switch operations occurs. The final configuration is shown in Figure 187.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 183 / 334
334
4.2.2 Squelching in case of isolated nodes
With some classes of multiple failures, some nodes in a 2f MS–SPRING 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.
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.
4.2.3 MS–SPRING Interworking
When a 2f MS–SPRING is interworked with another ring (either SNC/I or MS–SPRING), 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 path–AIS.
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 MS–SPRING 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.
This document does not address the case where the VC4 that crosses the boundary is terminated at its
primary service node.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 184 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
Node
Service
Primary
SC.5:OPERATION
2f MS–SPRING
SNCP or MS–SPRING
Figure 188. Drop and Continue at the service nodes.
334
3AL 61259 AA AA
Service
Node
Secondary
185 / 334
4.2.4 Provisioning of the APS Controller
The APS Controller blocks need a set of configuration information for properly execute their functions.

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 K1–K2 bytes,
’default APS bytes’; It is required that the ’default APS code’ on K1–K2 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 traversed nodes are identified by their ’node id’ and may not be more that 15 (the total
number of N.E. in a 2F MS–SPRING 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);
4.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
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)

1AA 00014 0004 (9007) A4 – ALICE 04.10
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.
957.130.872 H 3AL 61259 AA AA 186 / 334
334
4.2.4.2 Squelching tables: example
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 point–to–multipoint 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
A B C D E F G
VC12 #1
VC4 #1 VC12 #2
SSN PSN
VC12 #63
VC4 #2
VC4 #8
SSN PSN
Figure 189. Example of squelching table configuration
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 187 / 334
334
Table 1. VC4 squelching table for node A
Node A

West Input West Output East Input East Output
From To LVC From To LVC From To LVC From To LVC
VC4 #1 A G YES
VC4 #2
VC4 #8 A F NO
Table 2. LVC squelching table for node A (no entries)
Node A
From:
Table 3. VC4 squelching table for node B
Node B
VC4 #1 A G YES A G YES
VC4 #2
VC4 #8 A F NO A F NO
Table 4. LVC squelching table for node B (no entries)
Node B
From:
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 188 / 334
334
Table 5. VC4 squelching table for node C
Node C
VC4 #2
Table 6. LVC squelching table for node C (no entries)
Node C
From:
Table 7. VC4 squelching table for node D
Node D
VC4 #2
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 189 / 334
334
Table 8. VC4 squelching table for node E
Node E

VC4 #2 E G NO
Table 9. LVC squelching table for node E
Node E
From:
Table 10. VC4 squelching table for node F
Node F
VC4 #2 E G NO E G NO
VC4 #8 A F NO
Table 11. LVC squelching table for node F
Node F
From:
Vc12 #2 of VC4 #1 B, C
1AA 00014 0004 (9007) A4 – ALICE 04.10
Vc12 #63 of VC4 #1 E
957.130.872 H 3AL 61259 AA AA 190 / 334
334
Table 12. VC4 squelching table for node G
Node G
VC4 #1 A G YES
VC4 #2 E G NO
VC4 #8
Table 13. LVC squelching table for node G
Node G
From:
Vc12 #1 of VC4 #1 A
Vc12 #63 of VC4 #1 E

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 191 / 334
334
4.2.5 Provisioning of the Service Selectors
The Network Element can host a Service Selector per each inserted VC4. The provisioning information
must include:

a) The definition of the association between the inserted VC4 and the passed through VC4, completed
with the direction of the pass–through (i.e from East to West or from West to East).
b) The Selector’s Mode of operation (Revertive or Not Revertive).
c) In case of revertive operation, a Wait Time to Restore (WTR) must be specified (a common WTR
vakue can be chosen for all of the selectors contained in the network element).
The default status of the service selector is always on the tributary direction.
4.2.6 Commands for the APS Controller
The APS Controller may receive explicit commands from the operator; the allowed commands are
mutually exclusive and belong to the following list:
Table 14. Commands and their priority
Command Priority
Lockout of Protection, East 3
Lockout of Protection, West 3
Forced Switch, East 2
Forced Switch, West 2
Manual Switch, East 1
Manual Switch, West 1
When a command is issued, it remains active until it is explicitly cleared by the operator. When a command
is issued that has a priority higher or equal than the priority of the command that is active at that time, the
new command replaces the old one.
The commands may be overcome by the alarms detected at the N.E. or by bridge requests received on
the K1–K2 bytes: in these situations the command is not deleted, and becomes active again when the
overcoming conditions are removed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 192 / 334
334
4.2.7 Commands for the Service Selectors
It must be allowed the operator to modify the status of the Service Selectors via commands that include
the ’manual switch’ and the ’forced switch’. As usual, the ’manual switch’ has lower priority than the alarm
status, while the ’forced switch’ overcomes any alarm status.

The commands must be explicitly cleared by the operator.
4.2.8 Reports of the APS Controller
The APS Controller status must be reported to the Operator Interface, in order to provide a visible feedback
about the ring status.
The main ring status information is represented by the state of the SM block, defined as one of the three
allowed macro–states indicated in [1]: ’Idle’, ’Pass Through’ or ’Switching’. In the following this information
is referred as ’Node Status’.
The ’Switching’ state must be further qualified with the status of the BrSw block (referred as ’Switch Status’
in the following), that can be one of the following: ’idle’, ’bridge East’, ’bridge West’, ’bridge and switch East’
and ’bridge and switch West’.
Note that it is possible to have a ’Switching’ Node status and an ’Idle’ Switch Status at the same time, while
an ’Idle’ or ’Pass Through’ Node Status is always associated with an ’Idle’ Switch Status.
The representation of the Node and of the Switch Status at the operator interface may not be logically
associated with a specific unit of the system, since it reflects a status of the entire Network Element.
Both the Node and the Switch Status information can be provided by the unit that hosts the ’State Machine’.
Another indication is the ’K1–K2 error’.
is reported at each Aggregate interface, Note that the source of the’K1–K2 error’ indication is the State
Machine, if the functional decomposition described in this document is used.
A summary of the reports of the APS Controller is given in the following table:
Table 15. Reports of the APS Controller
Report Name Source Block Allowed values
Node Status SM Idle

Pass–Through
Switching
Switch Status SM or BrSw Idle

Bridge East
Bridge and Switch East
Bridge West
Bridge and Switch West
West K1K2 Error SM No Errors

Syntax Error
Wrong Source Node Id
Wrong Destination Node Id
Protocol Error
1AA 00014 0004 (9007) A4 – ALICE 04.10
East K1K2 Error SM same as above
957.130.872 H 3AL 61259 AA AA 193 / 334
334
4.3 Management of switches at RM interface
An MS–SPRING can be created on the map by means of the command Construction: Add Object: Ring:
MS–Spring... Checks are performed during validation and activation phase: only 1661SMC and 1664SM

are allowed.

Implementation, de–implementation and removing can only be performed on the complete ring and not
on single connections.
During the implementation, RM creates :
– the MS–Spring protection block

– protected MS–TPs
– protected MS–Trails
and sets the Node Identifier in the MS–SPRING.
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 Figure 192. )
– synchronize
– release
– force east, west
– lockout east, west
– change Wait To Restore time (5, 300, 600, 900 sec) ( see Figure 194. )
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.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 194 / 334
334
4.3.1 Display of the Protection blocks
a) From the browser point with the mouse at the MS–Spring and open the pop–up menu. Select item
Display all related items... ( see Figure 190. )
b) From the selection box select item All Protection blocks and click on No Filter button. The Protection
block drawing window is displayed. See Figure 191. on page 196)
Figure 190. MS–Spring: Display All related items...

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 195 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Protection blocks
957.130.872 H
SC.5:OPERATION
Figure 191. Protection blocks in a MS–Spring.
The figures which follow show the commands available to manage switches.
334
3AL 61259 AA AA
196 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Switch East
Figure 192. Protection block: Manage switch menu.
Switch West
334
Figure 193. Examples of actual position of the switches.
3AL 61259 AA AA
197 / 334
Figure 194. Protection block: Wait to Restore time.
4.3.1.1 Squelching Info
All the HO SbnConn’s belonging to HO–Paths and HO–Trails in MS–SPRING 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 HO–TTP and HO–CTP.
For broadcast paths, the squelching information related to legs is evaluated run time during the
implementation (when multiple legs and pass–through are merged into a single broadcast connection).
4.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.
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 SEN–IM level also when a failure on a single fiber will occur. This will
warn the operator on the reduced degree of protection.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 198 / 334
334
4.3.2 4–F NPE RING Switch Management
a) From the browser point with the mouse at the 4–F MS–Spring and open the pop–up menu. Select
item Display all related items...
b) From the selection box select item All Protection blocks in MS Spring 4–F and click on No Filter
button. The Protection block drawing window is displayed. See Figure 195.
Protection blocks
Figure 195. 4–F Protection blocks.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 199 / 334
334
c) From each protection block it is possible to issue the following pop–up commands:

Figure 196. Span Switch pop–up menu.
– MS Protection: Synchronize
– Span Switch: Forced West

– Span Switch: Forced East
– Span Switch: Manual West
– Span Switch: Manual East
– Span Switch: Lockout Work. West
– Span Switch: Lockout Work. East
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Span Switch: Lockout Prot. West

– Span Switch: Lockout Prot. East
– Span Switch: Release WTR West
– Span Switch: Release WTR East
957.130.872 H 3AL 61259 AA AA 200 / 334
334
– Span Switch: Release Forced West
– Span Switch: Release Forced East
– Span Switch: Release Manual West
– Span Switch: Release Manual East
– Span Switch: Release Lockout Work. West

– Span Switch: Release Lockout Work. East

– Span Switch: Release Lockout Prot. West
– Span Switch: Release Lockout Prot. East
– Ring Switch: Forced West

– Ring Switch: Forced East
– Ring Switch: Manual West
– Ring Switch: Manual East
– Ring Switch: Lockout Work. West
– Ring Switch: Lockout Work. East
– Ring Switch: Lockout Prot. West
– Ring Switch: Lockout Prot. East
– Ring Switch: Release WTR West
– Ring Switch: Release WTR East
– Ring Switch: Release Forced West
– Ring Switch: Release Forced East
– Ring Switch: Release Manual West
– Ring Switch: Release Manual East
– Ring Switch: Release Lockout Work. West
– Ring Switch: Release Lockout Work. East
– Ring Switch: Release Lockout Prot. West
– Ring Switch: Release Lockout Prot. East
– Wait to Restore Time: Set ring WTR

– Wait to Restore Time: Set east span WTR
– Wait to Restore Time: Set west span WTR
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 197. Wait to Restore Time set up dialog box.
957.130.872 H 3AL 61259 AA AA 201 / 334
334
The effect of the Span Switch and Ring Switch operations is described in Section NPE. See definitions
at paras 2.2 and 2.3.
The above mentioned commands are mainly used for maintenance purposes. See Section

MAINTENANCE, Chapter 4 Diagnostic of the NPE Ring.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 202 / 334
334
5 NETWORK MODIFICATIONS
5.1 Introduction
– Adding a Network Element
– Removing a Network Element
– Removing a PDH Tributary Board
– Network Modification with existing traffic
– Removing an SDH Tributary Board
– Adding a PDH Tributary Board
– Adding an SDH Tributary Board
– Configuration of a Transmux board
N.B. The execution of the Redo–Log 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..
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 203 / 334
334
5.1.1 Adding a Network Element in a SCNP network
5.1.1.1 Adding a Network Element (NE), case 1

The new Network Element must be inserted in the network as shown in Figure 198.

NE–2
NE–3
NE–1
NEW NETWORK ELEMENT
Figure 198. Adding a new Network Element, case 1
It is assumed that the new NE is already managed by EML.
a) The upload of the EML info from EML to RM–MIB is automatically performed.
b) In the relevant submap execute Construction: Upload EML(s) info:Available EML(s), then
Construction:UploadEML(s) info:Available NEs and Construction:Upload:NE Ports.
c) Using the Cut and Paste or the Move (drag with left click) operation the new NE is created in the
network maps and in the MIB data base.
d) In the relevant map select NE–3 and execute Construction:Upload:NE Ports.
e) By means of the command Add Connection, create the connection between the involved
NEs/topologies. (The ports not used must be removed).
f) Execute the Implementation of the new Physical Connection. (This causes also the NE
implementation, i.e. the reset of the NE )
The procedures which follow are:
– Upload NAP of the new NE
– Path Management
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 204 / 334
334
5.1.1.2 Adding a Network Element (NE), case 2
The new Network Element must be inserted in the network as shown in Figure 199.
NE–2
NE–3
NE–1
NEW NETWORK ELEMENT
Figure 199. Adding a new Network Element, case 2
a) The user must protect paths using the physical connection to be interrupted ( NE–1 Thru NE–3 ).You
can verify by means of the command Physical Connection: ( display ) Paths active in physical
connection which is the path actual route.
From the path list select all paths and protect them by means of Add Protection: Spare.
b) Move all paths from the physical connection to be interrupted (NE–1 thru NE–3)
1) For paths protected at above point a ), select them and use option Remove Protection: Keeping
Spare.
2) For paths previously protected, reroute manually on the main or spare route according to the
route type crossing the physical connection.
c) Deimplement the physical connection. The physical connection appears dotted.
d) Delete the physical connection.
e) The upload of the EML info from EML to MIB database is automatically performed.
f) In the relevant map (e.g. submap) execute a Construction: Upload EML(s) info:Available EML(s),
then Construction:UploadEML(s) info:Available NEs and Construction:Upload:NE Ports.
g) Using the Cut and Paste operation the new objects are added to the network maps.
h) Create the new connections.
i) Execute the Implementation of the new Physical Connection. (This causes also the NE
implementation, i.e. the reset of the NE )
The procedures which follow are:

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Upload NAP of the new NE

– Path Management
957.130.872 H 3AL 61259 AA AA 205 / 334
334
5.1.1.3 Adding a Network Element (NE) in a NPE Ring
5.1.1.3.1 Initial constraints

– Slow restoration is not supervised on HO–Trails or 140Mbit/s paths that are passing through the

physical connection where you will add the NE (this option enables the system to add protection
automatically and we do not want this behaviour during modification).
– The NE addition has no impact on the synchronisation sources and settings within the ring and on
attached rings or NE
– The correct software is installed and activated on ADMs
– The aggregate boards of the NE that will be inserted must be compatible with the ones of the NE in
the ring that will become neighbours of the added NE.
– The optical power budget will not exceed given limits if the new NE is inserted between the ADM
currently connected to each other.
– Optical attenuators for the aggregates must be available if it is necessary to fulfill the optical power
budget.
– No major alarms are active in the Network
– The NPE must not be operating in protecting mode when the process is starting. It means that all the
NEs are in idle state.
Reference Ring Topology
E 2 3
1 4
6 5
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 200. Reference ring topology
957.130.872 H 3AL 61259 AA AA 206 / 334
334
Let’s assume we want to insert a new ADM (NE n. 6) between NE_1 and NE_5.
In the following we will use NE_6 for identifying the ADM to be inserted in the NPE ring.
SEQUENCE
a) ECT : In the following we will use NE_6 for identifying the ADM to be inserted in the NPE ring.
Configure the NE to be added in the ring:
1) Define the equipment configuration
2) Define the ADM local configuration (NE address)
3) Define the ADM local configuration (NE address)
4) Pre–defining the NE Id and the ring map may introduce some additional constraints when the
NPE configuration is computed in RM
5) Define the contents of NPE tables (according to the configuration defined in the ring) (see point
m).
b) 1354RM : Dump of the paths crossing the NPE ring (ET). The dump will be used to restore the paths
keeping the path constraints (see point p).
c) 1354RM: Force the traffic away from the physical connection to be opened for introducing the new
NE. This is obtained by issuing a Forced Switch / Ring (FS–R) command onto the two ADMs (NE_1
and NE_5) that will be adjacent to the new one inserted in the ring.
d) Set download disabled on all the nodes crossed by the paths in the ET.
e) 1354RM: Remove all the paths in the ET (Deimplement / Deallocate / Delete path)
f) 1354RM: Remove the link between the NPE ring and external topologies (if any
g) 1354RM: Remove the NPE ring from 1354RM MIB (Deimplement / Delete ET).
h) Network: Disconnect the fibers between the NE_1 and NE_5.

Insert the new NE in the ring.
Reconnect NE_1 and NE_5 to NE–6
i) 1353SH
Create the new ADM in 1353SH MIB
j) 1353SH
Take in charge NE_6 in 1353SH environment (start supervision of the added NE)
k) 1354RM
Synchronize the EMLIM. This will align the network map with the new ring configuration.
l) 1354RM
Remove the connection between NE_1 and NE_5 from 1354RM map
Add NE_6 in the map.
Define the connections between NE_1, NE_6 and NE_5 in the map.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 207 / 334
334
m ) 1354RM
Recreate the 4f MS–SPRing Interoceanic (NPE) ET in 1354RM MIB (Activate / Implement ET)
When implementing a MS–SPRing topology, 1354RM automatically defines node ids and the related
ring map (node adjacency).

It has to be verified if a possible different definition of the ring map may affect the traffic when it is

downloaded to the NEs composing the NPE ring.
If so it will be necessary to define a procedure/tool assuring that the map ring stored in the ADMs is
compliant with the one generated by RM (see also point a)
n) 1354RM
Upload the NAPs from the network
o) 1354RM
Restore the connections between the NPE ring and external topologies (see point f).
p) 1354RM
Run the redo log file based on path dump prepared at point b).
The paths crossing the ET are re–created in RM MIB. The pass–through connections in NE_6 are
automatically created as a consequence of the path constraints
q) 1354RM
Perform a consistency audit of the NEs in the ET.
Inconsistencies may be found on cross connections in NE_6 (no cross–connection exist in the ADM)
No inconsistencies must be found on cross–connections in the ADMs already present in the ring.
r) 1354RM
Enable the download on the nodes on which it was disabled (see point d).
s) 1354RM
Perform a consistency download.
At the end of the download phase the 4f NPE ring will be under 1354RM control, the NPE will be
enabled and active.
t) 1354RM
Remove the FS–R command from NE_1 and NE_5 (se point c)
The traffic is now redirected on the main route.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 208 / 334
334
5.1.1.4 Remove an NE from NPE Ring
Initial constraints
– The synchronisation source of the ring must not depend on the ADM you want to remove. If it is the
case, you may modify the position of the synchronization source to have an adequate configuration
after the removal of the ADM.
– The ADM to remove must not be a Gateway Network Element (GNE) and it must not dispatch any
management data to other ADM (using a tributary board for example). If it is the case, take the
necessary measures.
– The aggregate boards of the ADMs connected to the ADM to remove must be compatible.
The correct software is installed and activated on ADMs
– The optical power budget of the two ADM that will be connected after the removal of the ADM must
be sufficient.
– An optical coupler for the fibers after the removal of the ADM must be available.
– The ALS is configured on the aggregate boards that will be connected.
– Slow restoration is not supervised on HO–Trails or 140Mbit/s paths that are crossing the ADM to
remove.
– No major alarms are active in the Network
– No paths/HO–trails terminate on the NE to remove.
– Be sure that the Ms–spring is not operating in protecting mode when the process is starting. It means
that all the NEs are in idle state.
Reference Ring Topology
Referring to Figure 200. on page 206, let’s assume we want to remove the NE identified with number 6
in the ring map representation
In the following we will use NE_6 for identifying the ADM to be removed from the NPE ring.
SEQUENCE
a) 1354RM
Dump of the paths crossing the NPE ring (ET).
The dump will be used to restore the paths keeping the path constraints (see point n of this procedure.
b) 1354RM
Force the traffic away from the physical connections to be opened for removing the NE.
This is obtained by issuing a Forced Switch / Ring (FS–R) command onto the two ADMs (NE_1 and
NE_5) that are adjacent to the ADM to be removed from the ring
c) 1354RM
Set download disabled on all the nodes crossed by the paths in the ET.
d) 1354RM
Remove all the paths crossing the ADM to be removed (Deimplement / Deallocate / Delete path)
1AA 00014 0004 (9007) A4 – ALICE 04.10
e) 1354RM
Remove the link between the NPE ring and external topologies (if any)
957.130.872 H 3AL 61259 AA AA 209 / 334
334
f) 1354RM
Remove the NPE ET from 1354RM MIB (Deimplement / Delete ET).
g) 1353SH

Stop supervision of NE_6

h) 1353SH
Delete the ADM from 1353SH MIB.
i) Network
Disconnect the fibers between the NE_1 and NE_6.
Disconnect the fibers between the NE_5 and NE_6.
Remove the NE from the ring.
Reconnect NE_1 and NE_5.
j) 1354RM
Remove the connection between NE_6 and the adjacent NEs from 1354RM map
Delete NE_6 in the map.
Define the connections between NE_1 and NE_5 in the map.
k) 1354RM
Recreate the 4f MS–SPRing Interoceanic (NPE) ET in 1354RM MIB (Activate / Implement ET)
When implementing a MS–SPRing topology, 1354RM automatically defines node ids and the related
ring map (node adjacency).
It has to be verified if a possible different definition of the ring map may affect the traffic when it is
downloaded to the NEs composing the NPE ring.
If so it will be necessary to define a procedure/tool assuring that the map ring stored in the ADMs is
compliant with the one generated by RM.
l) 1354RM
Restore the connections between the NPE ring and external topologies (see point e.
m ) 1354RM
Upload the NAPs from the network
n) 1354RM
Run the redo log file based on path dump prepared at point a). The paths crossing the ET are
re–created in RM MIB.
o) 1354RM
Perform a consistency audit of the NEs in the ET.
No inconsistencies must be found on cross–connections.
p) 1354RM
Enable the download on the nodes on which it was disabled (see point c.
q) 1354RM
Perform a consistency download. Activating 4f NPE does not affect the traffic on the paths defined
in the network
At the end of the download phase the 4f NPE ring will be under 1354RM control, the NPE will be
enabled and active.
r) 1354RM
1AA 00014 0004 (9007) A4 – ALICE 04.10
Remove the FS–R command from NE_1 and NE_5 (see point b).
957.130.872 H 3AL 61259 AA AA 210 / 334
334
5.1.2 Removing a Network Element (NE) from a SNCP ring
a) Select one physical connection terminating at the NE to delete

b) If the selected physical connection is implemented, it must be deimplemented executing the

command Supervision:Deimplement Object from the map pull–down menu. A confirmation dialog
box is presented. A message alerts that the system is deimplementing the physical connection. The
deimplemented physical connection is dotted in the map and is brown colored in the Browser.
c) The operator selects Construction:Delete in MIB. A message alerts that the system is deleting the
physical connection. The physical connection is deleted from the MIB database and appears dashed
in the map. Also the TPs supported by the SDH ports at the physical connection ends are removed
(payload).
d) The operator must execute above points a to c for all the physical connections connected to the NE.
e) Select the NE from the map and issue Construction: Delete in MIB.
5.1.3 Removing a PDH Tributary Board
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.
c) On the 1353SH station delete the relevant board. The board is no longer present in the views.
d) In the NE port list the ports deleted are no longer present.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 211 / 334
334
5.2 Network Modification with existing traffic
This procedure allows to modify the network with the existing traffic.

The procedure objective is to add an NE between two already existing NEs. For more complex operations

the procedure can be modified.
a) Select the physical connection to be modified and retrieve the crossing paths, by mainly focusing the
implemented paths.
b) (Optional) Unprotect the protected paths keeping the main or the spare one according to the usage
of the physical connection (main or spare on single path basis) and according to Customer’s
requirements.
c) (Optional) Refresh the list of crossing paths in order to verify the remaining ones.
d) Produce the ”.rmList” file describing the remaining (unprotected) paths. See paragraph 5.2.1
This file is the description of the paths or trails in a format allowing the ”play–back” at later time.
e) Put the EML(s) in the download disable mode acting from RM. Starting from this point the network
is not involved in any modifications at RM level.
f) Deimplement, deallocate the paths mentioned at above point c ).
g) Retrieve the HO–trails crossing the physical connection.
h) Repeat steps b ), c ), d ), f ) acting on HO–trails instead of paths.
i) Deimplement and delete the physical connection.
j) By means of CT, pre–configure the HO pass–through connections inside the NE to be inserted and
insert the NE in the network.
k) Define the NE in the EML (SH) and upload the new NE at RM level.
l) Modify the network at RM level (define and implement) adding the new NE.
m ) Play the HO–Trail file using the RM batch utility. The trails are recreated using exactly the old CTPs.
n) Play the path file back. See paragraph 5.2.2.
o) Add the protections to HO–Trails and path again.
p) Put EML in download enable mode. The old NEs are downloaded with tables completely equal to the
previous ones while the new NE is configured for the first time.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 212 / 334
334
5.2.1 rmList file create
SCOPE
This procedure can be used to create the description of the paths or trails in a format allowing the
”play–back” at later time.
SEQUENCE
a) From the path/trail list select the path/s or trail/s to record and issue View:Report: .rmList file only
selected.
Figure 201. View: Report full only selected.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 202. .rmList file naming.
957.130.872 H 3AL 61259 AA AA 213 / 334
334
b) In the textline of the dialog box of Figure 202. select the name ( full–name ) of the .rmfile to record
and click on OK. The new .rmfile can be see by means of the file manager, as in Figure 203.

Figure 203. .rmList file.
.rmList file
Figure 204. .rmList file: Create Command.
c) Move the mouse to the icon of this file and open the pop–up menu; select option
Create–RM–Command. A dialog box opens, asking for confirmation. Type Y and press Enter button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 214 / 334
334
d) The command file is created. See the create report in Figure 205. The command file is displayed in
the file manager window.
Figure 205. Create the Command file.
.rmCmd file
(command file)
Figure 206. .rmCmd file.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 215 / 334
334
5.2.2 rmLCmd file play
SCOPE

This procedure first describes how to change to Executable the characteristic of the previously created

command file. The sequence to launch the execution is also described,
SEQUENCE
a) From the path/trail list select the path/s or trail/s to record and issue View:Report: .rmList file only
selected.
b) In the file manager window point with the mouse at the command file to execute and open the pop–up
menu; select option Change Permissions...
c) A dialog box allows the operator to select ”Execute” for this file. Click on OK button.
Figure 207. Command file: Change Permissions

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 216 / 334
334
Figure 208. Change Permissions dialog box.
d) To launch the execution of the command file, in the file manager window ( see Figure 206. ) click twice
on the icon of the command file. A dialog box asks for confirmation. Type Y and click on OK.
Figure 209. Command file execution dialog box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 217 / 334
334
e) The command file is executed and the execution report is displayed in the dialog box ( see figure
herebelow.

Figure 210. Command file execution report.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 218 / 334
334
5.3 Add/Remove Tributary Board
5.3.1 Removing an SDH Tributary Board

a) Select the physical connection associated to the SDH port to be removed.
b) 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.
c) On the map delete the connection:
1) Deimplement the connection

2) Delete object in MIB
3) Delete object from all submaps.
d) On the 1353SH station delete the relevant board. The board is no longer present in the views.
e) On the map execute NE:Upload Ports: the port deleted is no longer present.
5.3.2 Adding a PDH Tributary Board
a) On the 1353SH station create the relevant board.
b) Execute an Upload NAPs for the relevant node. From this point on the ports are available to be used
in a path (NML assigned).
5.3.3 Adding an SDH Tributary Board
a) On the 1353SH 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 219 / 334
334
5.4 Configuration of a Transmux board
5.4.1 Payload Structure Configuration of a Transmux board
The payload configuration of a transmux board ( VC–4 Synchronous to Plesiochronous ) includes a

sequence of steps to execute on both 1354RM and 1353SH. Example which follows covers the
configuration of a 140 Mb Port to 2Mb terminations.
a) On 1354RM: Remove the VC–4 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 VC–4 NAP and issue Actions: Remove NAP.
3) the 140Mb port assignment status goes to OBSERVED.
4) Point to the Node and issue Actions: Display: Main Related Items: Ports. The Port List is
displayed. The 140Mb port assignment status is OBSERVED.
b) On 1353SH: Execute the payload structure configuration to VC–12.
c) On 1354RM: Execute the EML: Synchronize command. The 140 Mb Port (OBSERVED) is replaced
by the 2 Mb ports ( OBSERVED ).
d) 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
VC–12 TTPs ( NAPs).
5.4.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 VC–4
TTP–NAP.
a) On 1354RM: Remove the VC–12 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 VC–12 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 1353SH: Remove the payload structure configuration ( from VC–12 to VC–4 )
c) On 1354RM: Execute the EML: Synchronize command. The 2Mb Ports (OBSERVED) are replaced
by one 140 Mb port ( OBSERVED )
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 220 / 334
334
6 SPECIAL NETWORK VIEWS

– Creating a geographical map

– Layered Map
– Connectivity Inventory
6.1 Creating a geographical map
The network described using the partitioning concept (network, subnetwork, ring) can be represented also
in a geographical mode. In particular all the network elements are grouped into sites. In the SDH netview
the operator must create a new map. The sequence is the following:
a) Fom the Netview window select Map:Maps:New. In the map create dialog box digit the map name,
select layout=none, compound status=Propagate Most Critical and click on Map Management.
Figure 211. Map create dialog box.
b) The ”SDH Netview configuration” dialog box appears ( see Figure 212. ). The operator must set
TRUE for ”Synchroniz. by site” option and select Synchronize complete map (Map and Alarm
1AA 00014 0004 (9007) A4 – ALICE 04.10
Synchronization) for the synchronization type ( see Figure 212. )
c) Select Verify and then OK. Click on OK in the New Map dialog box. The new map is created. A dialog
box alerts that the new map has been created and asks the operator if he wants to open the new map.
957.130.872 H 3AL 61259 AA AA 221 / 334
334
d) Click on OK. The new map is opened as in Figure 213.

Figure 212. SDH Network layer configuration.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 213. Supervision: Synchronize Map.
957.130.872 H 3AL 61259 AA AA 222 / 334
334
e) Since the map is empty, a synchronization activity is required to populate the map. From the
pull–down menu bar select Supervision: Synchronize: Complete Map. The list of the available
networks is presented.
f) Select the network to which you want to synchronize the geographical map and click on Synchronize
button. The message area will contain the message ”Synchronizing... Wait’ and then
”Synchronization ended”. A report log window is also provided. At this point the network icon appears
in the new object holding area as in Figure 214.
Figure 214. Geogr. map construction.
g) You can add a graphical background to this submap, simply selecting the command Map:Submap:
Describe/Modify (see Figure 215. ). The submap description dialog box is opened ( left–hand side
of Figure 216. ).
h) Click on Browse... button. The list of the available graphical backgroungs is presented. ( right–hand
side of Figure 216. ).
N.B. To the default list the administrator can previously add any suitable ” .gif” file.
i) Select the file and click on OK. The selected background file is now written in the field ” Background
Graphics” of Figure 217. Click on OK of the submap description dialog box. The selected background
is added to the submap.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 223 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 216. Adding a graphical background.
Figure 215. Map: Submap: Describe/Modify.
334
3AL 61259 AA AA
224 / 334
Figure 217. Submap description.
j) By holding the middle button of the mouse, drag the network icon to the center of the window. See
Figure 218.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 218. Root geographical map with background.
957.130.872 H 3AL 61259 AA AA 225 / 334
334
k) Double click on the network icon. The network submap opens. See Figure 219.

Figure 219. Network submap.
This submap contains in its new objects holding area the icons of the locations belonging to the parent
network. These locations are those uploaded from EML layer during network construction.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 226 / 334
334
l) Drag these icons to the window working area. The connections are automatically displayed. See
Figure 220.
Figure 220. Network geographical map.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 227 / 334
334
m ) Double click on a location icon. The location submap opens, containing the related nodes in its new
object holding area. Drag the node icons to the window working area. The connections are
automatically displayed. See Figure 221.

Figure 221. Location submap
N.B. It is possible to open the corresponding logical map, thus displaying logical and geographical
maps at the same time.
N.B. The node submap is not yet available.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 228 / 334
334
6.2 Layered Map
The Supervision: Synchronize allows to select the following SDH layer submenus:
Physical
HO–AU4
LO–TU3
LO–TU12
To synchronize the Netview map to the HO–AU4/LO–TU3/ LO–TU12 layer, execute the following steps:
a) Select the pull–down menu item Supervision: Synchronize: HO–AU4/LO–TU3/ LO–TU12
The map is synchronized to the selected layer. You can navigate through the submaps.
b) A confirmation is required.
c) All the currently displayed connections are removed and the connections relevant to the selected
layer are displayed.
For the physical layer the displayed information concerns the connection user label.
For the HO–AU4, LO–TU3 and LO–TU12 layers is provided the information regarding the layer type, the
number of free link connections and the overall number of link connections.
It is advisable to perform a Save Map as....... operation for each layered map to be managed by
the Network Planner. In this way the different layered maps can be immediately displayed by the
Operator.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 229 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
ROOT MAP
RING ICON
SC.5:OPERATION
tion
icon
ICON
External connec-
NETWORK
Figure 222. View: SDH Layer: Physical Layer
334
3AL 61259 AA AA
NE icon
230 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
ROOT MAP
SUBNETWORK MAP
Figure 223. View: SDH Layer: HO–AU4
334
3AL 61259 AA AA
RING MAP
NETWORK MAP
231 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
ROOT MAP
SUBNETWORK MAP
SC.5:OPERATION
Figure 224. View: SDH Layer: HO–TU3
RING MAP
NETWORK MAP
334
3AL 61259 AA AA
232 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
ROOT MAP
SUBNETWORK MAP
SC.5:OPERATION
Figure 225. View: SDH Layer: LO–TU12
334
RING MAP
3AL 61259 AA AA
NETWORK MAP
233 / 334
6.3 Connectivity Inventory
6.3.1 General

This application can be launched from the Browser window by selecting the relevant tool button.
The application can also be invoked from the Netview map by means of the pull–down menu Supervision:
Network Connectivity. It is necessary to drag and drop the topology (NTW, SBN, ET) whose connectivity
information is to be analyzed only if started from Browser.
The Connectivity Inventory window which is displayed upon launching the application contains the
following pull–down menus:
– File contains the only option Exit, to close the application.
– Actions contains the following menus:
• Get topologies, which allows to further select between first level * and all levels**
• Get Connections, to display the connections on the window
• Forget Topologies, to delete the topologies actually displayed on the window
• Forget Connections, to delete the connections actually displayed on the window
• Refresh Connections, to synchronize (actualize) the actually displayed connections
• Show Attributes, to display the attributes of the selected connection object
The View pull–down menu only contains the option Displayed info and the Run pull–down menu allows
to start the browser on the selected object.
(*) It performs a get on topologies just one scope level below the dropped topology in the MIB tree, for
example the node contained in the dropped ET.
(**) It asks for which topology below the dropped one you want to perform the get, for example all nodes
contained in the dropped Network
Pop–up menus are also available on the displayed topologies and connections (generic and specific
actions).
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 234 / 334
334
6.3.2 Data Visualization
The purpose of this procedure is to get the topologies and connections useful to represent the connectivity.
Execute the following:

a) In the Connectivity Inventory window select the Actions:Get Topologies pull–down menu.
If you select the first level you will get the topologies just one level below the dropped ONE (E.g. SBN
for NTW, ET for SBN, NODE for ET); if you select all levels you can select among the following
topologies:
• subnetwork, ring, node, if you have dragged a network.
• ring, node if you dragged a subnetwork
• node if you have dragged a ring
Figure 226. Actions:Get Topologies:all levels

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 235 / 334
334
After the get topologies operation it is possible to enter a ”Get Connections” action. An example is shown
herebelow.

Figure 227. Connectivity Inventory : VC4 Trails
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 236 / 334
334
7 PERFORMANCE MONITORING
7.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 Customer’s needs.
After creating the measure, the user must associate (correlate) to it the transport/s to monitor and the
termination points (TPs). See Figure 229. on page 238.
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 228. shows the PM functional buttons in the browser window.
Retrieve Performance Monitoring Data

Merge Measures
Show Performance Monitoring Data
Create a new measure
Archive Performance Monitoring Data
Correlate path/trail to a measure

Delete Monitored Data
Display Performance Monitoring Archived Data

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 228. PM functional buttons in the browser window.
957.130.872 H 3AL 61259 AA AA 237 / 334
334
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.

In the following paragraphs it is given a description of the main procedures relevant to PM.
TRANSPORT CORRELATE MEASURE
PATH PATH
CORRELATE
CORRELATION OF THE TRANSPORT ( PATH / TRAIL ) TO THE MEASURE
TRANSPORT CORRELATE MEASURE
NAP CAP CTP
pmtp
CORRELATION OF THE TP TO THE MEASURE
Figure 229. PM main objects.

1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. PM transport view and PM TP view are described in Section GRAPHICAL INTERFACE.
957.130.872 H 3AL 61259 AA AA 238 / 334
334
7.2 Creating the Measure
a) From the Browser select the PM domain and open the pop–up menu. Select the command Create:
Measure. The object creation dialog box is presented.
Default TCA True
Figure 230. Measure Creation dialog box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 239 / 334
334
b) Enter the following attributes:
– measure name. The measure name can be modified, by means of the SHOW/Set Attributes
command, only if the measure status is PLANNED.

– 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 Ends On. 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.
– TP 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 type. 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.
– collect counter. 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.
– DEFAULT TCA. If TRUE, the default TCA will be associated to the measure, when associating the
TP to the measure.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
e) You can now navigate from the pmDomain, in order to find the new measure icon.( from the Browser
pmDomain select Display related items : Measures. The Measure List is presented).
957.130.872 H 3AL 61259 AA AA 240 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 232. Measure list
Figure 231. PM domain related items
334
3AL 61259 AA AA
241 / 334
7.3 Transport object Correlation to the Measure
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
Figure 233. Measure: Actions pull–down menu.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 242 / 334
334
c) 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.
Correlate path/trail to a measure
Figure 234. 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.
N.B. The correlation Measure–Transport can be also executed starting from the transport (path /trail)
by using the relevant pop–up menu.Figure 234. shows the Object Correlation dialog box. The
user will drag and drop the measure from the browser.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 243 / 334
334
7.4 Tp’s correlation to the Measure
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 pm–Granularity values.
– A virtual TP cannot be monitored.
– The measure state to correlate can be planned, activated or stopped.
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 pop–up 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 244 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
334
3AL 61259 AA AA
Figure 235. Performance Monitoring: Correlate to Measure
245 / 334
Figure 236. TPs correlated 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 ( see Figure 237. ), in order to select which measures you want to correlate the tp
to.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 237. Measure selection dialog box.
957.130.872 H 3AL 61259 AA AA 246 / 334
334
7.5 PMTP Attributes
If you issue a Show/Set attributes of a PMTP object, you will get the dialog box of Figure 238.
Figure 238. PMTP Show / Set Attributes

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 247 / 334
334
The PMTP main attributes are:
• 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 7.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 BID–UAS 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.
N.B. 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 248 / 334
334
7.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 239. and Figure 240. Notice that for a bidirectional path the involved CTPs ( if correlated ), become
PMTPs marked both as sink and source. Figure 241. shows an example of assignement of the attribute
SIDE for a unidirectional path.
NE–A NE–B
ctp ctp
MAIN
sink
B&S
B&S
ctp ctp source
ctp
SPARE
sink
Figure 239. Side of the pmctps in a b&s connection ( signal from NE–A to NE–B )
NE–A NE–B
ctp ctp
MAIN source
sink
B&S
ctp ctp
SPARE source ctp
Figure 240. Side of the pmctps in a b&s connection ( signal from NE–B to NE–A )
ctp ctp
nap nap
source source sink sink

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 241. Side of the ctp/nap for a unidirectional connection
957.130.872 H 3AL 61259 AA AA 249 / 334
334
7.6 Counter Report Profile Creation
INTRODUCTION

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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 250 / 334
334
SEQUENCE
a) 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...
Figure 242. Counter Report Create

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 251 / 334
334
b) Confirm the creation by selecting the button Create.
Now the counter report profile can be correlated to the measure. ( see paragraph 7.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 Report window
15m 15m / 1h / 1day
24h 1 day / 1 week / 1 month

/ 1 year
c) To verify the correlation, point at the measure and issue Display: Related items: counter Reports. See
Figure 243. and Figure 244.
Figure 243. Counter Report profile list.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 252 / 334
334
Figure 244. Counter report profiles.
An example of the document that will be generated by a counter report profile is shown in Figure 245.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 253 / 334
334
Figure 245. Example of generated counter report
N.B. The environmental variable PM_FORMAT can be set by the administrator to:
– PROPERTY ( format shown in Figure 245. )
– CSV ( new format with improved placement of rows, columns )

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 254 / 334
334
7.7 Threshold Report Profiles Creation
INTRODUCTION
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.
N.B. The environmental variable PM_FORMAT can be set by the administrator to:
– PROPERTY ( format shown in Figure 245. )
– CSV ( new format with improved placement of rows, columns )

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 255 / 334
334
Figure 246. 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 window
15m 15m / 1h / 1day
24h 1 day / 1 week / 1 month / 1 year
b) You can verify, by using the browser, that the Threshold Report Profile has been created. See
Figure 247.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 256 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
report
Threshold
957.130.872 H
SC.5:OPERATION
Now measure and Threshold report profiles can be correlated.
Figure 247. Threshold Report Profile list.
334
3AL 61259 AA AA
257 / 334
7.8 Report Profile Correlation
SCOPE

The scope is to correlate a measure to a certain report profile.

SEQUENCE
a) From Browser issue a Display Related items: Counter Reports or Threshold Reports on the PM
domain.
Figure 248. Measure correlation pop–up menu.
b) Select the measure from the Measure List, navigate it to the browser and select the command
Correlations: Correlate Reports. A dialog box is presented.
c) From Browser drag and drop the report profiles ( counter and threshold ) to the Correlation dialog
box drop area and click on button Create.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 258 / 334
334
Figure 249. Correlate report
d) To verify the correlation, in the browser, from the measure issue Display: Related Items: Counter
reports/ Threshold Reports.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 259 / 334
334
7.9 Measure Activation, Stop and Consistency
7.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.
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 260 / 334
334
7.9.2 Measure Stop
INTRODUCTION
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 Not–consistent
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 light–blue.
7.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
a) Select from the browser the measure and issue the Actions: Start/Consistency/Stop: Consistency
command.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 261 / 334
334
7.10 Threshold Crossing Alarm (TCA) Profile creation
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. The list contains the values suggested for ADMs ( 1641SM, 1651SM, 1661SM,
1664SM ).
15 m granularity
counter max min
– SES 810 not significant

– FESES 810 0
– ES 900 0
– FEES 900 0
– BBE ( VC4 ) 2159100 0
– FEBBE ( VC4 ) 2159100 0
– BBE ( VC3, VC12 ) 539100 0
– FEBBE ( VC3, VC12 ) 539100 0
24h granularity
counter max min
– SES ( 96x810 ) not significant

– FESES ( 96x810 ) not significant
– ES ( 96x900 ) not significant
– FEES ( 96x900 ) not significant
– BBE ( VC4 ) ( 96x2159100 ) not significant
– FEBBE ( VC4 ) ( 96x2159100 ) not significant
– BBE ( VC3, VC12 ) ( 96x539100 ) not significant
– FEBBE ( VC3, VC12 ) ( 96x539100 ) not significant
b) Select button Create to confirm.
N.B. At least one threshold value must be specified since default values are not present.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 262 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 250. TCA Profile creation.
334
3AL 61259 AA AA
263 / 334
7.11 Threshold Crossing Alarm (TCA) Profile Correlation to the PMTP
SEQUENCE

a) In the browser point with the mouse at the PMTP to correlate.

b) Point with the mouse at the PMTP to correlate and issue the pop–up 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.
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
1AA 00014 0004 (9007) A4 – ALICE 04.10
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 ) new cross connect equipment.
957.130.872 H 3AL 61259 AA AA 264 / 334
334
7.12 Merging of several Measures
INTRODUCTION
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. For more detailed information refer to Section DESCRIPTIONS
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 251.
Figure 251. Measure merging.
b) 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 265 / 334
334
7.13 Displaying PM data
INTRODUCTION

The collected PM data can be presented to the user by means of the ”Displaying PM data” option.

This graphical representation shows the collected data in two ways (switching on the ”Report Style”
button):
1) ”Graphical counters”: the values are displayed as histograms, with True on the ABSCISSA
2) ”Textual counters”: the values are presented as figures in a textual format.
SEQUENCE
a) Select the measure from the browser and select the functional button Show Performance Monitoring
Data. A dialog box is presented ( See Figure 252. )
b) You can select the Select button, thus obtaining the Request Control Transport selection dialog box.
Enter the suitable selections. See Figure 253.
c) Select the counters you want to display and click on the add counters arrow. Click on Apply. The PM
graphical counter report opens. Figure 254. to Figure 256. show examples of counter reports.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 266 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
add counters
Report Request Control Transport selection
Figure 252. RM db Report window
334
3AL 61259 AA AA
remove counters
267 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 254. Graphical Counters Report
334
Figure 253. Report Request Control Transport selection
3AL 61259 AA AA
268 / 334
Detailed counter selection Select TP
Figure 255. PM graphical counter report
If you select the button Select TP, you will get a TP selection dialog box. See Figure 257.
N.B. The upper right–hand side of the graphical report contains the legend of the displayed counters,
in particular:
• Loss of data=PM data have been lost by ADM.
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
Not available=PM data have been lost by the system
• Not measured=the user issued a command which affected the monitoring activity, such as path
deimplementation.
957.130.872 H 3AL 61259 AA AA 269 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 257. TP selection.
Figure 256. PM Counter Report
334
3AL 61259 AA AA
270 / 334
7.14 The pmNE
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 258. pmNE Show/Set attributes
957.130.872 H 3AL 61259 AA AA 271 / 334
334
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:
• Collect in progress ( receiving PM data from EML )
• Analyze in progress ( storing PM data in the RM–MIB )
• Consistency in progress ( a consistency activity is being executed )
– PM misalignment ( true/false ). This attribute is applicable to SEN–IM Network Elements, as specified

by the attribute IM type.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 272 / 334
334
7.15 Archive Performance Monitoring data
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 mag–tapes, 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
It is strongly recommended to execute Archive and Delete procedures of the PM

hystorical data upon reception of diagnostic messages alerting: “ Disk Full ...”
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 273 / 334
334
7.15.1 Archive Performance Monitoring data
SEQUENCE

a) In the browser window select the button Archive Performance Monitoring Data. The browser

functional button palette allows to select between 15m and 24h granularities ( See Figure 259. )
A confirmation is requested. If the user chooses to continue, the archive process starts and when
finished, presents an Archive Report ( See Figure 259. and Figure 262. )
Figure 259. Archive data functional buttons

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 260. Archive report
957.130.872 H 3AL 61259 AA AA 274 / 334
334
7.15.2 Retrieve Performance Monitoring data
INTRODUCTION
To Retrieve Monitoring data means to memorize on RM_MIB data stored on archived tape.
SEQUENCE
a) In the browser window select the button Retrieve Performance Monitoring Data.
A confirmation is requested. If the user chooses to continue, the retrieve process starts ( see
Figure 261. )
Figure 261. Retrieve confirmation box

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 275 / 334
334
7.15.3 Display Performance Monitoring data
INTRODUCTION

To display Performance Monitoring data means to display data that have been previously retrieved.

SEQUENCE
a) In the browser window select the button Display Performance Monitoring Data. A dialog box is
presented, containing the list of the measures you may display.
b) Select the measure and click on OK. A dialog box containing all the allowed selections is presented.
c) Enter the suitable selections and click on OK or Apply. The PM graphical window is opened.
PATH VC12 Path
Figure 262. Displayed archived data

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 276 / 334
334
7.15.4 Delete Monitored data
INTRODUCTION
To Delete Monitored data means to delete from RM–MIB all archived data. Only historical data are deleted.
SEQUENCE
a) In the browser window select the button Delete Monitored Data. A confirmation box is presented. If
the user selects OK, PM data are deleted.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 277 / 334
334
7.16 Archive Session
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.
7.16.1 Attribute Setting
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 278 / 334
334
7.17 Uncorrelate the transport from planned measures
INTRODUCTION
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: Uncorrelate
from Measure 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.
7.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.
SEQUENCE
a) From the browser point at the tp icon and issue the Performance Monitoring: Uncorrelate from Mea-
sure pop–up menu.
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 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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 279 / 334
334
7.19 Remove from RM menu
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 263. , 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
Figure 263. Object containment tree

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 280 / 334
334
7.20 Uncorrelate the counter/threshold report profile from the measure
INTRODUCTION
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.
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.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 281 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
334
3AL 61259 AA AA
282 / 334
8 OPERATOR ADMINISTRATION
8.1 Introduction
This function is used to perform operator management. It can be invoked in the following way:
a) Select icon SMF from the 1354RM menu palette. The SMF first level window opens.
Figure 264. SMF first level window.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 283 / 334
334
b) From the SMF first level window select (double click or selection + OK button) the Operator
Administration feature. The Operator Administrator menu is displayed. You can select the function
from the following:

Figure 265. Operator Administration feature.
1) List of Current login. This menu can be used to retrieve the currently connected operator.
2) List of Successful login. This menu can be used to obtain the list of the Successful login
operations.
3) List of Unsuccessful login. This menu can be used to obtain the list of the Unsuccessful login
operations.
4) List of Operators. This menu can be used to obtain the list of defined operators.
5) Add Operator. This menu can be used to add a new operator. See paragraph 8.1.1.
6) Remove Operator. This menu can be used to remove an operator.
7) Change password.
8) Change Initiator.
9) Initiator Management
10 ) Scheduled Rules Management
11 ) Maximum Operators logged
12 ) Forced Logout
13 ) Set Default Printer

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 284 / 334
334
8.1.1 Add Operator
a) From the Operator Administration menu select Add Operator. The Add User window is presented.
This window contains:
• Two radio buttons: Select WS and All WS.
– If you select the button Select WS, you can then select the WS/ WSs from a list displayed
on the right–hand side of the window.
– If you select the button All WS, the operator that is being created will be able to access
all specified WSs.
After selecting the Workstation/s click on the Apply button.
• Four text strings:
– username ( 3 thru 8 characters )

– real name ( Max. of 30 characters )
– password
– confirm password
The default password is ”system1”.
• A list of types from which you must select among:
– LookOnly
– Path Builder
– Constructor
– OS Administrator ( HP Term included )
– Administrator ( HP Term not included )
– cnm_pb . He is like a normal VPN ( virtual private network, but he can manage only NAPs
and PATHS.
– cnm_lo. He can only visualize resources belonging to his NAD, communication alarms and
performance data.
• A list of initiatotors is also available from which you can optionally select the initiator.
b) Select the type and press Add. The new operator is added.
Chapter 4 of Section System Management Features describe in detail the available initiators.
In addition, the user is able to create new initiators.
Figure 266. gives a block diagram og the objects involved in the operator definition.
N.B. A certain profile can be associated to more initiators, while obviously a initiator refers to only
one profile.
N.B. Figure which follows refers to the case of one initiator which manages one NAD;
Other cases are:
– a initiator managing a range of NADs

– a initiator managing its own NAD
1AA 00014 0004 (9007) A4 – ALICE 04.10
– a initiator managing its own NAD plus NAD 0 ( free resources )
957.130.872 H 3AL 61259 AA AA 285 / 334
334
default mapping

OPERATOR
WS1 WS3
PROFILE INITIATOR
FAD
(FUNCTIONS)
RULE1 RULE2
(No.)
NAD
NAD
( OBJECTS ) RESOURCE1 RESOURCE2
Figure 266. Operator definition objects.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 286 / 334
334
8.1.2 Remove Operator
a) From the main level function selection window select: Remove Operator. The relevant window is
presented. This window contains:
• Two radio buttons: WS and All WS.
– If button WS is selected, you can then select the WS/ WSs from a list displayed on the
right–hand side of the window.
– If button All WS is selected, the operator that is being removed will not be able to access
all specified WSs.
After selecting the Workstation/s click on Apply button.
b) Select the operator to remove and press the button Remove.
The detailed procedures relevant to the Operator Administration are described in the Handbook: System
Management Features, Chapter 4.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 287 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
334
3AL 61259 AA AA
288 / 334
9 RESTRICTED OPERATORS
CNM operators are defined in order to use a restricted interface. This interface is able to manage only
NAPs and PATHs belonging to the specified NAD ( Network Access Domain )
9.1 Configuration
SEQUENCE
a) Many Initiators ( two per each restricted network domain and with NAD>300) can be defined with
the same prefix:
• restr_pb
• restr_lo
E.g. you can define restr_pb1, restr_pb2,...and restr_lo1, restr_lo2,...
The description of the procedure of Add Initiator can be found at Section System Management
Features, Chapter 4. Operator Administration.
b) Assign NAPs to the relevant NAD.
NAD Change Command
1) Select the NAP(s) from the Nap list and issue the command NAD (Network Assignment
Domain): Change.
2) In the dialog box select the icon dictionary. The NAD selection box opens. Select the domain
1354NN and confirm by clicking on OK. Click again on OK of the dialog box.
c) Assignment of the path(s) to the relevant NAD
1) Select the path(s) from the Path list and issue the command Actions: NAD (Network
Assignment Domain): Change.
2) In the dialog box select the icon dictionary. The NAD selection box opens. Select the relevant
NAD and confirm by clicking on OK. Click again on OK of the dialog box.
d) Define a new operator with Initiator restr_pb1
e) Define a new operator with Initiator restr_lo1
The description of the procedure of Add Operator can be found at Section System Management
Features, Chapter 4. Operator Administration.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 289 / 334
334
9.2 Access of the operator with Initiator restr_pb1
This user cannot open a RM terminal and the vertical palette contains only the browser icon.

9.2.1 Browser main window
The Browser pull–down menu bar contains the following menus:
The File menu contains the only option Exit.
The Actions menu contains the following selectable items:
– Actions: Display: Main Related items... < F2 >

– Actions: Display: All Related items...
– Actions: Display: Align Item(s) < F6 >
– Actions: Display: Parent < Shift + F1 >
– Actions: Select: Items... < Alt + F1 >

– Actions: Select: All Items... < Alt + F2 >
– Actions: Select: Unselect all < Alt + F3 >
Actions: Close: Item < F3 >

– Actions: Close: Item by Class < Shift + F3 >
– Actions: Close: All Related items... < F4 >
– Actions: Details: show/set attributes < F5 >

– Actions: Details: Displayed info... < F9 >
The View menu contains the following selectable items:
– View: Displayed Info... < F8 >
– View: Report: Full... < Shift + F5 >

– View: Report: Full on selected... < Shift + F6 >
– View: Report: Short... < Shift + F7 >
– View: Report: Short on selected... < Shift + F8 >
The Options menu contains the following selectable items:
– Options: Filtered presentation

– Options: Not Filtered presentation
– Options: Immediate operations

– Options: Deferred operations
– Options: Default Graph refresh rate
– Options: Close window going to parent
– Enable AS link
The Specific menu contains items which depend on the selected object.
– Specific <objectclassname > actually selected

1AA 00014 0004 (9007) A4 – ALICE 04.10
The Windows menu contains the list of opened windows (views and multicolumn lists).
Iconified windows can be deiconified; deiconified windows can be iconified.
957.130.872 H 3AL 61259 AA AA 290 / 334
334
The Help menu contains the following selectable item.
Help: On Help....
– Help: On 1354RM....
– Help: On Browser....
– Help: On This Window....

– Help: About This Version....
– Help: On Index
All above mentioned menus are described in Section Graphical Interface, Chapter 12.
In addition, for each object class the pop–up menu contains object specific commands.
FUNCTIONAL BUTTONS
– File: the only option Exit is allowed.
– Paths tool. If you click on this button a submenu is opened. It includes the following buttons:
• go to parent menu
• go to home menu
• Create a new path
• Add leg to a path
• Show the queued job
– Alarms tool. If you click on this button a submenu is opened. It includes the following buttons:
• go to home menu
• show communication alarms
– PM. It shows the performance monitoring tools. If you click on this button a submenu is opened. It
includes the following buttons:
• go to home menu
• Create a new measure
• Correlate path/trail to a measure
• Merge measure
• Show Performance Monitoring Data
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 291 / 334
334
9.2.2 Browser navigated objects
From the Network domain the items to display are:

– Network

– Performance Monitoring domain
– Paths in Topology
From the Network the items to display are:
– NAPs
– Paths in Topology ( with Source/Sink)
From the Path list all actions are allowed on paths.
The available functional buttons are:
– Create a path
– Add Leg
– Alarm Tools: it contains the only function Show Communication Alarms
– Correlate path/trail to a measure
– Show the queued jobs
– Nap list: the only option remove Nap is not included
– Measure list. The functional buttons are:
• Create a new measure
• Correlate path/trail to a measure
• Merge measure
From the PM domain the items to display are:
– Measures
– Counter Reports
– Threshold Reports
From the PM domain the operator with Initiator cnm_pb1 can create:
– Measures
– Counter Reports
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 292 / 334
334
9.3 Access of the operator with Initiator restr_lo1
This user cannot open a RM terminal and the vertical palette contains only the browser icon.
9.3.1 Browser main window
The Browser pull–down menu bar contains the following menus:
The File menu contains the only option Exit.
The Actions menu contains the following selectable items:
– Actions: Display: Main Related items... < F2 >

– Actions: Display: All Related items...
– Actions: Display: Align Item(s) < F6 >
– Actions: Display: Parent < Shift + F1 >
– Actions: Select: Items... < Alt + F1 >

– Actions: Select: All Items... < Alt + F2 >
– Actions: Select: Unselect all < Alt + F3 >
Actions: Close: Item < F3 >

– Actions: Close: Item by Class < Shift + F3 >
– Actions: Close: All Related items... < F4 >
– Actions: Details: show/set attributes < F5 >

– Actions: Details: Displayed info... < F9 >
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 293 / 334
334
The View menu contains the following selectable items:
– View: Displayed Info... < F8 >

– View: Report: Full... < Shift + F5 >

– View: Report: Full on selected... < Shift + F6 >
– View: Report: Short... < Shift + F7 >
– View: Report: Short on selected... < Shift + F8 >
The Options menu contains the following selectable items:
– Options: Filtered presentation

– Options: Not Filtered presentation
– Options: Immediate operations

– Options: Deferred operations
– Options: Default Graph refresh rate
– Options: Close window going to parent
– Enable AS link
The Specific menu contains items which depend on the selected object.
– Specific <objectclassname > actually selected
The Windows menu contains the list of opened windows (views and multicolumn lists).
Iconified windows can be deiconified; deiconified windows can be iconified.
The Help menu contains the following selectable item.
Help: On Help....
– Help: On 1354RM....
– Help: On Browser....
– Help: On This Window....
– Help: About This Version....
– Help: On Index
All above mentioned menus are described in Section Graphical Interface, Chapter 12.
– File: the only option Exit is allowed.
– Alarms tool. If you click on this button a submenu is opened. It includes the following buttons:
• go to home menu
• show communication alarms
– PM. It shows the performance monitoring tools. If you click on this button a submenu is opened. It
includes the following buttons:
• go to home menu
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
Show Performance Monitoring Data
957.130.872 H 3AL 61259 AA AA 294 / 334
334
9.3.2 Browser navigated objects
From the Network domain the items to display are:

– Network
– Performance Monitoring domain

From the Network the items to display are:
– NAPs
– Paths in Topology ( with Source/Sink)
From the Path list all actions are allowed on paths.
The available functional buttons are:

– Alarm Tools: it contains the only function Show Communication Alarms
– Nap list: the only option remove Nap is not included
– Measure list. The functional buttons are:
From the PM domain the items to display are:
– Measures
– Counter Reports
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 295 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
334
3AL 61259 AA AA
296 / 334
10 EXPORT OF RESOURCES
Paragraphs which follow describe the following subjects:

– Global Export of resources at NN startup

– Manual export procedure to NN
– Export of resources on ISN interface for 1355VPN
10.1 Global Export of resources at NN startup
The global export procedure described in this paragraph refers to NN startup phase and covers the export
of all resources to be assigned to 1354NN.
As an alternative, during normal operation of the national network, to export a part of the resources to NN,
it is possible to execute a manual export procedure. .
The export mechanism is based on changing the resource network access domain.
In practice, the NAD (network access domain) of the necessary RM resource objects are changed so that
they belong to the Qnn Agent NAD. Then at Qnn Agent startup the Qnn Agent discovers its resources and
creates the appropriate Qnn objects. In order to be able to change NAD values for the relevant resources,
the operator must login as RM Administrator.
It is important to note that :
– This procedure should be executed by an experienced operator with a good understanding of RM

functionality
– requires some prior planning effort to decide in advance which free NAPS are for export
The export is performed in several stages:
– NAD global change for the Physical connections terminating to virtual nodes
– NN assignment of the NAPs
– NN assignment of the path(s)

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 297 / 334
334
10.1.1 NAD global change for the Physical connections terminating to virtual nodes
SEQUENCE

1) Select the Physical connection terminated to a virtual node and issue Browse: Object(s). See

Figure 267. The browser displays the physical connection. Select the physical connection icon
and issue the command NAD (Network Assignment Domain): Global Change. See Figure 268.
Figure 267. Browse the virtual connection.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 268. NAD global change.
957.130.872 H 3AL 61259 AA AA 298 / 334
334
2) In the dialog box of Figure 269. select the icon dictionary. The NAD selection box opens.Select
the domain 1354NN and confirm by clicking on OK. Click again on OK of the dialog box.
dictionary
Figure 269. Change NAD: 1354NN.
The above described procedure performs the following:
a) NN assignment of the ms–trail(s) and of the associated msctpcap(s).
b) NN assignment of the ho–lc(s) supported by the relevant mstrail(s)
c) NN assignment of the ho–trails(s) associated to the relevant holc(s)
d) NN assignment of all lo–lc(s) supported by the relevant ho–trail(s)

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 299 / 334
334
10.1.2 NN assignment of the NAPs
Paragraph 10.1.2.1 describes the usage of the command to export the NAP(s) to 1354NN.

In addition, paras 10.1.2.2 to 10.1.2.4 describe detailed examples of navigation through the browser in

order to assign to 1354NN the NAPs. The following cases are described:
– Export of idle NAPs at paragraph 10.1.2.2

– Export NAPs belonging to paths terminated within RM domain at paragraph 10.1.2.3
– Export NAPs belonging to paths terminated outside RM domain at paragraph 10.1.2.4
If the NAP(s) to be assigned to 1354NN is involved in a path, the relevant path must be
subsequently exported to 1354NN.
10.1.2.1 NAD Change Command
SEQUENCE
Domain): Change.
2) In the dialog box of Figure 270. ( left–hand side ) select the icon dictionary. The NAD selection
box opens. Select the domain 1354NN and confirm by clicking on OK. Click again on OK of the
dialog box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 270. NAD: Change for NAP(s).
957.130.872 H 3AL 61259 AA AA 300 / 334
334
10.1.2.2 Export of idle NAPs
The procedure which follows describes an example of export of the idle NAPs belonging to a certain node;
the correct usage of the browser filter to select the idle NAPs of a certain rate is described.
SEQUENCE
a) From the browser point the mouse to the network icon and issue the command Display: Main Related
Items...( See Figure 271. )
b) In the selection box select option All Nodes and click on No Filter button. The Node list is displayed.
See Figure 272.
Figure 271. Network:Display:Main Related Items...

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 301 / 334
334
c) From the Node list select the Node and isuue Display: Main Related items...

Figure 272. Node:Display Main Related items...
d) In the selection box of Figure 273. select option NAPs and click on Filter button. The Filter dialog box
is displayed. Figure 274. shows the usage of the filter to select the rate (in this example Set Equal
to VC12) and the Idle Indicator ( Set Equal to Idle ). Click on Apply button to end the selection. The
filtered NAP list is shown in Figure 275.
e) You can select the NAP/s to export ( multiple selection is allowed ) and issue the command Actions:
NAD Change. See Figure 275. on page 304
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 273. Selection of NAPs.
957.130.872 H 3AL 61259 AA AA 302 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 274. Filter options: rate and idle indicator.
334
3AL 61259 AA AA
303 / 334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
334
3AL 61259 AA AA
Figure 275. NAP List:NAD:Change of the selected Naps.
304 / 334
f) Change the NAD from Free Pool to 1354NN. See description at 10.1.2.1
The Event Report dialog box opens telling that the Change NAD action has been correctly started.
After a few seconds you can verify the successful change operation of the NAD attribute in the NAP
list ( see Figure 276. )
NAD attribute
Figure 276. NAD attribute display in the NAP list.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 305 / 334
334
10.1.2.3 Export NAPs belonging to paths terminated within RM domain
The procedure which follows describes an example of export of NAPs belonging to a certain path,
terminated within RM domain.

SEQUENCE
b) In the selection box select option Paths in topology. If you click on No Filter button, you will get the
complete Path list. If you select option Filter, thus choosing a filtered list, you will set filter parameters,
such as rate, path userlabel...
An example of Path list is shown in Figure 277.
NAPs View button
c) Select the path and click on button Naps View. The relevant Naps view is displayed. See Figure 278.
d) For each NAP do the following: select the NAP icon and issue Specific: NAD : Change pull down
menu.
e) Change the NAD from Free Pool to 1354NN. See description at 10.1.2.1
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 306 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 278. Naps View: NAD change of the NAPs.
334
3AL 61259 AA AA
307 / 334
10.1.2.4 Export of the nap belonging to a path terminated outside RM domain
The procedure which follows describes an example of export of the NAP belonging to a path terminated
outside the RM domain, i.e. a path terminated to a virtual node.

SEQUENCE
Items...( See Figure 271. on page 301)
b) In the selection box select option All Nodes. If you click on No Filter button, you will get the complete
Node list. If you select option Filter, thus choosing a filtered list, you will be able to set filter
parameters, such as userlabel, site..
An example of Node list is shown in Figure 279.
Figure 279. Node list: display main related items...of a virtual node.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 308 / 334
334
c) Select the Virtual Node and issue Actions: Display: Main Related Items.
d) In the selection box ( see Figure 280. ) select option Paths starting ( ending ) from (to) node. Click
on No Filter. The list of the paths terminated to the previously selected virtual node is presented. See
Figure 281.
e) Select the path and click on button Naps View. The relevant Naps view is displayed. See Figure 282.
f) For the REAL NAP do the following: select the NAP icon and issue Specific: NAD : Change pull down
menu item.
g) Change the NAD from Free Pool to 1354NN. See description at paragraph 10.1.2.1.
Figure 280. Selection of paths terminated to a node.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 309 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
NAPs VIEW button
957.130.872 H
VIRTUAL NAP
SC.5:OPERATION
Figure 282. Export of the real NAP.
Figure 281. List of paths terminated to a node.
334
3AL 61259 AA AA
REAL NAP
310 / 334
10.1.3 NN assignment of the path(s)
SEQUENCE
Assignment Domain): Change. See Figure 283.
Figure 283. Path NAD change.
Figure 284. NN assignment of the path(s).

1AA 00014 0004 (9007) A4 – ALICE 04.10
2) In the dialog box of Figure 284. ( left–hand side ) select the icon dictionary. The NAD selection
box opens. Select the domain 1354NN and confirm by clicking on OK. Click again on OK of the
dialog box.
957.130.872 H 3AL 61259 AA AA 311 / 334
334
10.2 Manual export procedure
As an alternative to the Global Export procedure, as far it concerned about exporting HO and LO link
connections, MS trail and HO trails, it is possible to execute a ” manual ” procedure, whose advantage is

time saving, being the Global Export procedure quite heavy.

The ”manual’ procedure requires a careful operator’s intervention.
The sequence of operations is listed herebelow:
a) export of HO and LO link connections. See details at para 10.2.1 at page 312
b) export of MS trails. See details at para 10.2.2 at page 322
c) export of HO trails. See details at para 10.2.3 at page 326
d) export of NAPs. See description at paragraph 10.1.2 at page 300
e) export of paths. See description at paragraph 10.1.3 at page 311
10.2.1 Export of HO and LO link connections
SEQUENCE
b) In the selection box of select option All Nodes and click on No Filter button. The Node list is displayed.
See Figure 272.
c) Select from the list the virtual node and issue Actions:Display:Main related items...( See
Figure 285. ).
d) From the selection box select option Ports in node. Click on Filter button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 312 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 285. Virtual Node:display:main related items.
334
3AL 61259 AA AA
313 / 334
Figure 286. Filter settings:SDH and Assigned.
e) In the Filter dialog box choose settings: Technology: Equal to SDH and Assignment status Equal to
Assigned . See Figure 286. Click on Apply button. The filtered Port list is displayed as in Figure 287.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 314 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 287. Filtered ( SDH and Assigned ) port list.
Figure 288. Port:Actions:Display;Main related items...
334
3AL 61259 AA AA
315 / 334
f) Select the ( virtual ) port and issue Actions: Display: Main related items...
g) From the selection box select option Physical Connection and click on No Filter. The Physical
Connection icon is displayed in the browser window. See Figure 289.

Figure 289. Browser:Network,Virtual node, SDH port, Physical Connection.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 316 / 334
334
h) Point with the mouse to the Physical Connection icon and issue the Display: All related items pop–up
menu item. See Figure 290.
Figure 290. Physical Connection;Display:All related items..

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 317 / 334
334
i) From the selection box of Figure 291. select option Link Connections in Physical Connections. Click
on No Filter button. The Link Connection list is displayed.

Figure 291. Selection box:Link Connections selected.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 318 / 334
334
j) From the pull–down menu bar select the command Actions: Select: Select All. All object instances
appear selected. See Figure 292.
Figure 292. Link Connection list:Actions:Select All.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 319 / 334
334
k) From the pull–down menu bar select the command Actions: NAD: Change. See Figure 293.

Figure 293. All Link Connections: Actions: NAD: Change.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 320 / 334
334
l) Change the NAD attribute to 1354NN.
In the dialog box of Figure 269. on page 299 select the icon dictionary. The NAD selection box
opens.Select the domain 1354NN and confirm by clicking on OK. Click again on OK of the dialog box.
m ) From the Link Connection list you can verify the successful NAD change operation.
( See Figure 294. )
NAD
Figure 294. Link Connection list: NAD=1354NN.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 321 / 334
334
10.2.2 Export of MS trails
SEQUENCE

a) Point with the mouse to the Physical Connection icon and issue the Display: All related items pop–up

menu item. See Figure 295.
Figure 295. Physical Connection: Display All Related items...

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 322 / 334
334
b) From the selection box select option MS trail. Click on No Filter button. The MS trail is displayed in
the browser window. See Figure 296. on page 323
Figure 296. Browser: navigated objects.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 323 / 334
334
c) Point with the mouse at the MS trail to export and issue the command NAD: Change.

Figure 297. MS trail: NAD: Change.
d) Change the NAD attribute to 1354NN.
In the dialog box of Figure 269. on page 299 select the icon dictionary. The NAD selection box
opens.Select the domain 1354NN and confirm by clicking on OK. Click again on OK of the dialog box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 324 / 334
334
e) To verify the successful change of the NAD execute a Show/Set Attributes (lens) of the trail. The
dialog box is displayed in Figure 298.
301=1354NN
Figure 298. MS trail: NAD change verify.
Note on NAD setting and check procedure
A resource is assigned to the Qnn Agent when NAD value is 1354NN in display (numeric value 301 in filter)
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 325 / 334
334
10.2.3 Export of HO trails
SEQUENCE

a) Point with the mouse to the Physical Connection icon and issue the Display: All related items pop–up

menu item. See Figure 295. on page 322.
b) From the selection box select option HO trail. Click on No Filter button. The HO trail list is displayed.
See Figure 299.
c) Select all trails and issue the command Actions: Nad: Change from the pull–down menu bar.
d) Change the NAD attribute to 1354NN.
In the dialog box of Figure 269. select the icon dictionary. The NAD selection box opens.Select the
domain 1354NN and confirm by clicking on OK. Click again on OK of the dialog box.
e) You can verify the successful change of the NAD simply by observing the NAD attribute in the HO
trail list. See Figure 300. on page 327.
Figure 299. HO trail: Actions: NAD: Change.

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 326 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
Figure 300. HO trail: NAD change verify.
334
3AL 61259 AA AA
327 / 334
10.3 Export of resources on ISN interface for 1355VPN
10.3.1 Introduction

The procedures which follow describe the export of resources to Virtual Private Network Management
system.
They are divided in:
• 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

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 328 / 334
334
10.3.1.1 Adding a VPN initiator
SEQUENCE
a) Select the Administration ( SMF) icon from the vertical palette.

b) Select the feature Operator Administration and confirm by pressing OK.

c) 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 for Standard VPN Operators ( not supported in this release )

• AC_R_EVPN for Enhanced VPN Operators
• AC_R_RVPN for Restricted VPN Operators
Click on the Add button to confirm the creation

1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 329 / 334
334
10.3.1.2 Add Operator
SCOPE

This function allows the Administrator to create a new operator at a time on WSs belonging to the network

configuration.
SEQUENCE
a) Select the SMF icon from the vertical palette.

b) Select the feature Operator Administration and confirm by pressing OK.
c) From the Operator Administration window select the option Add Operator and confirm by pressing
OK. The Add Operator dialog window is presented.
d) 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
– Initiator: the Initiator Name previously specified at paragraph 10.3.1.1 on page 329.
e) 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.
f) you can confirm the Operator creation by pressing button Add.
The Add Operator window contains the following:
– 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 pop–down menu for choosing among available profiles, with label ’Profiles’;
• 1 pop–down 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 330 / 334
334
10.3.1.3 VPN assignment of the end points
10.3.1.3.1 NAP Assignment

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
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
paragraph10.3.1.1 and confirm by clicking on OK. Click again on OK of the dialog box.
10.3.1.4 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.
paragraph 10.3.1.1 and confirm by clicking on OK. Click again on OK of the dialog box.
As a result of this operation, the boundary CTP is assigned to the above NAD.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 331 / 334
334
10.3.1.5 VPN assignment of the bandwidth
10.3.2 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 This assignment can be executed for all VPN types ( Standard / Enhanced /
Restricted )
This assignment is MANDATORY for Restricted VPN
SEQUENCE
Domain): Change.
paragraph 11.2 and confirm by clicking on OK. Click again on OK of the dialog box.
10.3.2.1 VPN assignment of the paths
10.3.2.1.1 VPN Assignment of paths terminated within an RM domain
SEQUENCE
paragraph 10.3.1.1 on page 329 and confirm by clicking on OK. Click again on OK of the dialog
box.
10.3.2.1.2 VPN Assignment of paths terminated outside an RM domain
SEQUENCE
paragraph 11.2 and confirm by clicking on OK. Click again on OK of the dialog box.
The NAP and the boundary CTP are not assigned automatically: the operator must execute the
procedures described at paragraphs 10.3.1.3.1 and 10.3.1.4 on page 331.
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 332 / 334
334
INDEX
C P
Connectivity, 234 Path, 87

Constraints, 104 Payload, 64

PM, 237
E
Q
ET, 24
Export, 297 Qnn Interface, 297
I R
Implementation, 60 Ring, 24, 32, 47, 52
L S
Leg, 107 Startup, 15

Subnetwork, 22
M
T
Map, 18
Measure, 239 Trail, 74
Multipath, 92
U
N
Upload, 81
NAP, 81
NE, 26
Operator, 283
1AA 00014 0004 (9007) A4 – ALICE 04.10
957.130.872 H 3AL 61259 AA AA 333 / 334
334
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
957.130.872 H
SC.5:OPERATION
END OF DOCUMENT
334
3AL 61259 AA AA
334 / 334

1354rm52b Manual Del Operador Vol 1

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1354rm52b Manual Del Operador Vol 1

Caricato da

Copyright:

Formati disponibili

QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

COD.MANUALE HDBK P/N: 957.130.872 H Ed.01 3AL 61259 AAAA Ed.01

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

SERVONO 8 SEPARATORI NUMERATI DA 1 A 8

3 INSERIRE SEPARATORE ’1’ - INSERT REGISTER ’1’

4 SC.1: HANDBOOK GUIDE 20 1/20 20/20

5 INSERIRE SEPARATORE ’2’ - INSERT REGISTER ’2’

6 SC.2: DESCRIPTIONS 146 1/146 146/146

7 INSERIRE SEPARATORE ’3’ - INSERT REGISTER ’3’

8 SC.3: NPE 188 1/188 188/188

9 INSERIRE SEPARATORE ’4’ - INSERT REGISTER ’4’

10 SC.4: GETTING STARTED 58 1/58 58/58

957.130.872 TQZZA 3AL 61259 AAAA TQZZA Y 1/ 6

not permitted without written authorization from Alcatel.

11 INSERIRE SEPARATORE ’5’ - INSERT REGISTER ’5’

12 SC.5: OPERATION 334 1/334 334/334

ASSEMBLARE VOL.2/2 – ASSEMBLE VOL.2/2

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 748

TOTALE FOGLI A4 TOTAL A4 SHEETS: 374

WARNING FOR A-UNITS OTHER THAN A-ITALY

• Labels are done according to A-Italy binder format.

957.130.872 TQZZA 3AL 61259 AAAA TQZZA Y 2/ 6

Originators 1354RM REL.5.2B

Domain : NETWORK MANAGEMENT

Name M.RAGNI E.CORRADINI F.CASASOLE

– ORIGINALE SU FILE: ALICE 6.10

Regional Network Manager for SDH and Optical Networks

957.130.872 TQZZA 3AL 61259 AAAA TQZZA Y 3/ 6

Regional Network Manager for SDH and Optical Networks

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01 OPERATOR’S HANDBOOK VOL.1/2

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01 OPERATOR’S HANDBOOK VOL.1/2

957.130.872 TQZZA 3AL 61259 AAAA TQZZA Y 5/ 6

957.130.872 H Ed.01 3AL 61259 AAAA Ed.01

1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3 1354RM REL.5.2B OPERATOR’S HANDBOOK DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

01 000721 validated M.RAGNI ITAVE V.PORRO ITAVE

957.130.872 H 3AL 61259 AA AA 1 / 20

1.1 General information

1.2 Handbook applicability

This handbook applies to the following product-releases:

PRODUCT ANV P/N Factory P/N

PRODUCT RELEASE VERSION (N.B.) ANV P/N Factory P/N

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

957.130.872 H 3AL 61259 AA AA 3 / 20

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

HANDBOOK EDITION 01PR 01 02 03 04 05

957.130.872 H 3AL 61259 AA AA 4 / 20

2.1 Handbooks related to the product’s software

Table 1. Handbooks related to the specific software application

Table 2. NR 5.0B Related Handbooks

Table 3. Documentation on CD–ROM

See para.5.5 on page 17.

REF ANV Part No. FACTORY Part No. NOTE

Envisaged after the release of all

Contains, in electronic format, the following handbooks: REF.[2] to [4]

957.130.872 H 3AL 61259 AA AA 5 / 20

Refer to WS supplier handbooks.